public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug target/31667] Integer extensions vectorization could be improved
[not found] <bug-31667-4@http.gcc.gnu.org/bugzilla/>
@ 2012-02-22 13:21 ` xiaoyuanbo at yeah dot net
2021-08-15 23:28 ` pinskia at gcc dot gnu.org
2021-08-21 21:44 ` linux at carewolf dot com
2 siblings, 0 replies; 3+ messages in thread
From: xiaoyuanbo at yeah dot net @ 2012-02-22 13:21 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31667
xiaoyuanbo <xiaoyuanbo at yeah dot net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |xiaoyuanbo at yeah dot net
--- Comment #2 from xiaoyuanbo <xiaoyuanbo at yeah dot net> 2012-02-22 12:46:37 UTC ---
know as byte one it is simulor
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug target/31667] Integer extensions vectorization could be improved
[not found] <bug-31667-4@http.gcc.gnu.org/bugzilla/>
2012-02-22 13:21 ` [Bug target/31667] Integer extensions vectorization could be improved xiaoyuanbo at yeah dot net
@ 2021-08-15 23:28 ` pinskia at gcc dot gnu.org
2021-08-21 21:44 ` linux at carewolf dot com
2 siblings, 0 replies; 3+ messages in thread
From: pinskia at gcc dot gnu.org @ 2021-08-15 23:28 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31667
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
We produce this now:
movdqa x(%rip), %xmm1
pxor %xmm0, %xmm0
movdqa %xmm1, %xmm2
punpckhbw %xmm0, %xmm1
movaps %xmm1, y+16(%rip)
movdqa x+16(%rip), %xmm1
punpcklbw %xmm0, %xmm2
movaps %xmm2, y(%rip)
movdqa %xmm1, %xmm2
punpckhbw %xmm0, %xmm1
movaps %xmm1, y+48(%rip)
movdqa x+32(%rip), %xmm1
punpcklbw %xmm0, %xmm2
movaps %xmm2, y+32(%rip)
movdqa %xmm1, %xmm2
punpckhbw %xmm0, %xmm1
movaps %xmm1, y+80(%rip)
movdqa x+48(%rip), %xmm1
punpcklbw %xmm0, %xmm2
movaps %xmm2, y+64(%rip)
movdqa %xmm1, %xmm2
punpckhbw %xmm0, %xmm1
punpcklbw %xmm0, %xmm2
movaps %xmm1, y+112(%rip)
movaps %xmm2, y+96(%rip)
And even ICC produce a similar thing except scheduled differently.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug target/31667] Integer extensions vectorization could be improved
[not found] <bug-31667-4@http.gcc.gnu.org/bugzilla/>
2012-02-22 13:21 ` [Bug target/31667] Integer extensions vectorization could be improved xiaoyuanbo at yeah dot net
2021-08-15 23:28 ` pinskia at gcc dot gnu.org
@ 2021-08-21 21:44 ` linux at carewolf dot com
2 siblings, 0 replies; 3+ messages in thread
From: linux at carewolf dot com @ 2021-08-21 21:44 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31667
--- Comment #6 from Allan Jensen <linux at carewolf dot com> ---
(In reply to Andrew Pinski from comment #5)
> We produce this now:
>
> movdqa x(%rip), %xmm1
> pxor %xmm0, %xmm0
> movdqa %xmm1, %xmm2
> punpckhbw %xmm0, %xmm1
> movaps %xmm1, y+16(%rip)
> movdqa x+16(%rip), %xmm1
> punpcklbw %xmm0, %xmm2
> movaps %xmm2, y(%rip)
> movdqa %xmm1, %xmm2
> punpckhbw %xmm0, %xmm1
> movaps %xmm1, y+48(%rip)
> movdqa x+32(%rip), %xmm1
> punpcklbw %xmm0, %xmm2
> movaps %xmm2, y+32(%rip)
> movdqa %xmm1, %xmm2
> punpckhbw %xmm0, %xmm1
> movaps %xmm1, y+80(%rip)
> movdqa x+48(%rip), %xmm1
> punpcklbw %xmm0, %xmm2
> movaps %xmm2, y+64(%rip)
> movdqa %xmm1, %xmm2
> punpckhbw %xmm0, %xmm1
> punpcklbw %xmm0, %xmm2
> movaps %xmm1, y+112(%rip)
> movaps %xmm2, y+96(%rip)
>
> And even ICC produce a similar thing except scheduled differently.
I hope that is because you forgot -msse4.1?
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2021-08-21 21:44 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-31667-4@http.gcc.gnu.org/bugzilla/>
2012-02-22 13:21 ` [Bug target/31667] Integer extensions vectorization could be improved xiaoyuanbo at yeah dot net
2021-08-15 23:28 ` pinskia at gcc dot gnu.org
2021-08-21 21:44 ` linux at carewolf dot com
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).