public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
* [gcc r13-3539] docs: document sanitizers can trigger warnings
@ 2022-10-28  7:16 Martin Liska
  0 siblings, 0 replies; only message in thread
From: Martin Liska @ 2022-10-28  7:16 UTC (permalink / raw)
  To: gcc-cvs

https://gcc.gnu.org/g:3f9c071324eff2222249b23a7531e447fc17d928

commit r13-3539-g3f9c071324eff2222249b23a7531e447fc17d928
Author: Martin Liska <mliska@suse.cz>
Date:   Wed Oct 26 13:07:57 2022 +0200

    docs: document sanitizers can trigger warnings
    
            PR sanitizer/107298
    
    gcc/ChangeLog:
    
            * doc/invoke.texi: Document sanitizers can trigger warnings.

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

diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 9f0e5460861..c0ca76544e8 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -16509,6 +16509,10 @@ by this option.
 
 @end table
 
+Note the enabled sanitizer options tend to increase a false-positive rate
+of selected warnings, most notably @option{-Wmaybe-uninitialized}.
+And thus we recommend to disable @option{-Werror}.
+
 While @option{-ftrapv} causes traps for signed overflows to be emitted,
 @option{-fsanitize=undefined} gives a diagnostic message.
 This currently works only for the C family of languages.

^ permalink raw reply	[flat|nested] only message in thread
only message in thread, other threads:[~2022-10-28  7:16 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-10-28  7:16 [gcc r13-3539] docs: document sanitizers can trigger warnings Martin Liska

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