summaryrefslogtreecommitdiff
path: root/numpy/core/include
diff options
context:
space:
mode:
authormattip <matti.picus@gmail.com>2018-05-10 09:42:17 +0300
committermattip <matti.picus@gmail.com>2018-05-10 09:42:17 +0300
commit1e00cc531007aa3418ad9deb7fbc5faaacce5795 (patch)
treed91a1a628429afc789c4d0553ad89c5bb168a400 /numpy/core/include
parentf5758d6fe15c2b506290bfc5379a10027617b331 (diff)
downloadnumpy-1e00cc531007aa3418ad9deb7fbc5faaacce5795.tar.gz
DOC: expand reasoning behind npy_*floatstatus_barrer()
Diffstat (limited to 'numpy/core/include')
-rw-r--r--numpy/core/include/numpy/npy_math.h5
1 files changed, 4 insertions, 1 deletions
diff --git a/numpy/core/include/numpy/npy_math.h b/numpy/core/include/numpy/npy_math.h
index 55e0fbc79..582390cdc 100644
--- a/numpy/core/include/numpy/npy_math.h
+++ b/numpy/core/include/numpy/npy_math.h
@@ -528,10 +528,13 @@ int npy_clear_floatstatus_barrier(char*);
int npy_get_floatstatus_barrier(char*);
/*
* use caution with these - clang and gcc8.1 are known to reorder calls
- * to this form of the function which can defeat the check
+ * to this form of the function which can defeat the check. The _barrier
+ * form of the call is preferable, where the argument is
+ * (char*)&local_variable
*/
int npy_clear_floatstatus(void);
int npy_get_floatstatus(void);
+
void npy_set_floatstatus_divbyzero(void);
void npy_set_floatstatus_overflow(void);
void npy_set_floatstatus_underflow(void);