[Clang][AMDGPU] Use unsigned int for tensor builtin D# groups (#230714)
The D# tensor descriptor groups of __builtin_amdgcn_tensor_load_to_lds
and __builtin_amdgcn_tensor_store_from_lds are bit fields, not signed
values. D0 was already declared as a vector of unsigned int; D1 through
D4 are now consistent with it.
OpenCL does not allow lax vector conversions, so the tests are updated
to pass unsigned vectors. The generated IR is unchanged.
Reference: https://github.com/llvm/llvm-project/pull/193310
Co-authored-by: Claude Opus 5 <noreply at anthropic.com>
editors/openoffice-4: Upgrade to 4.1.17 RC2
Upgrade Apache OpenOffice to version 4.1.17 RC2.
MFH: 2026Q4
(cherry picked from commit e5948c273e23a7d335c486f3e972f12647f8dc99)
[lldb][docs] Use project-local documentation links
Replace same-project absolute URLs with relative Markdown links and Sphinx
cross-references so local and archived documentation stays self-contained.
Update generated Python API docstrings accordingly, and enable the absolute
link check for the LLDB docs to keep it that way.
[docs] Enable absolute documentation link checks
Configure the LLVM documentation URL prefixes so the Sphinx build rejects
absolute links to documents in the same project. Clang is already configured.
Part of #214861
[clang][Parse] Delay template-id destruction in NTTP default arguments (#230513)
There was a UAF when the lambda appears within NTTP default arguments.
Co-authored-by: Emery Conrad <emery.conrad at chicagotrading.com>
Co-authored-by: Sebastian Schwartz <sebastian.schwartz at chicagotrading.com>
Co-authored-by: Emery Conrad <emery.conrad at chicagotrading.com>
Assisted-by: Claude Code (claude-opus-5-5)
{french,german}/wordpress: chase upstream distfile re-roll
Upstream re-rolled the 7.1.3 fr_FR and de_DE tarballs: the bundled
twentytwentytwo theme was dropped (matching the en_US distfile) and
the fr_FR translations were refreshed. The WordPress core files are
unchanged.
Update distinfo and bump PORTREVISION as package contents changed.
[CIR] Add bytecode encodings for attributes (#229586)
Without a BytecodeDialectInterface, MLIR encodes a dialect's attributes
through their assembly format, embedding the printed text in the
bytecode. This adds native encodings for 27 CIR attributes (constants,
constant initializers, global views, method/data-member pointers, C++
special-member attributes, and small metadata attributes), modelled on
the LLVM dialect's bytecode support.
On attribute-dense modules this shrinks the bytecode ~30-40% (8.6KB to
5.4KB across the new tests). The room ahead is huge, emitting bytecode
for CIRGenModule.cpp (441MB of CIR text) still exceeds 22GB RSS and 30
minutes with these encodings (64GB and 45 minutes without), since types
keep using the assembly fallback. This is paving towards selfhosting
with bytecode.
Coverage is partial by design: anything not listed keeps using the
assembly-format fallback, exactly as before. Types keep the fallback too
until the type encodings land separately.
[3 lines not shown]
Protect against autoconf/Xcode mishegas on macOS.
This seems to strike periodically, confuse a developer or two for a little
while, and then go away. Why? Because it happens in the interval between
Apple issuing a version of Xcode that supports a newer OS, and newer APIs,
and a given developer's system being upgraded (Apple typically ships Xcode
supporting a new version of macOS a little prior to the OS itself).
The symptom is that autoconf detects symbols that are weakly available with
the new Xcode but which will cause built executables to dump core if called
on the old host OS. This is evidently being addressed in newer versions of
autoconf but who knows when we'll get those across our tree. The fix is to
tell Xcode to use an older SDK if the potential for this condition is detected.
[scudo] Check quarantine batch bounds in release builds (#230247)
[Attacking Scudo's Quarantine, section 3: Write Where
Ptr](https://un1fuzz.github.io/articles/quarantine_attack.html#a3)
describes corrupting a quarantine batch's `Count` so that enqueue writes
the freed pointer outside the batch. The original [PoC and exploit code
are
here](https://github.com/un1fuzz/scudo_research/tree/main/quarantine_arbitrary_return).
`push_back()` currently guards its index with a debug-only check; an
oversized count also bypasses enqueue's full-batch equality check.
Make that bound a release-build check. Also validate both counts before
deciding whether batches can merge, enforce merge capacity in
production, and check the count before shuffling (which precedes
recycling). The capacity comparison uses subtraction after validating
both operands, avoiding corrupted-count addition wrapping around.
This closes the out-of-bounds enqueue primitive described in section 3.
It does not address section 2's Double Return attack using in-range
[23 lines not shown]
Always write INFO/version when storing an SMB share ACL
store_share_acl only wrote the INFO/version key into share_info.tdb when
the file did not exist. This fixes a regression introduced when we added
stateful failover for SMB to truenas 26 and adds test coverage.
