This is the mail archive of the gcc-patches@gcc.gnu.org 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 Fri, Nov 21, 2008 at 3:47 PM, Chris Lattner <clattner@apple.com> wrote:
>
> On Nov 21, 2008, at 1:59 PM, H.J. Lu wrote:
>
>> On Fri, Nov 21, 2008 at 1:48 PM, Chris Lattner <clattner@apple.com> wrote:
>>>
>>> On Nov 21, 2008, at 12:23 PM, H.J. Lu wrote:
>>>
>>>>>
>>>>> Your approach assumes there is value to having immtrin.h and
>>>>> myisaintrin.h.
>>>>> What value do you see there?  What audience are you serving?
>>>>>
>>>>> If there is no reason to have immtrin.h, there is no reason to proceed
>>>>> with
>>>>> this approach.
>>>>
>>>> There are always Xmmintrin.h for SSEs. We just added immintrin.h for
>>>> AVX.
>>>>
>>>
>>> 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
> practice?

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


-- 
H.J.


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