JDK-8358821 : patch_verified_entry causes problems, use nmethod entry barriers instead
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 25
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2025-06-07
  • Updated: 2025-06-28
  • Resolved: 2025-06-25
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 26
26 b04Fixed
Related Reports
Relates :  
JDK-8357017 - UnexpectedDeoptimizationAllTest.java crashes in C1 during nmethod registration
Description
See JDK-8357017 and JDK-8258229 for examples of problems caused by NativeJump::patch_verified_entry().

Recent JDK releases always use nmethod entry barriers, and already have support for redirecting to SharedRuntime::get_handle_wrong_method_stub().  We can replace verified entry point patching with a permanently armed entry barrier.
Comments
Changeset: cf75f1f9 Branch: master Author: Dean Long <dlong@openjdk.org> Date: 2025-06-25 19:25:34 +0000 URL: https://git.openjdk.org/jdk/commit/cf75f1f9c6d2bc70c7133cb81c73a0ce0946dff9
25-06-2025
A pull request was submitted for review. Branch: master URL: https://git.openjdk.org/jdk/pull/25764 Date: 2025-06-12 01:51:09 +0000
12-06-2025
ILW = same as JDK-8357017 = P3
07-06-2025