4 Commits

Author	SHA1	Message	Date
Bill Wendling	1da5257929	If the block that we're threading through is jumped to by an indirect branch, ... then we don't want to set the destination in the indirect branch to the destination. This is because the indirect branch needs its destinations to have had their block addresses taken. This isn't so of the new critical edge that's split during this process. If it turns out that the destination block has only one predecessor, and that being a BB with an indirect branch, then it won't be marked as 'used' and may be removed. PR10072 llvm-svn: 132638	2011-06-04 09:42:04 +00:00
Frits van Bommel	31cf7b99f9	Teach SimplifyCFG to turn ... (indirectbr (select cond, blockaddress(@fn, BlockA), blockaddress(@fn, BlockB))) into (br cond, BlockA, BlockB). llvm-svn: 120943	2010-12-05 18:29:03 +00:00
Dan Gohman	9178d0792f	Instead, teach SimplifyCFG to trim non-address-taken blocks from ... indirectbr destination lists. llvm-svn: 111122	2010-08-16 14:41:14 +00:00
Dan Gohman	d04a608a73	Teach SimplifyCFG how to simplify indirectbr instructions. ... - Eliminate redundant successors. - Convert an indirectbr with one successor into a direct branch. Also, generalize SimplifyCFG to be able to be run on a function entry block. It knows quite a few simplifications which are applicable to the entry block, and it only needs a few checks to avoid trouble with the entry block. llvm-svn: 111060	2010-08-14 00:29:42 +00:00