public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carsten.andrich at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/107138] [12 regression] std::variant<std::string, ...> triggers false-positive 'may be used uninitialized' warning
Date: Mon, 03 Oct 2022 20:24:42 +0000	[thread overview]
Message-ID: <bug-107138-4-cL389EreXC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107138-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from carsten.andrich at gmx dot de ---
(In reply to Marek Polacek from comment #1)
> I see the warning even without -fsanitize=undefined.

Yes. Just used -fsanitize=undefined as per the bug writing guidelines.

What I forgot to mention though: The issue only occurs with -O2 or higher. -O1
and -Og compile without the warnings.

  parent reply	other threads:[~2022-10-03 20:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-03 20:11 [Bug c++/107138] New: " carsten.andrich at gmx dot de
2022-10-03 20:14 ` [Bug c++/107138] " mpolacek at gcc dot gnu.org
2022-10-03 20:24 ` carsten.andrich at gmx dot de [this message]
2022-10-06 10:03 ` [Bug c++/107138] [12/13 " rguenth at gcc dot gnu.org
2022-11-17 11:47 ` marco.clemencic at gmail dot com
2022-11-17 11:49 ` marco.clemencic at gmail dot com
2022-11-17 11:51 ` marco.clemencic at gmail dot com
2022-11-22 10:57 ` marco.clemencic at gmail dot com
2022-11-22 12:31 ` redi at gcc dot gnu.org
2022-11-29 16:35 ` freddie_chopin at op dot pl
2022-11-29 17:21 ` redi at gcc dot gnu.org
2022-12-22 13:42 ` rguenth at gcc dot gnu.org
2023-05-08 12:25 ` [Bug c++/107138] [12/13/14 " rguenth at gcc dot gnu.org
2024-02-05 13:54 ` ppalka at gcc dot gnu.org
2024-03-15  0:41 ` [Bug c++/107138] [12 " law 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-107138-4-cL389EreXC@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).