Avoid raising unexpected floating point exceptions in libm

[dim]

Summary

When using clang with x86_64 CPUs that support AVX, some floating point
transformations may raise exceptions that would not have been raised by
the original code. To avoid this, use the -fp-exception-behavior=maytrap
flag, introduced in clang 10.0.0.

In particular, this fixes a number of test failures with ctanhf(3) and
ctanf(3), when libm is compiled with -mavx. An unexpected FE_INVALID
exception is then raised, because clang emits vdivps instructions to
perform certain divides. (The vdivps instruction operates on multiple
single-precision float operands simultaneously, but the exceptions may
be influenced by unused parts of the XMM registers. In this particular
case, it was calculating 0 / 0, which results in FE_INVALID.)

If -fp-exception-behavior=maytrap is specified however, clang uses
vdivss instructions instead, which work on one operand, and should not
raise unexpected exceptions.

Reported by: olivier
PR: 254911
MFC after: 1 week

[dim]

Note that we could also apply this flag *only* to lib/msun/src/s_ctanhf.c optionally, as this is the only case we know for certain that has issues with these spurious exceptions.

However, I guess that the performance gain from using e.g. vdivps and friends is not that shocking in libm. It would be nice if we also had performance tests next to functional tests... :)

[arichardson]

I had a similar patch locally using =strict, but it seems like maytrap should be sufficient.