aboutsummaryrefslogtreecommitdiff
path: root/clang/lib/FrontendTool/ExecuteCompilerInvocation.cpp
diff options
context:
space:
mode:
authorMatt Arsenault <Matthew.Arsenault@amd.com>2019-06-03 21:33:22 +0000
committerMatt Arsenault <Matthew.Arsenault@amd.com>2019-06-03 21:33:22 +0000
commit0ceda9fb5c8ff2a21ddcaa2f8a8b969a065b4553 (patch)
treecde31def4c09153b6a2a71778dd2d7b2871d6818 /clang/lib/FrontendTool/ExecuteCompilerInvocation.cpp
parent7500c97ce4bda8a0735b737231b26bde922620f5 (diff)
downloadllvm-0ceda9fb5c8ff2a21ddcaa2f8a8b969a065b4553.zip
llvm-0ceda9fb5c8ff2a21ddcaa2f8a8b969a065b4553.tar.gz
llvm-0ceda9fb5c8ff2a21ddcaa2f8a8b969a065b4553.tar.bz2
AMDGPU: Disable stack realignment for kernels
This is something of a workaround, and the state of stack realignment controls is kind of a mess. Ideally, we would be able to specify the stack is infinitely aligned on entry to a kernel. TargetFrameLowering provides multiple controls which apply at different points. The StackRealignable field is used during SelectionDAG, and for some reason distinct from this hook. StackAlignment is a single field not dependent on the function. It would probably be better to make that dependent on the calling convention, and the maximum value for kernels. Currently this doesn't really change anything, since the frame lowering mostly does its own thing. This helps avoid regressions in a future change which will rely more heavily on hasFP. llvm-svn: 362447
Diffstat (limited to 'clang/lib/FrontendTool/ExecuteCompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions