public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "froydnj at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/47977] powerpc (-mcpu=8548) Wrong code for double operations in little endian mode
Date: Thu, 03 Mar 2011 16:51:00 -0000 [thread overview]
Message-ID: <bug-47977-4-8wQNFArMWW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47977-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47977
--- Comment #2 from froydnj at codesourcery dot com <froydnj at codesourcery dot com> 2011-03-03 16:51:18 UTC ---
On Thu, Mar 03, 2011 at 04:08:53PM +0000, m.lazzarotto at robox dot it wrote:
> lwz 9,8(1) # What's the purpose ?
> lwz 10,12(1) # What's the purpose ?
> stw 9,8(1) # What's the purpose ?
> stw 10,12(1) # What's the purpose ?
These are an artifact of the lower-subreg pass; the E500 bits contain
some logic to clean up spurious moves introduced by using E500
floating-point, but the lower-subreg pass stymies those bits of logic.
A separate bug for a (sub-)target-specific pass to clean those artifacts
up would be appropriate, but I don't think it's going to happen any time
soon.
next prev parent reply other threads:[~2011-03-03 16:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 16:09 [Bug c/47977] New: " m.lazzarotto at robox dot it
2011-03-03 16:22 ` [Bug target/47977] " jsm28 at gcc dot gnu.org
2011-03-03 16:51 ` froydnj at codesourcery dot com [this message]
2011-03-04 13:11 ` [Bug c/47977] " m.lazzarotto at robox dot it
2011-03-04 15:35 ` [Bug target/47977] " joseph at codesourcery dot com
2020-06-02 23:50 ` segher 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-47977-4-8wQNFArMWW@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).