public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl dot tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/36992] New: Very stange code for _mm_move_epi64 Date: Fri, 01 Aug 2008 03:30:00 -0000 [thread overview] Message-ID: <bug-36992-682@http.gcc.gnu.org/bugzilla/> (raw) We should generate "movq" for _mm_move_epi64. But instead, we generate very strange code and never movq: [hjl@gnu-6 gcc]$ cat /tmp/m.c #include <emmintrin.h> __m128i test (__m128i b) { return _mm_move_epi64 (b); } [hjl@gnu-6 gcc]$ ./xgcc -B./ -S /tmp/m.c [hjl@gnu-6 gcc]$ cat m.s .file "m.c" .text .globl test .type test, @function test: .LFB493: pushq %rbp .LCFI0: movq %rsp, %rbp .LCFI1: movdqa %xmm0, -32(%rbp) movdqa -32(%rbp), %xmm0 movdqa %xmm0, %xmm0 movdq2q %xmm0, %mm0 movq %mm0, -40(%rbp) movq -40(%rbp), %rax movl $0, %edx movq %rax, -16(%rbp) movq %rdx, -8(%rbp) movdqu -16(%rbp), %xmm0 leave ret ... [hjl@gnu-6 gcc]$ ./xgcc -B./ -S /tmp/m.c -O2 [hjl@gnu-6 gcc]$ cat m.s .file "m.c" .text .p2align 4,,15 .globl test .type test, @function test: .LFB516: movhps .LC0(%rip), %xmm0 ret -- Summary: Very stange code for _mm_move_epi64 Product: gcc Version: 4.4.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: hjl dot tools at gmail dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36992
next reply other threads:[~2008-08-01 3:30 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-08-01 3:30 hjl dot tools at gmail dot com [this message] 2008-08-01 11:59 ` [Bug target/36992] " rguenth at gcc dot gnu dot org 2008-08-01 12:05 ` rguenth at gcc dot gnu dot org 2008-08-01 12:08 ` rguenth at gcc dot gnu dot org 2008-08-01 12:54 ` hjl dot tools at gmail dot com 2008-08-01 12:57 ` hjl dot tools at gmail dot com 2008-08-01 13:22 ` rguenth at gcc dot gnu dot org 2008-08-01 13:27 ` hjl dot tools at gmail dot com 2008-08-01 19:34 ` ubizjak at gmail dot com 2008-08-02 13:10 ` ubizjak at gmail dot com 2008-08-02 13:11 ` ubizjak at gmail dot com 2008-08-02 13:23 ` ubizjak at gmail dot com 2008-08-02 15:08 ` ubizjak at gmail dot com 2008-08-02 15:20 ` hjl dot tools at gmail dot com 2008-08-02 16:03 ` ubizjak at gmail dot com 2008-08-02 18:45 ` ubizjak at gmail dot com 2008-08-03 6:15 ` uros at gcc dot gnu dot org 2008-08-03 6:50 ` ubizjak at gmail dot com 2008-08-05 14:20 ` hjl dot tools at gmail dot com 2008-08-05 17:35 ` hjl dot tools at gmail dot com 2008-08-05 17:42 ` hjl at gcc dot gnu dot org 2008-08-07 13:18 ` hjl at gcc dot gnu dot org 2008-08-07 13:19 ` hjl dot tools 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=bug-36992-682@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).