diff options
author | nsz <nsz@port70.net> | 2012-03-17 13:46:15 +0100 |
---|---|---|
committer | nsz <nsz@port70.net> | 2012-03-17 13:46:15 +0100 |
commit | 88cfaf8a142a8c57beccb89398a6421c4bbf121a (patch) | |
tree | e31d28a5aac16410d4a0b5d59c871f507cf2d78a /src/fenv/fenv.c | |
parent | d3fc724759ef08a8032e76e14f8cd96bfb837e17 (diff) | |
download | musl-88cfaf8a142a8c57beccb89398a6421c4bbf121a.tar.gz musl-88cfaf8a142a8c57beccb89398a6421c4bbf121a.tar.bz2 musl-88cfaf8a142a8c57beccb89398a6421c4bbf121a.tar.xz musl-88cfaf8a142a8c57beccb89398a6421c4bbf121a.zip |
fix i386 fegetround and make fesetround faster
Note that the new fesetround has slightly different semantics:
Storing the floating-point environment with fnstenv makes the
next fldenv (or fldcw) "non-signaling", so unmasked and pending
exceptions does not invoke the exception handler.
(These are rare since exceptions are handled immediately and by
default all exceptions are masked anyway. But if one manually
unmasks an exception in the control word then either sets the
corresponding exception flag in the status word or the execution
of an exception raising floating-point operation gets interrupted
then it may happen).
So the old implementation did not trap in some rare cases
where the new implementation traps.
However POSIX does not specify anything like the x87 exception
handling traps and the fnstenv/fldenv pair is significantly slower
than the fnstcw/fldcw pair (new code is about 5x faster here and
it's dominated by the function call overhead).
Diffstat (limited to 'src/fenv/fenv.c')
0 files changed, 0 insertions, 0 deletions