-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
8296190: TestMD5Intrinsics and TestMD5MultiBlockIntrinsics don't test the intrinsics #10954
Conversation
👋 Welcome back yftsai! A progress list of the required criteria for merging this PR into |
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.
Lgtm
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.
Lgtm, and trivial.
@yftsai 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 706 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 (@eastig, @phohensee, @simonis) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
/integrate |
I'm a little surprised that this isn't detected. The tests you mention have a verification step (i.e. Also, it is a little unfortunate, that the new warmup value still implicitly depends on the Finally, I think the actual tests should be run with |
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.
I'm a little surprised that this isn't detected. The tests you mention have a verification step (i.e. compiler.testlibrary.intrinsics.Verifier) which should detect this. Can you please check why that is not the case and if this also affects other intrinsic tests?
Also, it is a little unfortunate, that the new warmup value still implicitly depends on the -XX:CompileThreshold=500 setting in the actual test. It would be more stable to get that value explicitly (e.g. by using the WhiteBox API) and use a strictly bigger warmup value.
Finally, I think the actual tests should be run with -Xbatch to be sure that the corresponding methods have really been compiled.
Hi, Volker. Perhaps we could let this patch go in to fix the immediate problem, and have Yifan file an issue for a definitive fix? |
The verifier detects the intrinsic compiled/inlined somewhere, but it doesn't get executed. In other words, the verifier alone didn't guarantee the intrinsic tested. Other tests like TestSHA512Intrinsics have the same problem and are fixed as well. WARMUP_ITERATIONS is now set strictly larger than Tier4InvocationThreshold. Both TestMD5Intrinsics and TestMD5MultiBlockIntrinsics are run with |
@@ -54,7 +54,7 @@ public class DigestSanityTestBase { | |||
private static final int MSG_SIZE = 1024; | |||
private static final int OFFSET = 0; | |||
private static final int ITERATIONS = 10000; | |||
private static final int WARMUP_ITERATIONS = 550; | |||
private static final int WARMUP_ITERATIONS = WHITE_BOX.getIntxVMFlag("Tier4InvocationThreshold").intValue() + 50; |
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.
If the flag Tier4InvocationThreshold
is not set, what will happen?
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.
The default value, 5000, would be returned.
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.
Hi Yi-Fan,
Thanks for doing the additional changes and for confirming that the test run with -Xbatch
.
Looks good now.
Best regards,
Volker
/integrate |
/sponsor |
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.
Lgtm.
Going to push as commit f43bb9f.
Your commit was automatically rebased without conflicts. |
@phohensee @yftsai Pushed as commit f43bb9f. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Increase WARMUP_ITERATIONS to get MD5 hash from the intrinsic.
Both TestMD5Intrinsics and TestMD5MultiBlockIntrinsics are run with options "-XX:CompileThreshold=500 -XX:Tier4InvocationThreshold=500", so the current value is too low for the intrinsic to be executed.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/10954/head:pull/10954
$ git checkout pull/10954
Update a local copy of the PR:
$ git checkout pull/10954
$ git pull https://git.openjdk.org/jdk pull/10954/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 10954
View PR using the GUI difftool:
$ git pr show -t 10954
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/10954.diff