public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86355] [8/9/10/11/12 Regression] Internal compiler error with pack expansion and fold expression
Date: Mon, 03 May 2021 19:01:31 +0000	[thread overview]
Message-ID: <bug-86355-4-PQfPGV6U8i@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-86355-4@http.gcc.gnu.org/bugzilla/>

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

Patrick Palka <ppalka at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jason at gcc dot gnu.org,
                   |                            |ppalka at gcc dot gnu.org
      Known to fail|                            |5.2.0, 6.4.0
   Target Milestone|---                         |8.5
      Known to work|                            |5.1.0
            Summary|Internal compiler error     |[8/9/10/11/12 Regression]
                   |with pack expansion and     |Internal compiler error
                   |fold expression             |with pack expansion and
                   |                            |fold expression

--- Comment #5 from Patrick Palka <ppalka at gcc dot gnu.org> ---
A reduced valid C++11 testcase:

template <int...> struct integral_constant {
  static const int value = 1;
};
template <class... T> using mp_all = integral_constant<T::value...>;
template <class... T> using check2 = mp_all<mp_all<T...,
integral_constant<0>>>;
check2<> x;

We started ICEing on this one after r6-1487.

       reply	other threads:[~2021-05-03 19:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-86355-4@http.gcc.gnu.org/bugzilla/>
2021-05-03 19:01 ` ppalka at gcc dot gnu.org [this message]
2021-05-14  9:50 ` [Bug c++/86355] [9/10/11/12 " jakub at gcc dot gnu.org
2021-05-26 21:37 ` jason at gcc dot gnu.org
2021-05-27 17:42 ` cvs-commit at gcc dot gnu.org
2021-06-01  8:11 ` rguenth at gcc dot gnu.org
2021-07-09 20:14 ` [Bug c++/86355] [9/10/11 " cvs-commit at gcc dot gnu.org
2022-05-13 17:13 ` [Bug c++/86355] [9/10 " cvs-commit at gcc dot gnu.org
2022-05-27  9:39 ` [Bug c++/86355] [10 " rguenth at gcc dot gnu.org
2022-06-28 10:35 ` jakub at gcc dot gnu.org
2023-07-07  8:02 ` rguenth at gcc dot gnu.org
2023-07-07  8:13 ` pdimov at gmail dot 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-86355-4-PQfPGV6U8i@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).