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++/98116] [11 Regression] ICE in strip_typedefs, at cp/tree.c:1744 since r11-5663-g329ae1d7751346ba
Date: Mon, 07 Dec 2020 16:49:47 +0000 [thread overview]
Message-ID: <bug-98116-4-3vzpJVUvtN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98116-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98116
--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Nathan Sidwell <nathan@gcc.gnu.org>:
https://gcc.gnu.org/g:9d0eb0ae948f0fbee208cfb9a86133abea650f81
commit r11-5824-g9d0eb0ae948f0fbee208cfb9a86133abea650f81
Author: Nathan Sidwell <nathan@acm.org>
Date: Mon Dec 7 07:02:58 2020 -0800
c++: check alias match for specializations [PR98116]
This fixes the underlying problem my recent (backedout) changes to
array type creation uncovered. We had paths through
structural_comptypes that ignored alias templates, even when
significant. This adds the necessary checks.
PR c++/98116
gcc/cp/
* typeck.c (structural_comptypes): Move early outs to comptype.
Always check template-alias match when comparing_specializations.
(comptypes): Do early out checking here.
gcc/testsuite/
* g++.dg/template/pr98116.C: Remove dg-ice.
* g++.dg/template/pr98116-2.C: New.
next prev parent reply other threads:[~2020-12-07 16:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 9:31 [Bug c++/98116] New: " marxin at gcc dot gnu.org
2020-12-03 9:31 ` [Bug c++/98116] " marxin at gcc dot gnu.org
2020-12-03 12:34 ` nathan at gcc dot gnu.org
2020-12-03 16:43 ` cvs-commit at gcc dot gnu.org
2020-12-03 16:44 ` nathan at gcc dot gnu.org
2020-12-04 15:27 ` nathan at gcc dot gnu.org
2020-12-04 16:39 ` cvs-commit at gcc dot gnu.org
2020-12-07 16:49 ` cvs-commit at gcc dot gnu.org [this message]
2020-12-07 16:51 ` nathan 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-98116-4-3vzpJVUvtN@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).