public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "freddie_chopin at op dot pl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/107919] Possibly false-positive "maybe-uninitialized" with GCC 12 on complex variant-variant-tuple-unique_ptr types
Date: Tue, 29 Nov 2022 16:48:36 +0000	[thread overview]
Message-ID: <bug-107919-4-enuHFKulwA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107919-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Freddie Chopin <freddie_chopin at op dot pl> ---
More possibly imporant notes:
1. The warning appears only with -O1 or -O2, with 0, s, g or 3 the warning is
gone.
2. Adding -fsanitize=undefined to compiler invocation makes the warning go away
as well - no terminal output is produced in that case.

  reply	other threads:[~2022-11-29 16:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-29 16:29 [Bug c++/107919] New: " freddie_chopin at op dot pl
2022-11-29 16:48 ` freddie_chopin at op dot pl [this message]
2022-11-30  9:12 ` [Bug tree-optimization/107919] " rguenth at gcc dot gnu.org
2022-11-30 10:59 ` rguenth at gcc dot gnu.org
2022-11-30 11:01 ` cvs-commit at gcc dot gnu.org
2022-11-30 11:01 ` rguenth at gcc dot gnu.org
2022-11-30 11:53 ` cvs-commit at gcc dot gnu.org
2024-05-16  7:48 ` rguenth 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-107919-4-enuHFKulwA@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).