http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59316
--- Comment #12 from joseph at codesourcery dot com <joseph at codesourcery dot com> --- One possibility would be to change libatomic/fenv.c to include a local atomic-fenv.h (for example) header instead of <fenv.h> (which would no longer need a configure check), so that if the generic file is OK for an architecture then that architecture would provide an atomic-fenv.h header in libatomic/config, defining the macros to correspond directly with the bits from the relevant status register (and any architecture without support would get a dummy atomic-fenv.h header not defining any of the macros). That way, the hook doesn't need any OS-dependence.