public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikpelinux at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/95952] [8 Regression] gcc-8 bootstrap failure on powerpc64-linux
Date: Wed, 01 Jul 2020 23:28:18 +0000	[thread overview]
Message-ID: <bug-95952-4-ZB1kUDGlnf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95952-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from Mikael Pettersson <mikpelinux at gmail dot com> ---
(In reply to Peter Bergner from comment #7)
> I've tried many 32-bit builds, but cannot reproduce the error.  I tried with
> top of the releases/gcc-8 branch, using releases/gcc-8 branch at commit
> 09f2293fac1785681f8ceaf6ae6d2d5cfe519b08 and varying configure options. 
> That said, I am using a trunk binutils build from today, because I needed a
> 32-bit binutils.  What version of binutils are you using?

binutils-2.23.88.0.1-13.fc20.ppc64

I can build a recent binutils release and retry the gcc-8 bootstrap with that
tomorrow.  But since gcc-9/10/11 all bootstrap Ok, I find it difficult to
suspect it's a binutils issue.

  parent reply	other threads:[~2020-07-01 23:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-28 22:29 [Bug bootstrap/95952] New: [8.4.1 regression] " mikpelinux at gmail dot com
2020-06-29 10:43 ` [Bug bootstrap/95952] [8 Regression] " rguenth at gcc dot gnu.org
2020-06-29 13:33 ` [Bug target/95952] " wschmidt at gcc dot gnu.org
2020-06-29 16:13 ` willschm at gcc dot gnu.org
2020-06-29 16:33 ` bergner at gcc dot gnu.org
2020-06-29 16:59 ` bergner at gcc dot gnu.org
2020-06-29 17:23 ` mikpelinux at gmail dot com
2020-07-01 22:43 ` segher at gcc dot gnu.org
2020-07-01 23:28 ` mikpelinux at gmail dot com [this message]
2020-07-02 15:25 ` willschm at gcc dot gnu.org
2020-07-02 15:30 ` bergner at gcc dot gnu.org
2020-07-02 16:10 ` mikpelinux at gmail dot com
2020-07-13 22:04 ` willschm at gcc dot gnu.org
2020-07-13 22:06 ` willschm at gcc dot gnu.org
2020-07-14 16:41 ` mikpelinux at gmail dot com
2020-07-14 17:16 ` willschm at gcc dot gnu.org
2020-07-17 14:56 ` cvs-commit at gcc dot gnu.org
2020-07-21 14:37 ` willschm at gcc dot gnu.org
2020-07-21 14:38 ` willschm 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-95952-4-ZB1kUDGlnf@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).