[gcc r13-3748] docs: update: document sanitizers can trigger warnings

[Martin Liska]

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

commit r13-3748-ga8fb90eb3949bfb101bd6f50f24a029e10119591
Author: Martin Liska <mliska@suse.cz>
Date:   Mon Nov 7 09:54:09 2022 +0100

    docs: update: document sanitizers can trigger warnings
    
    gcc/ChangeLog:
    
            * doc/invoke.texi: Improve wording.
    
    Co-Authored-By: Gerald Pfeifer <gerald@pfeifer.com>

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

diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 4a0fbca938e..94a2e20cfc1 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -16502,9 +16502,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}.
+Note that sanitizers tend to increase the rate of false positive
+warnings, most notably those around @option{-Wmaybe-uninitialized}.
+We recommend against combining @option{-Werror} and [the use of]
+sanitizers.
 
 While @option{-ftrapv} causes traps for signed overflows to be emitted,
 @option{-fsanitize=undefined} gives a diagnostic message.