public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/99920] [10 regression] ICE building gcc 10 on power 7 BE
Date: Wed, 07 Apr 2021 08:26:35 +0000	[thread overview]
Message-ID: <bug-99920-4-cDydYtRX7n@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99920-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from rguenther at suse dot de <rguenther at suse dot de> ---
On Wed, 7 Apr 2021, jakub at gcc dot gnu.org wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99920
> 
> --- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
> Built r152973 ../configure --disable-bootstrap --enable-languages=c,c++ ,
> installed and built gcc trunk with that as system compiler and can't reproduce
> it.  Maybe some SUSE patches or the SUSE compiler was configured a different
> way...

This is the SLES11 system compiler (the last BE SLES).  It's configured
with --with-cpu=power4 --enable-secureplt --with-long-double-128.  We
do have a patch with power7 enablement (but just recognizing the
command-line option, nothing else).  And yes, lots of more cobbled
up patches (and we never updated to a 4.3.6 baseline either).

That said, it's a bit too short notice to start digging into this
myself and honestly if FSF 4.3.4 and 4.3.6 are not affected I'd not
worry (and instead I'll see to fixing SLE11 instead if the need
arises).  SLE11 also has access to GCC 4.8.5 btw. (just with
binaries inconveniently named gcc-4.8).

  parent reply	other threads:[~2021-04-07  8:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-05 22:28 [Bug bootstrap/99920] New: " seurer at gcc dot gnu.org
2021-04-06  7:29 ` [Bug bootstrap/99920] " rguenth at gcc dot gnu.org
2021-04-06  7:31 ` jakub at gcc dot gnu.org
2021-04-06  9:24 ` jakub at gcc dot gnu.org
2021-04-06 13:02 ` seurer at gcc dot gnu.org
2021-04-06 13:09 ` rguenther at suse dot de
2021-04-06 13:30 ` jakub at gcc dot gnu.org
2021-04-06 16:04 ` jakub at gcc dot gnu.org
2021-04-06 17:11 ` seurer at gcc dot gnu.org
2021-04-06 17:40 ` seurer at gcc dot gnu.org
2021-04-07  8:13 ` jakub at gcc dot gnu.org
2021-04-07  8:26 ` rguenther at suse dot de [this message]
2021-04-07 17:57 ` seurer at gcc dot gnu.org
2021-04-07 18:56 ` jakub at gcc dot gnu.org
2021-04-08  8:55 ` rguenth at gcc dot gnu.org
2021-04-08 10:53 ` rguenth at gcc dot gnu.org
2021-04-08 11:19 ` rguenth at gcc dot gnu.org
2021-04-08 11:52 ` rguenth at gcc dot gnu.org
2021-04-08 11:53 ` rguenth at gcc dot gnu.org
2021-04-08 12:02 ` rguenth at gcc dot gnu.org
2021-04-08 14:15 ` seurer at gcc dot gnu.org
2022-01-11 11:10 ` [Bug bootstrap/99920] [10 regression] ICE building gcc 10 on power 7 BE with GCC 4.3.4 (SUSE) host compiler rguenth 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-99920-4-cDydYtRX7n@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).