- To: Ian Lance Taylor <iant@xxxxxxxxxx>
- Subject: Re: AVX types: __m256d versus __v4sd
- From: James Cloos <cloos@xxxxxxxxxxx>
- Date: Thu, 22 Mar 2012 16:43:58 -0400
- Cc: gcc-help@xxxxxxxxxxx
- Comment: DKIM? See http://www.dkim.org
- Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
- Copyright: Copyright 2012 James Cloos
- In-reply-to: <mcrehsnkzj4.fsf@dhcp-172-18-216-180.mtv.corp.google.com> (Ian Lance Taylor's message of "Tue, 20 Mar 2012 09:28:15 -0700")
- Openpgp: ED7DAEA6; url=http://jhcloos.com/public_key/0xED7DAEA6.asc
- Openpgp-fingerprint: E9E9 F828 61A4 6EA9 0F2B 63E7 997A 9F17 ED7D AEA6
- User-agent: Gnus/5.130004 (Ma Gnus v0.4) Emacs/24.0.94 (gnu/linux)
>>>>> "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?
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?
-JimC
--
James Cloos <cloos@xxxxxxxxxxx> OpenPGP: 1024D/ED7DAEA6
[Linux C Programming]
[Linux Kernel]
[eCos]
[Fedora Development]
[Fedora Announce]
[Autoconf]
[The DWARVES Debugging Tools]
[Yosemite Campsites]
[Yosemite News]
[Linux GCC]