public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/100108] [10/11 Regression] powerpc: recognize 32-bit CPU as POWER9 with -misel option
Date: Mon, 19 Apr 2021 14:52:30 +0000	[thread overview]
Message-ID: <bug-100108-4-hMqbJwkph6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100108-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Segher Boessenkool <segher at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #1)
> e500 support had been moved to the powerpcspe target; so assuming power9 for
> -misel is correct.
> 
> e500mc support is still there though.

There never *was* separate e500 support in GCC!

  parent reply	other threads:[~2021-04-19 14:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16  2:02 [Bug target/100108] New: [10 " rin at NetBSD dot org
2021-04-16  7:33 ` [Bug target/100108] [10/11 " rguenth at gcc dot gnu.org
2021-04-16 13:16 ` pinskia at gcc dot gnu.org
2021-04-16 13:50 ` rin at NetBSD dot org
2021-04-19 14:32 ` jakub at gcc dot gnu.org
2021-04-19 14:52 ` segher at gcc dot gnu.org [this message]
2021-04-19 14:59 ` segher at gcc dot gnu.org
2021-04-19 15:00 ` segher at gcc dot gnu.org
2021-04-19 15:03 ` jakub at gcc dot gnu.org
2021-04-20  1:02 ` rin at NetBSD dot org
2021-04-20 13:43 ` [Bug target/100108] [10/11/12 " cvs-commit at gcc dot gnu.org
2021-04-20 13:55 ` cvs-commit at gcc dot gnu.org
2021-04-20 14:58 ` [Bug target/100108] [10 " segher at gcc dot gnu.org
2021-04-22  0:49 ` rin at NetBSD dot org
2021-05-10 22:00 ` cvs-commit at gcc dot gnu.org
2021-05-10 22:01 ` segher at gcc dot gnu.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-100108-4-hMqbJwkph6@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).