On Tue, 25 Feb 2025 15:36:39 GMT, Magnus Ihse Bursie <i...@openjdk.org> wrote:
>> This is a retry to add `-ftrivial-auto-var-init=pattern` to gcc debug >> builds. The first attempt was buggy in multiple ways and had to be backed >> out. >> >> This is the description of the original bug report: >> >> gcc12 has added -ftrivial-auto-var-init=<choice>, 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. > > Magnus Ihse Bursie has updated the pull request with a new target base due to > a merge or a rebase. The pull request now contains four commits: > > - Merge branch 'master' into auto-var-init-redo > - Try filtering out -ftrivial-auto-var-init=pattern for libsleef. This patch > is getting uglier by the minute... > - Only add flag if it is supported > - 8345627: [REDO] Use gcc12 -ftrivial-auto-var-init=pattern in debug builds Marked as reviewed by erikj (Reviewer). ------------- PR Review: https://git.openjdk.org/jdk/pull/22691#pullrequestreview-2641670846
