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++/99445] [11 Regression] ICE in hashtab_chk_error, at hash-table.c:137 since r11-7011-g6e0a231a4aa2407b
Date: Wed, 31 Mar 2021 13:58:47 +0000 [thread overview]
Message-ID: <bug-99445-4-eNfXdnItrk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99445-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99445
--- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jason Merrill <jason@gcc.gnu.org>:
https://gcc.gnu.org/g:a2531859bf5bf6cf1f29c0dca85fd26e80904a5d
commit r11-7931-ga2531859bf5bf6cf1f29c0dca85fd26e80904a5d
Author: Jason Merrill <jason@redhat.com>
Date: Tue Mar 30 20:31:18 2021 -0400
c++: Alias template in pack expansion [PR99445]
In this testcase, iterative_hash_template_arg checks
alias_template_specialization_p to determine whether to treat a type as a
dependent alias, and structural_comptypes checks
dependent_alias_template_spec_p. Normally that difference isn't a problem
because canonicalizing template arguments strips non-dependent aliases, but
that wasn't happening for the pack expansion. Fixed thus.
gcc/cp/ChangeLog:
PR c++/99445
* tree.c (strip_typedefs): Handle TYPE_PACK_EXPANSION.
gcc/testsuite/ChangeLog:
PR c++/99445
* g++.dg/cpp0x/alias-decl-variadic1.C: New test.
next prev parent reply other threads:[~2021-03-31 13:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-07 9:28 [Bug other/99445] New: [11 Regression] ICE in doko at debian dot org
2021-03-08 8:34 ` [Bug c++/99445] [11 Regression] ICE in hashtab_chk_error, at hash-table.c:137 marxin at gcc dot gnu.org
2021-03-08 8:35 ` [Bug c++/99445] [11 Regression] ICE in hashtab_chk_error, at hash-table.c:137 since r11-7011-g6e0a231a4aa2407b marxin at gcc dot gnu.org
2021-03-08 8:57 ` rguenth at gcc dot gnu.org
2021-03-08 9:12 ` doko at debian dot org
2021-03-08 9:17 ` marxin at gcc dot gnu.org
2021-03-08 14:25 ` ppalka at gcc dot gnu.org
2021-03-08 14:41 ` marxin at gcc dot gnu.org
2021-03-09 11:45 ` jakub at gcc dot gnu.org
2021-03-16 9:25 ` marxin at gcc dot gnu.org
2021-03-31 0:14 ` jason at gcc dot gnu.org
2021-03-31 13:58 ` cvs-commit at gcc dot gnu.org [this message]
2021-03-31 21:32 ` jason at gcc dot gnu.org
2022-01-13 12:36 ` redi at gcc dot gnu.org
2022-01-13 17:27 ` redi at gcc dot gnu.org
2022-03-28 13:37 ` cvs-commit at gcc dot gnu.org
2022-03-28 19:13 ` cvs-commit 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-99445-4-eNfXdnItrk@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).