public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "lopresti at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/109671] New: Spurious dangling reference warning in GCC 13 Date: Fri, 28 Apr 2023 17:48:08 +0000 [thread overview] Message-ID: <bug-109671-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109671 Bug ID: 109671 Summary: Spurious dangling reference warning in GCC 13 Product: gcc Version: 13.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: lopresti at gmail dot com Target Milestone: --- #include <string> struct Foo; extern Foo &get_foo_by_name(const std::string &name); const Foo &bug(bool x) { const Foo &f = get_foo_by_name(x ? "x" : "y"); return f; } --- Compile with "-O2 -Wall" to get the incorrect warning: <source>: In function 'const Foo& bug(bool)': <source>:9:14: warning: possibly dangling reference to a temporary [-Wdangling-reference] 9 | const Foo &f = get_foo_by_name(x ? "x" : "y"); | ^ <source>:9:33: note: the temporary was destroyed at the end of the full expression 'get_foo_by_name(std::__cxx11::basic_string<char>(((const char*)(x ? "x" : "y")), std::allocator<char>()))' 9 | const Foo &f = get_foo_by_name(x ? "x" : "y"); | ~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~ -- Godbolt: https://godbolt.org/z/cn4W7ohGb The code is fine. (And no other compiler warns about this, including earlier GCC versions.)
next reply other threads:[~2023-04-28 17:48 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-28 17:48 lopresti at gmail dot com [this message] 2023-04-28 17:51 ` [Bug c++/109671] " pinskia at gcc dot gnu.org 2023-04-28 19:31 ` lopresti at gmail dot com 2023-05-01 1:15 ` lopresti at gmail dot com 2023-05-02 19:50 ` cvs-commit at gcc dot gnu.org 2024-01-19 17:35 ` mpolacek 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-109671-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).