https://gcc.gnu.org/bugzilla/show_bug.cgi?id=121167
Bug ID: 121167
Summary: The documentation warning about fsanitize= and false
warnings should be improved
Product: gcc
Version: 14.2.0
Status: UNCONFIRMED
Keywords: documentation
Severity: enhancement
Priority: P3
Component: sanitizer
Assignee: unassigned at gcc dot gnu.org
Reporter: pinskia at gcc dot gnu.org
CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org,
jakub at gcc dot gnu.org, kcc at gcc dot gnu.org
Target Milestone: ---
Right now the documentation for this is
```
Note that sanitizers tend to increase the rate of false positive warnings, most
notably those around -Wmaybe-uninitialized. We recommend against combining
-Werror and [the use of] sanitizers.
```
Which itself hidden and I have to go find it each time and it is only listed
under -fsanitize=undefined but after all of the options that it enables.
We should have a notice for -fsanitizer=address (and thread) too. And the
current notice should be at the towards the begining of the documentation for
-fsanitize=undefined.
And maybe even a notice under -Werror and one under each of the warnings which
happen during the optimizations (bounds, access and restrict and strlen ones).
