Duncan P. N. Exon Smith cf8b959e8d BitcodeReader: Fix some BlockAddress forward reference corner cases ... `BlockAddress`es are interesting in that they can reference basic blocks from *outside* the block's function. Since basic blocks are not global values, this presents particular challenges for lazy parsing. One corner case was found in PR11677 and fixed in r147425. In that case, a global variable references a block address. It's necessary to load the relevant function to resolve the forward reference before doing anything with the module. By inspection, I found (and have fixed here) two other cases: - An instruction from one function references a block address from another function, and only the first function is lazily loaded. I fixed this the same way as PR11677: by eagerly loading the referenced function. - A function whose block address is taken is dematerialized, leaving invalid references to it. I fixed this by refusing to dematerialize functions whose block addresses are taken (if you have to load it, you can't unload it). git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@214559 91177308-0d34-0410-b5e6-96231b3b80d8		2014-08-01 21:11:34 +00:00
..
llvm	BitcodeReader: Fix some BlockAddress forward reference corner cases	2014-08-01 21:11:34 +00:00
llvm-c	Remove lto_codegen_set_attr.	2014-08-01 14:57:05 +00:00