public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "meissner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/64205] [5 Regression] powerpc64-linux --with-cpu=G5 bootstrap failure Date: Tue, 03 Feb 2015 22:36:00 -0000 [thread overview] Message-ID: <bug-64205-4-6R0lv2Inn7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64205-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64205 --- Comment #4 from Michael Meissner <meissner at gcc dot gnu.org> --- Is -mcpu=power7 -mno-hard-dfp really a reasonable option? I built a toolchain using --with-cpu=power5 from subversion id 219607 on a powerpc64 linux system, and the system bootstrapped. If I compile the code that Peter mentioned using -m32 -O2 -fPIC -S foo01.c -mlong-double-128 -mno-minimal-toc -g -fbuilding-libgcc -fno-stack-protector -g -mcpu=power5, it compiles fine. As seger mentions, -mlra fixes this (but there are still problems with -mlra). It does fail if you enable the stfiwx instruction (added in power7), but disable DFP. How many people do this? I'm not sure this is a representation of the original bug. I suspect if you changed TARGET_NO_SDMODE_STACK in rs6000.h to eliminate the TARGET_DFP test it should work. #define TARGET_NO_SDMODE_STACK (TARGET_LFIWZX && TARGET_STFIWX)
next prev parent reply other threads:[~2015-02-03 22:36 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-12-05 23:52 [Bug target/64205] New: " amodra at gmail dot com 2014-12-08 13:35 ` [Bug target/64205] [5 Regression] " rguenth at gcc dot gnu.org 2014-12-11 11:49 ` rguenth at gcc dot gnu.org 2015-01-20 22:56 ` bergner at gcc dot gnu.org 2015-01-20 23:04 ` bergner at gcc dot gnu.org 2015-02-03 4:13 ` segher at gcc dot gnu.org 2015-02-03 22:36 ` meissner at gcc dot gnu.org [this message] 2015-02-03 22:46 ` meissner at gcc dot gnu.org 2015-02-05 20:54 ` meissner at gcc dot gnu.org 2015-02-05 20:55 ` meissner at gcc dot gnu.org 2015-02-06 19:16 ` meissner at gcc dot gnu.org 2015-02-06 19:34 ` jakub 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-64205-4-6R0lv2Inn7@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).