From fb45d8e692d41d0d5d0fea56791d5dca448009c5 Mon Sep 17 00:00:00 2001 From: David Malcolm Date: Wed, 2 Feb 2022 16:45:29 -0500 Subject: [PATCH] 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 --- gcc/doc/invoke.texi | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi index 7af5c51cc3c..8bd5293fce7 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.