diff options
| author | Matt Arsenault <Matthew.Arsenault@amd.com> | 2020-09-21 08:43:06 -0400 |
|---|---|---|
| committer | Matt Arsenault <Matthew.Arsenault@amd.com> | 2021-01-26 13:01:45 -0500 |
| commit | 5f9707b7960e9a86330dacb814b2ec55207e6f87 (patch) | |
| tree | 8e2792920eb5ce6f3430aee25af0a349079f4d34 /clang/lib/Frontend/CompilerInvocation.cpp | |
| parent | 92d1195b5f76548ca35bc00d97e0a28053b2c4a4 (diff) | |
| download | llvm-5f9707b7960e9a86330dacb814b2ec55207e6f87.zip llvm-5f9707b7960e9a86330dacb814b2ec55207e6f87.tar.gz llvm-5f9707b7960e9a86330dacb814b2ec55207e6f87.tar.bz2 | |
AMDGPU: Fix redundant FP spilling/assert in some functions
If a function has stack objects, and a call, we require an FP. If we
did not initially have any stack objects, and only introduced them
during PrologEpilogInserter for CSR VGPR spills, SILowerSGPRSpills
would end up spilling the FP register as if it were a normal
register. This would result in an assert in a debug build, or
redundant handling of the FP register in a release build.
Try to predict that we will have an FP later, although this is ugly.
Diffstat (limited to 'clang/lib/Frontend/CompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions