[PATCH 3/4] Add ILP32 support to aarch64
Joseph Myers
joseph@codesourcery.com
Tue Aug 8 17:22:00 GMT 2017
On Tue, 8 Aug 2017, Szabolcs Nagy wrote:
> i think correct trapping is not guaranteed by glibc,
> only correct status flags when the function returns,
> so spurious inexact is not a problem if it is already
> raised, and then i expect better code gen for the
> inexact clearing approach:
Since we have APIs for enabling / disabling exception traps, I think it's
expected that any spurious exceptions raised internally will be raised
inside an feholdexcept context so the user doesn't see traps. (We do not
claim anything about the number of times a given exception is raised
within a function, beyond whether it's zero or nonzero, or about the order
in which different exceptions are raised by a function raising multiple
exceptions, or about which subexceptions are raised on architectures such
as powerpc that support subexceptions.)
--
Joseph S. Myers
joseph@codesourcery.com
More information about the Libc-alpha
mailing list