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 81738383B6FD; Wed, 14 Dec 2022 12:26:24 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 81738383B6FD
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1671020784;
	bh=yb/XU2DAZL75doQ0CPs21scwbEprXZFGPWWOAQ9OGXg=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=nPjBLrbxfNTlGA0atLTPlfA2lIG3Ey2/9f5o2MtBT9sa2fmmyVuo7o1NmusTosumH
	 qm4CblV73LoBubotAknGk/2xVM3Fz3FRRO2Wiix/2S4unHfFlTiIcuJyMIBd38OyhC
	 EQ0Zbuv2qEr8YNsxLWW5vvLJ341fKdV0LchLEBRU=
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/108099] ICE when parsing signed __int128_t typedef
Date: Wed, 14 Dec 2022 12:26:24 +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: 12.2.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi 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: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-108099-4-HXaBo2b9Og@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-108099-4@http.gcc.gnu.org/bugzilla/>
References: <bug-108099-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
List-Id: <gcc-bugs.sourceware.org>

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

--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #2)
> (In reply to Jonathan Wakely from comment #1)
> > __int128_t is already a typedef, so you can't add a signed or unsigned
> > qualifier to it.
>=20
> i.e. the same reason this doesn't work:
>=20
> using I =3D int;
> signed I i =3D 0;

Hmm, actually g++ *does* allow this, unless you use -pedantic-errors:

using I =3D int;
using II =3D signed I;

It's not valid C++ though.=