diff options
| author | Adrian Prantl <aprantl@apple.com> | 2016-05-09 19:57:15 +0000 |
|---|---|---|
| committer | Adrian Prantl <aprantl@apple.com> | 2016-05-09 19:57:15 +0000 |
| commit | fe7a38245303a221798837bfd1ecdbb5c6af9e49 (patch) | |
| tree | c7c5b49eb5dfc34fd2f4bed2fcebd939b887a83f /lldb/packages/Python/lldbsuite/test/python_api/debugger/TestDebuggerAPI.py | |
| parent | e5e4713a56835d088254770c5e8b77dd6bde83c9 (diff) | |
| download | bcm5719-llvm-fe7a38245303a221798837bfd1ecdbb5c6af9e49.tar.gz bcm5719-llvm-fe7a38245303a221798837bfd1ecdbb5c6af9e49.zip | |
Allow the LTO code generator to strip invalid debug info from the input.
This patch introduces a new option -lto-strip-invalid-debug-info, which
drops malformed debug info from the input.
The problem I'm trying to solve with this sequence of patches is that
historically we've done a really bad job at verifying debug info. We want
to be able to make the verifier stricter without having to worry about
breaking bitcode compatibility with existing producers. For example, we
don't necessarily want IR produced by an older version of clang to be
rejected by an LTO link just because of malformed debug info, and rather
provide an option to strip it. Note that merely outdated (but well-formed)
debug info would continue to be auto-upgraded in this scenario.
rdar://problem/25818489
http://reviews.llvm.org/D19987
This reapplies 268936 with a test case fix for Linux (-exported-symbol foo)
llvm-svn: 268965
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/debugger/TestDebuggerAPI.py')
0 files changed, 0 insertions, 0 deletions
