This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/36992] Very stange code for _mm_move_epi64
- From: "hjl dot tools at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 5 Aug 2008 14:19:09 -0000
- Subject: [Bug target/36992] Very stange code for _mm_move_epi64
- References: <bug-36992-682@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #18 from hjl dot tools at gmail dot com 2008-08-05 14:19 -------
With -msse4, we got
bash-3.2$ ./xgcc -B./ -msse4 -S
/export/gnu/src/gcc-work/gcc/gcc/testsuite/gcc.target/i386/pr36992-1.c
bash-3.2$ ./xgcc -B./ -msse4 -S
/export/gnu/src/gcc-work/gcc/gcc/testsuite/gcc.target/i386/pr36992-1.c -O2
bash-3.2$ cat pr36992-1.s
.file "pr36992-1.c"
.text
.p2align 4,,15
.globl test
.type test, @function
test:
.LFB516:
pextrq $0, %xmm0, %rax
pxor %xmm0, %xmm0
pinsrq $0, %rax, %xmm0
ret
Why can't we just emit movq pattern for _mm_move_epi64?
--
hjl dot tools at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36992