public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ed at catmur dot uk" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/109640] New: Spurious Wdangling-reference for argument to temporary lambda cast to rvalue reference Date: Wed, 26 Apr 2023 23:24:05 +0000 [thread overview] Message-ID: <bug-109640-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109640 Bug ID: 109640 Summary: Spurious Wdangling-reference for argument to temporary lambda cast to rvalue reference Product: gcc Version: 13.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: ed at catmur dot uk Target Milestone: --- bool b() { int a; int&& i = [](int& r) -> int&& { return static_cast<int&&>(r); }(a); auto const l = [](int& r) -> int&& { return static_cast<int&&>(r); }; int&& j = l(a); return &i == &j; } <source>: In function 'bool b()': <source>:3:11: warning: possibly dangling reference to a temporary [-Wdangling-reference] 3 | int&& i = [](int& r) -> int&& { return static_cast<int&&>(r); }(a); | ^ <source>:3:68: note: the temporary was destroyed at the end of the full expression '<lambda closure object>b()::<lambda(int&)>().b()::<lambda(int&)>(a)' 3 | int&& i = [](int& r) -> int&& { return static_cast<int&&>(r); }(a); | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~ The heuristic appears to be confused by the lambda itself being a temporary, even though it is captureless.
next reply other threads:[~2023-04-26 23:24 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-26 23:24 ed at catmur dot uk [this message] 2023-04-26 23:40 ` [Bug c++/109640] " pinskia at gcc dot gnu.org 2023-04-26 23:59 ` ed at catmur dot uk 2023-04-27 15:54 ` mpolacek at gcc dot gnu.org 2023-05-02 19:49 ` cvs-commit at gcc dot gnu.org 2024-01-18 23:05 ` mpolacek at gcc dot gnu.org 2024-01-23 21:36 ` cvs-commit at gcc dot gnu.org 2024-01-23 22:35 ` mpolacek at gcc dot gnu.org 2024-01-30 18:24 ` cvs-commit 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-109640-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).