public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Liam.Jackson@qa-systems.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/114562] New: ICE when trying to bind rvalue reference to lvalue with comma operator and forwarding reference to pointer
Date: Tue, 02 Apr 2024 10:15:16 +0000	[thread overview]
Message-ID: <bug-114562-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114562

            Bug ID: 114562
           Summary: ICE when trying to bind rvalue reference to lvalue
                    with comma operator and forwarding reference to
                    pointer
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: Liam.Jackson@qa-systems.com
  Target Milestone: ---

Created attachment 57846
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57846&action=edit
Source to reproduce ice

Compiling the attached source would expect to raise an error such as 

error: cannot bind rvalue reference of type 'const void*&&' to lvalue of type
'void* const'

Instead the following ICE occurs:

<source>: In instantiation of 'static T Create<T>::create(U&&) [with U = void*
const&; T = MyClass]':
<source>:34:28:   required from here
   34 |     Create<MyClass>::create(MyClass::NONE);
      |     ~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~
<source>:28:13: internal compiler error: in convert_like_internal, at
cp/call.cc:8879
   28 |      return T( ( (beforeParam()), (u) ) );
      |             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
0x266d8bc internal_error(char const*, ...)
        ???:0
0xa572eb fancy_abort(char const*, int, char const*)
        ???:0
0xa81334 build_new_method_call(tree_node*, tree_node*, vec<tree_node*, va_gc,
vl_embed>**, tree_node*, int, tree_node**, int)
        ???:0
0xa8265b build_special_member_call(tree_node*, tree_node*, vec<tree_node*,
va_gc, vl_embed>**, tree_node*, int, int)
        ???:0
0xa8ff69 perform_direct_initialization_if_possible(tree_node*, tree_node*,
bool, int)
        ???:0
0xd33f73 build_functional_cast(unsigned int, tree_node*, tree_node*, int)
        ???:0
0xc92ed3 instantiate_decl(tree_node*, bool, bool)
        ???:0
0xcbc0ab instantiate_pending_templates(int)
        ???:0
0xb5a619 c_parse_final_cleanups()
        ???:0
0xdaf328 c_common_parse_file()
        ???:0


It may be possible to construct an example source which is expected to compile
successfully yet still triggers this ICE. This has not been explored.

             reply	other threads:[~2024-04-02 10:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-02 10:15 Liam.Jackson@qa-systems.com [this message]
2024-04-02 14:35 ` [Bug c++/114562] [11/12/13/14 Regression] ICE when trying to bind rvalue reference to lvalue with comma operator and forwarding reference to pointer since r10-7410 jakub at gcc dot gnu.org
2024-04-02 14:50 ` 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++/114562] [11/12/13 " cvs-commit at gcc dot gnu.org
2024-05-24 13:26 ` [Bug c++/114562] [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:30 ` jason 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-114562-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: link
Be 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).