Andrew Pinski wrote:
Yes this was intentional, you should not be using the builtin functions,
instead use intrinsics from the header files.
I've just rewritten the code to use the intrinsics from the header files
(xmmintrin.h). It now reads _mm_foo() instead of __builtin_ia32_foo().
The problem n
As I have written in an earlier post here, I'm trying to vectorize some
loops with intrinsics and I have also got a gcc 4.1 snapshot (20050410).
However when I try to compile my code with the gcc-4.1 snapshot I get:
/msys/1.0/home/mingw/bin/gcc.exe -g -Wall -O3 -msse -mtune=pentium3
-DHAVE_CONF
Richard Guenther wrote:
Try
typedef float v4sf __attribute__((vector_size(16)));
note that the base type (float) now matters, and the vector size
is in bytes. This works even for gcc 3.3, so I don't know exactly
when it was introduced.
D'oh!
...but now I get a more serious problem
/msys/1.0/lo
Hi,
I just started to work on some loop vectorizing for my project. Some
weeks ago I got a snapshot of GCC-4.1-20050313. It compiled my code but
I was not able to get the auto-vectorization working. (Yes, I understand
why)
I decided to try sse intrinsics (X86 Built-in Functions as the manual
s
