RFR (L): 7153771: array bound check elimination for c1

Roland Westrelin roland.westrelin at oracle.com
Fri Mar 15 09:58:16 PDT 2013

> Why not use Deoptimization::Reason_range_check? You use Reason_none.

Actually there's a reason for this: c1 in this change records when there's a predicate failure caused by an optimistic optimization. An optimistic optimization can be loop invariant code motion, so it's not always related to range check elimination.


More information about the hotspot-compiler-dev mailing list