[AMDGPU][AsmParser] Split the MTBUF formats into modifiers and regular operands (#241259)
This eliminates the hacks parsing formats together with soffsets that
may follow them and printing them in printRegularOperand() instead of
using the custom printer as usual.
The legacy forms are supported as aliases using the regular-operand
formats.
Assisted-By: Claude
[X86] LowerINSERT_VECTOR_ELT - insertelt(X,-1,IDX) - freeze the base element to prevent OR(poison,-1) -> poison folds. (#243410)
When lowering a allones insertion to a OR(X,<0,0,-1,0>) style pattern,
ensure the base element is frozen incase its uninitialised/poison
Fixes #241272
[AMDGPU][Docs] Fix terminology for memory model and DMA operations
- Define operations in terms of actions performed by dynamic instances.
- Use consistent wording for effects and their propagation.
- Clean up section headings, scope properties, and minor wording.
- Normalize async load/store names in stages, examples, and scheduling.
Assisted-by: AI
devel/py-*: Change *_DEPENDS from py-graphql-core to py-graphql-core32
* Adjust ports that either directly or indirectly require py-graphene
(which is currently incompatible with py-graphql-core 3.3+) or have a
corresponding upper limit, from py-graphql-core to py-graphql-core32.
* Bump PORTREVISION due dependency change.
Reviewed by: sunpoet (via private mail)
devel/py-graphql-core32: New port
GraphQL-core is a port of graphql-js to Python.
Note: This port is limited to the 3.2.x release series because
devel/py-graphene is currently not compatible with newer versions
of py-graphql-core.
Reviewed by: sunpoet (via private mail)
net/rsync: update 3.5.1 -> 3.5.2
Changelog: https://download.samba.org/pub/rsync/NEWS#3.5.2
Major changes:
- Fix CVE-2026-119741 (previously commited in 3.5.1_1)
- Fixed interrupted --append and --inplace transfers writing the final 256 KiB buffer twice
- Fixed uploads through rrsync when the destination file already exists.
- Fixed poor matching performance on large sparse and repeated-block files when duplicate
checksum chains exhausted the search limit
- Prevented the --inplace matcher from advancing its aligned basis index beyond the available
checksum entries
- Recovered from failed hard-link creation without aborting or hanging the generator.
- Prevented an out-of-bounds write while invalidating a sender checksum after a file read error
when the negotiated checksum length is zero
- Prevented the --inplace matcher from advancing its aligned basis index beyond the available
checksum entries
- Recovered from failed hard-link creation without aborting or hanging the generator
- Prevented an out-of-bounds write while invalidating a sender checksum after a file read error
[17 lines not shown]
libreswan: Remove fixed vulnerabilities
In pkg-vulnerabilities we only tracks vulnerabilities for packages that
are in pkgsrc tree (not pkgsrc-wip). When a pkgsrc-wip is imported in
pkgsrc we start tracking them.
Given that libreswan has all the CVEs listed now in the TODO fixed, stop
mentioning them.
[mlir][LLVM] Include LLVM dialect partition headers instead of LLVMDialect.h
Most includers of `LLVMDialect.h` use only a few LLVM dialect ops, or none at all, but still pay for all 323 op declarations. Widely included headers such as `OpenMPDialect.h`, `NVVMDialect.h` and `GPUCommonPass.h` include it as well, spreading the cost to TUs that never use the LLVM dialect.
Building on #242301, this patch makes every file include what it uses: the partition headers of the ops it uses, `LLVMDialectDecl.h`, `LLVMTypes.h`, `LLVMAttrs.h` or `LLVMInterfaces.h` if it only uses the dialect, types, attributes or interfaces, and forward declarations where a declaration suffices. Headers no longer include LLVM dialect headers on behalf of their includers. Files that use ops from at least 8 of the 14 partitions keep `LLVMDialect.h`.
This reduces the TUs including `LLVMDialect.h` in an MLIR, flang and CIR build from 386 to 41. Downstream code that relied on getting LLVM dialect ops transitively has to include the partition headers it needs.
Measurements of the users of the LLVM dialect, where "Memory" is the sum of the max RSS of every TU:
| Compiler | Wall time (s) | CPU time (s) | Total memory (GiB) |
|----------|--------------------|---------------------|-----------------------|
| clang | 53.9 -> 49.2 (-9%) | 1484 -> 1131 (-24%) | 79.4 -> 60.8 (-23%) |
| clang -g | 68.1 -> 62.9 (-8%) | 1639 -> 1245 (-24%) | 83.8 -> 65.3 (-22%) |
| gcc | 62.3 -> 57.4 (-8%) | 1388 -> 1036 (-25%) | 119.8 -> 88.5 (-26%) |
| gcc -g | 94.4 -> 85.5 (-9%) | 2193 -> 1555 (-29%) | 157.1 -> 116.7 (-26%) |
[clang][bytecode] Decay pointers when adding a zero offset (#242785)
Let zero offsets go through the `OffsetHelper` path, but return early
for non-arrays so we don't change those.
[CIR] Add address_points to #cir.vtable + generation (#242059)
This patch adds address_points to vtable attr constants, which hold the
index/offset in a vtable of the 'address point's. The 'address-point' is
the split location in each element between the RTTI/offset, and the
virtual function component to the vtable.
This is currently not used/useful yet, as it is necessary for
calculating relative-v-tables, but not for classic offset-based vtable
caluclations.