This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] A new meta intrinsic header file for current and future x86 instrinsics.

On Nov 21, 2008, at 4:20 PM, H.J. Lu wrote:
So "immintrin.h" is defined as "the header you #include for AVX", not as
"the header you #include to get current and future intel features"?

What difference does it make?

If AMD or another X86 vendor supports AVX some day, we need a header for
AVX. This header should be AVX only, not "random stuff intel has added in
the last 10 years".

Please take a look at what in gcc trunk today. The current structure supports
it with a 2 line change.

This is exactly the situation with the xmmintrin.h headers. What problem
are you trying to solve by deviating from the standard and established

The standard and established practice is to add a new Xmmintrin.h, which is immintrin.h, for a new ISA extension.

If your answer to the previous question is "immintrin.h is the header for AVX, and when we add new [non-"AVX 1"] stuff to the ISA it won't go in immintrin.h" then I have no objection to adding immintrin.h.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]