public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <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: Thu, 16 May 2024 07:48:09 +0000 [thread overview] Message-ID: <bug-107919-4-kky71S8WVP@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 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |13.0 Resolution|--- |FIXED Known to work| |13.1.0, 14.1.0 Known to fail| |12.3.0 Status|ASSIGNED |RESOLVED --- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> --- With GCC 13 and newer we also do not diagnose with -O2 or -O3. I have a patch for trunk (GCC 15) that's going to regress for -O1 (but not -O2 or -O3), still declaring this fixed as reported.
prev parent reply other threads:[~2024-05-16 7: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 ` [Bug tree-optimization/107919] " freddie_chopin at op dot pl 2022-11-30 9:12 ` 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 [this message]
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-kky71S8WVP@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: linkBe 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).