Request for reviews (M): 7059047: EA: can't find initializing store with several CheckCastPP

Tom Rodriguez tom.rodriguez at
Tue Nov 1 12:45:51 PDT 2011

I'm not sure I follow the distinction that's being made with ControlEscape, or ArgEscape for that matter.  They seem to be about what optimizations we can do on an object more than whether they are escaping or not, which makes the naming confusing.  Or am I misunderstand what's happening?  Is this how they would be translated?

NoEscape      == ScalarReplaceable
ControlEscape == NonEscaping
ArgEscape     == LocallyEscaping
GlobalEscape  == GlobalEcaping

Would be it be possible to come up with more descriptive names for these states?

Why is has_non_escaping_obj assigned to twice?

// mark all nodes reachable from ArgEscape nodes
!   has_non_escaping_obj = propagate_escape_state(&cg_worklist, &worklist, PointsToNode::ArgEscape);

!   // mark all nodes reachable from ControlEscape nodes
!   has_non_escaping_obj = propagate_escape_state(&cg_worklist, &worklist, PointsToNode::ControlEscape);

Should the second one be |=?

Do we eliminate locking on ControlEscape objects?


On Nov 1, 2011, at 11:41 AM, Vladimir Kozlov wrote:

> 7059047: EA: can't find initializing store with several CheckCastPP
> Added new escape state: ControlEscape. Use it instead of ArgEscape and (NoEscape && !_scalar_replaceable) in cases where not escaped objects can't be scalar replaced because of flow-insensitive analysis limitations. It is preparation for  7105605 changes.
> Split adjust_escape_state() method into two. New find_init_values() method is used to find fields initializing values for not escaped allocations. It is called before deferred edges are removed since it affects results. adjust_escape_state() now is called after all deferred edges are removed to get correct results.
> Factored out escape state propagation code into new method propagate_escape_state().
> Removed methods is_scalar_replaceable() and hidden_alias() which are not used and corresponding fields in PointsToNode (which will reduce used memory).
> Tested with CTW, jtreg, NSK, refworkload.
> Thanks,
> Vladimir

More information about the hotspot-compiler-dev mailing list