public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dje at watson dot ibm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/27287] [4.1/4.2 Regression] returning constant double
Date: Thu, 31 Aug 2006 13:50:00 -0000	[thread overview]
Message-ID: <20060831135016.1517.qmail@sourceware.org> (raw)
In-Reply-To: <bug-27287-11164@http.gcc.gnu.org/bugzilla/>



------- Comment #34 from dje at watson dot ibm dot com  2006-08-31 13:50 -------
Subject: Re:  [4.1/4.2 Regression] returning constant double 

>>>>> guenter at roeck-us dot net writes:

guenter> Hmm ... what would be the point ? evlwwsplat copies 32 bit memory
content into
guenter> the upper and lower 32 bits of the target register. The upper part is
not
guenter> needed in the given case, so moving data into it would not provide any
benefit.
guenter> Am I missing something ?

        Because the pattern is emitting evmergelo/evmergehi for the r->r
case, which is the equivalent data transfer and duplication, for no
apparent reason.

guenter> Would using evlwwsplat make subsequent optimizations more difficult ?
That
guenter> might be an argument against it. Other than that, I don't really care
which
guenter> opcodes to use, as long as the resulting code works.

        The choice of emitting mnemonics is performed as the very last
stage, so the compiler does not have any knowledge of this if the RTL
description does not express this.

David


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27287


  parent reply	other threads:[~2006-08-31 13:50 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-24 15:58 [Bug c/27287] New: pukes eliot at sonic dot net
2006-04-24 15:59 ` [Bug c/27287] pukes eliot at sonic dot net
2006-04-24 16:20 ` [Bug target/27287] loading 0 constant causes an ICE (freescale's messy targets) pinskia at gcc dot gnu dot org
2006-04-25 16:44 ` eliot at sonic dot net
2006-07-08  2:29 ` [Bug target/27287] [4.1/4.2 Regression] returning constant double pinskia at gcc dot gnu dot org
2006-07-08  2:29 ` pinskia at gcc dot gnu dot org
2006-07-08  2:35 ` pinskia at gcc dot gnu dot org
2006-07-08  2:37 ` pinskia at gcc dot gnu dot org
2006-07-08  3:14 ` dje at gcc dot gnu dot org
2006-07-13 16:08 ` edmar at freescale dot com
2006-07-13 16:31 ` dje at watson dot ibm dot com
2006-07-13 18:01 ` edmar at freescale dot com
2006-07-13 19:58 ` dje at watson dot ibm dot com
2006-07-13 20:09 ` edmar at freescale dot com
2006-07-13 20:36 ` dje at watson dot ibm dot com
2006-07-13 20:48 ` edmar at freescale dot com
2006-07-14 17:19 ` edmar at freescale dot com
2006-07-14 17:44 ` dje at gcc dot gnu dot org
2006-07-14 17:47 ` [Bug target/27287] [4.1 " dje at gcc dot gnu dot org
2006-07-26 20:23 ` dje at gcc dot gnu dot org
2006-07-26 20:26 ` dje at gcc dot gnu dot org
2006-08-29 19:12 ` guenter at roeck-us dot net
2006-08-29 19:26 ` dje at watson dot ibm dot com
2006-08-29 20:23 ` guenter at roeck-us dot net
2006-08-29 20:49 ` dje at gcc dot gnu dot org
2006-08-29 20:51 ` [Bug target/27287] [4.1/4.2 " pinskia at gcc dot gnu dot org
2006-08-29 21:09 ` dje at gcc dot gnu dot org
2006-08-30 15:16 ` guenter at roeck-us dot net
2006-08-30 18:00 ` guenter at roeck-us dot net
2006-08-30 18:08 ` dje at watson dot ibm dot com
2006-08-30 18:42 ` dje at watson dot ibm dot com
2006-08-30 20:40 ` guenter at roeck-us dot net
2006-08-31  2:36 ` dje at gcc dot gnu dot org
2006-08-31  5:15 ` guenter at roeck-us dot net
2006-08-31 13:50 ` dje at watson dot ibm dot com [this message]
2006-08-31 14:24 ` dje at watson dot ibm dot com
2006-09-01 19:56 ` dje at watson dot ibm dot com
2006-09-01 21:25 ` mmitchel at gcc dot gnu dot org
2006-09-02 13:23 ` guenter at roeck-us dot net
2006-09-11 17:05 ` dje at gcc dot gnu dot org
2006-09-13  5:25 ` [Bug target/27287] [4.1 " pinskia at gcc dot gnu dot org
2006-10-05 15:18 ` dje at gcc dot gnu dot org
2006-10-05 15:47 ` pinskia at gcc dot gnu dot 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=20060831135016.1517.qmail@sourceware.org \
    --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).