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: Fri, 01 Sep 2006 19:56:00 -0000 [thread overview]
Message-ID: <20060901195605.7296.qmail@sourceware.org> (raw)
In-Reply-To: <bug-27287-11164@http.gcc.gnu.org/bugzilla/>
------- Comment #36 from dje at watson dot ibm dot com 2006-09-01 19:56 -------
Subject: Re: [4.1/4.2 Regression] returning constant double
What is confusing to me is that the r->r case is using evmergehi
and evmergelo. This is placing the value in both halves of the SIMD
register. It seems like this could have been done with two "mr".
It is ambiguous whether the pattern is trying to load the full 64
bit register or not.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27287
next prev parent reply other threads:[~2006-09-01 19:56 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
2006-08-31 14:24 ` dje at watson dot ibm dot com
2006-09-01 19:56 ` dje at watson dot ibm dot com [this message]
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=20060901195605.7296.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).