summaryrefslogtreecommitdiffstats
path: root/llvm/lib/ExecutionEngine/RuntimeDyld
diff options
context:
space:
mode:
authorManman Ren <mren@apple.com>2012-10-12 23:39:43 +0000
committerManman Ren <mren@apple.com>2012-10-12 23:39:43 +0000
commit7e48b252e74a83ba161ffea8d9bdd6a2a0b56c5f (patch)
treeedd303416f9a192287a8735af90dadc0b8ce7296 /llvm/lib/ExecutionEngine/RuntimeDyld
parentea561dcffb7f49b339af2ed90efcfb87f56b9f74 (diff)
downloadbcm5719-llvm-7e48b252e74a83ba161ffea8d9bdd6a2a0b56c5f.tar.gz
bcm5719-llvm-7e48b252e74a83ba161ffea8d9bdd6a2a0b56c5f.zip
ARM: tail-call inside a function where part of a byval argument is on caller's
local frame causes problem. For example: void f(StructToPass s) { g(&s, sizeof(s)); } will cause problem with tail-call since part of s is passed via registers and saved in f's local frame. When g tries to access s, part of s may be corrupted since f's local frame is popped out before the tail-call. The current fix is to disable tail-call if getVarArgsRegSaveSize is not 0 for the caller. This is a conservative approach, if we can prove the address of s or part of s is not taken and passed to g, it should be okay to perform tail-call. rdar://12442472 llvm-svn: 165853
Diffstat (limited to 'llvm/lib/ExecutionEngine/RuntimeDyld')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud