diff options
| author | Matt Arsenault <Matthew.Arsenault@amd.com> | 2025-02-23 09:00:37 +0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-02-23 09:00:37 +0700 |
| commit | ccad5e77442f7f237939395ebce1ae7adf187380 (patch) | |
| tree | 5a731da2e1614ebeca6bc40b3ba8a32fb038d54d /lldb/test/API/functionalities/scripted_process/TestStackCoreScriptedProcess.py | |
| parent | 6e611264c6d7e6dd5f746360a74f8edf656dbf32 (diff) | |
AMDGPU: Respect amdgpu-no-agpr in functions and with calls (#128147)
Remove the MIR scan to detect whether AGPRs are used or not,
and the special case for callable functions. This behavior was
confusing, and not overridable. The amdgpu-no-agpr attribute was
intended to avoid this imprecise heuristic for how many AGPRs to
allocate. It was also too confusing to make this interact with
the pending amdgpu-num-agpr replacement for amdgpu-no-agpr.
Also adds an xfail-ish test where the register allocator asserts
after allocation fails which I ran into.
Future work should reintroduce a more refined MIR scan to estimate
AGPR pressure for how to split AGPRs and VGPRs.
Diffstat (limited to 'lldb/test/API/functionalities/scripted_process/TestStackCoreScriptedProcess.py')
0 files changed, 0 insertions, 0 deletions