public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92068] [8/9/10 Regression] ICE on invalid in process_partial_specialization
Date: Sun, 15 Mar 2020 22:09:21 +0000	[thread overview]
Message-ID: <bug-92068-4-SA4FqfnTM1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-92068-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by Jason Merrill
<jason@gcc.gnu.org>:

https://gcc.gnu.org/g:2fa5f9e380b794053a0dd8a8cc63f8bfab370d22

commit r9-8378-g2fa5f9e380b794053a0dd8a8cc63f8bfab370d22
Author: Jason Merrill <jason@redhat.com>
Date:   Sat Mar 14 17:10:39 2020 -0400

    c++: Fix ICE-after-error on partial spec [92068]

    Here the template arguments for the partial specialization are valid
    arguments for the template, but not for a partial specialization, because
    'd' can never be deduced to anything other than an empty pack.

    gcc/cp/ChangeLog
    2020-03-14  Jason Merrill  <jason@redhat.com>

            PR c++/92068
            * pt.c (process_partial_specialization): Error rather than crash on
            extra pack expansion.

  parent reply	other threads:[~2020-03-15 22:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-92068-4@http.gcc.gnu.org/bugzilla/>
2020-03-14  0:40 ` jason at gcc dot gnu.org
2020-03-14 21:13 ` cvs-commit at gcc dot gnu.org
2020-03-15 22:09 ` cvs-commit at gcc dot gnu.org [this message]
2020-03-15 22:09 ` cvs-commit at gcc dot gnu.org
2020-03-15 22:10 ` 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-92068-4-SA4FqfnTM1@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).