[clang] NFC: add asserts enforcing template parameters have valid positions
Some tests are violating these assertions, so they are commented out.
For the test in `clang/test/SemaTemplate/concepts.cpp`, that was broken by #195995
and needs a partial revert at least.
[clang] CTAD: fix transformation of template template parameters (#197611)
This fixes the CTAD template parameter transforms so they produce
template template parameters which have correct depth for their own
template parameters.
This also stops calling SubstDecl directly on the non-type template
parameters, so that a template parameter with correct position is
produced directly, instead of manually fixing that up later. This helps
#197598 by making it possible to add assertions that the positions are
always valid.
[AArch64][GlobalISel] Add always legal action builders. (#197238)
This defined some always legal actions, removing our dependency on the
Legacy ruleset in aarch64.
[AMDGPU][NFC] Remove redundant hasMadU64U32NoCarry helper
Use hasMadNC64_32Insts() (backed by SubtargetFeature) for MAD 64_32
no-carry and drop the old helper.
[NFC] Format two AMDGPU files (#197672)
- `llvm/lib/Target/AMDGPU/MCTargetDesc/AMDGPUTargetStreamer.cpp`
- `llvm/lib/Target/AMDGPU/AMDGPUAsmPrinter.cpp`
[UniformityAnalysis] Fix nodivergencesource calls (#197656)
NFC #168903 introduced a subtle behavior change for calls with the
nodivergencesource attribute and divergent operands.
Calls with the nodivergencesource attribute are *not* always uniform.
They just do not introduce any new divergence. If any operand is
divergent,
the result must still be reported as divergent.
Revert to pre-#168903 behavior by allowing the standard propagation to
work for target's NeverUniform while keeping Default and AlwaysUniform
unchanged.
AMDGPU/GlobalISel: Legalize scalar extloads with large memory type (#197648)
Add narrowScalar for scalar sext/zextload when the memory type is
larger then 32 bits. There is no narrow scalar implementation when
NarrowSize < MemSize (split load) but we don't want that anyway.
Narrow scalar to MemSize creates large normal load + extension to dst.
[NFC][Analysis] Use `isa<ConstantPointerNull>` for null pointer checks (#197544)
Make Analysis null pointer checks use `isa<ConstantPointerNull>` rather
than generic null value checks (`isNullValue()`).
[libc] Fix shared math for gcc-7 or older compatibility. (#197476)
- Add gcc-7 or older compatibility for cpp::is_assignable and
cpp::is_constructible.
- Apply LIBC_CONSTEXPR to FPUtil/rounding_mode.h
NAS-140995 / 26.0.0-RC.1 / Add NFSv4 multi-client race tests (by ixhamza) (#18946)
### Summary
This commit adds multi-client NFSv4 race tests under
`tests/sharing_protocols/nfs/test_nfs_mt_races.py`.
Existing NFS coverage drives the server through a single PynfsClient
session or via the in-kernel Linux NFS client; in both cases requests
are serialized through one client identity, so the server's multi-client
serialization paths get exercised only incidentally. This left the
server's behavior under genuinely concurrent multi-client load
(share-state, byte-range locks, namespace mutations, data writes, and
metadata mutations) largely unverified.
These tests close those gaps by spawning N independent NFSv4 clients
(each with its own clientid and session) per scenario and asserting the
exact server response distribution against the expected serialization
outcome. A regression in any covered path (for example, the lock manager
[15 lines not shown]
[RISCV] Check SP-relative offset in needsFrameBaseReg when FP offset overflows (#197368)
When a frame pointer is present, `needsFrameBaseReg` previously only
checked the FP-relative offset to decide if a virtual base register was
needed. If the worst-case FP offset exceeded the 12-bit immediate range,
a base register was always materialized, even when the SP-relative
offset would fit.
Since `getFrameIndexReference` can now select SP over FP when the offset
fits in the compressed instruction immediate range, also check the
SP-relative offset before deciding a base register is needed. This
avoids unnecessary base register materialization and results in some
code size savings.
[libc] prefer *at syscalls in sys/stat wrappers (#195792)
- so the changes flips the #ifdef order to prefer the *at syscalls over normal ones.
- In modern architectures, *at system calls are preferred over normal
system calls.
- so by checking for "*at" sys calls first, we ensure better
compatibility with modern systems.
- then normal syscalls moved to else for support of older ones.
Signed-off-by: udaykiriti <udaykiriti624 at gmail.com>
gnupg2: updated to 2.5.20
Noteworthy changes in version 2.5.20 (2026-05-13)
* New and extended features:
- gpgsm: Implement GCM encryption. Note that decryption works
since version 2.3.2.
- gpgsm: New option --attribute and server command SETATTR to
include arbitrary signed or unsigned attributes into a signature.
Enable only with libksba 1.7.0 or later.
- gpgsm: Introduce system attribute _signingCertificateV2.
* Bug fixes:
- gpg: Fix wrong assertion failure which could very rarely occur
during key signature checking.
- gpg: Consider certify-only keys for revocation signature check.
- gpgsm: Fix possible double free in the CMS parser.
[13 lines not shown]
libksba: updated to 1.8.0
Noteworthy changes in version 1.8.0 (2026-05-13) [C24/A16/R0]
* New function ksba_cms_get_attribute.
* Support building of unsigned attributes with
ksba_cms_add_attribute.
Add NFSv4 multi-client race tests
Add 18 multi-client NFSv4 race tests under
tests/sharing_protocols/nfs/test_nfs_mt_races.py. Each test spawns
N=8 worker threads, each driving its own PynfsClient (distinct
clientid + session), with a barrier-synchronised start so the
server sees concurrent requests. Status distributions are
aggregated and asserted to match RFC 8881 expectations exactly.
Coverage:
- OPEN/CLOSE share-state: DENY_WRITE / DENY_READ mutex; compatible
OPEN(READ) coexistence (RFC 8881 §9.7).
- Byte-range LOCK: shared READ_LT coexistence; disjoint WRITE_LT
coexistence; conflicting WRITE_LT on the same range; readers
blocked by a held WRITE_LT; writers blocked by a held READ_LT
(§9.1). The conflict tests use a sequential holder client +
racer pool; an internal grace-retry helper handles
NFS4ERR_GRACE so the holder's LOCK is reliably acquired across
server-side grace transitions.
[32 lines not shown]
NAS-140995 / 27.0.0-BETA.1 / Add NFSv4 multi-client race tests (#18943)
### Summary
This commit adds multi-client NFSv4 race tests under
`tests/sharing_protocols/nfs/test_nfs_mt_races.py`.
Existing NFS coverage drives the server through a single PynfsClient
session or via the in-kernel Linux NFS client; in both cases requests
are serialized through one client identity, so the server's multi-client
serialization paths get exercised only incidentally. This left the
server's behavior under genuinely concurrent multi-client load
(share-state, byte-range locks, namespace mutations, data writes, and
metadata mutations) largely unverified.
These tests close those gaps by spawning N independent NFSv4 clients
(each with its own clientid and session) per scenario and asserting the
exact server response distribution against the expected serialization
outcome. A regression in any covered path (for example, the lock manager
[11 lines not shown]
