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 61BF23858D37; Wed, 28 Jun 2023 22:19:31 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 61BF23858D37
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1687990771;
	bh=/IDN0fGbIysYu22OOCs9AXF9tLnDZrfIwHU7BA6aNq0=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=Ew2K+7mk0Tq+7r4M89mV+7PvnjADC1c2A8twYi62TkoJiwKsvXsAhSrLzF8CpT36C
	 4HFdvL06iAVSqAW7v9VfiuV+HYnCQ2t8Ll/Yp+cR0M4ziJCMD3UKcwXIgXkCkxIZw+
	 QMeyXq0IAhxOvr3tDu62VqArPKwSYqcMR7ZygmhA=
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/110461] [14 regression] ICE when building
 openh264 with new vector_type checking
Date: Wed, 28 Jun 2023 22:19:31 +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: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia 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: 14.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-110461-4-FRWzZL7nDz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-110461-4@http.gcc.gnu.org/bugzilla/>
References: <bug-110461-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=3D110461

--- Comment #8 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to David Binderman from comment #7)
> I get something similar with -O1 -march=3Dznver1.=20
>=20
> The problem seems to have started in the last couple of days:

Yes it is exactly the same issue. Also it started with r14-2150-gfe48f26513=
34bc
(which just added the extra checking to make sure TYPE_PRECISION was not be=
ing
used for vector types).=