diff options
| author | Michael Liao <michael.liao@intel.com> | 2014-12-04 00:56:38 +0000 |
|---|---|---|
| committer | Michael Liao <michael.liao@intel.com> | 2014-12-04 00:56:38 +0000 |
| commit | d8faa61b2033fedb097905e72e7dfaa57e8c3368 (patch) | |
| tree | 2656ee02386a3d10134ef8f991c833c133faf4c8 /llvm/lib/Object/MachOObjectFile.cpp | |
| parent | 029042b278c2349b2c35d7b8e53dabfda57a2d3c (diff) | |
| download | llvm-d8faa61b2033fedb097905e72e7dfaa57e8c3368.zip llvm-d8faa61b2033fedb097905e72e7dfaa57e8c3368.tar.gz llvm-d8faa61b2033fedb097905e72e7dfaa57e8c3368.tar.bz2 | |
[X86] Restore X86 base pointer after call to llvm.eh.sjlj.setjmp
Commit on
- This patch fixes the bug described in
http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-May/062343.html
The fix allocates an extra slot just below the GPRs and stores the base pointer
there. This is done only for functions containing llvm.eh.sjlj.setjmp that also
need a base pointer. Because code containing llvm.eh.sjlj.setjmp saves all of
the callee-save GPRs in the prologue, the offset to the extra slot can be
computed before prologue generation runs.
Impact at run-time on affected functions is::
- One extra store in the prologue, The store saves the base pointer.
- One extra load after a llvm.eh.sjlj.setjmp. The load restores the base pointer.
Because the extra slot is just above a gap between frame-pointer-relative and
base-pointer-relative chunks of memory, there is no impact on other offset
calculations other than ensuring there is room for the extra slot.
http://reviews.llvm.org/D6388
Patch by Arch Robison <arch.robison@intel.com>
llvm-svn: 223329
Diffstat (limited to 'llvm/lib/Object/MachOObjectFile.cpp')
0 files changed, 0 insertions, 0 deletions