MAINT: Use NPY_NAN* instead of NAN.

WarrenWeckesser · WarrenWeckesser · commit 5c010e6e767a · 2024-06-22T11:52:48.000-04:00
With some compilers, NAN is expanded to an expression that
is evaluated at runtime. That can cause various floating
point exception flags to be set, including FE_OVERFLOW.
diff --git a/numpy/_core/src/umath/funcs.inc.src b/numpy/_core/src/umath/funcs.inc.src
@@ -268,6 +268,7 @@ npy_ObjectClip(PyObject *arr, PyObject *min, PyObject *max) {
  * #ctype = npy_cfloat, npy_cdouble, npy_clongdouble#
  * #ftype = npy_float, npy_double, npy_longdouble#
  * #c = f, ,l#
+ * #C = F, ,L#
  */
 
 static void
@@ -321,8 +322,8 @@ nc_log1p@c@(@ctype@ *x, @ctype@ *r)
          *  +/- pi, otherwise it is +/- 0.0 (i.e. same as x_im).
          */
         if (npy_isnan(x_re)) {
-            npy_csetreal@c@(r, NAN);
-            npy_csetimag@c@(r, NAN);
+            npy_csetreal@c@(r, NPY_NAN@C@);
+            npy_csetimag@c@(r, NPY_NAN@C@);
         }
         else if (x_re >= -1) {
             /*
