public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pilarlatiesa at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/110075] New: Bogus -Wdangling-reference Date: Thu, 01 Jun 2023 10:26:25 +0000 [thread overview] Message-ID: <bug-110075-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110075 Bug ID: 110075 Summary: Bogus -Wdangling-reference Product: gcc Version: 13.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: pilarlatiesa at gmail dot com Target Milestone: --- $ cat test.cpp #include <map> #include <string> class T { static inline std::map<std::string, int> const m = {{"foo", 0}}; public: static int const &Get(std::string const &s) { return m.at(s); } }; int main() { [[maybe_unused]] int const &i = T::Get("foo"); } $ ./gcc-13/bin/g++ -Wall test.cpp test.cpp: In function ‘int main()’: test.cpp:14:31: warning: possibly dangling reference to a temporary [-Wdangling-reference] 14 | [[maybe_unused]] int const &i = T::Get("foo"); | ^ test.cpp:14:41: note: the temporary was destroyed at the end of the full expression ‘T::Get(std::__cxx11::basic_string<char>(((const char*)"foo"), std::allocator<char>()))’ 14 | [[maybe_unused]] int const &i = T::Get("foo"); | ~~~~~~^~~~~~~
next reply other threads:[~2023-06-01 10:26 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-01 10:26 pilarlatiesa at gmail dot com [this message] 2023-06-09 18:53 ` [Bug c++/110075] " pilarlatiesa at gmail dot com 2023-10-28 21:26 ` roystgnr at gmail dot com 2024-01-19 17:25 ` mpolacek at gcc dot gnu.org 2024-01-24 7:50 ` ostash at ostash dot kiev.ua 2024-01-24 15:51 ` mpolacek at gcc dot gnu.org 2024-01-28 16:21 ` ostash at ostash dot kiev.ua 2024-01-30 16:44 ` mpolacek at gcc dot gnu.org 2024-03-01 21:18 ` 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-110075-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).