aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Bitcode/Reader/BitcodeReader.cpp
diff options
context:
space:
mode:
authorBill Wendling <isanbard@gmail.com>2009-06-16 04:06:15 +0000
committerBill Wendling <isanbard@gmail.com>2009-06-16 04:06:15 +0000
commitf6c6a7f1b7d2e53f5c5699d6c5703164638e0079 (patch)
treea89677054a6271c2eb2391bdba5629ba38604c23 /llvm/lib/Bitcode/Reader/BitcodeReader.cpp
parent4a172428e5126caa612966ae2bb788b0e14d81ee (diff)
downloadllvm-f6c6a7f1b7d2e53f5c5699d6c5703164638e0079.zip
llvm-f6c6a7f1b7d2e53f5c5699d6c5703164638e0079.tar.gz
llvm-f6c6a7f1b7d2e53f5c5699d6c5703164638e0079.tar.bz2
The DWARF to compact encoding converter assumes that the DW_CFA_def_cfa_offset
comes after the DW_CFA_def_cfa_register, because the CFA is really ESP from the start of the function and only gets an offset when the "subl $xxx,%esp" instruction happens, not the other way around. And reapply r72898: The DWARF unwind info was incorrect. While compiling with `-fomit-frame-pointer', we would lack the DW_CFA_advance_loc information for a lot of function, and then they would be `0'. The linker (at least on Darwin) needs to encode the stack size. In some cases, the stack size is too large to directly encode. So the linker checks to see if there is a "subl $xxx,%esp" instruction at the point where the `DW_CFA_def_cfa_offset' says the pc was. If so, the compact encoding records the offset in the function to where the stack size is embedded. But because the `DW_CFA_advance_loc' instructions are missing, it looks before the function and dies. So, instead of emitting the EH debug label before the stack adjustment operations, emit it afterwards, right before the frame move stuff. llvm-svn: 73465
Diffstat (limited to 'llvm/lib/Bitcode/Reader/BitcodeReader.cpp')
0 files changed, 0 insertions, 0 deletions