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/102801] Incorrect -Wmaybe-uninitialized warning/interaction for a std::optional only when a nested struct is also present. Date: Thu, 22 Sep 2022 13:18:49 +0000 [thread overview] Message-ID: <bug-102801-4-LZAgulSvzE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102801-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102801 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to work| |12.2.1, 13.0 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> --- The testcase no longer warns after GCC 12.2 or on GCC 13 trunk for me. I can re-confirm diagnostics with GCC 10 and GCC 11. I'm going to add the testcase and close this bug.
next prev parent reply other threads:[~2022-09-22 13:18 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-17 12:47 [Bug c++/102801] New: Incorrect -Wmaybe-uninitialized warning/interation " calin.culianu at bitcoincashnode dot org 2021-10-17 16:43 ` [Bug c++/102801] Incorrect -Wmaybe-uninitialized warning/interaction " redi at gcc dot gnu.org 2021-10-17 20:33 ` egallager at gcc dot gnu.org 2021-10-17 21:59 ` calin.culianu at bitcoincashnode dot org 2022-09-22 13:18 ` rguenth at gcc dot gnu.org [this message] 2022-09-22 13:19 ` [Bug tree-optimization/102801] " 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-102801-4-LZAgulSvzE@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).