[mlir][GPU] Refactor GPUOps lowering (#188905)
This change promotes `gpu.func` / `gpu.launch` metadata that was
previously carried as discardable attributes into proper inherent ODS
fields (`kernel`, `workgroup_attributions`), renames the block-argument
helpers to avoid clashing with generated getters, and routes `func.func`
and `gpu.func` lowering through a shared helper that maps discardable
`llvm.*` attributes into `llvm.func` properties.
Downstream producers (Flang CUDA device func transform, kernel
outlining, sparse GPU codegen, XeGPU) set kernels via `setKernel(true)`
instead of manually attaching `gpu.kernel`.
Fixes #185174
Assisted-by: CLion code completion, GPT 5.3 - Codex
[mlir][linalg] Fix crash when folding tensor.cast into unpack using static packed shape for inner tiles (#188000)
This change fixes #187975 and #188405, a crash in Linalg tensor-cast
folding for pack/unpack when tile sizes are dynamic or otherwise not
provably constant.
Previously, canonicalization could reach getNewMixedTileSizes and
unconditionally access `getConstantIntValue(tile).value()`. For dynamic
tile operands, that value can be absent, causing
`std::bad_optional_access/assert` aborts.
When folding `tensor.cast` into `linalg.unpack` (and the same helper is
used for linalg.pack), mixed inner tile sizes are updated from the
refined packed tensor type. Every static trailing packed dimension gets
a matching static tile attribute, replacing SSA tile values and
overwriting tile constants that disagreed with that type.
Dynamic packed dimensions still keep the original tile operands.
Assisted-by: CLion code completion
[LV] Change VPLane::getAsRuntimeExpr to use constant 64-bit indices (#193206)
The canonical form preferred by instcombine is to use 64-bit values for
the index when it is a constant. We should try to do the same where
possible in the loop vectoriser as this reduces churn in the compiler.
It also makes other work easier, such as removing extra unnecessary
passes on the RUN line in the test directory which I plan to do
afterwards.
NAS-140691 / 26.0.0-BETA.2 / Inherit `canmount` when migrating Incus containers (#18779)
## Summary
Fixes a regression in the legacy Incus → container migration
(`container.migrate`, first shipped in 26.0.0-BETA.1) that left migrated
containers unable to start on every subsequent boot with:
```
libvirtError: internal error: guest failed to start: Failure in libvirt_lxc startup:
cannot find init path '/sbin/init' relative to container root: No such file or directory
```
## Root cause
Incus sets `canmount=noauto` locally on each container dataset so it can
manage mounts itself. `container.migrate_specific_pool` inherited
`mountpoint` and cleared `readonly` on the legacy datasets but did
**not** touch `canmount`.
[33 lines not shown]
net-mgmt/netbox: Update to 4.5.8
* The first code that is backward-incompatible with Python 3.11 has
appeared in this release, which was to be expected since the support
for it was officially discontinued with the Netbox 4.5 release.
The actual workaround to get Python 3.11 compatibility is quite simple
and as long as this remains the case until the NetBox 4.6 release,
which requires Django 6.0 and thus Python 3.12+, compatibility with
Python 3.11 can still be provided.
Changelog:
Enhancements:
* Display the device role's color in the device view
* Update humanize_speed template filter to support decimal Gbps/Tbps
values
Bug Fixes:
[21 lines not shown]
devel/py-dj52-strawberry-graphql: Update to 0.314.3
* Add APOLLO-FEDERATION option, which has been introduced with the
0.314.0 release, and keep it non-default like the other options to
keep the dependencies at a minimum.
* Relax the version requirements for py-uv-build as well to be able to
build the port in the quarterly branch, where py-uv-build is present
at version 0.10.10.
Changelog since 0.312.4:
https://github.com/strawberry-graphql/strawberry/blob/0.314.3/CHANGELOG.md
MFH: 2026Q2
(cherry picked from commit acf2f77846437ff52d4858b1cfc6e35044edbfba)
[clangd][test] Fix test failures when LLVM_WINDOWS_PREFER_FORWARD_SLASH is ON (#193160)
This commit addresses several test failures in Clangd that occur on
Windows when the CMake option -DLLVM_WINDOWS_PREFER_FORWARD_SLASH=ON is
enabled.
Key changes:
- Updated testRoot() and TestScheme to dynamically return native path
styles.
- Normalized expected paths in URI tests using a helper that calls
llvm::sys::path::native.
[LLVM][ConstantFolding] Use correct type when flushing denormals. (#193254)
flushDenormalConstant always created a scalar ConstantFP even when
passed a vector type. I've had to change the return type from
ConstantFP* to Constant* because ConstantFP::get does not necessarily
return a ConstantFP. This can be reverted when ConstantFP vectors are
enabled by default (although additional work is required to support
zero).
[DA] Remove unnecesasry SCEV negation operation (NFCI) (#193447)
Previously, we needed to normalize the coefficient to positive in the
Weak Crossing SIV test because the subsequent analysis relied on the
sign of `Delta`. However, since that logic has been removed, we no
longer need to make the coefficient positive.
[CIR] Fix __builtin_clz/__builtin_ctz poison_zero to respect target (#192865)
CIR was hardcoding poisonZero=true for all clz/ctz builtins, ignoring
the target's isCLZForZeroUndef(). This caused incorrect UB on targets
like AArch64 where clz/ctz of zero is well-defined.
Also add support for __builtin_c[lt]zg fallback (2-arg) variants with
compare+select, and add NYI stubs for elementwise variants.
[IRBuilder][NFC] Add `CreateFAbs` helper (#193421)
This PR refactors the common logic for creating the `llvm.fabs`
intrinsic into a shared helper.
The refactoring was found while reviewing #192182. As it affects code
beyond the scope of that original change, it is split into a seprate PR
here.
NFC intended.
[clang][ssaf][NFC] Rework how the Force linker anchors are defined and used (#189409)
- Moves them to the `clang::ssaf` namespace.
- Drops the custom force linker header used for testing, because all
object files are directly linked into the unittest executable, so we
don't need special handling there. This reduces complexity.
- Updates the documentation to reflect the new use.
