www/dooble: Update to 2026.08.21
Link with gpgme for use with the application lock function.
Replace /usr/local with ${LOCALBASE}.
Install dictionaries into ${DATADIR} to avoid pageedit conflict.
Remove the unnecessary desktop-file-edit.
Changelog:
https://github.com/textbrowser/dooble/releases#release-2026.08.21
PR: 297900
Approved by: Eric Camachat <eric at camachat.org> (maintainer)
Approved by: osa (mentor)
Co-authored-by: mce
[lldb/test] Suppress crash reports from LLDB's gtest death tests (#218981)
PolicyStackDeathTest.GuardDestroyedOnDifferentThread and
ProcessRunLockDeathTest.MoveLockedAcrossThreads deliberately trip
thread-affinity checks that call report_fatal_error, so the forked
death-test child dies via SIGABRT. On platforms with a system crash
reporter that leaves a crash log behind for each run, which CI scrapes
and reports as a test failure even though both tests pass.
Call llvm::sys::Process::PreventCoreFiles() as the first statement
inside the EXPECT_DEATH block. EXPECT_DEATH forks by default, so this
only affects the child process and leaves the runner's own signal
handling alone. The assertions still hold: report_fatal_error writes to
stderr before aborting, so the regex still matches, and the nonzero exit
status satisfies ExitedUnsuccessfully.
Signed-off-by: Med Ismail Bennani <ismail at bennani.ma>
[LV] Remove dead EpilogueLoopVectorizationInfo::EpiloguePlan (NFC). (#220383)
The field has had no readers since 7f3428d3ed71 ("[VPlan] Compute
induction end values in VPlan.", #112145), which removed the last one.
Remove the dead field.
[SROA] Remove pointer bitcast lookthrough for selects (#220199)
`isSafeSelectToSpeculate` finds load users of the select through
bitcasts. But bitcasts from pointer to pointer don't happen anymore (or
are really uncommon?) after the introduction of opaque pointers. Remove
this functionality.
llvm-opt-benchmark shows no perf diff.
security/openconnect-gui: Remove deprecation notice and expiration date
As per new policies you need to track multiple branches.
I don't have time, hardware or interest trying to additionally keep up
with quarterly so I'll revert deprecation and expiration date
Reported by: joneum
www/dtse: Remove deprecation notice and expiration date
As per new policies you need to track multiple branches.
I don't have time, hardware or interest trying to additionally keep up
with quarterly so I'll revert deprecation and expiration date
Reported by: joneum
devel/etcd: Remove deprecation notice and expiration date
As per new policies you need to track multiple branches.
I don't have time, hardware or interest trying to additionally keep up
with quarterly so I'll revert deprecation and expiration date
Reported by: joneum
[flang][cuda] Look through declare/xdeclare when placing embox descriptors (#220361)
isDeviceAllocation() stopped at fir.declare / fircg.ext_declare, so an
embox of managed data could land on the stack. That happens with -g,
where declare is rewritten to fircg.ext_declare and kept until codegen.
Walk through those ops so the descriptor for managed data is still
allocated in managed memory. Also dyn_cast the adaptor block argument
instead of assuming it is always a BlockArgument.
Add a cuda-code-gen.mlir case for embox of a CUFMemAlloc result reached
through fircg.ext_declare.
rtwn: add support for the RTL8723BU
Pushed using the RTL8723BU.
Reviewed by: ziaee, avos, adrian
Relnotes: yes
Differential Revision: https://reviews.freebsd.org/D59205
[DirectX] Make DXILDebugInfo report that it Modified the IR (#220242)
fixes https://github.com/llvm/llvm-project/issues/220241
When Running Expensive Checks the following tests fail: Failed Tests
(7):
LLVM :: CodeGen/DirectX/DebugInfo/dbg-assign.ll
LLVM :: CodeGen/DirectX/DebugInfo/dbg-declare-undef.ll
LLVM :: CodeGen/DirectX/DebugInfo/dbg-value-arglist.ll
LLVM :: CodeGen/DirectX/DebugInfo/dbg-value.ll
LLVM :: CodeGen/DirectX/DebugInfo/debug-info.ll
LLVM :: CodeGen/DirectX/DebugInfo/di-label.ll
LLVM :: CodeGen/DirectX/debug-info.ll
DXILDebugInfo can modify the IR via convertFromNewDbgValues and other
places. We need to report these modification. It uses the DXILWriter as
its legacy pass, but the writer doesn't know that debuginfo can be
modified so update the Writer too so it can report modifications.
[3 lines not shown]
[VPlan] Insert into vector preheader after phi recipes (NFC). (#220384)
Several transforms insert or hoist recipes to the start of the vector
preheader. Insert after any phi recipes instead
This is NFC today, but prepares for modeling the full epilogue skeleton
in VPlan, which requires adding phi nodes in the preheader before
execute.
[LLDB] Support Re-export Symbol for FunctionCall (#208998)
A symbol can be a stub that is re-exported to another library. For
example, ELF can specify an auxiliary library and emit a zero-sized
symbol in the symbol table. This can cause expression evaluation to
resolve the stub instead of the actual function. Fix this by resolving
re-exported symbols to their actual addressed.
[LV] Add tests showing incorrect handling of large vscale ranges (NFC). (#219290)
Add tests with very large VScale max (2^30) showing incorrect handling
of wrapping when computing VF * vscale max in computeVF. We incorrectly
determine that no scalar epilogue is needed for the first test function
with a low trip count loop, and vectorize with a scalar epilogue instead
of tail-folding.
PR: https://github.com/llvm/llvm-project/pull/219290
Revert "[lldb] Drop the trailing separator from the qWasmGlobal instance suffix" (#220388)
Reverts llvm/llvm-project#220338. @jasonmolenda says that the key-value
semi-colon separated format says "end with a ;", which indeed matches
existing packets:
```
send packet: $qMemoryRegionInfo:16fdff310#a5
read packet: $start:16f604000;size:7fc000;permissions:rw;dirty-pages:16fdf0000,16fdf4000,16fdf8000,16fdfc000;type:stack;#00
```
truss: add -t to select which system calls are reported
truss reports every system call a process makes, which for anything
larger than a toy program buries the calls of interest. Add -t, taking
a comma-separated expression naming the system calls to report.
A term is the name of a system call, which may contain the fnmatch(3)
wildcards; a system call number in decimal; or "@group" naming a group
of related system calls. A term prefixed with '!' excludes what that
one term matches rather than including it, and applies to no other
term. An expression whose terms are all negated subtracts from the set
of every system call; any other expression selects from an empty one.
Terms apply in order and the last one to match a system call decides
whether it is reported. Repeating -t appends, so "-t a -t b" and
"-t a,b" are equivalent. An empty term is ignored, so an empty
expression filters nothing and a stray comma is not an error.
truss -t @file,@net fetch https://www.freebsd.org/
truss -t '!@memory' make buildworld
[60 lines not shown]
Improve metadirective loop checks
Tie lastprivate guards and updates to their induction-variable
computations. Require the fallback SIMD linear clause to contain only the
expected variable.
Capture loop-bound and step producers in the dynamic and static collapse
checks. Require the last-iteration comparisons to use those values so the
tests reject internally consistent but semantically incorrect guards.
[LAA] Remove over-eager assert after monotonicity check. (#220363)
The assert added in https://github.com/llvm/llvm-project/pull/210626 is
overly aggressive. SCEV may fail to prove the condition because
SplitIntoInitAndPostInc/getSCEVAtScope may drop flags needed to prove
the condition in the assert.
Add a test case where the start value is not 0, and remove assert.
Fixes https://github.com/llvm/llvm-project/issues/220286.
[MLIR][XeVM] Legalize large vectors when shuffle second operand is poison (#220360)
The SPIR-V backend now rejects OpTypeVector with a component count
outside {2, 3, 4, 8, 16} with a fatal error, instead of silently
emitting invalid SPIR-V that IGC happened to accept (36135544a13c). This
exposed a gap in the large-vector legalization performed by
convert-xevm-to-llvm.
HandleVectorExtractPattern exists to split vectors wider than 16
elements so that they never reach the backend, but its
isExtractingContiguousSlice guard required both shufflevector source
operands to be the same value. XeGPU lowering can produce a contiguous
slice extraction whose second operand is poison instead of a copy of the
first one:
%0 = llvm.mlir.poison : vector<32xf16>
%1 = llvm.load %p : !llvm.ptr -> vector<32xi16>
%2 = llvm.bitcast %1 : vector<32xi16> to vector<32xf16>
%3 = llvm.shufflevector %2, %0 [0, 1, 2, 3, 4, 5, 6, 7] : vector<32xf16>
[13 lines not shown]
