You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I dug in a little bit, and the problem appears to be the compiler optimizing too liberally. If I add a printf between the operation and PyUFunc_getfperr() in scalarmathmodule.c.src, it works.
@name@_ctype_@oper@(arg1, arg2, &out);
printf("Result is %g\n", out);
#endif
#if @fperr@
/* Check status flag. If it is set, then look up what to do */
retstatus = PyUFunc_getfperr();
I'm guessing the compiler thinks it can reorder the float operation to after PyUFunc_getfperr, since PyUFunc_getfperr is independent of it except for the float exception state.
Original ticket http://projects.scipy.org/numpy/ticket/1671 on 2010-11-11 by @mwiebe, assigned to unknown.
All these cases should be raising, I believe:
The text was updated successfully, but these errors were encountered: