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++/104107] [9/10/11 Regression] parsing crashes on class template instantiation since r9-6853-g17838af989014f5e
Date: Mon, 28 Mar 2022 19:13:19 +0000	[thread overview]
Message-ID: <bug-104107-4-rNRJCbhspJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104107-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:450e82794245c49248711f1479c491d84cb46c57

commit r11-9708-g450e82794245c49248711f1479c491d84cb46c57
Author: Jason Merrill <jason@redhat.com>
Date:   Thu Feb 10 17:57:38 2022 -0500

    c++: TTP in member alias template [PR104107]

    In the first testcase, coerce_template_template_parms was adding too much
of
    outer_args when coercing to match P's template parameters, so that when
    substituting into the 'const T&' parameter we got an unrelated template
    argument for T.  We should only add outer_args when the argument template
is
    a nested template.

            PR c++/104107
            PR c++/95036

    gcc/cp/ChangeLog:

            * pt.c (coerce_template_template_parms): Take full parms.
            Avoid adding too much of outer_args.
            (coerce_template_template_parm): Adjust.
            (template_template_parm_bindings_ok_p): Adjust.
            (convert_template_argument): Adjust.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp0x/alias-decl-ttp2.C: New test.
            * g++.dg/cpp1z/ttp2.C: New test.

  parent reply	other threads:[~2022-03-28 19:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-19  0:01 [Bug c++/104107] New: parsing crashes on class template instantiation gzoumix at hotmail dot com
2022-01-19  0:14 ` [Bug c++/104107] [9/10/11/12 Regression] " pinskia at gcc dot gnu.org
2022-01-19  0:30 ` pinskia at gcc dot gnu.org
2022-01-19  0:31 ` pinskia at gcc dot gnu.org
2022-01-19 10:57 ` rguenth at gcc dot gnu.org
2022-01-31 15:11 ` [Bug c++/104107] [9/10/11/12 Regression] parsing crashes on class template instantiation since r9-6853-g17838af989014f5e marxin at gcc dot gnu.org
2022-02-10 22:55 ` jason at gcc dot gnu.org
2022-02-15  5:06 ` cvs-commit at gcc dot gnu.org
2022-02-16  0:12 ` [Bug c++/104107] [9/10/11 " jason at gcc dot gnu.org
2022-03-28 19:13 ` cvs-commit at gcc dot gnu.org [this message]
2022-03-28 19:13 ` [Bug c++/104107] [9/10 " jason at gcc dot gnu.org
2022-05-27  9:47 ` [Bug c++/104107] [10 " rguenth at gcc dot gnu.org
2022-06-28 10:47 ` jakub at gcc dot gnu.org
2023-03-15 12:45 ` cvs-commit at gcc dot gnu.org
2023-07-07  9:49 ` rguenth 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-104107-4-rNRJCbhspJ@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).