[Bug target/28069] __m128 local variables don't get properly aligned.

2007-08-26 Thread zuxy dot meng at gmail dot com
--- Comment #5 from zuxy dot meng at gmail dot com 2007-08-26 07:58 --- *** This bug has been marked as a duplicate of 27537 *** -- zuxy dot meng at gmail dot com changed: What|Removed |Added

[Bug target/28069] __m128 local variables don't get properly aligned.

2006-09-23 Thread dannysmith at users dot sourceforge dot net
--- Comment #4 from dannysmith at users dot sourceforge dot net 2006-09-23 06:34 --- (In reply to comment #2) In a way this is a dup of bug 27537. Though there is an attribute to realign the stack in 4.2.0 so using that might just fix this issue instead. Indeed, 5c5 void

[Bug target/28069] __m128 local variables don't get properly aligned.

2006-09-20 Thread fxcoudert at gcc dot gnu dot org
--- Comment #3 from fxcoudert at gcc dot gnu dot org 2006-09-20 07:54 --- Not specific to mingw32. -- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added

[Bug target/28069] __m128 local variables don't get properly aligned.

2006-06-17 Thread zuxy dot meng at gmail dot com
--- Comment #1 from zuxy dot meng at gmail dot com 2006-06-17 06:25 --- Created an attachment (id=11685) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11685action=view) The file that gcc fails to compile correctly. Use gcc -S -msse and look at the assembly. GCC allocates __m128

[Bug target/28069] __m128 local variables don't get properly aligned.

2006-06-17 Thread pinskia at gcc dot gnu dot org
--- Comment #2 from pinskia at gcc dot gnu dot org 2006-06-17 06:30 --- (In reply to comment #1) Use gcc -S -msse and look at the assembly. GCC allocates __m128 locals directly on the stack without adjusting ESP, which might not be 16-byte aligned. But GCC uses movaps, which