Hi,
here's my results:
Intel Core 2 Duo, 2.16GHz, 667MHz bus, 4MB Cache
running under OSX 10.5.2
please note that the auto-vectorizer of gcc-4.3 is doing really well
gr~~~
-
gcc version 4.0.1 (Apple Inc. build 5465)
xbook-2:temp thomas$ gcc -msse -O2 vec_bench.c -o vec
Am 22.03.2008 um 19:20 schrieb Travis E. Oliphant:
>I think the thing to do is to special-case the code so that if the
>strides work for vectorization, then a different bit of code is executed
>and this current code is used as the final special-case.
>Something like this would be relatively strai
for the noise,
Thomas
--
Thomas Grill
http://g.org
smime.p7s
Description: S/MIME cryptographic signature
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
Am 02.03.2008 um 04:24 schrieb Travis E. Oliphant:
Thomas Grill wrote:
Hi all,
i did some profiling on OS X/Intel 10.5 (numpy 1.0.4) and was
surprised to find calls to the system function feclearexcept to be by
far the biggest cpu hog, taking away about 30% of the cpu in my case.
Would it be
mp; fpstatus) ? UFUNC_FPE_UNDERFLOW : 0) \
| ((FE_INVALID& fpstatus) ? UFUNC_FPE_INVALID : 0); \
(void) feclearexcept(FE_DIVBYZERO | FE_OVERFLOW |\
FE_UNDERFLOW | FE_INVALID); \
} \
}
greetings, Thomas
--
Thomas Grill
http://g.o
