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 0C0D13858C3A; Fri,  9 Jun 2023 13:14:01 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0C0D13858C3A
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1686316442;
	bh=Ei+X+WaH2m40hka1QGb4dOglJJLVn3RfqXoUQZMpltg=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=wYcq+32qCVw/kmdQ6LSaTYuOMp4ZuafIytGdbOAr/0HPILQt3Cp9I1svMtFKvs9Nd
	 Qs3+BKrAL4n4xY1X84r/m3RsaL1f2Xijgt1YtcbXgNkcgGiJX8duofZrTRDiRuXLHu
	 yKE5WDlQVerzsLQpKN72n31qjy1Sy6/cKy1INIrA=
From: "amacleod at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/109886] UBSAN error: shift exponent 64 is too large for
 64-bit type when compiling gcc.c-torture/compile/pr96796.c
Date: Fri, 09 Jun 2023 13:14:01 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amacleod at redhat dot com
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-109886-4-pAhkvy6RRT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-109886-4@http.gcc.gnu.org/bugzilla/>
References: <bug-109886-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=3D109886

--- Comment #10 from Andrew Macleod <amacleod at redhat dot com> ---
(In reply to Martin Jambor from comment #9)
> A buildbot run which checked out this revision unfortunately still reports
> this problem with UBSAN-bootstrapped compiler.

Oh, I see..  there's a second problem, and that is that range_cast doesn't
check if the type is supported before it blindly sets it to varying :-P

One more patcxh coming today to deal with that.. I was going to move cast to
the header file anyway, I will tweak the definition at the same time.=