8346278: Clean up some flag handing in flags-cflags.m4

[magicus]

WARNING_CFLAGS_JVM should not be used to set arbitrary warning flags for Hotspot.

We do not need to check for gcc 6+ anymore.

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8346278: Clean up some flag handing in flags-cflags.m4 (Bug - P4)

Reviewers

• Erik Joelsson (@erikj79 - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 22762

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/22762.diff

Using Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back ihse! 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]

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

8346278: Clean up some flag handing in flags-cflags.m4

Reviewed-by: erikj

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 master branch:

• d737978: 8343477: Remove unnecessary @SuppressWarnings annotations (compiler)
• 8133eb2: 8346150: Jib dependency on autoconf missing for 'docs' profile
• 45a3297: 8346248: serviceability/dcmd/vm/{SystemMapTest.java,SystemMapTest.java} failing on macos-aarch64

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
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.

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

[openjdk]

@magicus The following label will be automatically applied to this pull request:

• build

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

[magicus]

Verified that this builds properly on GHA and the Oracle CI system.

[mlbridge]

Webrevs

• 00: Full (9089defa)

[magicus]

/integrate

[openjdk]

Going to push as commit 3030230.
Since your change was applied there have been 13 commits pushed to the master branch:

• fd0207d: 8345327: JDK 24 RDP1 L10n resource files update
• 31c3b19: 8346174: UMAX/UMIN are missing from XXXVector::reductionOperations
• c75b1d4: 8346082: Output JVMTI agent information in hserr files
• 51662c2: 8346232: Remove leftovers of the jar --normalize feature
• d335941: 8345678: compute_modifiers should not be in create_mirror
• 57adf64: 8346261: Cleanup in JDP tests
• 23708d0: 8346257: Problemlist jdp tests for macosx-aarch64
• f8974ba: 8345838: Remove the appcds/javaldr/AnonVmClassesDuringDump.java test
• e7d21fc: 8346285: Update jarsigner compatibility test for change in default digest algorithm
• cb92595: 8336356: [s390x] preserve Vector Register before using for string compress / expand
• ... and 3 more: https://git.openjdk.org/jdk/compare/dbffe33251da4472945d97ab54c7e3354d7f42d2...master

Your commit was automatically rebased without conflicts.

[openjdk]

@magicus Pushed as commit 3030230.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.