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 180453858CD1; Thu, 29 Jun 2023 19:13:36 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 180453858CD1
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1688066016;
	bh=Rin2dzn2rp6F0gfl+dNH9gWqIC2lFGbH2smv8Tuh8YI=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=wA1UaqBbZ1LwkeD0vdELbzkjuBgXbfshbfE+krwmW4PJbqJuOHMo47dv6Y0vXd+Cl
	 K/hQXs4p1x+YZIMRYzUeZKKmOSjRuNgwrfYu+VpO9uUa0AJUx8QfWGj5IkuA5sPvAv
	 XcLZPeXz5RDRuugSzPS1uy1RWk5wiIad09ss43kw=
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/110487] invalid wide Boolean value
Date: Thu, 29 Jun 2023 19:13:35 +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: 14.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: pinskia at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-110487-4-pivGYAIkU9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-110487-4@http.gcc.gnu.org/bugzilla/>
References: <bug-110487-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=3D110487

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Part of the issue is what does TYPE_PRECISION on BOOLEAN_TYPE really mean.=
=20
there are many more of these issues all over GCC about boolean types assumi=
ng
being TYPE_PRECISION =3D=3D 1 even and such.=