-
Notifications
You must be signed in to change notification settings - Fork 252
8248668: AArch64: Avoid MIN/MAX macros when using MSVC #263
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 rnkovacs! A progress list of the required criteria for merging this PR into |
|
This backport pull request has now been updated with issue and summary from the original commit. |
|
@rnkovacs 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 12 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. ➡️ To flag this PR as ready for integration with the above commit message, type |
|
/contributor add Bernhard Urban-Forster burban@openjdk.org |
|
@rnkovacs Could not parse
|
Webrevs
|
|
@rnkovacs could we also attribute the contributor to the author of the change on jdk/jdk (monica.beckwith@microsoft.com, luhenry@openjdk.org)? Thank you! |
|
Hi @luhenry, sorry, I was trying to follow the new SKARA Backports doc saying "Note that author metadata recorded in the backport commit is the author of the backport commit, not the author of the original commit. Likewise the reviewers recorded in the commit message are the reviewers of the backport commit, not the reviewers of the original commit." I am more than happy to add you two though if that's OK with everyone. |
|
/contributor add Monica Beckwith mbeckwit@openjdk.org |
|
@rnkovacs |
|
@rnkovacs |
|
/contributor add Bernhard Urban-Forster burban@openjdk.org |
|
@rnkovacs |
|
@rnkovacs I was not aware of SKARA Backports doc, thanks for pointing it out. Up to you then! And thank you for backporting all of that to JDK 11, can't wait to try it out :) |
|
/integrate |
|
I'm not sure what's up with the Windows x64 hotspot test failure (it says |
You can try to merge master into this PR. With that GHA will run again and we can check if it occurs again. Please do so and I'll sponsor the change if the issue is not reproduced. |
7c70d35 to
cda127b
Compare
|
Reka, you need to add another /integrate comment in order for /sponsor to work. |
|
/integrate |
|
Thank you, Paul. |
|
/sponsor |
|
Going to push as commit 63fc945.
Your commit was automatically rebased without conflicts. |
|
@RealCLanger @rnkovacs Pushed as commit 63fc945. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Changes apply cleanly. Testing: tier1.
This is part of the Windows/AArch64 port.
Progress
Issue
Contributors
<mbeckwit@openjdk.org><luhenry@openjdk.org><burban@openjdk.org>Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk11u-dev pull/263/head:pull/263$ git checkout pull/263Update a local copy of the PR:
$ git checkout pull/263$ git pull https://git.openjdk.java.net/jdk11u-dev pull/263/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 263View PR using the GUI difftool:
$ git pr show -t 263Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk11u-dev/pull/263.diff