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
8273933: [TESTBUG] Test must run without preallocated exceptions #5560
8273933: [TESTBUG] Test must run without preallocated exceptions #5560
Conversation
|
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.
That sounds reasonable. You should also update the copyright year.
@neliasso This change now passes all automated pre-integration checks. 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 124 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.
|
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.
Just wondering, why does -XX:-OmitStackTraceInFastThrow
not help?
Mailing list message from Nils Eliasson on hotspot-compiler-dev: On 2021-09-20 08:11, Tobias Hartmann wrote:
That flag should work too - both are needed: ? if (treat_throw_as_hot Where treat_throw_as_hot is dependent on the ProfileTraps flag and 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 good to me!
I changed the patch to disable OmitStackTraceInFastThrow instead of ProfileTraps, after a suggestion from @TobiHartmann. Disabling ProfileTraps has more side effects - so just disabling OmitStackTraceInFastThrow should keeps the test environment closer to default. |
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!
@TobiHartmann and @chhagedorn - Thanks for the review! |
/integrate |
Going to push as commit 4d95a5d.
Your commit was automatically rebased without conflicts. |
Executing vmTestbase/jit/t/t105/t105.java with the fix for (JDK-8273277) makes the test fail when run with the following arguments:
-XX:+TieredCompilation
-XX:Tier0BackedgeNotifyFreqLog=0
-XX:Tier2BackedgeNotifyFreqLog=0
-XX:Tier3BackedgeNotifyFreqLog=0
-XX:Tier2BackEdgeThreshold=1
-XX:Tier3BackEdgeThreshold=1
-XX:Tier4BackEdgeThreshold=1
-Xbatch
The problem is that the tests expects a detailed message from ArrayIndexOutOfBoundsException, but this test will trigger the optimization that reuses preallocated exceptions that have an empty detailed exceptions.
It is wrong for the test to assume exceptions messages.
Solution disable preallocated exceptions with the flag -XX:-ProfileTraps.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/5560/head:pull/5560
$ git checkout pull/5560
Update a local copy of the PR:
$ git checkout pull/5560
$ git pull https://git.openjdk.java.net/jdk pull/5560/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 5560
View PR using the GUI difftool:
$ git pr show -t 5560
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/5560.diff