8365265: x86 short forward jump exceeds 8-bit offset in methodHandles_x86.cpp when using Intel APX

[vamsi-parasa]

Hi all,

This pull request contains a backport of commit 38a26141 from the openjdk/jdk repository.

The commit being backported was authored by Srinivas Vamsi Parasa on 13 Aug 2025 and was reviewed by Aleksey Shipilev, Jatin Bhateja and Andrew Haley.

Thanks!

---

Progress

• Change must not contain extraneous whitespace
• JDK-8365265 needs maintainer approval
• Commit message must refer to an issue

Issue

• JDK-8365265: x86 short forward jump exceeds 8-bit offset in methodHandles_x86.cpp when using Intel APX (Bug - P3 - Approved)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk25u.git pull/261/head:pull/261
$ git checkout pull/261

Update a local copy of the PR:
$ git checkout pull/261
$ git pull https://git.openjdk.org/jdk25u.git pull/261/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 261

View PR using the GUI difftool:
$ git pr show -t 261

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk25u/pull/261.diff

Using Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back sparasa! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

@vamsi-parasa This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8365265: x86 short forward jump exceeds 8-bit offset in methodHandles_x86.cpp when using Intel APX

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 6 new commits pushed to the master branch:

• 954430c: 8345810: Custom launchers must be linked with pthread to avoid dynamic linker issues
• affde09: 8362282: runtime/logging/StressAsyncUL.java failed with exitValue = 134
• 73eb1d7: 8357141: Update to use jtreg 7.5.2
• ... and 3 more: https://git.openjdk.org/jdk25u/compare/ee89511ee1dbb905df6a4d77bbb785c3863e3c5f...master

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

[openjdk]

This backport pull request has now been updated with issue from the original commit.

[mlbridge]

Webrevs

• 00: Full (0b2c2534)

[vamsi-parasa]

/integrate

[openjdk]

@vamsi-parasa
Your change (at version 0b2c253) is now ready to be sponsored by a Committer.

[shipilev]

/sponsor

[openjdk]

Going to push as commit ee6a040.
Since your change was applied there have been 6 commits pushed to the master branch:

• 954430c: 8345810: Custom launchers must be linked with pthread to avoid dynamic linker issues
• affde09: 8362282: runtime/logging/StressAsyncUL.java failed with exitValue = 134
• 73eb1d7: 8357141: Update to use jtreg 7.5.2
• ... and 3 more: https://git.openjdk.org/jdk25u/compare/ee89511ee1dbb905df6a4d77bbb785c3863e3c5f...master

Your commit was automatically rebased without conflicts.

[openjdk]

@shipilev @vamsi-parasa Pushed as commit ee6a040.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

[vamsi-parasa]

@shipilev @vamsi-parasa Pushed as commit ee6a040.

Thank you Aleksey!