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 D5EBD3858D37; Tue, 20 Sep 2022 06:54:14 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D5EBD3858D37
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1663656854;
	bh=DeXjZANDx4Fi0fsZ8cE8PSR4d2LGnRJUZ0LheVrEP+0=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=pg5Z7W8Q2iDkUP/XK4drJVVA4hSqv2caohqMQaEMEnLNHC6zeqHJa/XPkc7qgyS6n
	 4zzgfECCjY+pERC2Kr7boDYZXUSZTqwrDENsnyqUG0CFNWWliBFnDkV2jqieXR0SJK
	 fRW06+fVRhFupi8853tXu8YWYXtRnlX5bzRFa4x4=
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/106972] internal compiler error: in extract_insn, at
 recog.c:2770 on ARMeb when building gcc itself
Date: Tue, 20 Sep 2022 06:54:11 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 11.3.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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-106972-4-8gEwR0gQn7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-106972-4@http.gcc.gnu.org/bugzilla/>
References: <bug-106972-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=3D106972

--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Thomas Petazzoni from comment #2)
> Thanks for the quick feedback! I am not super familiar with iwmmxt, but a=
s I
> understand it is used in Marvell PXA270 and above. While these are fairly
> old indeed, their support is still maintained in the upstream Linux kerne=
l,
> so it would be odd to no longer have gcc support for them.

Marvell does not provide any support for them in the last 4 years or more. =
With
my Marvell hat on, it makes sense to remove the GCC support as it definitely
has bitrotten and I have no resources at all to do any upstream fixes for i=
t.=