-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
8273895: compiler/ciReplay/TestVMNoCompLevel.java fails due to wrong data size with TieredStopAtLevel=2,3 #5548
Conversation
…data size with TieredStopAtLevel=2,3
👋 Welcome back chagedorn! A progress list of the required criteria for merging this PR into |
@chhagedorn 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.
Good.
@chhagedorn 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 18 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 |
Thanks Vladimir and Dean for your reviews! |
/integrate |
Going to push as commit a561eac.
Your commit was automatically rebased without conflicts. |
@chhagedorn Pushed as commit a561eac. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
TestVMNoCompLevel.java
is first letting the VM crash with-XX:CICrashAt=1
(methodTestMain::test()
), then removes the compilation level information from the compile entry in the replay file and then replay compiles with and without tiered compilation. When running the replay file with tiered compilation off, it results in the assertion failure.When letting the VM crash with
-XX:TieredStopAtLevel=2,3
(C1 only), we get a slightly different MDO size forTestMain::test()
compared to letting the VM crash with-XX:-TieredCompilation
(C2 only). The C1 reported MDO forTestMain::test()
is slightly smaller than the C2 MDO. The reason for that can be traced back to JDK-8251462 which changed this code inis_speculative_trap_bytecode()
. This now only returns true if C2 is enabled.is_speculative_trap_bytecode()
is called when initializing an MDO here:jdk/src/hotspot/share/oops/methodData.cpp
Line 1235 in 2ef6871
If C2 is enabled, then we reserve some extra data space for trap data. But when running with C1 only, this is no longer done since JDK-8251462, so we allocate no extra data space in the MDO for the crashing method
TestMain::test()
.When now crashing first with
-XX:TieredStopAtLevel=2,3
, we collect an MDO without the extra trap data for the replay file. But when replay compiling afterwards with-XX:-TieredCompilation
, we try to compile it with C2 (we removed the compilation level from the compile entry). We initialize the MDO ofTestMain::test()
with the extra trap data which is a mismatch to the reported C1 only MDO without extra trap data and we fail with the assertion.I suggest to just not run this test with
-XX:TieredStopAtLevel=2,3
to not try to compile a C1 method with profiling data with C2 in order to avoid this MDO mismatch assertion failure. I'm not sure either of the value of this test as this old format is not created anymore. But we might still want to keep this test around.Thanks,
Christian
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/5548/head:pull/5548
$ git checkout pull/5548
Update a local copy of the PR:
$ git checkout pull/5548
$ git pull https://git.openjdk.java.net/jdk pull/5548/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 5548
View PR using the GUI difftool:
$ git pr show -t 5548
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/5548.diff