diff options
author | Antonio Frighetto <me@antoniofrighetto.com> | 2025-03-24 09:18:32 +0100 |
---|---|---|
committer | Antonio Frighetto <me@antoniofrighetto.com> | 2025-03-24 09:19:53 +0100 |
commit | ade22765174e64f6c02233eff8d55e6726e1bab1 (patch) | |
tree | 0cdf009d1a1a01c2c25b058e9768fd15c786a4f3 /lldb/packages/Python/lldbsuite/test/configuration.py | |
parent | 376aa741b59f9d6a44049f007d29fca832f8a4bf (diff) | |
download | llvm-ade22765174e64f6c02233eff8d55e6726e1bab1.zip llvm-ade22765174e64f6c02233eff8d55e6726e1bab1.tar.gz llvm-ade22765174e64f6c02233eff8d55e6726e1bab1.tar.bz2 |
[RegAllocFast] Ensure live-in vregs get reloaded after INLINEASM_BR spills
We have already ensured in 9cec2b246e719533723562950e56c292fe5dd5ad
that `INLINEASM_BR` output operands get spilled onto the stack, both
in the fallthrough path and in the indirect targets. Since reloads of
live-ins values into physical registers contextually happen after all
MIR instructions (and ops) have been visited, make sure such loads are
placed at the start of the block, but after prologues or `INLINEASM_BR`
spills, as otherwise this may cause stale values to be read from the
stack.
Fixes: #74483, #110251.
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/configuration.py')
0 files changed, 0 insertions, 0 deletions