Interesting. It's conceptually similar to the low-level vec interface
of macstl, although they don't mention macstl -- but given that it
dates from 2003 and the first public version of macstl is July 2003,
that makes sense.
vec <short, 8> A;
vec <short, 8> B;
vec <short, 8> C;
A = *pSrcA; // or A = vec <short, 8>::load (pSrcA);
B = *pSrcB; // or B = vec <short, 8>::load (pSrcB);
C = A + B;
The current macstl has a PERL script called macstlizer that tries to
parse regular C code using Altivec intrinsics and convert it to
macstl C++ code. Then there's a #include that maps most of the
Altivec intrinsics into equivalent SSE intrinsics. The preferred
option would be to use platform-independent operations such as +, but
that would be difficult to do accurately in a automated script
conversion, since the platform-independent ops are almost exactly
equivalent to their C/C++ language definitions, while the Altivec and
SSE ops have certain edge cases for certain types.
Do not post admin requests to the list. They will be ignored.
PerfOptimization-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden