JDK-8209684 : Intrinsics that assume some input non null should use GraphKit::must_be_not_null()
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 9,10,11,12
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2018-08-20
  • Updated: 2020-04-22
  • Resolved: 2018-08-22
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.
JDK 11 JDK 12
11.0.5Fixed 12 b09Fixed
Description
A number of intrinsics omit null checks on inputs that are known to be not null. They should use GraphKit::must_be_not_null() instead.
Comments
Fix Request (11u) This is needed for Shenandoah to work reliably in 11u; otherwise compiler optimizations barf. Patch applies cleanly to 11u, passes tier1, tier2 test suite.
30-07-2019
Testing passed clean. Fix is ready for push.
21-08-2018
ILW = Crash during C2 compilation because not-null assumption is not explicit in IR, with Shenandoah GC, disable affected intrinsic or use different GC = HLL = P4
20-08-2018