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 bootstrap/97163] Build error with -mcpu=power9 on ppc64
Date: Tue, 22 Sep 2020 23:09:08 +0000	[thread overview]
Message-ID: <bug-97163-4-5FKnnyzWFP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97163-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Segher Boessenkool <segher at gcc dot gnu.org> ---
Ah.

Is there no better way to detect GCC impostors?  Oh well.

Since we require 4.5 as bootstrap compiler, this makes no difference
at all for compilers that truthfully claim to be GCC, so it has my
blessing if you want that :-)

Thanks!

  parent reply	other threads:[~2020-09-22 23:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-22 11:44 [Bug libstdc++/97163] New: " pkubaj at anongoth dot pl
2020-09-22 11:45 ` [Bug libstdc++/97163] " pkubaj at anongoth dot pl
2020-09-22 13:17 ` [Bug bootstrap/97163] " jakub at gcc dot gnu.org
2020-09-22 16:48 ` segher at gcc dot gnu.org
2020-09-22 16:54 ` jakub at gcc dot gnu.org
2020-09-22 21:32 ` segher at gcc dot gnu.org
2020-09-22 21:40 ` jakub at gcc dot gnu.org
2020-09-22 23:09 ` segher at gcc dot gnu.org [this message]
2020-09-26  8:09 ` cvs-commit at gcc dot gnu.org
2020-10-05  8:24 ` cvs-commit at gcc dot gnu.org
2021-04-16 12:37 ` pkubaj at anongoth dot pl
2021-04-20 23:29 ` cvs-commit at gcc dot gnu.org
2021-04-22 16:48 ` cvs-commit at gcc dot gnu.org
2021-04-22 17:06 ` jakub at gcc dot gnu.org
2021-09-11 14:29 ` pinskia 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-97163-4-5FKnnyzWFP@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).