Date: Mon, 19 Sep 2022 14:45:28 +0000 From: bugzilla-noreply@freebsd.org To: java@FreeBSD.org Subject: [Bug 264065] java/openjdk8: Crashes on aarch64 when built with clang13: # Internal Error (assembler_aarch64.hpp:237) .. guarantee(val < (1U << nbits)) failed: Field too big for insn Message-ID: <bug-264065-8522-oRhm1F0XGK@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-264065-8522@https.bugs.freebsd.org/bugzilla/> References: <bug-264065-8522@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D264065 --- Comment #31 from Dimitry Andric <dim@FreeBSD.org> --- (In reply to Ronald Klop from comment #30) > The tijmp failure I mentioned in comment #23 was build with this openjdk8: >=20 > http://ampere2.nyi.freebsd.org/data/main-arm64-default/p23c196516a66_s45a= d955714/logs/openjdk8-8.342.07.1.log >=20 > That openjdk is build without bringing in llvm12. Yes, I can see it in the log. It is building 8.342.07.1 with the system cla= ng 14.0.5. > So did the fixes really go into this openjdk8? Yes, I have verified that even before my changes, when 8.342.07.1 was committed, the two fixes are applied in the upstream sources. > Or why else do they not work? The "build with clang 13" fix works, since it does build with clang >=3D 13= (in this case, 14.0.5). The "aarch64 assertion failure" fix does not seem to work, and that is the = big mystery. This fix came verbatim from openjdk8 upstream, but maybe it does n= ot cover all situations. It is hard to tell without access to a full aarch64 debugging environment and a reproduction case. The upstream bug for this, https://bugs.openjdk.org/browse/JDK-8247766, does have a bunch of duplicates, but most of them are for backports to older JDK branches. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-264065-8522-oRhm1F0XGK>