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 7583C385829C; Tue, 20 Sep 2022 14:52:52 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7583C385829C
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1663685572;
	bh=Oejil3+Dj6W6kDXSBziLvxu4y0Y1/VH/XVAkzTLDA4w=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=UeHuS3NtF3I69nguTM4WI533Xj8jmK8CPPauuVj2hb1EvyjHkzaxEgUjPR9cDgTA3
	 hUA9l5YOSJ5ualNK5vJmreMttbLWOgPoFB0xHqeXeF8P/dEsGiUQnDcfcg8YvVeTFx
	 4xcSqzsq44lrJ6rE44aUjXGSZtK4Nvey3nQMTAJQ=
From: "rearnsha 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 14:52:52 +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: rearnsha 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-FQac5aE6Kw@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 #4 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
I don't think we're talking about removing support for the CPU, just support
for the iwmmxt extension.  That is, you can still use it as an Arm cpu, but
without the vector engine.=