about summary refs log tree commit diff
path: root/src/thread/pthread_setspecific.c
diff options
context:
space:
mode:
authorRich Felker <dalias@aerifal.cx>2012-12-05 12:52:40 -0500
committerRich Felker <dalias@aerifal.cx>2012-12-05 12:52:40 -0500
commitb088f85582d8787911ef48449574bed4131b44a2 (patch)
tree24ff727622ed97f3467e4384a4fdba670745e6ba /src/thread/pthread_setspecific.c
parent91b05889098c65425920b4c3bcd0712b73ea97eb (diff)
downloadmusl-b088f85582d8787911ef48449574bed4131b44a2.tar.gz
musl-b088f85582d8787911ef48449574bed4131b44a2.tar.xz
musl-b088f85582d8787911ef48449574bed4131b44a2.zip
remove mips setjmp/longjmp code to save/restore fenv
nothing in the standard requires or even allows the fenv state to be
restored by longjmp. restoring the exception flags is not such a big
deal since it's probably valid to clobber them completely, but
restoring the rounding mode yields an observable side effect not
sanctioned by ISO C. saving/restoring it also wastes a few cycles and
16 bytes of code.

as for historical behavior, reportedly SGI IRIX did save/restore fenv,
and this is where glibc and uClibc got the behavior from. a few other
systems save/restore it too (on archs other than mips), even though
this is apparently wrong. further details are documented here:

http://www-personal.umich.edu/~williams/archive/computation/setjmp-fpmode.html

as musl aims for standards conformance rather than coddling historical
programs expecting non-conforming behavior, and as it's unlikely that
any historical programs actually depend on the incorrect behavior
(such programs would break on other archs, anyway), I'm making the
change not to save/restore fenv on mips.
Diffstat (limited to 'src/thread/pthread_setspecific.c')
0 files changed, 0 insertions, 0 deletions