I've seen for a long time now problems in test-fenv.

Test: after fesetenv (FE_NOMASK_ENV) processes will abort
      when feraiseexcept (FE_DIVBYZERO) is called.
  Fail: Process didn't receive signal and exited with status 512.

(several times)

Test: after fesetenv (FE_NOMASK_ENV) processes will abort
      when feraiseexcept (FE_INVALID) is called.
  Fail: Process didn't receive signal and exited with status 512.

(also several times)

Test: after fesetenv (FE_NOMASK_ENV) processes will abort
      when feraiseexcept (FE_INEXACT) is called.
  Fail: Process didn't receive signal and exited with status 512.

... you get the picture.  Nobody else seeing this?  It's a G5, it
happens in 32 and 64 bit mode, and it is 100% reproducible.

-- 
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖