JDK-8193133 : Assertion failure because 0xDEADDEAD can be in-heap
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 8
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: aarch64
  • Submitted: 2017-12-06
  • Updated: 2021-02-02
  • Resolved: 2017-12-07
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
openjdk8u292 b01Fixed
Related Reports
Relates :  
JDK-8257192 - Integrate AArch64 JIT port into 8u
Description
In the aarch64-port of jdk8u, I sometimes trip an assert because a MacroAssembler::mov() is emitted with an address 0xDEADDEAD, which sometimes can be in-heap, while the assert checks that it is not in-heap. This only affects the jdk8u-branch in aarch64-port/jdk8u. It does not affect jdk9 and jdk9: the assert is not present there.
Comments
URL: https://hg.openjdk.java.net/jdk8u/jdk8u/hotspot/rev/f57189b7648d User: andrew Date: 2021-02-02 05:24:08 +0000
02-02-2021
URL: https://hg.openjdk.java.net/jdk8u/jdk8u-dev/hotspot/rev/f57189b7648d User: andrew Date: 2021-02-01 20:00:27 +0000
01-02-2021
Fixed by this changeset: http://hg.openjdk.java.net/aarch64-port/jdk8u/hotspot/rev/97df73117bbe
07-12-2017