public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/114561] Comma operator with forwarding reference to pointer raises invalid lvalue required error Date: Tue, 02 Apr 2024 11:33:51 +0000 [thread overview] Message-ID: <bug-114561-4-HrJmIOIOdg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114561-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114561 --- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> --- Further reduced: void create(void* u) { const void* const& r = ( (void)0, u ); } void test_func() { create(0); } The result of (0, u) is an lvalue of type void* which should then be converted to a const void* prvalue, which is then bound to the reference.
next prev parent reply other threads:[~2024-04-02 11:33 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-02 10:06 [Bug c++/114561] New: " Liam.Jackson@qa-systems.com 2024-04-02 11:08 ` [Bug c++/114561] " redi at gcc dot gnu.org 2024-04-02 11:28 ` redi at gcc dot gnu.org 2024-04-02 11:33 ` redi at gcc dot gnu.org [this message] 2024-04-02 11:35 ` redi at gcc dot gnu.org 2024-04-02 14:38 ` [Bug c++/114561] [11/12/13/14 Regression] Comma operator with forwarding reference to pointer raises invalid lvalue required error since r10-7410 jakub at gcc dot gnu.org 2024-04-02 14:38 ` jakub at gcc dot gnu.org 2024-04-02 14:45 ` jason at gcc dot gnu.org 2024-04-02 18:11 ` cvs-commit at gcc dot gnu.org 2024-05-01 20:31 ` [Bug c++/114561] [11/12/13 " cvs-commit at gcc dot gnu.org 2024-05-24 13:26 ` [Bug c++/114561] [11/12 " cvs-commit at gcc dot gnu.org 2024-05-24 13:27 ` cvs-commit at gcc dot gnu.org 2024-05-24 13:29 ` jason at gcc dot gnu.org 2024-05-24 13:42 ` Liam.Jackson@qa-systems.com
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-114561-4-HrJmIOIOdg@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).