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
8197859: VS2017 Complains about UINTPTR_MAX definition in globalDefinitions_VisCPP.hpp #77
Conversation
|
This backport pull request has now been updated with issue and summary from the original commit. |
@apavlyutkin this pull request can not be integrated into git checkout 8197859
git fetch https://git.openjdk.org/jdk8u-dev master
git merge FETCH_HEAD
# resolve conflicts and follow the instructions given by git merge
git commit -m "Merge master"
git push |
Webrevs
|
ping |
Guys, this one stops a seria of backports required to support VS 2019/22. Could somebody to review it? Thank you |
ping |
1 similar comment
ping |
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.
Why is generated-configure.sh
part of this change? It doesn't touch m4 scripts.
Ah, you mentioned it in the description. Forgotten in #33. Either way, this shouldn't be part of this backport. It's unrelated and just confuses people when looking at the backport after the fact. Please open and 8u-specific bug and correct this. Also, it's not clear why |
Ok, I removed generated-configure.sh from the PR, probably the best option here to commit it after the rest of VS2019 backports (there are 2-3 more) are done |
ping |
@apavlyutkin This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration! |
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.
It would be good if some Windows build person could review this patch as well.
// Some MS Visual Studio versions do not seem to have INT64_C and UINT64_C | ||
// even with __STDC_CONSTANT_MACROS defined. | ||
#ifndef INT64_C | ||
#define INT64_C(c) (c ## i64) | ||
#endif | ||
#ifndef UINT64_C | ||
#define UINT64_C(c) (c ## ui64) | ||
#endif |
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.
These removals aren't in the original changeset. See JDK-8272714 and JDK-8272214. I guess we should conditionalize on the VS version in use if that's a problem?
The definitions now are done by including of |
@apavlyutkin |
@apavlyutkin |
OK, thanks. |
Luckily the guys from my old job still use msvs-2008. I asked them to check presense of |
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 copyright date should stay at 2018 because that's what the original commit had. Other than that, lgtm.
fixed |
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.
Thanks, lgtm.
@apavlyutkin 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 101 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 (@jerboaa, @phohensee) but any other Committer may sponsor as well.
|
Thank you for the review |
/integrate |
@apavlyutkin |
/sponsor |
Going to push as commit b98d485.
Your commit was automatically rebased without conflicts. |
@yan-too @apavlyutkin Pushed as commit b98d485. |
Hi! Please review another backport from MSVS2019 seria. This one fixes type declarations made by globalDefinitions_VisCPP.hpp. The patch from 11u applied with the following changes:
_MSC_VER >= 1800
because the header was introduced only in MSVS 2013 but we have to keep support of the earlier MSVS versions_MSC_VER < 1800
stdint.h
Verification: 2019 build (both 32/64) now fails with
error (to be fixed by backport of 8043492)
Regression: 2017/2013/2012/2010 full build - ok
@kimbarrett @dholmes-ora if you took a look at that it would be very much appreciated
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk8u-dev pull/77/head:pull/77
$ git checkout pull/77
Update a local copy of the PR:
$ git checkout pull/77
$ git pull https://git.openjdk.org/jdk8u-dev pull/77/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 77
View PR using the GUI difftool:
$ git pr show -t 77
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk8u-dev/pull/77.diff