[LLVM][Constants] Store "splat (float 0.0)" as ConstantFP rather than ConstantAggregateZero. (#195284)
The original split is awkward because, not unreasonably, some code paths
expect constant folding of ConstantFP operands to yield a ConstantFP
result.
Fixes https://github.com/llvm/llvm-project/issues/194590
[flang][NFC] Converted select-type.f90 test to HLFIR (#195777)
Lower/select-type.f90 took special care to convert from legacy lowering
to HLFIR lowering.
Assisted-by: AI
[flang-rt] Avoid libstdc++ guard symbols in RTNAME(Timef) (#195984)
The function-local `static Lock timef_lock;` introduced by PR #185377
required thread-safe-static initialization, which causes the compiler to
emit calls to `__cxa_guard_acquire`/`__cxa_guard_release` from
libsupc++/libc++abi -- a C++ runtime library dependency that flang-rt
explicitly avoids (see comment in
flang-rt/include/flang-rt/runtime/lock.h).
Move `timef_lock` to namespace scope, matching the existing
`rand_seed_lock` pattern in the same file. The other function-local
statics (`start`, `ticks_per_sec`, `isInit`) have constant initializers
and are unaffected.
Assisted-by: AI
memcached: updated to 1.6.41
1.6.41
Overview
Important bugfix release over regressions starting from 1.6.34 and 1.6.40. The glitches are not likely critical but we want to raise awareness of them.
In 1.6.34 we introduced new memory mover code. In very rare cases a bug can lead to the memory mover becoming unable to make progress and pages will no longer be moved for either a period of time or forever.
This also introduced a rare crash when slabs_mover=2 start option is in use. However it is highly recommended that nobody use this option as it will give poor hit rates for most workloads.
In 1.6.40 we introduced a rewritten protocol parser. The lru tuning command was made inaccessible and is now fixed in this release.
Finally, this repairs a bug in extstore where frequently accessed items can be lost during data compaction. This has existed since extstore was written and is not a recent regression. It is more likely to happen on highly loaded systems with low memory available to keep active items in RAM vs disk.
Several ASAN triggering but otherwise harmless bugs were also fixed.
Fixes
[15 lines not shown]
[Dexter] Add timestamps to DAP logging (#193705)
DAP logs are currently optionally output by Dexter to assist in
debugging or analyzing Dexter sessions. The output currently includes
the contents of every DAP message sent to/from the debug adapter, but
for some long-running programs it can also be useful to know when
messages have been sent and received; to assist, this patch adds
timestamps to DAP messages in the log.
[SPIRV] Fix failure on the `llvm.trap` test (#195996)
The `llvm.trap` test was failing with the expensive checks enabled,
because the backend incorrectly created the `OpConstant` and
`OpConstantNull` instructions for the operand of `OpAbortKHR` in the
same basic block. When there are multiple `llvm.trap` intrinsics, they
reuse the same operand, which doesn't dominate all the users. This
commit moves the constant into the function entry block to ensure it
dominates all the users.
Assisted-by: Claude Opus 4.6 <noreply at anthropic.com>
py-fsspec: updated to 2026.4.0
2026.4.0
Fixes
- proper install in ci to grab versions
- encode URLs in HTTP pipe_file
- implement delete and write_test for dirFS
- allow multiple local protocols
- context closing for tar and zip
- fix cat_file and cat_ranges for WholeFileCache
Other
- usage warning to HTTP FS
- update adl: message following retirement
Move two functions from atomic_init_testset.c
sync_val_compare_and_swap_1 --> atomic_cas_8_cas.c
sync_val_compare_and_swap_2 --> atomic_cas_16_cas.c
this helps with pullups
graphics/blender: Fix build after switch to NumPy 2.x
"ld: error: unable to find library -laudaspace-py"
This happens because configure can't find numpy and because of this the
shared library libaudaspace-py.so won't compile:
-- numpy found at '/usr/local/lib/python3.11/site-packages'
CMake Warning at build_files/cmake/macros.cmake:1210 (message):
Python package 'numpy' include dir path could not be found in:
'/usr/local/lib/python3.11/site-packages/numpy/core/include',
'/usr/local/lib/python3/site-packages/numpy/core/include',
'/usr/local/lib/python3.11/dist-packages/numpy/core/include',
'/usr/local/lib/python3/dist-packages/numpy/core/include',
'/usr/local/lib/python3.11/vendor-packages/numpy/core/include',
'/usr/local/lib/python3/vendor-packages/numpy/core/include',
The 'WITH_PYTHON_NUMPY' option will be disabled.
[11 lines not shown]
[clang-tidy] `use-ranges`: avoid unsafe result fix-its
Preserve callable results with .fun, allow structured-binding-safe rewrites, and keep diagnostics while suppressing unsafe fix-its when ranges result objects do not match the original result shape.
Assisted by Codex.
[libc] Add a simple scope_exit wrapper and use it in socket tests (#192615)
This is slightly different from the other CPP reimplementations in that
the real scope_exit is only an experimental C++ class. If that's an
issue, I'm happy to put the class somewhere else.
It could probably be used in more places, but right now I'm adding it to
socket tests, as that's what I'm familiar with. It (mostly -- it doesn't
help with crashes) solves the issue where a failing test does not clean
up the unix domain socket, which then fails the test on the subsequent
run.
[lldb] Do not refcount breakpoints in lldb-server (#195858)
We did not say so explictly, but I'd argue that via #195815, we are
supporting stubs which do not refcount breakpoints. In these stubs the
set/clear breakpoint packets are idempotent:
- setting a breakpoint for the second time is a no-op (returns OK)
- clearing a breakpoint clears it, regardless of how many times it has
been set
- clearing a non-existent breakpoint (either because it was already
cleared, or because it was never set) returns an error
This makes lldb-server one of those stubs, which makes the code slightly
simpler, but more importantly, ensures we do not regress this behavior.
x11/xterm: update to 410
Patch #410 - 2026/05/01
- amend one of the fixes for Debian #738794 in patch #407, which caused combining characters to be outlined (report by "Martin").
- clarify in ctlseqs.ms which modes listed for DECSET are readonly (prompted by discussion with Thomas Wolff).
[MLIR][vector] vector.deinterleave to vector.shuffle decomposition (#177897)
This PR adds a rewrite pattern for vector.deinterleave ops that rewrites
them using vector.shuffle ops. This is similar to the existing pattern
for vector.interleave and allows for supporting these ops for lowering
to targets without native deinterleave support. A transform dialect op
is also added to apply this pattern.
---------
Co-authored-by: Andrzej Warzyński <andrzej.warzynski at gmail.com>
sysutils/pciutils: update to 3.15.0
2026-04-05 Martin Mares <mj at ucw.cz>
* Released as 3.15.0.
* New capabilities are decoded: MMIO Register Block Locator,
Flit Error Injection, Flit Logging.
* Decoding of PCIe capabilities updated to Gen7.
* Both lspci and setpci warn when the "-s" or "-d" option
is given multiple times.
* Improved display of interrupts in "lspci -vv". Routing of
interrupt pins is shown only if the pins are not disabled.
Routing of MSI(X) interrupts is shown when available
(which is currently supported by the sysfs back-end only).
* Minor improvements to Windows back-ends.
* The dump back-end can read the dump from stdin when given "-"
as a file name.
* FreeBSD supports 64-bit addresses.
* Added README.DJGPP.
* Updated pci.ids.
