[mlir][scf] Read the written tile of a `scf.forall` through block arg (#241838)
When a producer of the init of an `scf.forall` is fused into the loop,
the fused op reads the init from outside the loop, while the iteration
writes the same tile through the `shared_outs` block argument. One-shot
bufferize cannot prove that these touch the same tile, so it allocates a
buffer and copies the whole tensor.
E.g., after tiling a `linalg.mmt4d` and fusing the `linalg.pack` of its
accumulator:
```mlir
%r = scf.forall (%i, %j) in (8, 8) shared_outs(%out = %C) -> (tensor<96x64xf32>) {
%c = tensor.extract_slice %C[%off0, %off1] [12, 8] [1, 1] // reads the outer value
...
scf.forall.in_parallel {
tensor.parallel_insert_slice %u into %out[%off0, %off1] [12, 8] [1, 1]
}
}
[15 lines not shown]
[flang][OpenMP] Emit portability warning on simd do with firstprivate & lastprivate (#242294)
Currently using `!omp parallel do simd lastprivate(a) firstprivate(a)`
does not copy the value of `a` into its body.
E.G.
```fortran
integer a
a=10
!$omp parallel do simd lastprivate(a) firstprivate(a)
do i=1,1
if (a/=10) print *, 'Fail'
end do
!$omp end parallel do simd
end
```
Prints fail.
The result of discussion on
https://github.com/llvm/llvm-project/pull/236741 and other PRs was that
this behaviour correctly implements the OpenMP spec, since `!$omp do
[9 lines not shown]
[DAG] SimplifyDemandedVectorElts - fdiv/frem of zero elements is NaN, not known zero (#241878)
`SimplifyDemandedVectorElts` treats an `fdiv`/`frem` element as known
zero when both operands are known zero, but `0.0 / 0.0` and `frem(0.0,
0.0)` are NaN. This dates back to 4cf1da0e021b, which added the FP
binops to the integer `ADD`/`SUB` case.
This patch stops reporting known zero elements for `FDIV` and `FREM`.
Fixes #241254
Assisted-by: Claude Opus 5.5
[CIR] Fold extractvalue when lowering complex real and imag
Lower cir.complex.real and cir.complex.imag with createOrFold, so the
llvm.extractvalue folds through the llvm.insertvalue chain that
cir.complex.create lowers to. Until now the fold depended on the CIR
folders seeing the original cir.complex.create, which only happens
while dialect conversion keeps replaced ops around for rollback. The
LLVM folder works on the converted values in either mode and also
catches extracts of complex results that never came from a
cir.complex.create, such as the cir.complex.fadd result in
complex-compound-assignment.cpp, which now matches classic codegen.
Assisted-by: Claude Code (claude-opus-5-5).
[X86] Add i16 partial reduction tests for targets without VNNI (NFC) (#240903)
Adds test coverage for i16 × i16 → i32 partial reductions on targets
without VNNI, ahead of lowering them to PMADDWD (#223374).
- `vector-partial-reduce-smla.ll`: sext-only and mismatched-extend
cases.
- New `vector-partial-reduce-smla-widen.ll`: `<4 x i16>` inputs with a
`<4 x i32>` accumulator, which need input widening. It has non-VNNI RUN
lines only, since this shape crashes on VNNI targets today (TODO in the
file).
- `LoopVectorize/X86/CostModel/partial-reduce-dot-product.ll`: s16 × s16
on SSE2, AVX1, AVX2 and AVX512BW, and a negative u16 × u16 case.
Code drafted by both human and AI, and reviewed by human.
[lldb][Darwin] Batch debugserver Mach-O load-command reads (#232684)
**Why:** During attach, debugserver reads each image's Mach-O
load-command headers and payloads separately. Targets with many dynamic
libraries repeat this work across every image.
**Change:** Read commands through a bounded 16 KB window. Keep
breakpoint-byte restoration and command validation; fall back to an
exact read when optional data is unreadable. This PR changes the
server-side traversal.
**Validation:** Standalone arm64 debugserver builds; four API cases pass
with matching current-main LLDB and with Apple LLDB. They cover parsing,
window boundaries, breakpoints, unreadable data and malformed commands.
A 32-bit inferior has not been tested.
<details>
<summary>Prior reviews</summary>
[14 lines not shown]
powerpc: save and restore VRSAVE with the vector state
VRSAVE was never saved or restored, although user code can write it
and the mcontext carries it, so every process saw the value the
previous process on that CPU had left there.
Two processes pinned to the same CPU and writing different values to
VRSAVE each read back the other's; each reads back its own now.
Reviewed by: jhibbits
MFC after: 1 week
Differential Revision: https://reviews.freebsd.org/D61544
powerpc: move get_pcpu() to machine/pcpu.h
Every other arch defines get_pcpu() in machine/pcpu.h, powerpc has it in
machine/cpufunc.h, which is entirely under _KERNEL. lsof includes
sys/systm.h without _KERNEL first on purpose, so on powerpc cpufunc.h
turns into an empty header and pcpup later expands to a call of an
undeclared get_pcpu(). Since sys/mount.h started pulling in sys/proc.h
this breaks the lsof build on powerpc64 and powerpc64le.
Reviewed by: jhibbits
MFC after: 1 week
Differential Revision: https://reviews.freebsd.org/D61305
py-stevedore: updated to 5.10.0
5.10.0
* reno: Update master for unmaintained/2025.1
* Write the entry point cache atomically
* doc: Remove tested python versions
* Simplify coverage command options
* Do not generate bytecode in tests
* Reuse test commands in cover target
* Add cover target
* Ensure recursive detection of package files
* Replace repository link
* Update master for stable/2026.2
* docs: Add example for dispatch managers
[CodeGen] Fix assertion when discovering partial live-outs (#224323)
Preserve live-through lanes when discovering partial live-outs and avoid
counting the same register twice. Add a target-independent regression
test.
Assisted-by: OpenAI Codex
[compiler-rt][clang][CMake] Match "lld" only in the linker file name (#242747)
Skipping HOST_LINK_VERSION detection when CMAKE_LINKER matches .*lld.*
is too broad. Since that matched the entire path, "lld" in unrelated
parts of the directory structure would erroneously match.
This happened on a real environment when "lld" appeared in the Nix store
path hash for a recent build.
I originally noted this issue in clang itself, but subsequent review
found the same issue in compiler-rt which has also been corrected.
Note: I used an LLM to help diagnose the issue and draft the patch. I
wrote the commit message and PR body, but not the title. I read the
patch and tested it
IPsec: Pre-Shared Keys - check uniqueness when only the remote identifier changes (#11224)
The reference to ident.check001 sat straight under <Constraints>, where
getConstraintValidators() skips it, so the identifier pair was only
checked when the local identifier changed.
Co-authored-by: Claude Opus 5.5 <noreply at anthropic.com>
py-pywavelets: updated to 1.10.0
1.10.0
Padding error when padding width is 0 for antisymmetric and smooth
cwt always fails with the message AttributeError: 'pywt._extensions._pywt.Wavelet' object has no attribute 'complex_cwt'
Scaling mismatch between PyWavelets CWT and my implementation
swt documentation mistake
DWT of read-only numpy arrays fails
WaveletPacketND.reconstruct() raises IndexError for non-power-of-two...
bgpipe: Update to version 0.26.0
What's Changed
ExaBGP compatibility (healthcheck, Flowspec, tests against real ExaBGP, docs); limit memory, nexthop-self, EPIPE, byte counters by @pforemski in #61
cc120: Use FLAGS.gcc.o to clean up drivers' Makefiles
The macros defined in CFLAGS are only required by gcc.cc, so define them
in CFLAGS.gcc.o and move to drivers/Makefile.inc, and thus clean up the
makefiles of each driver.
While there, remove the unused "Makefile.cco" include from c++/Makefile.
cc120: Fix -Wmissing-include-dirs warnings in cc_tools
cc_tools is built *before* support-libs, so some of include dirs for
support-libs can be missing, causing the following warnings:
```
cc1plus: warning: /usr/obj/usr/src/gnu/usr.bin/cc120/cc_tools/libcpp/../../support-libs/libdecnumber: No such file or directory [-Wmissing-include-dirs]
```
Fix the warnings by introducing GCC_NO_INCS to not include all the -I
directories.
cc120: Extract {PREPROCESSOR,DRIVER}_DEFINES from dragonfly-native.h
Refactor dragonfly-native.h to create {PREPROCESSOR,DRIVER}_DEFINES
make variables for use in libbackend and drivers. These two variables
are also defined in GCC's own makefile.
PREPROCESSOR_DEFINES is only used by cppdefault.cc, and DRIVER_DEFINES
is used by gcc.cc and gcc-ar.cc (so applies to gcc-ar, gcc-nm and
gcc-ranlib LTO wrappers).
The intention is to make some defines in DRIVER_DEFINES available to
gcc-ar.cc, which doesn't include "tm.h" to obtain "dragonfly-native.h".
So this is a required change for the upcoming gcc-{ar,nm,ranlib} LTO
wrappers.
cc120: Clean up dragonfly-native.h
* Add file-level description.
* Remove unnecessary MD_EXEC_PREFIX and MD_EXEC_PREFIX*, which are
defaulted to be empty strings by gcc.cc.
* Add comment for STARTFILE_PREFIX_SPEC.
* Set a dummy value for STANDARD_STARTFILE_PREFIX and remove
STANDARD_STARTFILE_PREFIX_{1,2}, which are unused when
STARTFILE_PREFIX_SPEC is defined.