public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pluto at agmk dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/38320] missed movd opcode (32bits mm -> r/m32).
Date: Sun, 30 Nov 2008 10:25:00 -0000 [thread overview]
Message-ID: <20081130102349.21286.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38320-7667@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from pluto at agmk dot net 2008-11-30 10:23 -------
(In reply to comment #1)
> You need -mtune=core to generate "movd %xmm0, %rax". Gcc 4.4 works.
is movd faster only on core2 architecture?
and what about 32-bits?
$ /opt/gcc44/bin/gcc movd.c -O2 -S -march=core2 -m32
foo: pushl %ebp
movl %esp, %ebp
subl $16, %esp
movq %mm0, -16(%ebp) <===? movd mm0, eax
movl -16(%ebp), %eax <===/
leave
ret
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38320
next prev parent reply other threads:[~2008-11-30 10:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-29 23:58 [Bug target/38320] New: " pluto at agmk dot net
2008-11-30 0:53 ` [Bug target/38320] " hjl dot tools at gmail dot com
2008-11-30 10:25 ` pluto at agmk dot net [this message]
2008-11-30 11:45 ` ubizjak at gmail dot com
2009-09-17 9:10 ` ubizjak at gmail dot com
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=20081130102349.21286.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).