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 fesetexceptfl
On Minix 3.3, I see these test failures:
FAIL: test-fenv-except-state-1
==
../../gltests/test-fenv-except-state-1.c:62: assertion 'fetestexcept
(FE_OVERFLOW) == FE_OVERFLOW' failed
FAIL test-fenv-except-state-1 (exit status: 134)
FAIL: test-fenv-except-tracking-4
==
