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 89CEE3858C20; Fri,  3 Feb 2023 08:49:51 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 89CEE3858C20
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1675414191;
	bh=IxWX0IFVyx/CHpWQfbZhdS0rQrd9MNlsdYKT5FNDRQE=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=YIYzTMxsBUR5XSiGwvZ/btqBroCYEfsii/yHVGkHRryW61z3GDMhX3SSOqTLKTmJF
	 NBbPYXQXHmw11IRKAeM2Jb0SmVdslpPI2Ah2MjWxOuf/IR7Tqq4j4P2u0FHEcOm5Rx
	 4n9NPr4LeW8i+c300jhye1VaLrH9k1gOpQLuev3g=
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/108639] [13 Regression] ICE on valid code at
 -O1 and above: in decompose, at wide-int.h:984 since r13-5578
Date: Fri, 03 Feb 2023 08:49:51 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 13.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: aldyh at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 13.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-108639-4-pPiWZSCafB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-108639-4@http.gcc.gnu.org/bugzilla/>
References: <bug-108639-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=3D108639

--- Comment #12 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
Yeah, I've been mulling around the idea of removing the type from storage of
both irange and frange.  It seems we need it for setting a type (setting the
endpoints for varying, querying HONOR_NANS, HONOR_INFINITIES,e tc), but not=
 in
the storage itself.  Something to keep in mind when moving to wide_ints.

It does seem we need to keep the sign and precision somewhere.  The precisi=
on
lives in the wide-int, but the sign bit still needs storage??=