diff options
| author | David Malcolm <dmalcolm@redhat.com> | 2022-02-02 16:45:29 -0500 |
|---|---|---|
| committer | David Malcolm <dmalcolm@redhat.com> | 2022-02-02 16:50:39 -0500 |
| commit | fb45d8e692d41d0d5d0fea56791d5dca448009c5 (patch) | |
| tree | 8cdc1601d7312623d9b2b47c0274936759f8ff7a | |
| parent | 14d642df2b3f0d981fd7c0d3f832b26942c49b85 (diff) | |
| download | gcc-fb45d8e692d41d0d5d0fea56791d5dca448009c5.zip gcc-fb45d8e692d41d0d5d0fea56791d5dca448009c5.tar.gz gcc-fb45d8e692d41d0d5d0fea56791d5dca448009c5.tar.bz2 | |
docs: mention analyzer interaction with -ftrivial-auto-var-init [PR104270]
gcc/ChangeLog:
PR analyzer/104270
* doc/invoke.texi (-ftrivial-auto-var-init=): Add reference to
-Wanalyzer-use-of-uninitialized-value to paragraph documenting that
-ftrivial-auto-var-init= doesn't suppress warnings.
Signed-off-by: David Malcolm <dmalcolm@redhat.com>
| -rw-r--r-- | gcc/doc/invoke.texi | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi index 7af5c51..8bd5293 100644 --- a/gcc/doc/invoke.texi +++ b/gcc/doc/invoke.texi @@ -12304,7 +12304,8 @@ Initialize automatic variables with either a pattern or with zeroes to increase the security and predictability of a program by preventing uninitialized memory disclosure and use. GCC still considers an automatic variable that doesn't have an explicit -initializer as uninitialized, @option{-Wuninitialized} will still report +initializer as uninitialized, @option{-Wuninitialized} and +@option{-Wanalyzer-use-of-uninitialized-value} will still report warning messages on such automatic variables. With this option, GCC will also initialize any padding of automatic variables that have structure or union types to zeroes. |