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/95952] [8 Regression] gcc-8 bootstrap failure on powerpc64-linux Date: Wed, 01 Jul 2020 22:43:55 +0000 [thread overview] Message-ID: <bug-95952-4-UR5eWBjPjE@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 Segher Boessenkool <segher at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |segher at gcc dot gnu.org --- Comment #7 from Peter Bergner <bergner at gcc dot gnu.org> --- 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? --- Comment #8 from Segher Boessenkool <segher at gcc dot gnu.org> --- So what is the instruction / builtin / anything where it fails?
next prev parent reply other threads:[~2020-07-01 22:43 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 [this message] 2020-07-01 23:28 ` mikpelinux at gmail dot com 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-UR5eWBjPjE@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: linkBe 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).