public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nathan at acm dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/94454] ICE 'canonical types differ for identical types' Date: Thu, 02 Apr 2020 16:50:40 +0000 [thread overview] Message-ID: <bug-94454-4-zZwZGRn7pB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94454-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94454 --- Comment #6 from Nathan Sidwell <nathan at acm dot org> --- On 4/2/20 12:37 PM, iains at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94454 > > --- Comment #5 from Iain Sandoe <iains at gcc dot gnu.org> --- > (In reply to Nathan Sidwell from comment #4) >> Oh, it is from the template specialization hash table. I suggest making >> that very poor to increase collisions: >> >> pt.c: >> static hashval_t >> hash_tmpl_and_args (tree tmpl, tree args) >> { >> hashval_t val = iterative_hash_object (DECL_UID (tmpl), 0); >> return val; // INSERT THIS LINE >> return iterative_hash_template_arg (args, val); >> } >> >> sorry for not realizing this earlier > > [not wishing to disturb the c-reduce sessions already started] > > On Darwin17 @r10-7488, which was always succeeding > > I bootstrapped with this patch, and then built a --disable-bootstrap with the > "spec_hasher::hash always returns 0" applied too. Ok, BTW spec_hasher::hash forwards to hash_tmpl_and_args. They must agree, so ... > Neither made any difference, the entire ranges-v3 suite built without issue. surprises me. > > Maybe that's informative in its own right. > > Will hopefully have some kind of reduced test-case for x86-64-linux tomorrow. >
next prev parent reply other threads:[~2020-04-02 16:50 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-02 12:28 [Bug c++/94454] New: " iains at gcc dot gnu.org 2020-04-02 12:28 ` [Bug c++/94454] " iains at gcc dot gnu.org 2020-04-02 12:38 ` iains at gcc dot gnu.org 2020-04-02 12:44 ` jakub at gcc dot gnu.org 2020-04-02 12:45 ` jakub at gcc dot gnu.org 2020-04-02 13:00 ` nathan at gcc dot gnu.org 2020-04-02 16:37 ` iains at gcc dot gnu.org 2020-04-02 16:50 ` nathan at acm dot org [this message] 2020-04-02 18:19 ` iains at gcc dot gnu.org 2020-04-02 18:40 ` iains at gcc dot gnu.org 2020-04-02 19:48 ` iains at gcc dot gnu.org 2020-04-13 19:13 ` nathan at gcc dot gnu.org 2020-04-13 19:24 ` iains at gcc dot gnu.org 2020-04-14 17:30 ` nathan at gcc dot gnu.org 2020-04-14 17:36 ` nathan at gcc dot gnu.org 2020-04-20 13:55 ` nathan at gcc dot gnu.org 2020-04-20 13:56 ` 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-94454-4-zZwZGRn7pB@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).