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/65569] New: Fix for PR target/65240 causes a regression in building Spec for power4/power5/power6 Date: Wed, 25 Mar 2015 18:55:00 -0000 [thread overview] Message-ID: <bug-65569-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65569 Bug ID: 65569 Summary: Fix for PR target/65240 causes a regression in building Spec for power4/power5/power6 Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: major Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: meissner at gcc dot gnu.org CC: pthaugen at us dot ibm.com Host: powerpc64-unknown-linux-gnu Target: powerpc64-unknown-linux-gnu Build: powerpc64-unknown-linux-gnu The fix for PR target/65240 causes a regression in building the dealII benchmark for 64-bit power4/power5/power6 systems. The reason is the fix eliminated support for floating point constants being in RTL other than 0.0 on VSX systems. The extenddftf2_fprs pattern expects to be able to create a 0.0 to do the conversion, and for pre-VSX systems, you can't create a 0.0 in a register without doing a load.
next reply other threads:[~2015-03-25 18:42 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-25 18:55 meissner at gcc dot gnu.org [this message] 2015-03-25 18:56 ` [Bug target/65569] " meissner at gcc dot gnu.org 2015-03-25 18:56 ` meissner at gcc dot gnu.org 2015-03-25 21:35 ` meissner at gcc dot gnu.org 2015-03-26 8:34 ` meissner at gcc dot gnu.org 2015-03-26 8:35 ` meissner at gcc dot gnu.org 2015-03-26 8:44 ` meissner at gcc dot gnu.org 2015-10-02 18:54 ` meissner at gcc dot gnu.org 2015-10-02 20:57 ` meissner 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-65569-4@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).