summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/expression_command/call-function/main.cpp
diff options
context:
space:
mode:
authorHal Finkel <hfinkel@anl.gov>2016-08-31 00:52:03 +0000
committerHal Finkel <hfinkel@anl.gov>2016-08-31 00:52:03 +0000
commit97a189c7169cfaf927c32b3870675ae161970e09 (patch)
tree707bff6ac017b683897648b167de71564726b7aa /lldb/packages/Python/lldbsuite/test/expression_command/call-function/main.cpp
parent3766d106c811117325e6a7b6054cfa351c61aa5e (diff)
downloadbcm5719-llvm-97a189c7169cfaf927c32b3870675ae161970e09.tar.gz
bcm5719-llvm-97a189c7169cfaf927c32b3870675ae161970e09.zip
[PowerPC] Don't spill the frame pointer twice
When a function contains something, such as inline asm, which explicitly clobbers the register used as the frame pointer, don't spill it twice. If we need a frame pointer, it will be saved/restored in the prologue/epilogue code. Explicitly spilling it again will reuse the same spill slot used by the prologue/epilogue code, thus clobbering the saved value. The same applies to the base-pointer or PIC-base register. Partially fixes PR26856. Thanks to Ulrich for his analysis and the small inline-asm reproducer. llvm-svn: 280188
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/call-function/main.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud