diff options
author | Maciej W. Rozycki <macro@codesourcery.com> | 2013-08-22 17:50:20 +0100 |
---|---|---|
committer | Maciej W. Rozycki <macro@codesourcery.com> | 2013-08-22 17:55:17 +0100 |
commit | b72ca61b71abd3e2d5b6cdb0680d7179f95be222 (patch) | |
tree | 79913c2c6a952e2eda419b7d0766df4c13b2f48b /po | |
parent | d1141ff6c875bc53c5ef6cd62b1bbfe91bdccd21 (diff) | |
download | glibc-b72ca61b71abd3e2d5b6cdb0680d7179f95be222.tar.gz glibc-b72ca61b71abd3e2d5b6cdb0680d7179f95be222.tar.xz glibc-b72ca61b71abd3e2d5b6cdb0680d7179f95be222.zip |
MIPS: Correct the handling of reserved FCSR bits
Reserved bits in the Floating-Point Control and Status Register (FCSR) should not be implicitly cleared by fedisableexcept or feenableexcept, there is no reason to. Among these are the 8 condition codes and one of the two bits reserved for architecture implementers (bits #22 & #21). As to the latter, there is no reason to treat any of them as reserved either, they should be user controllable and settable via __fpu_control override as the user sees fit. For example in processors implemented by MIPS Technologies, such as the 5Kf or the 24Kf, these bits are used to change the treatment of denormalised operands and tiny results: bit #22 is Flush Override (FO) and bit #21 is Flush to Nearest (FN). They cause non-IEEE-compliant behaviour, but some programs may have a use for such modes of operation; the library should not obstruct such use just as it does not for the architectural Flush to Zero (FS) bit (bit #24). Therefore the change adjusts the reserved mask accordingly and also documents the distinction between bits 22:21 and 20:18.
Diffstat (limited to 'po')
0 files changed, 0 insertions, 0 deletions