public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ostash at ostash dot kiev.ua" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/110075] Bogus -Wdangling-reference Date: Wed, 24 Jan 2024 07:50:41 +0000 [thread overview] Message-ID: <bug-110075-4-pLbtkfNKo0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110075-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110075 Viktor Ostashevskyi <ostash at ostash dot kiev.ua> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ostash at ostash dot kiev.ua --- Comment #4 from Viktor Ostashevskyi <ostash at ostash dot kiev.ua> --- I have even simpler reproducer: --- class X{}; const X x1; const X x2; const X& get(const int& i) { return i == 0 ? x1 : x2; } void foo() { [[maybe_unused]] const X& x = get(10); } --- <source>: In function 'void foo()': <source>:23:31: warning: possibly dangling reference to a temporary [-Wdangling-reference] 23 | [[maybe_unused]] const X& x = get(10); | ^ <source>:23:38: note: the temporary was destroyed at the end of the full expression 'get(10)' 23 | [[maybe_unused]] const X& x = get(10); |
next prev parent reply other threads:[~2024-01-24 7:50 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-01 10:26 [Bug c++/110075] New: " pilarlatiesa at gmail dot com 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 [this message] 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-pLbtkfNKo0@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).