summaryrefslogtreecommitdiffstats
path: root/llvm/test/Linker/broken.ll
Commit message (Collapse)AuthorAgeFilesLines
* Don't verify inputs to the Linker if ODR merging.Rafael Espindola2016-06-291-1/+1
| | | | | | | | | | | | | | | | | | This fixes pr28072. The point, as Duncan pointed out, is that the file is already partially linked by just reading it. Long term I think the solution is to make metadata owned by the module and then the linker will lazily read it and be in charge of all the linking. Running a verifier in each input will defeat the lazy loading, but will be legal. Right now we are at the unfortunate position that to support odr merging we cannot verify the inputs, which mildly annoying (see test update). llvm-svn: 274148
* tools: Unify how verifyModule() is calledDuncan P. N. Exon Smith2015-03-311-1/+1
| | | | | | | | | Unify the error messages for the various tools when `verifyModule()` fails on an input module. The "brave new way" is: lltool: path/to/input.ll: error: input module is broken! llvm-svn: 233667
* llvm-link: Verify input modulesDuncan P. N. Exon Smith2015-03-251-0/+8
Otherwise, broken input modules can cause assertions. I've updated two of the testcases that started failing (modules that had `Require` flags but didn't meet their own requirements), but Rafael and I decided that test/Linker/2011-08-22-ResolveAlias.ll should just be deleted outright -- it's a leftover of the way llvm-gcc used to implement weakref. llvm-svn: 233229
OpenPOWER on IntegriCloud