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++/103769] [11/12 Regression] checking ICE in hashtab_chk_error with alias template and pack expansion after r11-7931 Date: Mon, 28 Mar 2022 13:37:08 +0000 [thread overview] Message-ID: <bug-103769-4-g9dKPhAmOf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103769-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103769 --- Comment #9 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:07be8f8da4c6840a1fd6b2229b147e50cc6f03dc commit r12-7848-g07be8f8da4c6840a1fd6b2229b147e50cc6f03dc Author: Jason Merrill <jason@redhat.com> Date: Fri Mar 25 11:26:06 2022 -0400 c++: ICE with alias in pack expansion [PR103769] This was breaking because when we stripped the 't' typedef in s<t<Args>...> to be s<Args...>, the TYPE_MAIN_VARIANT of "Args..." was still "t<Args>...", because type pack expansions are treated as types. Fixed by using the right function to copy a "type". PR c++/99445 PR c++/103769 gcc/cp/ChangeLog: * tree.cc (strip_typedefs): Use build_distinct_type_copy. gcc/testsuite/ChangeLog: * g++.dg/cpp0x/variadic-alias5.C: New test.
next prev parent reply other threads:[~2022-03-28 13:37 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-19 16:39 [Bug c++/103769] New: ICE in hashtab_chk_error alias template and pack expansion ppalka at gcc dot gnu.org 2021-12-19 16:42 ` [Bug c++/103769] [11/12 Regression] checking ICE in hashtab_chk_error with alias template and pack expansion after r11-7931 ppalka at gcc dot gnu.org 2021-12-30 16:13 ` pinskia at gcc dot gnu.org 2021-12-30 16:18 ` pinskia at gcc dot gnu.org 2022-01-01 4:19 ` pinskia at gcc dot gnu.org 2022-01-07 8:05 ` slyfox at gcc dot gnu.org 2022-01-07 9:09 ` slyfox at gcc dot gnu.org 2022-01-07 9:27 ` marxin at gcc dot gnu.org 2022-01-08 20:02 ` slyfox at gcc dot gnu.org 2022-01-17 12:37 ` rguenth at gcc dot gnu.org 2022-03-23 14:10 ` jason at gcc dot gnu.org 2022-03-28 13:37 ` cvs-commit at gcc dot gnu.org [this message] 2022-03-28 19:13 ` [Bug c++/103769] [11 " cvs-commit at gcc dot gnu.org 2022-03-28 19:14 ` jason at gcc dot gnu.org 2022-03-29 19:02 ` alexander.lelyakin at googlemail dot com 2022-11-30 5:27 ` pinskia 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-103769-4-g9dKPhAmOf@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: linkBe 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).