diff options
| author | Matt Arsenault <Matthew.Arsenault@amd.com> | 2021-11-03 21:01:53 -0400 |
|---|---|---|
| committer | Matt Arsenault <Matthew.Arsenault@amd.com> | 2021-11-23 18:01:12 -0500 |
| commit | 273a0c8bc9c774aa0d5982c23dc3d62b68ef4338 (patch) | |
| tree | 920d618f7ba85cc17693c999a9593e958468c42b /lldb/packages/Python/lldbsuite/test/gdbclientutils.py | |
| parent | 73a05cc8dfa114e29cd4d463c77a5577571c8c56 (diff) | |
| download | llvm-273a0c8bc9c774aa0d5982c23dc3d62b68ef4338.zip llvm-273a0c8bc9c774aa0d5982c23dc3d62b68ef4338.tar.gz llvm-273a0c8bc9c774aa0d5982c23dc3d62b68ef4338.tar.bz2 | |
PrologEpilogInserter: Use explicit control for scavenge slot placement
AMDGPU is unusual in that the both stack is indexed in the same
direction as stack growth (up). We therefore always need the emergency
stack slots placed as low as possible to ensure they are in range of
load/store instruction immediate offsets. The existing logic is mostly
OK, but failed if we required stack realignment.
I don't understand what the existing control isFPCloseToIncomingSP is
supposed to mean, but can only be used to stop placing the scavenge
slots earlier. Make this explicit so that targets can opt-in rather
than opt-out only.
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/gdbclientutils.py')
0 files changed, 0 insertions, 0 deletions