-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8361144: Strenghten the Ideal Verification in PhaseIterGVN::verify_Ideal_for by comparing the hash of a node before and after Ideal #26064
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 bmaillard! A progress list of the required criteria for merging this PR into |
❗ This change is not yet ready to be integrated. |
@benoitmaillard 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
|
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.
Have you considered adding a test for this? Is that feasible?
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.
Thanks @benoitmaillard! Definitely an additional check worth doing. I left a couple of inline comments.
Co-authored-by: Damon Fenacci <damon.fenacci@oracle.com>
@galderz I have considered doing it, but there is no known case that triggers the condition. This change was suggested by @eme64 when discussing the related JDK-8359602. |
/contributor add @eme64 |
@benoitmaillard |
This PR adds a node hash comparison after calling
Ideal
inPhaseIterGVN::verify_Ideal_for
to introduce an additional layer of verification for missed optimizations. Previously, we relied on the return value ofIdeal
, which is expected to benullptr
if no transformation was done.By also checking the node's hash before and after
Ideal
, we could catch inconsistencies in the implementation or unintended modifications to the graph. Both of these may indicate missed or incomplete optimizations.Testing
Thank you for reviewing!
Progress
Issue
Reviewers
Contributors
<epeter@openjdk.org>
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/26064/head:pull/26064
$ git checkout pull/26064
Update a local copy of the PR:
$ git checkout pull/26064
$ git pull https://git.openjdk.org/jdk.git pull/26064/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 26064
View PR using the GUI difftool:
$ git pr show -t 26064
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/26064.diff
Using Webrev
Link to Webrev Comment