diff options
| author | Davide Italiano <davide@freebsd.org> | 2016-04-03 03:39:09 +0000 |
|---|---|---|
| committer | Davide Italiano <davide@freebsd.org> | 2016-04-03 03:39:09 +0000 |
| commit | 842fa53026a505ad89f8f9d996e15cf8c72c05d1 (patch) | |
| tree | 1f975e64dcd3fbd3e35b20571d3f533d4bd81c9a /llvm/lib/Target/X86 | |
| parent | 6bdfe01a202722f643a310e3e6d68f0a1af105e2 (diff) | |
| download | bcm5719-llvm-842fa53026a505ad89f8f9d996e15cf8c72c05d1.tar.gz bcm5719-llvm-842fa53026a505ad89f8f9d996e15cf8c72c05d1.zip | |
[LTO] Implement -disable-verify, which disables bitcode verification.
So, there are some cases when the IR Linker produces a broken
module (which doesn't pass the verifier) and we end up asserting
inside the verifier. I think it's always a bug producing a module
which does not pass the verifier but there are some cases in which
people can live with the broken module (e.g. if only DebugInfo
metadata are broken). The gold plugin has something similar.
This commit is motivated by a situation I found in the
wild. It seems that somebody else discovered it independently
and reported in PR24923.
llvm-svn: 265258
Diffstat (limited to 'llvm/lib/Target/X86')
0 files changed, 0 insertions, 0 deletions
