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

[Chris Lattner <clattner at apple dot com>]

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".

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?

-Chris