Skip to content

8320682: [AArch64] C1 compilation fails with "Field too big for insn" #3432

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

bulasevich
Copy link

@bulasevich bulasevich commented Apr 3, 2025

This is a backport from openjdk/jdk#16951 to change the NMethodSizeLimit limit to 1MB to avoid the issue:

$ jdk-fastdebug/bin/java -XX:NMethodSizeLimit=10M -version

# A fatal error has been detected by the Java Runtime Environment:
#
#  Internal Error (/jdk17u-dev/src/hotspot/cpu/aarch64/assembler_aarch64.hpp:267), pid=334227, tid=334241
#  guarantee(chk == -1 || chk == 0) failed: Field too big for insn

The minor merge conflicts have been resolved:

  • Copyright year
  • TestC1Globals.java in the original fix was an update of an already existing file. Here is is just a new file

Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue
  • JDK-8320682 needs maintainer approval

Issue

  • JDK-8320682: [AArch64] C1 compilation fails with "Field too big for insn" (Bug - P3 - Approved)

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk17u-dev.git pull/3432/head:pull/3432
$ git checkout pull/3432

Update a local copy of the PR:
$ git checkout pull/3432
$ git pull https://git.openjdk.org/jdk17u-dev.git pull/3432/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 3432

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk17u-dev/pull/3432.diff

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Apr 3, 2025

👋 Welcome back bulasevich! 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
Copy link

openjdk bot commented Apr 3, 2025

@bulasevich 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:

8320682: [AArch64] C1 compilation fails with "Field too big for insn"

Reviewed-by: phh

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 59 new commits pushed to the master branch:

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. Possible candidates are the reviewers of this PR (@phohensee) but any other Committer may sponsor as well.

➡️ 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 openjdk bot changed the title Backport JDK-8320682 8320682: [AArch64] C1 compilation fails with "Field too big for insn" Apr 3, 2025
@openjdk
Copy link

openjdk bot commented Apr 3, 2025

This backport pull request has now been updated with the original issue, but not the original commit. If you have the original commit hash, please update the pull request title with Backport <hash>.

@openjdk openjdk bot added the backport label Apr 3, 2025
@bulasevich bulasevich marked this pull request as ready for review April 3, 2025 14:09
@openjdk openjdk bot added the rfr Pull request is ready for review label Apr 3, 2025
@mlbridge
Copy link

mlbridge bot commented Apr 3, 2025

Webrevs

@openjdk
Copy link

openjdk bot commented Apr 10, 2025

⚠️ @bulasevich This change is now ready for you to apply for maintainer approval. This can be done directly in each associated issue or by using the /approval command.

@openjdk openjdk bot added the approval label Apr 14, 2025
@bulasevich
Copy link
Author

/approval request
The issue is applicable to jdk17u as well. The change is safe and well tested.

@openjdk
Copy link

openjdk bot commented Apr 14, 2025

@bulasevich
8320682: The approval request has been created successfully.

@openjdk openjdk bot added ready Pull request is ready to be integrated and removed approval labels Apr 15, 2025
@bulasevich
Copy link
Author

/integrate

@openjdk openjdk bot added the sponsor Pull request is ready to be sponsored label Apr 15, 2025
@openjdk
Copy link

openjdk bot commented Apr 15, 2025

@bulasevich
Your change (at version 3ecde24) is now ready to be sponsored by a Committer.

@phohensee
Copy link
Member

/sponsor

@openjdk
Copy link

openjdk bot commented Apr 15, 2025

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

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Apr 15, 2025
@openjdk openjdk bot closed this Apr 15, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review sponsor Pull request is ready to be sponsored labels Apr 15, 2025
@openjdk
Copy link

openjdk bot commented Apr 15, 2025

@phohensee @bulasevich Pushed as commit bec2e07.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport integrated Pull request has been integrated
Development

Successfully merging this pull request may close these issues.

2 participants