Quentin Colombet 6b53c89899 [X86] Model FAULTING_LOAD_OP as a terminator and branch. ... This operation may branch to the handler block and we do not want it to happen anywhere within the basic block. Moreover, by marking it "terminator and branch" the machine verifier does not wrongly assume (because of AnalyzeBranch not knowing better) the branch is analyzable. Indeed, the target was seeing only the unconditional branch and not the faulting load op and thought it was a simple unconditional block. The machine verifier was complaining because of that and moreover, other optimizations could have done wrong transformation! In the process, simplify the representation of the handler block in the faulting load op. Now, we directly reference the handler block instead of using a label. This has the benefits of: 1. MC knows how to issue a label for a BB, so leave that to it. 2. Accessing the target BB from its label is painful, whereas it is direct from a MBB operand. Note: The 2 bytes offset in implicit-null-check.ll comes from the fact the unconditional jumps are not removed anymore, as the whole terminator sequence is not analyzable anymore. Will fix it in a subsequence commit. llvm-svn: 268327		2016-05-02 22:58:54 +00:00
..
llvm	[X86] Model FAULTING_LOAD_OP as a terminator and branch.	2016-05-02 22:58:54 +00:00
llvm-c	Properly name LLVMSetIsInBounds's argument. NFC	2016-05-01 02:23:14 +00:00