public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/63491] Ice in LRA with simple vector test case on power Date: Mon, 16 Mar 2015 21:45:00 -0000 [thread overview] Message-ID: <bug-63491-4-qEdHNAhh5m@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63491-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63491 --- Comment #11 from Peter Bergner <bergner at gcc dot gnu.org> --- Ok, I found the difference. The problem on the external gcc112 system (ie, the big-endian system) is that the system binutils doesn't support POWER8, so during gcc config/build, the power8 gcc support was disabled. I built/installed a new binutils and used that for my build and now my external build also ICEs. Vlad can you try using my build on gcc112? /home/bergner/gcc/build/gcc-fsf-mainline-r221324-2/gcc/xgcc -B/home/bergner/gcc/build/gcc-fsf-mainline-r221324-2/gcc -O1 -m64 -mcpu=power8 -mlra -S pr63491.i It uses /home/bergner/binutils/install/binutils-power8/bin/{as,ld}.
next prev parent reply other threads:[~2015-03-16 21:45 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-63491-4@http.gcc.gnu.org/bugzilla/> 2014-10-09 18:06 ` bergner at gcc dot gnu.org 2014-10-09 18:18 ` dje at gcc dot gnu.org 2014-10-10 15:18 ` bergner at gcc dot gnu.org 2015-02-13 16:51 ` vmakarov at gcc dot gnu.org 2015-02-18 21:24 ` bergner at gcc dot gnu.org 2015-03-10 19:12 ` vmakarov at gcc dot gnu.org 2015-03-10 21:39 ` bergner at gcc dot gnu.org 2015-03-11 22:10 ` bergner at gcc dot gnu.org 2015-03-12 16:02 ` bergner at gcc dot gnu.org 2015-03-16 21:45 ` bergner at gcc dot gnu.org [this message] 2015-03-18 17:22 ` vmakarov at gcc dot gnu.org 2015-03-19 22:12 ` vmakarov 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-63491-4-qEdHNAhh5m@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).