public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marc@nieper-wisskirchen.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/103989] New: [12 regression] std::optional and bogus -Wmaybe-unitialized at -Og Date: Wed, 12 Jan 2022 12:10:14 +0000 [thread overview] Message-ID: <bug-103989-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103989 Bug ID: 103989 Summary: [12 regression] std::optional and bogus -Wmaybe-unitialized at -Og Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: marc@nieper-wisskirchen.de Target Milestone: --- With the trunk version of GCC compiling the following program with -std=c++17 -Og -Wall -Werror gives a bogus maybe-uninitialized error (in the standard library component for the shared pointer): //// #include <optional> #include <memory> struct A { A (int a) : a {a} {} const std::shared_ptr <int> x; int a; }; class B { public: B (const std::optional <A>& a) : a {a} { } public: const std::optional <A> a; }; int main () { B b {std::nullopt}; } //// Compiling it with -std=c++17 -O1 -Wall -Werror doesn't produce the error. As the code compiles find at -Og and -O1 with GCC 11.2, this is a regression. The error triggering is brittle. It goes away if the dummy member variable a in class A is removed, for example. For experimentation, the test case can be found here: https://godbolt.org/z/arGKT7d5n.
next reply other threads:[~2022-01-12 12:10 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-12 12:10 marc@nieper-wisskirchen.de [this message] 2022-01-12 12:16 ` [Bug tree-optimization/103989] [12 regression] std::optional and bogus -Wmaybe-unitialized at -Og since r12-1992-g6feb628a706e86eb marxin at gcc dot gnu.org 2022-01-12 12:54 ` rguenth at gcc dot gnu.org 2022-01-12 17:44 ` jakub at gcc dot gnu.org 2022-01-12 19:11 ` pinskia at gcc dot gnu.org 2022-01-13 11:10 ` jakub at gcc dot gnu.org 2022-01-13 11:39 ` rguenth at gcc dot gnu.org 2022-01-13 11:56 ` Jan Hubicka 2022-01-13 11:56 ` hubicka at kam dot mff.cuni.cz 2022-01-13 12:03 ` Jan Hubicka 2022-01-13 12:03 ` hubicka at kam dot mff.cuni.cz 2022-01-13 12:25 ` rguenth at gcc dot gnu.org 2022-01-13 13:39 ` hubicka at kam dot mff.cuni.cz 2022-01-13 13:44 ` rguenther at suse dot de 2022-01-13 13:55 ` hubicka at kam dot mff.cuni.cz 2022-01-13 13:58 ` rguenth at gcc dot gnu.org 2022-01-13 14:11 ` Jan Hubicka 2022-01-13 14:11 ` hubicka at kam dot mff.cuni.cz 2022-01-13 15:01 ` cvs-commit at gcc dot gnu.org 2022-01-13 15:05 ` jakub at gcc dot gnu.org 2022-01-13 15:10 ` rguenther at suse dot de 2022-01-18 12:35 ` rguenth at gcc dot gnu.org 2022-01-18 14:43 ` cvs-commit at gcc dot gnu.org 2022-01-18 14:43 ` cvs-commit at gcc dot gnu.org 2022-01-18 14:43 ` 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-103989-4@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).