- To: James Cloos <cloos@xxxxxxxxxxx>
- Subject: Re: AVX types: __m256d versus __v4sd
- From: Ian Lance Taylor <iant@xxxxxxxxxx>
- Date: Thu, 22 Mar 2012 14:04:59 -0700
- Cc: gcc-help@xxxxxxxxxxx
- Comment: DKIM? See http://www.dkim.org
- Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
- In-reply-to: <m3aa3874d5.fsf@carbon.jhcloos.org> (James Cloos's message of "Thu, 22 Mar 2012 16:43:58 -0400")
- User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)
James Cloos <cloos@xxxxxxxxxxx> writes:
>>>>>> "ILT" == Ian Lance Taylor <iant@xxxxxxxxxx> writes:
>
> ILT> Marc Glisse <marc.glisse@xxxxxxxx> writes:
>>> On the other hand, Intel only documents __m256d (the may_alias
>>> version), so portability says to use that one.
>
> ILT> Yes.
>
> Does that also apply for the __m128 types?
Yes.
> If so, do the current info docs (I've only looked at 4.6 and earlier)
> document that? Should they be updated to do so?
The gcc documentation does not document the use of the Intel
intrinsics. They are documented by Intel.
I would not be opposed to documenting these intrinsics in the gcc docs,
but there is nothing there at present.
Ian
[Linux C Programming]
[Linux Kernel]
[eCos]
[Fedora Development]
[Fedora Announce]
[Autoconf]
[The DWARVES Debugging Tools]
[Yosemite Campsites]
[Yosemite News]
[Linux GCC]