8288754: GCC 12 fails to build zReferenceProcessor.cpp

[shipilev]

Clean backport to improve GCC 12 support.

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8288754: GCC 12 fails to build zReferenceProcessor.cpp

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk18u pull/176/head:pull/176
$ git checkout pull/176

Update a local copy of the PR:
$ git checkout pull/176
$ git pull https://git.openjdk.org/jdk18u pull/176/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 176

View PR using the GUI difftool:
$ git pr show -t 176

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk18u/pull/176.diff

[bridgekeeper]

👋 Welcome back shade! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

This backport pull request has now been updated with issue from the original commit.

[openjdk]

@shipilev 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:

8288754: GCC 12 fails to build zReferenceProcessor.cpp

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 master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[mlbridge]

Webrevs

• 00: Full (6cbb93c8)

[RealCLanger]

Hm, I think as per https://mail.openjdk.org/pipermail/jdk-updates-dev/2022-June/014674.html, JDK18u is done. I guess it's of no use doing backports to 18 still.

[shipilev]

Hm, I think as per https://mail.openjdk.org/pipermail/jdk-updates-dev/2022-June/014674.html, JDK18u is done. I guess it's of no use doing backports to 18 still.

Right, I missed the 18u timeline. Closing.