[llvm-commits] add nounwind flag to BasicBlock
nicholas at mxc.ca
Wed Mar 12 02:01:47 CDT 2008
This adds the nounwind flag (as seen on CallInst and Function) to basic
Why not just leave the unwind-dest null? That could mean one of two
things, either that an unwind should propagate up or that the basic
block will never unwind. In the second case, simplifycfg could merge it
with another BB that has an 'unwinds to', but in the first case merging
them would change the actual behaviour of the code.
Like the nounwind flag on call and functions, this flag can be computed
by looking at the instructions inside the block, we just don't want to
do that computation every time. This just memoizes that analysis for
Please review this patch.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 6988 bytes
Desc: not available
Url : http://lists.cs.uiuc.edu/pipermail/llvm-commits/attachments/20080312/28d10ef1/attachment.bin
More information about the llvm-commits