Philip Reames 5b39acd111 [LICM] Compute a must execute property for the prefix of the header as we go ...

Computing this property within the existing walk ensures that the cost is linear with the size of the block. If we did this from within isGuaranteedToExecute, it would be quadratic without some very fancy caching.

This allows us to reliably catch a hoistable instruction within a header which may throw at some point *after* our hoistable instruction. It doesn't do anything for non-header cases, but given how common single block loops are, this seems very worthwhile.

llvm-svn: 331557

2018-05-04 21:35:00 +00:00

62 KiB

Raw Blame History

View Raw