public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-7808] Docs: Document that taint analyzer checker disables some warnings [PR103533] Date: Fri, 25 Mar 2022 00:57:46 +0000 (GMT) [thread overview] Message-ID: <20220325005746.601E63858C2C@sourceware.org> (raw) https://gcc.gnu.org/g:319ba7e241e7e21f9eb481f075310796f13d2035 commit r12-7808-g319ba7e241e7e21f9eb481f075310796f13d2035 Author: Avinash Sonawane <rootkea@gmail.com> Date: Tue Mar 22 07:32:44 2022 +0530 Docs: Document that taint analyzer checker disables some warnings [PR103533] gcc/ChangeLog: PR analyzer/103533 * doc/invoke.texi: Document that enabling taint analyzer checker disables some warnings from `-fanalyzer`. Signed-off-by: Avinash Sonawane <rootkea@gmail.com> Diff: --- gcc/doc/invoke.texi | 33 +++++++++++++++++++++++++++------ 1 file changed, 27 insertions(+), 6 deletions(-) diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi index 4da4a1170f5..8b16b35ec12 100644 --- a/gcc/doc/invoke.texi +++ b/gcc/doc/invoke.texi @@ -421,14 +421,13 @@ Objective-C and Objective-C++ Dialects}. -fanalyzer-checker=@var{name} @gol -fno-analyzer-feasibility @gol -fanalyzer-fine-grained @gol --fanalyzer-state-merge @gol --fanalyzer-state-purge @gol +-fno-analyzer-state-merge @gol +-fno-analyzer-state-purge @gol -fanalyzer-transitivity @gol -fanalyzer-verbose-edges @gol -fanalyzer-verbose-state-changes @gol -fanalyzer-verbosity=@var{level} @gol -fdump-analyzer @gol --fdump-analyzer-stderr @gol -fdump-analyzer-callgraph @gol -fdump-analyzer-exploded-graph @gol -fdump-analyzer-exploded-nodes @gol @@ -438,6 +437,7 @@ Objective-C and Objective-C++ Dialects}. -fdump-analyzer-feasibility @gol -fdump-analyzer-json @gol -fdump-analyzer-state-purge @gol +-fdump-analyzer-stderr @gol -fdump-analyzer-supergraph @gol -Wno-analyzer-double-fclose @gol -Wno-analyzer-double-free @gol @@ -9659,22 +9659,24 @@ Enabling this option effectively enables the following warnings: -Wanalyzer-free-of-non-heap @gol -Wanalyzer-malloc-leak @gol -Wanalyzer-mismatching-deallocation @gol --Wanalyzer-possible-null-argument @gol --Wanalyzer-possible-null-dereference @gol -Wanalyzer-null-argument @gol -Wanalyzer-null-dereference @gol +-Wanalyzer-possible-null-argument @gol +-Wanalyzer-possible-null-dereference @gol -Wanalyzer-shift-count-negative @gol -Wanalyzer-shift-count-overflow @gol -Wanalyzer-stale-setjmp-buffer @gol +@ignore -Wanalyzer-tainted-allocation-size @gol -Wanalyzer-tainted-array-index @gol -Wanalyzer-tainted-divisor @gol -Wanalyzer-tainted-offset @gol -Wanalyzer-tainted-size @gol +@end ignore -Wanalyzer-unsafe-call-within-signal-handler @gol -Wanalyzer-use-after-free @gol --Wanalyzer-use-of-uninitialized-value @gol -Wanalyzer-use-of-pointer-in-stale-stack-frame @gol +-Wanalyzer-use-of-uninitialized-value @gol -Wanalyzer-write-to-const @gol -Wanalyzer-write-to-string-literal @gol } @@ -10015,6 +10017,25 @@ such as the @code{taint} checker that implements @option{-Wanalyzer-tainted-array-index}, and this option is required to enable them. +@emph{Note:} currently, @option{-fanalyzer-checker=taint} disables the +following warnings from @option{-fanalyzer}: + +@gccoptlist{ @gol +-Wanalyzer-double-fclose @gol +-Wanalyzer-double-free @gol +-Wanalyzer-exposure-through-output-file @gol +-Wanalyzer-file-leak @gol +-Wanalyzer-free-of-non-heap @gol +-Wanalyzer-malloc-leak @gol +-Wanalyzer-mismatching-deallocation @gol +-Wanalyzer-null-argument @gol +-Wanalyzer-null-dereference @gol +-Wanalyzer-possible-null-argument @gol +-Wanalyzer-possible-null-dereference @gol +-Wanalyzer-unsafe-call-within-signal-handler @gol +-Wanalyzer-use-after-free @gol +} + @item -fno-analyzer-feasibility @opindex fanalyzer-feasibility @opindex fno-analyzer-feasibility
reply other threads:[~2022-03-25 0:57 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20220325005746.601E63858C2C@sourceware.org \ --to=dmalcolm@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).