-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8373724: Assertion failure in TestSignumVector.java with UseAPX #28999
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 jbhateja! A progress list of the required criteria for merging this PR into |
|
@jatin-bhateja 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 34 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 |
|
@jatin-bhateja 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
|
b75d280 to
bc86d54
Compare
|
@jatin-bhateja 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. |
|
@jatin-bhateja Thanks for looking into this. There is a build failure in GHA with the following message: |
| match(Set dst (OrL src1 (LoadL src2))); | ||
| effect(KILL cr); | ||
| flag(PD::Flag_sets_sign_flag, PD::Flag_sets_zero_flag, PD::Flag_sets_parity_flag, PD::Flag_clears_overflow_flag, PD::Flag_clears_carry_flag, PD::Flag_ndd_demotable_commutative); | ||
| flag(PD::Flag_sets_sign_flag, PD::Flag_sets_zero_flag, PD::Flag_sets_parity_flag, PD::Flag_clears_overflow_flag, PD::Flag_clears_carry_flag, PD::Flag_ndd_demotable_opr1, PD::Flag_ndd_demotable_opr2); |
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.
Remove PD::Flag_ndd_demotable_opr2 as the second operand is a memory operand.
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.
We already have a check for memory operands (mapping to multiple input edges) in place, ADLC generates DFA for both direct and flipped versions of the memory patterns. So Flag_ndd_demotable_opr2 will cover the flipped operand case.
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 for the clarification. May be we should then add PD::Flag_ndd_demotable_opr2 to the following as well to be consistent:
xorI_rReg_rReg_mem_ndd
orI_rReg_rReg_mem_ndd
mulI_rReg_rReg_mem_ndd
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 @sviswa7 , comment addressed
sviswa7
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 good to me.
|
/integrate |
Thanks @sviswa7 for your reviews. |
|
Going to push as commit 640343f.
Your commit was automatically rebased without conflicts. |
|
@jatin-bhateja Pushed as commit 640343f. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
|
I will review this changeset now after integration, but, for future reference, please note that HotSpot changes require at least two reviews before integration (see https://openjdk.org/guide/#life-of-a-pr). |
@dlunde I'm planning to backport this to JDK-26. Please let me know when you're finished reviewing as soon as possible, so I can do so. Thanks! |
@missa-prime Will do! |
|
I agree with these changes. Nice that the assert caught this case! I'm running some tests for the changeset over the weekend, for both JDK 26 and JDK 27. I'll report back on Monday, and then you can go ahead with the backport @missa-prime (if no issues show up in testing). |
Existing demotable instruction patterns for negI/L_rReg_ndd have 'src' as their second operand, this leads to an failure during register biasing. Changing the NDD demotion flags names to encode explicit operand position i.e. Flag_ndd_demotable_opr1 and Flag_ndd_demotable_opr2 , splitting commutative flag into seperate new flags and fine tuning assertion checks based on new naming convention fixes the issue.
Failing test test/hotspot/jtreg/compiler/vectorization/TestSignumVector.java passes with the patch.
Kindly review and share your feedback.
Best Regards,
Jatin
PS: Validation performed using Intel SDE 9.58.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/28999/head:pull/28999$ git checkout pull/28999Update a local copy of the PR:
$ git checkout pull/28999$ git pull https://git.openjdk.org/jdk.git pull/28999/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 28999View PR using the GUI difftool:
$ git pr show -t 28999Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/28999.diff
Using Webrev
Link to Webrev Comment