[lldb][AArch64][Linux] Add function to get regset dependencies (#212476)
This function encodes relations between sets so that you
don't have to remember all the dependencies.
There are some places where we do:
if some condition:
Invalidate(some set);
I've chosen not to put that logic in this new function so
that it can be a simple switch case.
The few places we need extra state to make the decision
are also all SVE/SME related. This code will likely remain
bespoke anyway.
Whereas the simple paths will all get collapsed into
a generic handler later.
[2 lines not shown]
ARM: Read float ABI from the "float-abi" module flag (#212981)
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>
sdmmc: dmamap_load bounce buffer on demand
When using a bounce buffer, cmd->c_dmamap->dm_segs[0]->ds_len did not agree with cmd->c_datalen because the bounce buffer is loaded once at initialization, so cmd->c_dmamap->dm_segs[0]->ds_len never gets updated before executing a sdmmc command.
This is problematic when the dmamap is passed on to an API like fdt_dma that treats the dmamap as the source of truth.
This problem probably hasn't surfaced yet because it needs three preconditions:
- using bounce buffers is already an edge case for when we can't allocate block size aligned dma memory
- the driver needs CAPS_DMA, but not CAPS_MULTI_SEG_DMA
- the driver needs to use cmd->c_dmamap->dm_segs[0]->ds_len and not cmd->c_datalen
The fix is to bus_dmamap_load the bounce buffer just when we need it. This allows us to load it with the correct size.
DAG: Gracefully diagnose missing FP conversion libcalls when softening
Diagnose the missing libcall and return poison instead.
Co-authored-by: Claude (Claude-Opus-4.8) <noreply at anthropic.com>
[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]
