diff options
| author | Adrian Prantl <aprantl@apple.com> | 2016-05-06 19:26:47 +0000 |
|---|---|---|
| committer | Adrian Prantl <aprantl@apple.com> | 2016-05-06 19:26:47 +0000 |
| commit | 541a9c58d405842eb7fc175b88e71bcc469b13fd (patch) | |
| tree | ef72116f2c1076798ff9d4d1a428cc0e316f8bb9 /llvm/lib/IR/ConstantFold.h | |
| parent | de87e5f87565b78706e0d0289632ea8ccba4f211 (diff) | |
| download | bcm5719-llvm-541a9c58d405842eb7fc175b88e71bcc469b13fd.tar.gz bcm5719-llvm-541a9c58d405842eb7fc175b88e71bcc469b13fd.zip | |
Refactor the Verifier so it can diagnose IR validation errors and debug
info metadata errors separately. (NFC)
This patch refactors the Verifier so it can diagnose IR validation errors
and debug info metadata errors separately.
The motivation behind this change is that broken (or outdated) debug info
can be "recovered" from by stripping the debug info.
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.
http://reviews.llvm.org/D19986
rdar://problem/25818489
llvm-svn: 268778
Diffstat (limited to 'llvm/lib/IR/ConstantFold.h')
0 files changed, 0 insertions, 0 deletions
