RFR(S): 8064703: crash running specjvm98's javac following 8060252

Vladimir Kozlov vladimir.kozlov at oracle.com
Mon Dec 1 17:28:08 UTC 2014

null_check() will "confuse" tightly_coupled_allocation(). Why you moved it?

Vladimir k

On 12/1/14 4:28 AM, Roland Westrelin wrote:
> http://cr.openjdk.java.net/~roland/8064703/webrev.00/
> If an arraycopy is used to initialize a just allocated array, when possible we skip the array initialization and let arraycopy do the initialization. If an uncommon trap is triggered after the allocation and before the arraycopy, then an uninitialized array can escape the compiled method to the interpreter. This is fixed by making the uncommon trap resume execution at the allocation rather than the arraycopy and redo the allocation (Vladimir’s suggestion).
> Roland.

More information about the hotspot-compiler-dev mailing list