[AMDGPU] Fix eliminateFrameIndex assertion when reusing the frame register. (#215182)
This is a follow-up patch that solves the crashing test in the #215180
On a flat-scratch target, a frame index used by a VALU instruction with
a live frame register but no scavengeable SGPR entered the branch that
assumes no frame register exists, tripping `assert(!FrameReg && "there
is a frame register!")`.
Restore the `!FrameReg` term in the guard so this case falls through to
the existing path that reuses the frame register as the temporary
(offset folded in, then restored). The `!FrameReg` assertion is moved
into the SVS
fallback, where it actually holds.
ARM: Read float ABI from the "float-abi" module flag
Use the value from the module flag if present, otherwise
fall back on the legacy TargetOptions field until that is
removed.
Co-authored-by: Claude (Claude-Opus-4.8) <noreply at anthropic.com>
VPN: OpenVPN: Connection Status - add some input validation for control characters
PR: GHSA-fqmm-g6xw-qhm4
(cherry picked from commit 024d986d43538b5261413f6cf5b815175e9253b1)
evbarm/ti_edma: enable on am18xx SoCs
The linux dt-bindings allow two different ways to specify power/clock domains for the edma3. This commit adds support for the way used on the am18xx (powerdomains).
[LV] Prefer fixed VFs for epilogue vectorization (#211814)
Unless forced (via `-scalable-vectorization=always`), or if the fixed
vector cost is much higher than scalable vectors (which occurs for some
loops, such as histograms), prefer fixed vectors for the epilogue.
There are currently some hidden costs for scalable epilogues that are
not modeled (such as reduced post-vectorization unrolling).
This restriction likely can be lifted/reworked once we support
predicated vector epilogue.
net-mgmt/netbox: Update to 4.6.8
Changelog:
Performance Improvements:
* Avoid N+1 queries when resolving generic relations (e.g. assigned
objects) via the GraphQL API
* Improve performance when provisioning new custom fields
* Omit implicit pagination when prefetching to-one relations via
the GraphQL API
* Improve caching logic when retrieving custom fields via
get_for_model()
Bug Fixes:
* Clear a device's stale rack assignment when changing its site
* Enforce object permissions on custom script write operations via
the REST API
* Avoid re-executing the LDAP configuration file on every
permission check
[24 lines not shown]
DAG: Gracefully diagnose missing fp128 ldexp/frexp libcalls (#215626)
When the fp128 ldexp/frexp libcall is unavailable (e.g. MSVC),
LegalizeDAG crashed instead of emitting a diagnostic. The expansion
path introduces a cast to an integer type, so we can't introduce that
wide integer if it's not legal at this point.
Co-authored-by: Claude (Claude-Opus-4.8) <noreply at anthropic.com>
[mlir][python] Define __index__ on PyIntegerAttribute (#215555)
In nanobind v2.14.0+, integer casting from Python objects to C++ integer
types was updated to require `__index__` (`PyNumber_Index`) instead of
`__int__`.
https://nanobind.readthedocs.io/en/latest/changelog.html#version-2-14-0-aug-7-2026
Because `PyIntegerAttribute` defined `__int__` but not `__index__`,
passing `IntegerAttr` instances to bindings expecting integer sequences
failed. Specifically, in `mlir/test/python/ir/attributes.py`:
# CHECK: input: [IntegerAttr(4 : i64), IntegerAttr(2 : i64)] (<class
'list'>),
# CHECK-SAME: result: array<i8: 4, 2>
create_and_print(DenseI8ArrayAttr, [Attribute.parse(f"{x}") for x in [4,
2]])
[11 lines not shown]
shells/shuck: import shuck-0.1.1
A fast shell script linter, formatter, and language server, written
in Rust.
Shuck parses, analyzes, formats, and powers editor feedback for
shell scripts. It catches common bugs, style issues, security
hazards, performance traps, and portability problems; formats shell
sources with configurable layout rules; and ships a first-party
Language Server Protocol (LSP) server for editor diagnostics, fixes,
navigation, symbols, hover, completion, and formatting. It also
lints shell embedded in supported non-shell files such as GitHub
Actions workflows. A caching layer keeps incremental runs fast.
