I wrote:
> which clearly indicates a problem with the feclearexcept() function.
But when feclearexcept() is buggy, the configure test
checking whether fesetexceptflag is guaranteed non-trapping...
is not conclusive: It may fail
- because feclearexcept is buggy,
- or because fesetexceptflag is trapping,
- or both.
The way to find out is to configure with gl_cv_func_fesetexceptflag_works1=yes
and look at the unit test results.
In this case, we see a test failure of test-fenv-except-state-2 (it crashes
due to SIGFPE). This proves that on this platform, the answer is: "both".
2023-11-06 Bruno Haible <br...@clisp.org>
fenv-exceptions-state-c99: Update doc regarding Minix.
* doc/posix-functions/fesetexceptflag.texi: Mention the Minix bug.
diff --git a/doc/posix-functions/fesetexceptflag.texi
b/doc/posix-functions/fesetexceptflag.texi
index 3523dbb8f8..7a3971a3a5 100644
--- a/doc/posix-functions/fesetexceptflag.texi
+++ b/doc/posix-functions/fesetexceptflag.texi
@@ -17,7 +17,7 @@
glibc 2.37/i386, glibc 2.37/x86_64,
@c https://sourceware.org/bugzilla/show_bug.cgi?id=30988
glibc 2.37/powerpc,
-musl libc, Mac OS X 10.5, mingw, Haiku.
+musl libc, Mac OS X 10.5, Minix 3.3, mingw, Haiku.
@item
This function clears too many floating-point exception flags on
@c https://sourceware.org/bugzilla/show_bug.cgi?id=30998
