This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Status of SSE support in current gcc mainline
- To: David Korn <dkorn at pixelpower dot com>
- Subject: Re: Status of SSE support in current gcc mainline
- From: Jan Hubicka <jh at suse dot cz>
- Date: Fri, 23 Mar 2001 16:35:18 +0100
- Cc: "'Daniel Berlin'" <dberlin at redhat dot com>, kumar at chaos dot ph dot utexas dot edu, Dave Korn <davek-ml at ntlworld dot com>, Jan Hubicka <jh at suse dot cz>, Samuel Figueroa <figueroa at apple dot com>, Bernd Schmidt <bernds at cambridge dot redhat dot com>, gcc at gcc dot gnu dot org
- References: <718D38CAB6E0D011B2C90060970C28A56427B3@exchangeserver.pixelpower.com>
> >-----Original Message-----
> >From: Daniel Berlin [mailto:dberlin@redhat.com]
> >Sent: 23 March 2001 14:50
>
> >> Vectors are always 16 bytes on altivec. The doc states that 'p' is a
> >> pointer to a vector.
> >
> >I must have misread that part, i thought it also said that sizeof(p)
> >is 16, not sizeof(*p)==16.
>
> Well, whatever the actual case is, it's simply a thinko if the size of
> a pointer-to-vector is 16 bytes, and not an essential part of the
> programming model!
>
> >Errr, look at how, for instance, Intel does SSE programming. They have
> >a few datatypes defined, a whole bunch of intrinsics, and C++ classes
> >that encapsulate the intrinsics in a vector class, etc.
> >
> >They didn't make basic changes to the actual language to try to
> >accomodate their code.
>
> Do you have a pointer to any docs handy? I'd be interested to see this.
Just download the Intel's instruction set reference (you can get it via
search from www.intel.com). It contains definition of the extensions as well.
Honza