public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pali at kernel dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/108853] Add new -mcpu=e500 alias for -mcpu=8540
Date: Tue, 21 Feb 2023 23:02:18 +0000	[thread overview]
Message-ID: <bug-108853-4-3dPHngxqnP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108853-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Pali Rohár <pali at kernel dot org> ---
I'm still using processors with e500 cores with recent Linux kernel versions
and I know also other people who also still using them.

Note that NXP still supports some QorIQ processors which have integrated e500
cores. So it is not truth that they are no longer supported by FreeScale/NXP.

I know that e500 support was mostly removed out of GCC, but something is still
there.

And due to this removal, LLVM and clang recently gained some usable e500v2
implementation. I was told that it was heavily tested on FreeBSD with desktop
applications.

Also musl libc in last year got e500 support.

So, no, e500 cpu core is not dead and people still care about it.

  parent reply	other threads:[~2023-02-21 23:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-19 23:18 [Bug target/108853] New: " pali at kernel dot org
2023-02-21 22:48 ` [Bug target/108853] " pinskia at gcc dot gnu.org
2023-02-21 22:52 ` pinskia at gcc dot gnu.org
2023-02-21 23:02 ` pali at kernel dot org [this message]
2023-02-21 23:07 ` pinskia at gcc dot gnu.org
2023-05-08  9:58 ` pali at kernel dot org

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-108853-4-3dPHngxqnP@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).