summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/process/main.cpp
diff options
context:
space:
mode:
authorAdrian Prantl <aprantl@apple.com>2017-04-24 18:45:59 +0000
committerAdrian Prantl <aprantl@apple.com>2017-04-24 18:45:59 +0000
commit083e6a5b5cd0fe07a9a12deab2c7654413e8334a (patch)
tree44c588034b1f158136ababacda38efcbe63d9851 /lldb/packages/Python/lldbsuite/test/python_api/process/main.cpp
parent285f88d4a3b99dcfef3d5c00eb0db50127ac27e3 (diff)
downloadbcm5719-llvm-083e6a5b5cd0fe07a9a12deab2c7654413e8334a.tar.gz
bcm5719-llvm-083e6a5b5cd0fe07a9a12deab2c7654413e8334a.zip
Don't emit CFI instructions at the end of a function
When functions are terminated by unreachable instructions, the last instruction might trigger a CFI instruction to be generated. However, emitting it would be be illegal since the function (and thus the FDE the CFI is in) has already ended with the previous instruction. Darwin's dwarfdump --verify --eh-frame complains about this and the specification supports this. Relevant bits from the DWARF 5 standard (6.4 Call Frame Information): "[The] address_range [field in an FDE]: The number of bytes of program instructions described by this entry." "Row creation instructions: [...] The new location value is always greater than the current one." The first quotation implies that a CFI cannot describe a target address outside of the enclosing FDE's range. rdar://problem/26244988 Differential Revision: https://reviews.llvm.org/D32246 llvm-svn: 301219
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/process/main.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud