Anne Archibald wrote:
> This particular
> feature - seterr - is the sort of thing an overaggressive optimizer
> can easily butcher, though, so it could easily be the result of the
> particular configuration on the buildbot machine.
gcc claims to be IEEE compliant at all level of optimizations (-O*):
"""
-ffast-math:
Sets -fno-math-errno, -funsafe-math-optimizations,
-fno-trapping-math, -ffinite-math-only, -fno-rounding-math,
-fno-signaling-nans and fcx-limited-range.
This option causes the preprocessor macro "__FAST_MATH__" to
be defined.
This option should never be turned on by any -O option since
it can result in incorrect output for programs which depend on an exact
implementation of IEEE or ISO rules/specifications for math functions.
"""
So I don't think that's the problem.
cheers,
David
_______________________________________________
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
