-
Notifications
You must be signed in to change notification settings - Fork 238
8248414: AArch64: Remove uses of long and unsigned long ints #215
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 vkempik! A progress list of the required criteria for merging this PR into |
This backport pull request has now been updated with issue from the original commit. |
@VladimirKempik 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 no new commits pushed to the ➡️ To integrate this PR with the above commit message to the |
Hello @phohensee , as this backport is also part of winaarch64 backport, I'm going to withdraw this to not make MS folks to do the job twice, could your repeat your approval there as well, the patches are almost identical #222 |
Yes, this patch is almost identical to a small part of #222, but the latter is huge. I'll take a shot at reviewing it though. |
On second thought, see my comment on #222. I'd prefer to push this backport separately. |
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.
Did a little more spelunking and found that some of the changes in this patch (e.g., aarch64.ad) are in JDK-8248403. I did a quick backport of that issue, see #246.
Yes, definitely. The two integer type cleanup patches were because of Windows/Mac, but they are logically independent of the ports. It really wouldn't help to merge them. |
Substantial cleanups,I mean. I have no objection to tidying up bits and pieces as we go along,and John Rose has said that we should. |
Hi, Vladimir. Note that the current patch has a conflict in immediate_aarch64.cpp due to the backport of JDK-8248403. |
Note that your current patch has a conflict due to the backport of JDK-8248403. Please update the PR. |
Thanks for heads up! fixed merge conflict |
/integrate |
Going to push as commit bf01efa.
Your commit was automatically rebased without conflicts. |
@VladimirKempik Pushed as commit bf01efa. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
This is a backport of 8248414 to jdk11u-dev
The backport didn't apply clean, partially due to backport of JDK-8247766
It's needed for mac-aarch and win-aarch64 ports
It will be followed by 8250824 and 8251930.
Sections of aarch64.ad file between line 10260-12560 were regenerated from aarch64_ad.m4
Original commit - openjdk/jdk@c7d8485
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk11u-dev pull/215/head:pull/215
$ git checkout pull/215
Update a local copy of the PR:
$ git checkout pull/215
$ git pull https://git.openjdk.java.net/jdk11u-dev pull/215/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 215
View PR using the GUI difftool:
$ git pr show -t 215
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk11u-dev/pull/215.diff