interfaces: be more conservative with -no_dad #10951
In e0e1401f8739e we're enabling it always which also affects
assigned tunnels such as WireGuard which tend to avoid wanting
DAD so make room for leaving the flag unchanged and change it
everywhere else explicitly per type.
[AMDGPU] Validate scale_sel in v_cvt_scale_*
These instructions can be block16 or block32 depending on the target
and scale_sel bits. Block16 is not supported in strict mode.
Re-enable the rest of the instructions in the strict mode but validate
the scale selector.
[compiler-rt] Fix -shared-libsan usage with internal symbolizer (#227717)
Summary:
https://github.com/llvm/llvm-project/pull/226551 exposed a preexisting
issue when using `-shared-libsan` nad the internal symbolizer builds.
The symbolizer will try to look up the symbol via `RTLD_NEXT`, which
goes in load order. If the sanitizer library is loaded *after* `libc.so`
then this `dlsym` call will miss it.
The solution is to have a fallback that checks using `RTLD_DEFAULT`.
This
should allow us to find the symbol in these exceptional cases. I don't
expect much fallout as this covers a case that currently returns `NULL`.
Loading it in means it could grab a reference ahead of the runtime that
was intended to be intercepted, but for this use-case I don't think this
will apply.
[clang] Fix crash constant-evaluating the construction of huge arrays (#226899)
Fixes #173728
The constant evaluator runs on ordinary code all the time (range checks
for `-W` warnings, `isEvaluatable` in codegen), and it
default-constructs an array by building one `APValue` per element. The
element count got truncated to `unsigned` first and nothing checked its
size, so a local like `struct T {} s[0xFFFFFFFF][0]` ran it out of
memory; with the issue's reproducer, where the count wraps to 2^64 - 4,
an assertions build hits the "bounds check failed" assertion in
`adjustIndex` first. Copying such an array, e.g. into a lambda capture,
had the same problem. This goes back to at least Clang 3.4. The bytecode
interpreter has its own version: it emits code for every element, so a
constructor with a member like `T a[0xFFFFFFFF]` runs it out of memory
too.
Array default construction and `ArrayInitLoopExpr` now go through the
existing `CheckArraySize` guard, the same one `new` already uses, so
[6 lines not shown]
[LLDB] Acquire the module mutex at the start of SetLoadAddress (#227149)
Fixes a potential dead-lock from parallel module loading.
I received a quick-stack of LLDB hung loading a core with parallel
module loading enabled, where two threads were trying to mutate a given
module and an object file, but having acquired the module mutex first in
one case, and the object file's section mutex first in the second case,
which each trying to subsequently acquire the other lock.
In the update case, [SetLoadAddress acquires the section list mutex and
then tries to acquire the module
mutex](https://github.com/llvm/llvm-project/blob/60f717946cb5ca911b6be22169b9bd646225c59f/lldb/source/Symbol/ObjectFile.cpp#L614)
```
SectionList *ObjectFile::GetSectionList(bool update_module_section_list) {
std::lock_guard<std::recursive_mutex> guard(m_sections_mutex);
if (m_sections_up)
return m_sections_up.get();
[26 lines not shown]
powerdns-recursor: Update to 5.4.7
Released: 1st of October 2026
Bug Fixes
Rec: Fix Lua to YAML conversion of custom RPZ policies
References: pull request 18029
Rec: retrieve DNSSEC data with RPZ processing disabled
References: pull request 18035
Rec: Catch exception thrown by parsing system resolver result
References: pull request 18068
Fix(rec): Wipe caches when wiping all NTA’s
References: pull request 18070
Rec and auth: fix axfr failure to invalidate fd on close in all cases.
References: pull request 18084
[2 lines not shown]
[clang][OpenMP] Don't use fused dist schedule for teams loop emitted as distribute (#228129)
Fix teams loop reductions lowered as 'distribute' lose their loop.
Claude assisted with this patch.
[AMDGPU] Canonicalize num_records to its actual width in InstCombine
llvm.amdgcn.make.buffer.rsrc is overloaded on the type of its
num_records argument, but the hardware field it ends up in has a fixed
width (32 bits, or 45 bits on gfx1250 and up). Rewrite the intrinsic to
use that width, zero-extending or truncating num_records as needed, so
that IR-level optimizations can see that the extra bits of, for example,
the i64 that Clang emits are not demanded.
Targets that aren't concrete enough for the buffer resource layout to be
known are left alone.
AI disclosure: This was my idea but Claude wrote the code (and I've
tried to tighten up the comments)
[AMDGPU] Pre-commit tests for num_records canonicalizations (#217067)
Add tests for having InstCombine canonicalize the num_records argument
of llvm.amdgcn.make.buffer.rsrc to the width it will ultimately have,
which lets later passes see that, for example, the high bits of the i64
that Clang emits aren't used.
AI disclosure: Claude generated these and I've looked at them
py-cbor2: updated to 6.1.5
6.1.5
- Fixed :class:`CBORSimpleValue` hashing inconsistently with the integer it compares equal to
- Fixed canonical encoding with value sharing enabled emitting shared references to container
keys that were never written to the stream, because the throwaway encoding used to sort the keys
registered them as shared values; the output then failed to decode, or decoded with the wrong
keys substituted in
- Fixed shared references (tag 29) to a map or an unhandled tag resolving to the raw
:class:`dict` or :class:`CBORTag` instead of the value returned by ``object_hook`` or
``tag_hook``, a regression from 5.x
- Fixed the encoder not giving a nested stringref namespace (tag 256) its own index space
- Fixed the decoder returning its internal break marker as a value when a break stop code
appeared where a data item was expected
- Fixed a ``PanicException`` when trying to decode an epoch-form date (tag 100) with a payload near
``i32::MAX`` which then overflowed the addition instead of raising a clean decode error
- Fixed the decoder accepting a string-form datetime (tag 0) without a UTC offset and returning
a naive :class:`~datetime.datetime` instead of rejecting it
[2 lines not shown]
py-ruff: updated to 0.16.10
0.16.10
Preview features
Add a migration guide for categories
[pyupgrade] Add rule for context manager iterator annotations (UP052)
Performance
Reduce memory used by diagnostics
Server
Avoid running uv format in untrusted workspaces
Documentation
[7 lines not shown]
Read NTP peers from the chronyd socket
Stop running chronyc and ask chronyd directly over its unix socket. Replies are checked the same way libchrony checks them. Drop the NTPPeer wrapper so the alert reads the peer entries as they are. Add a unit test for the request and reply handling.
[Clang][RISCV][P-ext] Add packed Q-format widening accumulate intrinsics (#228009)
Add support for the Packed "Q-format" Multiply with Widening Accumulate
intrinsics:
- `__riscv_pmqwacc_i32x2`
- `__riscv_pmqrwacc_i32x2`
RV32 selects the direct instructions, while RV64 lowers to the
spec-listed `zip16p` and packed Q-format accumulate sequences.
fssconfig(8): Clarify some details.
- Note up front that fssdev can be mounted with mount(8).
- Emphasize that fssconfig -c takes a mount point, not an arbitrary
directory.
- Break the prose paragraph of options for snapstore into a bulleted
list.
- Clarify that you needn't use fssconfig(8) at all with dump(8).
- Move dump -X/-x option up front to make it more obvious.
llvm: remove Mips target support
The Mips architecture has been removed from all supported branches now.
MFC after: 1 week
(cherry picked from commit b5d1e0c5a4929e2be3bc58aad8e5b707860ec0fd)
