Am 02.03.2008 um 04:24 schrieb Travis E. Oliphant:
if(__builtin_expect(fpstatus,0)) \
Why the use of __builtin_expect here instead of fpstatus == 0?
Oops, nevertheless it should rather be something like
if(__builtin_expect(fpstatus == 0,1))
or
if(__builtin_expect(fpstatus,0) == 0)
sorry f
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 p
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 possible to change UFUNC_CHECK_STATUS in ufu
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 possible to change UFUNC_CHECK_STATUS in ufuncobject.h in
a way that
