summaryrefslogtreecommitdiff
path: root/llvm/lib/IR/Dominators.cpp
diff options
context:
space:
mode:
authorSebastian Neubauer <sebastian.neubauer@amd.com>2021-04-12 10:25:54 +0200
committerSebastian Neubauer <sebastian.neubauer@amd.com>2021-04-12 11:01:38 +0200
commitf9a8c6a0e50540f68e6740a849a7caf5e4d46ca6 (patch)
treeddd01dac8b35608ae506a18434ec16074d3cf46e /llvm/lib/IR/Dominators.cpp
parent731bf28a6092286dde6972803b35c026e32bd6b1 (diff)
downloadllvm-dev-main-update.tar.gz
[AMDGPU] Save VGPR of whole wave when spillingdev-main-update
Spilling SGPRs to scratch uses a temporary VGPR. LLVM currently cannot determine if a VGPR is used in other lanes or not, so we need to save all lanes of the VGPR. We even need to save the VGPR if it is marked as dead. The generated code depends on two things: - Can we scavenge an SGPR to save EXEC? - And can we scavenge a VGPR? If we can scavenge an SGPR, we - save EXEC into the SGPR - set the needed lane mask - save the temporary VGPR - write the spilled SGPR into VGPR lanes - save the VGPR again to the target stack slot - restore the VGPR - restore EXEC If we were not able to scavenge an SGPR, we do the same operations, but everytime the temporary VGPR is written to memory, we - write VGPR to memory - flip exec (s_not exec, exec) - write VGPR again (previously inactive lanes) Surprisingly often, we are able to scavenge an SGPR, even though we are at the brink of running out of SGPRs. Scavenging a VGPR does not have a great effect (saves three instructions if no SGPR was scavenged), but we need to know if the VGPR we use is live before or not, otherwise the machine verifier complains. Differential Revision: https://reviews.llvm.org/D96336
Diffstat (limited to 'llvm/lib/IR/Dominators.cpp')
0 files changed, 0 insertions, 0 deletions