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
8269120: Build failure with GCC 6.3.0 after JDK-8017163 #4551
Conversation
|
Webrevs
|
What platform is still on GCC 6.3.0? It has been released in December 21, 2016 and actually the whole release series is apparently "no longer supported" according to the GNU homepage (link). I kind of understand supporting still supported compilers, but officially unsupported ones with the last release 3 years ago (which is 6.5.0 btw)? Not having looked into the change too much, but there might be more similar trouble when implementing JDK-8267834 when the JDK 17 release trouble dies down a bit, as |
Debian 9 "stretch" ships with GCC 6.3.0 [1], and it is supported until 2022 [2]. Plenty of servers (including some of my CI nodes) run it. [1] https://packages.debian.org/search?keywords=gcc |
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.
Ship it.
@shipilev 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 3 new commits pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the
|
Is this kind of move trivial? In other words, do we want to wait for anyone else to chime in? |
I'm looking at it. I don't much like it, and have some other suggestions that you may or may not have already tried. I don't have ready access to gcc6, so hard to experiment. |
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.
Much better! Looks good.
Cool. Just checking: this looks trivial to you, right? I'd like to make CIs happier tonight. |
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. Thanks for finding a better alternative.
/integrate |
Going to push as commit 6237630.
Your commit was automatically rebased without conflicts. |
One of my CI servers that carry GCC 6.3.0 fails after JDK-8017163 with:
I believe the cause is that
next_ptr
is the member oftemplate<class Elem> class G1CardSetAllocator
, so this confuses the compiler. For a fix, I moved thetypedef
toG1CardSetContainer
, which is not templated.Additional testing:
tier1
passesProgress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/4551/head:pull/4551
$ git checkout pull/4551
Update a local copy of the PR:
$ git checkout pull/4551
$ git pull https://git.openjdk.java.net/jdk pull/4551/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 4551
View PR using the GUI difftool:
$ git pr show -t 4551
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/4551.diff