public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/104076] New: bogus -Wdangling-pointer on a conditional Date: Mon, 17 Jan 2022 22:10:27 +0000 [thread overview] Message-ID: <bug-104076-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104076 Bug ID: 104076 Summary: bogus -Wdangling-pointer on a conditional Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: msebor at gcc dot gnu.org Target Milestone: --- As reported in https://gcc.gnu.org/pipermail/gcc-patches/2022-January/588620.html, the new -Wdangling-pointer issues a false positive for the following test case: $ cat t.C && g++ -S -Wall t.C #include <initializer_list> struct S1 { S1 (int); ~S1 (); }; struct S2 { S2 (std::initializer_list<S1>); }; S2 f1(); S2 f2(bool b) { return b ? f1() : S2{0}; } t.C: In function ‘S2 f2(bool)’: t.C:16:1: warning: dangling pointer to an unnamed temporary may be used [-Wdangling-pointer=] 16 | } | ^ t.C:15:25: note: unnamed temporary defined here 15 | return b ? f1() : S2{0}; | ^ t.C:16:1: warning: dangling pointer to an unnamed temporary may be used [-Wdangling-pointer=] 16 | } | ^ t.C:15:25: note: unnamed temporary defined here 15 | return b ? f1() : S2{0}; | ^
next reply other threads:[~2022-01-17 22:10 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-17 22:10 msebor at gcc dot gnu.org [this message] 2022-01-17 22:11 ` [Bug middle-end/104076] " msebor at gcc dot gnu.org 2022-01-18 23:15 ` msebor at gcc dot gnu.org 2022-01-19 1:04 ` cvs-commit at gcc dot gnu.org 2022-01-19 1:18 ` msebor at gcc dot gnu.org 2022-02-02 13:54 ` rguenth at gcc dot gnu.org 2022-02-02 19:12 ` msebor at gcc dot gnu.org 2022-03-17 19:31 ` msebor at gcc dot gnu.org 2022-04-25 7:57 ` 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-104076-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).