public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jonathan.poelen at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/99281] New: internal compiler error: in assign_temp, at function.c:984
Date: Fri, 26 Feb 2021 04:34:24 +0000	[thread overview]
Message-ID: <bug-99281-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 99281
           Summary: internal compiler error: in assign_temp, at
                    function.c:984
           Product: gcc
           Version: 10.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: jonathan.poelen at gmail dot com
  Target Milestone: ---

g++ -std=c++17 test.cpp
during RTL pass: expand
test.cpp: In function ‘int main()’:
test.cpp:27:5: internal compiler error: in assign_temp, at function.c:984
   27 |     pack_type<X>{get(1)};
      |     ^~~~~~~~~~~~~~~~~~~~

Compile with -O1 or higher.

struct Data
{
    Data() {}
    ~Data() {}

    long long i;
};

struct X
{
    Data a;
    int b;
};

template<class T>
X get(T const&)
{
    return X{};
}

template<class... Ts>
struct pack_type : Ts...
{};

int main()
{
    pack_type<X>{get(1)};
}

             reply	other threads:[~2021-02-26  4:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-26  4:34 jonathan.poelen at gmail dot com [this message]
2021-02-26  7:38 ` [Bug c++/99281] " rguenth at gcc dot gnu.org
2021-02-26  8:51 ` rguenth at gcc dot gnu.org
2021-02-26 11:34 ` cvs-commit at gcc dot gnu.org
2021-02-26 11:38 ` rguenth at gcc dot gnu.org
2024-04-05 23:01 ` pinskia 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-99281-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).