This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: RFC: A new meta intrinsic header file for x86 intrinsics
- From: Jakub Jelinek <jakub at redhat dot com>
- To: "H.J. Lu" <hjl dot tools at gmail dot com>
- Cc: GCC Development <gcc at gcc dot gnu dot org>, "Ye, Joey" <joey dot ye at intel dot com>, "Guo, Xuepeng" <xuepeng dot guo at intel dot com>, "Girkar, Milind" <milind dot girkar at intel dot com>
- Date: Tue, 4 Nov 2008 10:47:04 +0100
- Subject: Re: RFC: A new meta intrinsic header file for x86 intrinsics
- References: <6dc9ffc80804041013mfdce2b4g61bf923e6dc9d66f@mail.gmail.com> <47FBDF5F.2010800@codesourcery.com> <20080409013801.GA13627@lucon.org> <47FC28A6.7080800@codesourcery.com> <6dc9ffc80811031417p714515cep15e7fdf9fee2653a@mail.gmail.com>
- Reply-to: Jakub Jelinek <jakub at redhat dot com>
On Mon, Nov 03, 2008 at 02:17:40PM -0800, H.J. Lu wrote:
> My question is if we should put AVX intrinsics directly in immintrin.h or in
> a separate file. If we put AVX and future intrinsics directly in immintrin.h,
> immintrin.h may become very large and harder to maintain. Another
> choice is to put AVX intrinsics in a separate file, saying avxintrin.h:
>
> #ifndef _IMMINTRIN_H_INCLUDED
> # error "Never use <avxintrin.h> directly; include <immintrin.h> instead."
> #else
> AVX intrinsics
> #endif /* _IMMINTRIN_H_INCLUDED */
I think a separate header with such an error is better.
Note, you can just #endif right after the error and put AVX intrinsics in
the file, no need to have everything inside of the #else.
Jakub