This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/24073] (vector float){a, b, 0, 0} code gen is not good
- From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 27 Sep 2005 14:33:29 -0000
- Subject: [Bug target/24073] (vector float){a, b, 0, 0} code gen is not good
- References: <20050927040602.24073.pinskia@gcc.gnu.org>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From pinskia at gcc dot gnu dot org 2005-09-27 14:33 -------
(In reply to comment #4)
> I think that following example wins the contest:
>
> vector float f(void) { return (vector float){ a, a, b, b}; }
For this, it is a different bug. The issue with the above is that ix86_expand_vector_init_duplicate check
for mmx_okay is bad.
Currently, we have
if (!mmx_ok && !TARGET_SSE)
but I if I change it to:
if (!mmx_ok)
we get:
movss _a, %xmm0
movss _b, %xmm1
unpcklps %xmm0, %xmm0
unpcklps %xmm1, %xmm1
movlhps %xmm1, %xmm0
Which looks ok to me. That testcase should be opened into another bug as it is obviously wrong.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24073