This is the mail archive of the
mailing list for the GCC project.
Re: [PATCH] A new meta intrinsic header file for current and future x86 instrinsics.
- From: "H.J. Lu" <hjl dot tools at gmail dot com>
- To: "Chris Lattner" <clattner at apple dot com>
- Cc: "rajagopal, dwarak" <dwarak dot rajagopal at amd dot com>, "Uros Bizjak" <ubizjak at gmail dot com>, "Richard Guenther" <richard dot guenther at gmail dot com>, "Guo, Xuepeng" <xuepeng dot guo at intel dot com>, gcc-patches at gcc dot gnu dot org, jakub at redhat dot com, "Ye, Joey" <joey dot ye at intel dot com>, "Lin, Weiliang" <weiliang dot lin at intel dot com>, "Harle, Christophe" <christophe dot harle at amd dot com>, "Sebastian Pop" <sebpop at gmail dot com>
- Date: Fri, 21 Nov 2008 12:23:45 -0800
- Subject: Re: [PATCH] A new meta intrinsic header file for current and future x86 instrinsics.
- References: <820531547ADB6847AF89CC220F6128F1737F@pdsmsx001.ccr.corp.intel.com> <email@example.com> <firstname.lastname@example.org> <9E1304B144EBEB4C97F4162BFAC4788602D3AAB5@SAUSEXMB2.amd.com> <email@example.com> <9E1304B144EBEB4C97F4162BFAC4788602D3AAC8@SAUSEXMB2.amd.com> <firstname.lastname@example.org> <EDA71DF9-E597-4F94-BE64-B3C9CA6E4BCE@apple.com> <email@example.com> <5659869B-5D04-44A3-A1B5-FD125FDDF765@apple.com>
On Fri, Nov 21, 2008 at 11:03 AM, Chris Lattner <firstname.lastname@example.org> wrote:
> On Nov 21, 2008, at 10:55 AM, H.J. Lu wrote:
>> On Fri, Nov 21, 2008 at 10:07 AM, Chris Lattner <email@example.com>
>>> On Nov 21, 2008, at 10:04 AM, H.J. Lu wrote:
>>>>> Hi H.J,
>>>>> We have already responded that vendor specific header files are not a
>>>>> proposal that is acceptable to AMD.
>>>>> We agree with Uros and Richi's views that we should not have vendor
>>>>> specific header files. We should instead have architecture extension
>>>>> specific header files.
>>>> It is just a name, nothing more. You can call it <MyISAintrin.h> if you
>>> The X86 world has more than just Intel and AMD in it. Go by features,
>> We can have <x86intrin.h> which has
>> #include <immtrin.h> // ISA extensions from Intel
>> #include <myISAintrin.h> // ISA extensions from AMD
>> #include <yourISAintrin.h> // ISA extensions from XYZ
>> Intel, AMD and XYZ can add new ISA extensions to
>> their header files. It doesn't stop FOOBAR from
>> creating a processor which implements ISAs
>> from <immtrin.h>, <myISAintrin.h> and <yourISAintrin.h>.
> 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