Array not zeroed on creation

[Nils Eliasson]

The bug reproduces with a fill or a corresponding zeroing for loop. But 
not without. So the bug is that there should be a check of uses between 
the allocation and the fill (or that the check is incomplete).

//Nils

Vitaly Davidovich skrev 2012-09-07 15:24:
>
> Dan,
>
> I've cc'd compiler dev and removed hotspot dev as this looks like a 
> compiler issue.  Hope you don't mind.
>
> My hunch is that the Arrays.fill() is tripping this up - is it 
> reproducable if fill() is removed?
>
> Sent from my phone
>
> On Sep 7, 2012 8:39 AM, "Dan Hicks" <danhicks at fastmail.fm 
> <mailto:danhicks at fastmail.fm>> wrote:
>
>     This bug has come to my attention:
>     http://stackoverflow.com/questions/12317668/java-int-array-initializes-with-nonzero-elements
>
>     Basically there is a reproducible (by several people) situation
>     where a new int array is not zeroed.  The author reports the error
>     is reproducible on HotSpot 64-bit server VM, Java version from
>     1.7.0_04 to 1.7.0_10 on Gentoo Linux, Debian Linux (both kernel
>     3.0 version) and MacOS Lion.  (Not tested on 32-bit or Windows.)
>
>     Reportedly bug7196857 has been filed with Oracle.
>
>     -- 
>     Dan Hicks
>     Nothing makes us so lonely as our secrets.  --Paul Tournier
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/attachments/20120907/32434b64/attachment.html