[aarch64-port-dev ] hg: aarch64-port/jdk8u/hotspot: 8157306: Random infrequent null pointer exceptions in javac

[Andrew Hughes]

----- Original Message -----
> On 09/08/16 01:07, Andrew Hughes wrote:
> > I thought only AArch64-specific patches were to be added to this
> > tree, outside of merges with upstream jdk8u/jdk8u?  This isn't
> > AArch64-specific and should go to jdk8u-dev.
> 
> It *is* AArch64-specific in the sense that it's a bug which has only
> ever been seen on AArch64.  I did think for some time about making it
> #ifdef AARCH64, but if it affects any non-AArch64 target it will only
> fix a bug.  Given that this bug has never been observed on any
> non-AArch64 target, I'm not going to report it against jdk8.
> 
> Andrew.
> 

Ok, but this does result in a deviation from upstream for other
architectures using this tree.

I don't think this is a bad thing, but I would appreciate some clarification
on what is appropriate for this tree. As a case in point, Zero is broken
(crashes on -version) in this tree and will remain so until we pick up
8154210 from 8u112, probably in early November after the October CPU. Is
this to be expected, or should we consider including such fixes which
cause major runtime crashes?

$ /mnt/builder/chailatte/images/j2sdk-image/bin/java -version
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  Internal Error (os_linux_zero.cpp:254), pid=7141, tid=0x00007f5cd844b700
#  fatal error: caught unhandled signal 11
#
# JRE version:  (8.0) (build )
# Java VM: OpenJDK 64-Bit Zero VM (25.71-b00 interpreted mode linux-amd64 )

Thanks,
-- 
Andrew :)

Senior Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)

PGP Key: ed25519/35964222 (hkp://keys.gnupg.net)
Fingerprint = 5132 579D D154 0ED2 3E04  C5A0 CFDA 0F9B 3596 4222