public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/107298] Failure to compile code with std::optional and ASan/UBSan
Date: Wed, 19 Oct 2022 07:19:19 +0000	[thread overview]
Message-ID: <bug-107298-4-5eudmEwTjO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107298-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107298

--- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> ---
> Is there some documentation explaining this, or telling Sanitizer
> users to turn off warnings-as-errors?

Unfortunately, it is not, but we should include it.

Generally speaking, -Wmaybe-uninitialized is a warning with a pretty high
false-positive rate. And it's known that sanitizers tend to introduce new
warnings which are false positives. Anyway, let me update the documentation.

  parent reply	other threads:[~2022-10-19  7:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-17 15:01 [Bug sanitizer/107298] New: " jzwinck at gmail dot com
2022-10-17 19:24 ` [Bug sanitizer/107298] " marxin at gcc dot gnu.org
2022-10-17 19:24 ` marxin at gcc dot gnu.org
2022-10-18  7:18 ` jzwinck at gmail dot com
2022-10-19  7:19 ` marxin at gcc dot gnu.org [this message]
2022-10-28  7:16 ` cvs-commit at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-107298-4-5eudmEwTjO@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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).