public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <bug-106972-4-8gEwR0gQn7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106972-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106972

--- 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 as 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 kernel,
> 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 it.

  parent reply	other threads:[~2022-09-20  6:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-20  6:24 [Bug c/106972] New: " thomas.petazzoni@free-electrons.com
2022-09-20  6:32 ` [Bug target/106972] " pinskia at gcc dot gnu.org
2022-09-20  6:48 ` thomas.petazzoni@free-electrons.com
2022-09-20  6:54 ` pinskia at gcc dot gnu.org [this message]
2022-09-20 14:52 ` rearnsha at gcc dot gnu.org
2022-09-20 15:00 ` thomas.petazzoni@free-electrons.com
2022-09-20 15:10 ` rearnsha at gcc dot gnu.org
2022-09-25 19:43 ` thomas.petazzoni@free-electrons.com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-106972-4-8gEwR0gQn7@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).