From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 86335388A024; Thu,  2 Apr 2020 18:40:06 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 86335388A024
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1585852806;
 bh=q3qmapfIhMES+OcfO4NXbYhF0K08dcDQaAwCChpakkQ=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=Km1j1mU0rdHjSIP6cly9F92Ynp0xH3Phww4rLwcZkDipYfKJf/dMGcT7FtJ7gXOfZ
 mnazfwUTSEV+HR5BnaLU4M3OSprUfed5WBCcFDM9e1V4dS4g1vEW73/OeExcirGf1+
 pelY5FM06l6uPoR2/vwU4E/616kTr+tijORYGFiE=
From: "iains at gcc dot gnu.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 18:40:06 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-94454-4-2xz3T4BOdz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-94454-4@http.gcc.gnu.org/bugzilla/>
References: <bug-94454-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <http://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <http://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2020 18:40:06 -0000

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D94454

--- Comment #8 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Nathan Sidwell from comment #6)
> On 4/2/20 12:37 PM, iains at gcc dot gnu.org wrote:
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D94454
> >=20
> > --- 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 maki=
ng
> >> that very poor to increase collisions:
> > I bootstrapped with this patch, and then built a --disable-bootstrap wi=
th the
> > "spec_hasher::hash always returns 0" applied too.
>=20
> Ok, BTW spec_hasher::hash forwards to hash_tmpl_and_args.  They must=20
> agree, so ...
>=20
> > Neither made any difference, the entire ranges-v3 suite built without i=
ssue.
>=20
> surprises me.

hum .. both alter the code that's executed to compute the hash - which is t=
he
code that seems to be complaining.=20

So .. maybe I need to cook up something that computes the hash via the path
that's failing, but then throws it away... still might not exercise the cas=
e.=