subject:"\[Bug target\/54349\] _mm_cvtsi128_si64 unnecessary stores value at stack"

[Bug target/54349] _mm_cvtsi128_si64 unnecessary stores value at stack

2016-02-26 Thread solar-gcc at openwall dot com

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54349 --- Comment #11 from Alexander Peslyak --- Turns out that gcc 4.6.x to 4.8.x generating "movd" instead of "movq" is actually a deliberate hack, to support binutils older than 2.17 ("movq" support committed in 2005, released in 2006) and (presumab

[Bug target/54349] _mm_cvtsi128_si64 unnecessary stores value at stack

2016-02-26 Thread solar-gcc at openwall dot com

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54349 Alexander Peslyak changed: What|Removed |Added CC||solar-gcc at openwall dot com --- Co

[Bug target/54349] _mm_cvtsi128_si64 unnecessary stores value at stack

2013-04-29 Thread ubizjak at gmail dot com

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54349 Uros Bizjak changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|

[Bug target/54349] _mm_cvtsi128_si64 unnecessary stores value at stack

2013-04-29 Thread ubizjak at gmail dot com

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54349 Uros Bizjak changed: What|Removed |Added Target Milestone|--- |4.9.0 --- Comment #8 from Uros Bi

[Bug target/54349] _mm_cvtsi128_si64 unnecessary stores value at stack

2013-04-29 Thread ubizjak at gmail dot com

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54349 Uros Bizjak changed: What|Removed |Added Target||x86 URL|

[Bug target/54349] _mm_cvtsi128_si64 unnecessary stores value at stack

2013-04-29 Thread ubizjak at gmail dot com

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54349 Uros Bizjak changed: What|Removed |Added AssignedTo|hubicka at gcc dot gnu.org |ubizjak at gmail dot com --- Comm

[Bug target/54349] _mm_cvtsi128_si64 unnecessary stores value at stack

2013-04-28 Thread ubizjak at gmail dot com

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54349 Uros Bizjak changed: What|Removed |Added CC||Ganesh.Gopalasubramanian at

[Bug target/54349] _mm_cvtsi128_si64 unnecessary stores value at stack

2013-04-26 Thread neleai at seznam dot cz

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54349 --- Comment #4 from Ondrej Bilka 2013-04-27 01:06:45 UTC --- I found that AMD Bulldozer optimization guide states that moves from xmm to GPR register should be done directly:" 10.4 Moving Data Between General-Purpose and XMM/YMM Registe