This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: AVX types: m256d versus v4sd

From: James Cloos <cloos at jhcloos dot com>
To: Ian Lance Taylor <iant at google dot com>
Cc: gcc-help at gcc dot gnu dot org
Date: Thu, 22 Mar 2012 17:12:41 -0400
Subject: Re: AVX types: __m256d versus __v4sd
Copyright: Copyright 2012 James Cloos
Openpgp: ED7DAEA6; url=http://jhcloos.com/public_key/0xED7DAEA6.asc
Openpgp-fingerprint: E9E9 F828 61A4 6EA9 0F2B 63E7 997A 9F17 ED7D AEA6
References: <alpine.DEB.2.02.1203182010020.2543@laptop-mg.saclay.inria.fr> <mcrehsnkzj4.fsf@dhcp-172-18-216-180.mtv.corp.google.com> <m3aa3874d5.fsf@carbon.jhcloos.org> <mcr3990bb44.fsf@dhcp-172-18-216-180.mtv.corp.google.com>

>>>>> "ILT" == Ian Lance Taylor <iant@google.com> writes:

ILT> The gcc documentation does not document the use of the Intel
ILT> intrinsics.  They are documented by Intel.

I was thinking of (gcc.info.bz2)X86 Built-in Functions, documenting such
builtins as v2df __builtin_ia32_hsubpd (v2df, v2df) and the like.

-JimC
-- 
James Cloos <cloos@jhcloos.com>         OpenPGP: 1024D/ED7DAEA6

Follow-Ups:
- Re: AVX types: __m256d versus __v4sd
  - From: Ian Lance Taylor

References:
- AVX types: __m256d versus __v4sd
  - From: Marc Glisse
- Re: AVX types: __m256d versus __v4sd
  - From: Ian Lance Taylor
- Re: AVX types: __m256d versus __v4sd
  - From: James Cloos
- Re: AVX types: __m256d versus __v4sd
  - From: Ian Lance Taylor

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: AVX types: __m256d versus __v4sd

Re: AVX types: m256d versus v4sd