public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
* [gcc r13-5613] doc: add notes about limitations of -fanalyzer
@ 2023-02-01  2:22 David Malcolm
  0 siblings, 0 replies; only message in thread
From: David Malcolm @ 2023-02-01  2:22 UTC (permalink / raw)
  To: gcc-cvs

https://gcc.gnu.org/g:a90316c6ceddfbb47b3c2161baf446ccb87df5ff

commit r13-5613-ga90316c6ceddfbb47b3c2161baf446ccb87df5ff
Author: David Malcolm <dmalcolm@redhat.com>
Date:   Tue Jan 31 21:18:00 2023 -0500

    doc: add notes about limitations of -fanalyzer
    
    gcc/ChangeLog:
            * doc/invoke.texi (Static Analyzer Options): Add notes about
            limitations of -fanalyzer.
    
    Signed-off-by: David Malcolm <dmalcolm@redhat.com>

Diff:
---
 gcc/doc/invoke.texi | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index d12f318adfd..b45b629069b 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -10064,6 +10064,13 @@ code, and issues warnings for problems found on them.
 
 This analysis is much more expensive than other GCC warnings.
 
+In technical terms, it performs coverage-guided symbolic execution of
+the code being compiled.  It is neither sound nor complete: it can
+have false positives and false negatives.  It is a bug-finding tool,
+rather than a tool for proving program correctness.
+
+The analyzer is only suitable for use on C code in this release.
+
 Enabling this option effectively enables the following warnings:
 
 @gccoptlist{ @gol

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2023-02-01  2:22 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-02-01  2:22 [gcc r13-5613] doc: add notes about limitations of -fanalyzer David Malcolm

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).