ENH: ufunc: Change object/reference handling code to treat NULL as Py_None more consistently

1 files changed, 6 insertions, 4 deletions

diff --git a/numpy/core/src/scalarmathmodule.c.src b/numpy/core/src/scalarmathmodule.c.src
index d1a66e101..418e81531 100644
--- a/numpy/core/src/scalarmathmodule.c.src
+++ b/numpy/core/src/scalarmathmodule.c.src
@@ -704,10 +704,12 @@ static PyObject *
     PyObject *ret;
     npy_@name@ arg1, arg2;
     /*
-     * NOTE: In gcc >= 4.1, the compiler will reorder floating point operations and
-     *       floating point error state checks.  In particular, the arithmetic operations
-     *       were being reordered so that the errors weren't caught.  Declaring this output
-     *       variable volatile was the minimal fix for the issue. (Ticket #1671)
+     * NOTE: In gcc >= 4.1, the compiler will reorder floating point
+     *       operations and floating point error state checks. In
+     *       particular, the arithmetic operations were being reordered
+     *       so that the errors weren't caught.  Declaring this output
+     *       variable volatile was the minimal fix for the issue.
+     *       (Ticket #1671)
      */
     volatile npy_@otyp@ out;
 #if @twoout@