-
Notifications
You must be signed in to change notification settings - Fork 20
8370405: C2: mismatched store from MergeStores wrongly scalarized in allocation elimination #10
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
Conversation
|
👋 Welcome back shade! A progress list of the required criteria for merging this PR into |
|
@shipilev 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: 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 19 new commits pushed to the
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. ➡️ To integrate this PR with the above commit message to the |
|
This backport pull request has now been updated with issue from the original commit. |
|
The parent pull request that this pull request depends on has now been integrated and the target branch of this pull request has been updated. This means that changes from the dependent pull request can start to show up as belonging to this pull request, which may be confusing for reviewers. To remedy this situation, simply merge the latest changes from the new target branch into this pull request by running commands similar to these in the local repository for your personal fork: git checkout JDK-8370405-c2-mismatched-store
git fetch https://git.openjdk.org/jdk25u-dev.git master
git merge FETCH_HEAD
# if there are conflicts, follow the instructions given by git merge
git commit -m "Merge master"
git push |
0b6efa6 to
be9f05c
Compare
|
@shipilev Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information. |
|
|
|
/approval request Fixes JDK 23 regression that will show up on JDK 25 as correctness bug. The fix is fairly new, but it is simple and conservative: blocks scalar replacement when mismatches stores are detected. New regression test fails without the fix, passes with it. All other tests pass. Risk is medium: touches C2, but in fairly conservative manner. |
|
Push approval granted. /integrate |
|
Going to push as commit d1b5b9a.
Your commit was automatically rebased without conflicts. |
Fixes JDK 21 -> JDK 25 regression in C2 that can lead to miscompilation. There is a regression test that captures the failure.
Additional testing:
allProgress
Issue
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk25u-dev.git pull/10/head:pull/10$ git checkout pull/10Update a local copy of the PR:
$ git checkout pull/10$ git pull https://git.openjdk.org/jdk25u-dev.git pull/10/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 10View PR using the GUI difftool:
$ git pr show -t 10Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk25u-dev/pull/10.diff
Using Webrev
Link to Webrev Comment