-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8371881: C2: Fix potential SEGV in VTransformReductionVectorNode tracing #28323
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
base: master
Are you sure you want to change the base?
Conversation
|
👋 Welcome back vish-chan! A progress list of the required criteria for merging this PR into |
|
@vish-chan 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 27 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. 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 (@shipilev, @eme64) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
|
@vish-chan 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. |
Webrevs
|
shipilev
left a comment
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 fine, but @eme64 should take a look as well.
/reviewers 2
eme64
left a comment
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.
@vish-chan @shipilev thanks for working on this!
Looks reasonable to me :)
Co-authored-by: Aleksey Shipilëv <[email protected]>
|
@eme64 I'm not sure but your approval might be required. |
eme64
left a comment
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.
Sorry, missed the swap from "Comment" to "Approve" 🙈
|
/integrate |
|
@vish-chan |
This PR fixes a potential SEGV and removes dead code:
• Fix: Prevent potential SEGV in VTransformReductionVectorNode - [from @shipilev] This fixes a crash in diagnostic code when isa_ReductionVector() unexpectedly returns nullptr. While this indicates the graph is already corrupted, the additional crash in
TRACE_OPTIMIZEmakes debugging harder. The fix adds defensive null checking to prevent the diagnostic crash and improve error handling.• Cleanup: Remove unused first_red variable
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/28323/head:pull/28323$ git checkout pull/28323Update a local copy of the PR:
$ git checkout pull/28323$ git pull https://git.openjdk.org/jdk.git pull/28323/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 28323View PR using the GUI difftool:
$ git pr show -t 28323Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/28323.diff
Using Webrev
Link to Webrev Comment