fd-find: update to 10.5.1.
Bugfixes
Fix --absolute-path turning verbatim (\\?\) search paths into relative paths on Windows: \\?\UNC\server\share is now reported as \\server\share, and \\?\Volume{...} paths are kept intact, see #2207 (@Duo-ee)
Make --ignore and --no-hidden after -u override only their half of -u, see #2192 (@NavpreetSSidhu)
Fix inline case-insensitive regex flags incorrectly making other --and patterns case-sensitive, see #2184 (@mabunemeh)
Accept --format templates that start with - when passed as a separate argument, see #2126 (@vulragrag-star)
Don't incorrectly escape newlines in error messages, see #2104
Restore jemalloc as default allocator on supported systems
Fix the cargo binstall release URL, which named the crate (fd-find) instead of the binary (fd) and fell back to a third-party mirror
Fix integer overflow when parsing size constraints, rejecting values that exceed u64::MAX instead of panicking, see #2196 (@parneetsingh022).
Various fixes and updates to zsh completion
Fix --glob patterns when using --full-path on windows. See #2067.
proc-cli: Update to version 2.3.0
Changes since 2.2.0:
- on, info, for and why show the same card for a process
- process tables show the user, uptime and command
- ports says if each port is reachable from the network
- values proc cannot read show as "-", not 0
- JSON adds parent name, child count, CPU time, open files
rsync: update to 3.5.2.
# NEWS for rsync 3.5.2 (4 Nov 2026)
## Changes in this version:
### BUG FIXES:
- Fixed interrupted `--append` and `--inplace` transfers writing the final
256 KiB buffer twice. An interrupted destination now remains a clean prefix
which the next transfer can resume or repair.
- Fixed uploads through `rrsync` when the destination file already exists.
Existing files are now reached beneath a pinned parent directory instead of
being passed as an unwritable `/proc/self/fd/N` destination.
- Fixed poor matching performance on large sparse and repeated-block files
when duplicate checksum chains exhausted the search limit. Valid basis
blocks are no longer hidden behind duplicate entries.
- Bounded strong-checksum work when a malicious receiver supplies weak
checksums that collide with consecutive rolling windows
(CVE-2026-119741).
[46 lines not shown]
[Offload] Don't report ELF symbols that run past its section (#238709)
It seems that the L0 ELF contains variables considered to be zero-filled
in sections not marked with `SHT_NOBITS`. Being zero-filled their size
goes beyon the limits of the memory image which produces failures when
checking the bounds in `olGetSymbol`.
This fix adds a workaround for variables in L0 images which would extend beyond their ELF section
as having no contents in the image.
Fixes regression introduced by #235935
Failure analysis done by Claude.
[ARM] Fix A32 single-register PUSH/POP preferred disassembly aliases
For A32, `POP`/`PUSH` of a single register encodes as an `LDR`/`STR`.
When the code for this was first committed in 2011 in change 8ba76c6d5,
the Arm ARM only mentioned that `POP` is listed as the "standard syntax".
Later, in 2014, the Arm ARM DDI0487A.e, §F7.1.137 was updated to
specifically say that `POP`/`PUSH` "is always the preferred disassembly."
I suspect the intention was to prefer pop/push, but:
* for PUSH: the decoder supplied positive 4294967292, so comparing it
with -4 failed. Changed this to a int32_t.
* for POP: the decoder supplied a packed addressing-mode value, so
comparing the entire value with 4 failed. We need to check
that the direction is add and the offset is 4
and then tests were then added in change ed6d3e813 for disassembly
with ldr/str.
[2 lines not shown]
bhyve: check paddr_guest2host return in _vq_record
_vq_record() stored the result of paddr_guest2host() without checking for
NULL. A guest descriptor with an invalid address causes a NULL dereference
in every virtio driver. Return early on failure; the caller sees zero
descriptors and discards the chain.
The indirect path already performs this check (line 357).
Reviewed by: bnovkov
Differential Revision: https://reviews.freebsd.org/D60870
MFC after: 1 week
Coalescer: Preserve read-undef when coalescing into a larger reg.
When rewriting a %1:gpr32 def into %0.sub_32:gpr64, the new def operand
can be marked with undef if no lanes from the larger gpr64 reg are live.
Assisted-by: codex (test reduction)
[mlir][Interfaces] Check types when replacing successor inputs (#238121)
In RegionBranchOpInterface, operations can override areTypesCompatible
to allow non-identical types along control-flow edges. For example, an
operation some_op may forward an operand of type wrapper<T> to a block
argument of type T, or yield a value of type T to an op result of type
wrapper<T>.
Previously, MakeRegionBranchOpSuccessorInputsDead and
RemoveDuplicateSuccessorInputUses replaced uses of successor inputs
directly via replaceAllUsesWith without checking that the replacement
value has the same type. When areTypesCompatible permits type
transitions along region boundaries, this produced ill-typed IR and
verification failures.
This patch fixes the issue by:
1. Guarding MakeRegionBranchOpSuccessorInputsDead to skip replacing a
successor input if replacement.getType() != value.getType().
2. Incorporating Type into the equivalence key (MapKey) in
[2 lines not shown]
[Clang] Fix crash on comparisons of `_BitInt` vectors wider than 128 bits (#232797)
Fixes #200665
`Sema::GetSignedVectorType` picks the element type for the result of a
vector comparison by matching the element's size against `char`,
`short`, `int`, `__int128`, `long` and `long long`, and asserts when
nothing matches. Since `_BitInt` became a legal vector element in Clang
16, any `_BitInt` wider than 128 bits falls off the end of that chain:
`a > 0` on a `_BitInt(512)` vector trips the assertion, and a release
build hands back a `long long` vector instead. The malformed input in
the report is incidental; a plain `v3i512 f(v3i512 a) { return a > 0; }`
crashes the same way.
The `_BitInt` case is now handled where the asserts used to fire: after
the builtin size checks, a `_BitInt` element with no builtin counterpart
produces the signed `_BitInt` of the same width, in the same vector kind
and with the same element count. Widths that match a builtin integer
keep mapping to it exactly as before, so nothing changes for `_BitInt`
[2 lines not shown]
[BPF] Expand atomicrmw sub into atomicrmw add of negated value (#236193)
https://github.com/llvm/llvm-project/pull/184715 changed `InstCombine`
to rewrite `atomicrmw add(p, sub(0, x))` into `atomicrmw sub(p, x)`. The
64-bit `atomic_load_sub` patterns were placed outside `BPFHasALU32`,
causing `-mcpu=v1/v2` to lower subtractions to `XFADDD`
(`atomic_fetch_add`) even when the return value is unused. This causes
Linux 5.10 kernels (still supported per
https://www.kernel.org/category/releases.html and used in Android) to
reject the BPF program. Since BPF has no atomic sub instruction, we
allow atomic sub to lower to atomic add of negated value by removing the
`atomic_load_sub` patterns from `BPFInstrInfo.td`.
As a result, this PR partially reverts
https://github.com/llvm/llvm-project/pull/107343 and
https://github.com/llvm/llvm-project/pull/210371.
Assisted-by: Gemini
[lldb] Let language plugins register their mangling schemes (#232925)
Currently Mangled recognizes the names of each mangling scheme by
hardcoded prefixes, so a language plugin can't bring a scheme that
LLDB doesn't already know.
This patch adds a registry of mangling schemes to Mangled. Language
plugins register the prefixes of their schemes when they are
initialized, and Mangled hands the names of those schemes to the
plugin that registered them. The registry also records each scheme's
language, which replaces Language::HandlesManglingScheme().
CPlusPlusLanguage now registers the Itanium and MSVC schemes.
Assisted-by: Claude
Depends on https://github.com/llvm/llvm-project/pull/232922
[AArch64] Eliminate shouldCoalesce restriction.
This does not enforce much, we are already very careful about ORRW,
which is only considered as a copy instruction when we can prove it's
not performing a required zero extension.
[AArch64] Add tests to document SUBREG_TO_REG and INSERT_SUBREG behaviour
This will help when/if slowly deprecating SUBREG_TO_REG and corresponding
optimisations. The point is to show that SUBREG_TO_REG does not provide
extra guarantees regarding upper bits compared to e.g. INSERT_SUBREG or
REG_SEQUENCE.
