-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
8299658: C1 compilation crashes in LinearScan::resolve_exception_edge #15348
Conversation
👋 Welcome back mdoerr! A progress list of the required criteria for merging this PR into |
@TheRealMDoerr The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That looks reasonable to me.
@TheRealMDoerr 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 74 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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks reasonable.
For sure you can't continue if from_value isn't a valid operand.
Thanks for the reviews! I think it's time for verifying it in the field. Let's ship it with an EA build. |
Going to push as commit cf2d33c.
Your commit was automatically rebased without conflicts. |
@TheRealMDoerr Pushed as commit cf2d33c. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
This is a quick fix for the C1 problem described in the JBS issue.
When we find an illegal operand (modelled by nullptr) while resolving an exception edge we can propagate this state to the phi function and skip the edge.
If somebody finds a better way to propagate the "illegal" state to the phi function, I can change or close this PR.
Please review. A nice regression test would be a good thing, but probably not easy to write.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/15348/head:pull/15348
$ git checkout pull/15348
Update a local copy of the PR:
$ git checkout pull/15348
$ git pull https://git.openjdk.org/jdk.git pull/15348/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 15348
View PR using the GUI difftool:
$ git pr show -t 15348
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/15348.diff
Webrev
Link to Webrev Comment