[Mingw-w64-public] Problem with intrinsics header files in gcc 4.9 and up : redux

In the intrin.h header there is an include of x86intrin.h whenever __GNUC__ is defined and we are compiling for x86 or x64. If you look at the x86intrin.h header file you will see it includes header files for all intrinsics regardless of whether the CPU feature exists or not. This is true for gcc

Re: [Mingw-w64-public] Problem with intrinsics header files in gcc 5.1 implementation

On 7/4/2015 7:42 AM, Edward Diener wrote: > In the intrin.h header there is an include of x86intrin.h whenever > __GNUC__ is defined and we are compiling for x86 or x64. > > If you look at the x86intrin.h header file you will see it includes > header files for all intrinsics. This leads to multiple

[Mingw-w64-public] Problem with intrinsics header files in gcc 5.1 implementation

In the intrin.h header there is an include of x86intrin.h whenever __GNUC__ is defined and we are compiling for x86 or x64. If you look at the x86intrin.h header file you will see it includes header files for all intrinsics. This leads to multiple typedefs using the same name for __m64, __m128,