public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wilson 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: Sat, 14 Mar 2020 16:57:40 +0000	[thread overview]
Message-ID: <bug-94044-4-vbU1XxJ3Me@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 #9 from Jim Wilson <wilson at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #8)
> So perhaps to ease reproduction, tweak the hash function in this case to
> always return 0?

Yes, that works.  I just didn't have a chance to look at the hash function last
night.  With the hash function hacked I can reproduce for any target and any
-std=c++X value.

diff --git a/gcc/cp/pt.c b/gcc/cp/pt.c
index 789ccdb..4337928 100644
--- a/gcc/cp/pt.c
+++ b/gcc/cp/pt.c
@@ -1733,7 +1733,8 @@ hash_tmpl_and_args (tree tmpl, tree args)
 hashval_t
 spec_hasher::hash (spec_entry *e)
 {
-  return hash_tmpl_and_args (e->tmpl, e->args);
+  return 0;
+  //  return hash_tmpl_and_args (e->tmpl, e->args);
 }

 /* Recursively calculate a hash value for a template argument ARG, for use

  parent reply	other threads:[~2020-03-14 16:57 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 [this message]
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
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-vbU1XxJ3Me@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).