[ANN] macstl 0.2.1 -- portable SIMD toolkit beats the autovectorizing Intel ICC 8.1

glenlow@pixelglow.com (Glen Low)
16 Feb 2005 20:50:37 -0500

          From comp.compilers

Related articles
[ANN] macstl 0.2.1 -- portable SIMD toolkit beats the autovectorizing glenlow@pixelglow.com (2005-02-16)
| List of all articles for this month |

From: glenlow@pixelglow.com (Glen Low)
Newsgroups: comp.compilers
Date: 16 Feb 2005 20:50:37 -0500
Organization: http://groups.google.com
Keywords: tools, parallel

Thanks for all your patience and help with debugging macstl 0.2 --
especially Paul Baxter and Derek Piasecki who helped with AMD64
issues. I'm happy to announce the immediate availability of macstl
0.2.1, which features support for Intel ICC 8.1 on Windows and partial
support for IBM XLC++ 6.0 on Mac OS X.


macstl is a portable SIMD (single instruction multiple data) toolkit
featuring fast transcendental and integer division functions, complex
number arithmetic and cross-platform programming, all in an
easy-to-use syntax. macstl requires Mac OS X 10.3 or Windows 2000, XP
or Server 2003. The library is open-source and free when derived code
is reciprocated, otherwise it is $99 for a Personal license and $499
for a Corporate License.

Here's the list of changes:

* Fixed member and binary min and max for vec <unsigned short, 4>
* Fixed #include error with own projects [DCh].
* Added support for Intel ICC 8.1 [ACu].
* Fixed truncation of signed constants in unsigned parameters [DPi].
* Added partial support for IBM XLC 6.0.
* Fixed header access paths and missing functions malloc, free,
vm_allocate, vm_copy, vm_deallocate for Codewarrior.
* Fixed #include <sys/mman.h> error, domain in trigonometric test for
VC++. Improved inlining for ICC.

I haven't got the latest benchmarks up yet, but so far macstl 0.2.1
beats the autovectorizing Intel ICC -- some 2x to 16x faster than
autovectorized code!!

Cheers, Glen Low
pixelglow software | simply brilliant stuff

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.