https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107298
--- Comment #3 from John Zwinck <jzwinck at gmail dot com> --- Martin, this bug is the only false positive I see in a large corporate codebase. I think your comment makes it sound like this is a documented thing where there are tons of false positives and it's not practical to do anything about them, and I am not sure how to square this with my experience that almost all warnings from -Wall and -Wextra work just fine with ASan & UBSan. Is there some documentation explaining this, or telling Sanitizer users to turn off warnings-as-errors?
