8287122: Use gcc12 -ftrivial-auto-var-init=pattern in debug builds

[magicus]

gcc12 has added -ftrivial-auto-var-init=, which specifies how automatic variables without an initializer should be initialized. The default choice is "uninitialized", which is the default C/C++ behavior. Alternatives are "pattern" and "zero". For improved debugging, helping to detect uninitialized uses, the "pattern" choice should be used.

---

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-8287122: Use gcc12 -ftrivial-auto-var-init=pattern in debug builds (Enhancement - P4)

Reviewers

• Erik Joelsson (@erikj79 - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 22587

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/22587.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:

8287122: Use gcc12 -ftrivial-auto-var-init=pattern in debug builds

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 1 new commit pushed to the master branch:

• 5da0eee: 8285692: Enable _FORTIFY_SOURCE=2 when building with Clang

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.

[mlbridge]

Webrevs

• 00: Full (3cd0ede9)

[magicus]

/integrate

[openjdk]

Going to push as commit 41c8971.
Since your change was applied there has been 1 commit pushed to the master branch:

• 5da0eee: 8285692: Enable _FORTIFY_SOURCE=2 when building with Clang

Your commit was automatically rebased without conflicts.

[openjdk]

@magicus Pushed as commit 41c8971.

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