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++/94044] [10 Regression] internal compiler error: in comptypes, at cp/typeck.c:1490 on riscv64-unknown-linux-gnu and arm-eabi Date: Mon, 23 Mar 2020 10:41:21 +0000 [thread overview] Message-ID: <bug-94044-4-8gAXsOmYee@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94044-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94044 --- Comment #11 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:26b3e568a60e9fd851efb436531752a5e49e6419 commit r10-7330-g26b3e568a60e9fd851efb436531752a5e49e6419 Author: Nathan Sidwell <nathan@acm.org> Date: Mon Mar 23 03:39:49 2020 -0700 [PR94044] Fix ICE with sizeof<argumentpack> Thanks to Jim for figuring out how to reproduce the problem, I was able to apply pr94044-jig.diff to poorly hash the specialization table. (That places all the specializations of a particular template in the same bucket, forcing us to compare the arguments.) The testcase creates sizeof_exprs containing argument packs, and we can no longer use same_type_p on those. PR c++/94044 * tree.c (cp_tree_equal) [SIZEOF_EXPR]: Detect argument pack operand.
next prev parent reply other threads:[~2020-03-23 10:41 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-94044-4@http.gcc.gnu.org/bugzilla/> 2020-03-12 9:35 ` kito.cheng at gmail dot com 2020-03-12 11:14 ` nathan at gcc dot gnu.org 2020-03-13 13:33 ` nathan at gcc dot gnu.org 2020-03-13 16:12 ` kito.cheng at gmail dot com 2020-03-13 19:31 ` nathan at gcc dot gnu.org 2020-03-14 3:53 ` wilson at gcc dot gnu.org 2020-03-14 10:32 ` jakub at gcc dot gnu.org 2020-03-14 16:57 ` wilson at gcc dot gnu.org 2020-03-16 11:55 ` nathan at gcc dot gnu.org 2020-03-20 11:44 ` rguenth at gcc dot gnu.org 2020-03-23 10:41 ` cvs-commit at gcc dot gnu.org [this message] 2020-03-23 10:41 ` 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-94044-4-8gAXsOmYee@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).