1997-06-21 04:02:21 +02:00
|
|
|
/* FPU control word bits. Mips version.
|
2014-01-01 12:03:15 +01:00
|
|
|
Copyright (C) 1996-2014 Free Software Foundation, Inc.
|
1997-06-21 04:02:21 +02:00
|
|
|
This file is part of the GNU C Library.
|
1997-07-13 01:22:49 +02:00
|
|
|
Contributed by Olaf Flebbe and Ralf Baechle.
|
1997-06-21 04:02:21 +02:00
|
|
|
|
|
|
|
|
The GNU C Library is free software; you can redistribute it and/or
|
2001-07-06 06:56:23 +02:00
|
|
|
modify it under the terms of the GNU Lesser General Public
|
|
|
|
|
License as published by the Free Software Foundation; either
|
|
|
|
|
version 2.1 of the License, or (at your option) any later version.
|
1997-06-21 04:02:21 +02:00
|
|
|
|
|
|
|
|
The GNU C Library is distributed in the hope that it will be useful,
|
|
|
|
|
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
|
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
|
2001-07-06 06:56:23 +02:00
|
|
|
Lesser General Public License for more details.
|
1997-06-21 04:02:21 +02:00
|
|
|
|
2001-07-06 06:56:23 +02:00
|
|
|
You should have received a copy of the GNU Lesser General Public
|
2012-03-10 00:56:38 +01:00
|
|
|
License along with the GNU C Library. If not, see
|
|
|
|
|
<http://www.gnu.org/licenses/>. */
|
1997-06-21 04:02:21 +02:00
|
|
|
|
|
|
|
|
#ifndef _FPU_CONTROL_H
|
|
|
|
|
#define _FPU_CONTROL_H
|
|
|
|
|
|
1997-07-13 01:22:49 +02:00
|
|
|
/* MIPS FPU floating point control register bits.
|
1997-06-21 04:02:21 +02:00
|
|
|
*
|
1997-07-13 01:22:49 +02:00
|
|
|
* 31-25 -> floating point conditions code bits 7-1. These bits are only
|
|
|
|
|
* available in MIPS IV.
|
|
|
|
|
* 24 -> flush denormalized results to zero instead of
|
|
|
|
|
* causing unimplemented operation exception. This bit is only
|
|
|
|
|
* available for MIPS III and newer.
|
|
|
|
|
* 23 -> Condition bit
|
2013-08-22 18:50:20 +02:00
|
|
|
* 22-21 -> reserved for architecture implementers
|
MIPS: IEEE 754-2008 NaN encoding support
It has been a long practice for software using IEEE 754 floating-point
arithmetic run on MIPS processors to use an encoding of Not-a-Number
(NaN) data different to one used by software run on other processors.
And as of IEEE 754-2008 revision [1] this encoding does not follow one
recommended in the standard, as specified in section 6.2.1, where it
is stated that quiet NaNs should have the first bit (d1) of their
significand set to 1 while signalling NaNs should have that bit set to
0, but MIPS software interprets the two bits in the opposite manner.
As from revision 3.50 [2][3] the MIPS Architecture provides for
processors that support the IEEE 754-2008 preferred NaN encoding format.
As the two formats (further referred to as "legacy NaN" and "2008 NaN")
are incompatible to each other, tools have to provide support for the
two formats to help people avoid using incompatible binary modules.
The change is comprised of two functional groups of features, both of
which are required for correct support.
1. Dynamic linker support.
To enforce the NaN encoding requirement in dynamic linking a new ELF
file header flag has been defined. This flag is set for 2008-NaN
shared modules and executables and clear for legacy-NaN ones. The
dynamic linker silently ignores any incompatible modules it
encounters in dependency processing.
To avoid unnecessary processing of incompatible modules in the
presence of a shared module cache, a set of new cache flags has been
defined to mark 2008-NaN modules for the three ABIs supported.
Changes to sysdeps/unix/sysv/linux/mips/readelflib.c have been made
following an earlier code quality suggestion made here:
http://sourceware.org/ml/libc-ports/2009-03/msg00036.html
and are therefore a little bit more extensive than the minimum
required.
Finally a new name has been defined for the dynamic linker so that
2008-NaN and legacy-NaN binaries can coexist on a single system that
supports dual-mode operation and that a legacy dynamic linker that
does not support verifying the 2008-NaN ELF file header flag is not
chosen to interpret a 2008-NaN binary by accident.
2. Floating environment support.
IEEE 754-2008 features are controlled in the Floating-Point Control
and Status (FCSR) register and updates are needed to floating
environment support so that the 2008-NaN flag is set correctly and
the kernel default, inferred from the 2008-NaN ELF file header flag
at the time an executable is loaded, respected.
As the NaN encoding format is a property of GCC code generation that is
both a user-selected GCC configuration default and can be overridden
with GCC options, code that needs to know what NaN encoding standard it
has been configured for checks for the __mips_nan2008 macro that is
defined internally by GCC whenever the 2008-NaN mode has been selected.
This mode is determined at the glibc configuration time and therefore a
few consistency checks have been added to catch cases where compilation
flags have been overridden by the user.
The 2008 NaN set of features relies on kernel support as the in-kernel
floating-point emulator needs to be aware of the NaN encoding used even
on hard-float processors and configure the FPU context according to the
value of the 2008 NaN ELF file header flag of the executable being
started. As at this time work on kernel support is still in progress
and the relevant changes have not made their way yet to linux.org master
repository.
Therefore the minimum version supported has been artificially set to
10.0.0 so that 2008-NaN code is not accidentally run on a Linux kernel
that does not suppport it. It is anticipated that the version is
adjusted later on to the actual initial linux.org kernel version to
support this feature. Legacy NaN encoding support is unaffected, older
kernel versions remain supported.
[1] "IEEE Standard for Floating-Point Arithmetic", IEEE Computer
Society, IEEE Std 754-2008, 29 August 2008
[2] "MIPS Architecture For Programmers, Volume I-A: Introduction to the
MIPS32 Architecture", MIPS Technologies, Inc., Document Number:
MD00082, Revision 3.50, September 20, 2012
[3] "MIPS Architecture For Programmers, Volume I-A: Introduction to the
MIPS64 Architecture", MIPS Technologies, Inc., Document Number:
MD00083, Revision 3.50, September 20, 2012
2013-09-18 22:04:27 +02:00
|
|
|
* 20 -> reserved (read as 0, write with 0)
|
|
|
|
|
* 19 -> IEEE 754-2008 non-arithmetic ABS.fmt and NEG.fmt enable
|
|
|
|
|
* 18 -> IEEE 754-2008 recommended NaN encoding enable
|
1997-07-13 01:22:49 +02:00
|
|
|
* 17 -> cause bit for unimplemented operation
|
|
|
|
|
* 16 -> cause bit for invalid exception
|
|
|
|
|
* 15 -> cause bit for division by zero exception
|
|
|
|
|
* 14 -> cause bit for overflow exception
|
|
|
|
|
* 13 -> cause bit for underflow exception
|
|
|
|
|
* 12 -> cause bit for inexact exception
|
|
|
|
|
* 11 -> enable exception for invalid exception
|
|
|
|
|
* 10 -> enable exception for division by zero exception
|
|
|
|
|
* 9 -> enable exception for overflow exception
|
|
|
|
|
* 8 -> enable exception for underflow exception
|
|
|
|
|
* 7 -> enable exception for inexact exception
|
|
|
|
|
* 6 -> flag invalid exception
|
|
|
|
|
* 5 -> flag division by zero exception
|
|
|
|
|
* 4 -> flag overflow exception
|
|
|
|
|
* 3 -> flag underflow exception
|
|
|
|
|
* 2 -> flag inexact exception
|
|
|
|
|
* 1-0 -> rounding control
|
1997-06-21 04:02:21 +02:00
|
|
|
*
|
|
|
|
|
*
|
1997-07-13 01:22:49 +02:00
|
|
|
* Rounding Control:
|
|
|
|
|
* 00 - rounding to nearest (RN)
|
|
|
|
|
* 01 - rounding toward zero (RZ)
|
1999-02-16 10:35:56 +01:00
|
|
|
* 10 - rounding (up) toward plus infinity (RP)
|
1997-07-13 01:22:49 +02:00
|
|
|
* 11 - rounding (down)toward minus infinity (RM)
|
1997-06-21 04:02:21 +02:00
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#include <features.h>
|
|
|
|
|
|
2006-09-21 23:01:02 +02:00
|
|
|
#ifdef __mips_soft_float
|
|
|
|
|
|
|
|
|
|
#define _FPU_RESERVED 0xffffffff
|
|
|
|
|
#define _FPU_DEFAULT 0x00000000
|
|
|
|
|
typedef unsigned int fpu_control_t;
|
2012-12-04 23:07:03 +01:00
|
|
|
#define _FPU_GETCW(cw) (cw) = 0
|
|
|
|
|
#define _FPU_SETCW(cw) (void) (cw)
|
2006-09-21 23:01:02 +02:00
|
|
|
extern fpu_control_t __fpu_control;
|
|
|
|
|
|
|
|
|
|
#else /* __mips_soft_float */
|
|
|
|
|
|
2013-09-23 18:29:58 +02:00
|
|
|
/* Masks for interrupts. */
|
1997-07-13 01:22:49 +02:00
|
|
|
#define _FPU_MASK_V 0x0800 /* Invalid operation */
|
|
|
|
|
#define _FPU_MASK_Z 0x0400 /* Division by zero */
|
|
|
|
|
#define _FPU_MASK_O 0x0200 /* Overflow */
|
|
|
|
|
#define _FPU_MASK_U 0x0100 /* Underflow */
|
|
|
|
|
#define _FPU_MASK_I 0x0080 /* Inexact operation */
|
|
|
|
|
|
2013-09-23 18:29:58 +02:00
|
|
|
/* Flush denormalized numbers to zero. */
|
1997-07-13 01:22:49 +02:00
|
|
|
#define _FPU_FLUSH_TZ 0x1000000
|
1997-06-21 04:02:21 +02:00
|
|
|
|
MIPS: IEEE 754-2008 NaN encoding support
It has been a long practice for software using IEEE 754 floating-point
arithmetic run on MIPS processors to use an encoding of Not-a-Number
(NaN) data different to one used by software run on other processors.
And as of IEEE 754-2008 revision [1] this encoding does not follow one
recommended in the standard, as specified in section 6.2.1, where it
is stated that quiet NaNs should have the first bit (d1) of their
significand set to 1 while signalling NaNs should have that bit set to
0, but MIPS software interprets the two bits in the opposite manner.
As from revision 3.50 [2][3] the MIPS Architecture provides for
processors that support the IEEE 754-2008 preferred NaN encoding format.
As the two formats (further referred to as "legacy NaN" and "2008 NaN")
are incompatible to each other, tools have to provide support for the
two formats to help people avoid using incompatible binary modules.
The change is comprised of two functional groups of features, both of
which are required for correct support.
1. Dynamic linker support.
To enforce the NaN encoding requirement in dynamic linking a new ELF
file header flag has been defined. This flag is set for 2008-NaN
shared modules and executables and clear for legacy-NaN ones. The
dynamic linker silently ignores any incompatible modules it
encounters in dependency processing.
To avoid unnecessary processing of incompatible modules in the
presence of a shared module cache, a set of new cache flags has been
defined to mark 2008-NaN modules for the three ABIs supported.
Changes to sysdeps/unix/sysv/linux/mips/readelflib.c have been made
following an earlier code quality suggestion made here:
http://sourceware.org/ml/libc-ports/2009-03/msg00036.html
and are therefore a little bit more extensive than the minimum
required.
Finally a new name has been defined for the dynamic linker so that
2008-NaN and legacy-NaN binaries can coexist on a single system that
supports dual-mode operation and that a legacy dynamic linker that
does not support verifying the 2008-NaN ELF file header flag is not
chosen to interpret a 2008-NaN binary by accident.
2. Floating environment support.
IEEE 754-2008 features are controlled in the Floating-Point Control
and Status (FCSR) register and updates are needed to floating
environment support so that the 2008-NaN flag is set correctly and
the kernel default, inferred from the 2008-NaN ELF file header flag
at the time an executable is loaded, respected.
As the NaN encoding format is a property of GCC code generation that is
both a user-selected GCC configuration default and can be overridden
with GCC options, code that needs to know what NaN encoding standard it
has been configured for checks for the __mips_nan2008 macro that is
defined internally by GCC whenever the 2008-NaN mode has been selected.
This mode is determined at the glibc configuration time and therefore a
few consistency checks have been added to catch cases where compilation
flags have been overridden by the user.
The 2008 NaN set of features relies on kernel support as the in-kernel
floating-point emulator needs to be aware of the NaN encoding used even
on hard-float processors and configure the FPU context according to the
value of the 2008 NaN ELF file header flag of the executable being
started. As at this time work on kernel support is still in progress
and the relevant changes have not made their way yet to linux.org master
repository.
Therefore the minimum version supported has been artificially set to
10.0.0 so that 2008-NaN code is not accidentally run on a Linux kernel
that does not suppport it. It is anticipated that the version is
adjusted later on to the actual initial linux.org kernel version to
support this feature. Legacy NaN encoding support is unaffected, older
kernel versions remain supported.
[1] "IEEE Standard for Floating-Point Arithmetic", IEEE Computer
Society, IEEE Std 754-2008, 29 August 2008
[2] "MIPS Architecture For Programmers, Volume I-A: Introduction to the
MIPS32 Architecture", MIPS Technologies, Inc., Document Number:
MD00082, Revision 3.50, September 20, 2012
[3] "MIPS Architecture For Programmers, Volume I-A: Introduction to the
MIPS64 Architecture", MIPS Technologies, Inc., Document Number:
MD00083, Revision 3.50, September 20, 2012
2013-09-18 22:04:27 +02:00
|
|
|
/* IEEE 754-2008 compliance control. */
|
|
|
|
|
#define _FPU_ABS2008 0x80000
|
|
|
|
|
#define _FPU_NAN2008 0x40000
|
|
|
|
|
|
2013-09-23 18:29:58 +02:00
|
|
|
/* Rounding control. */
|
1997-07-13 01:22:49 +02:00
|
|
|
#define _FPU_RC_NEAREST 0x0 /* RECOMMENDED */
|
1997-06-21 04:02:21 +02:00
|
|
|
#define _FPU_RC_ZERO 0x1
|
1997-07-13 01:22:49 +02:00
|
|
|
#define _FPU_RC_UP 0x2
|
|
|
|
|
#define _FPU_RC_DOWN 0x3
|
2013-09-23 18:34:15 +02:00
|
|
|
/* Mask for rounding control. */
|
|
|
|
|
#define _FPU_RC_MASK 0x3
|
1997-06-21 04:02:21 +02:00
|
|
|
|
MIPS: IEEE 754-2008 NaN encoding support
It has been a long practice for software using IEEE 754 floating-point
arithmetic run on MIPS processors to use an encoding of Not-a-Number
(NaN) data different to one used by software run on other processors.
And as of IEEE 754-2008 revision [1] this encoding does not follow one
recommended in the standard, as specified in section 6.2.1, where it
is stated that quiet NaNs should have the first bit (d1) of their
significand set to 1 while signalling NaNs should have that bit set to
0, but MIPS software interprets the two bits in the opposite manner.
As from revision 3.50 [2][3] the MIPS Architecture provides for
processors that support the IEEE 754-2008 preferred NaN encoding format.
As the two formats (further referred to as "legacy NaN" and "2008 NaN")
are incompatible to each other, tools have to provide support for the
two formats to help people avoid using incompatible binary modules.
The change is comprised of two functional groups of features, both of
which are required for correct support.
1. Dynamic linker support.
To enforce the NaN encoding requirement in dynamic linking a new ELF
file header flag has been defined. This flag is set for 2008-NaN
shared modules and executables and clear for legacy-NaN ones. The
dynamic linker silently ignores any incompatible modules it
encounters in dependency processing.
To avoid unnecessary processing of incompatible modules in the
presence of a shared module cache, a set of new cache flags has been
defined to mark 2008-NaN modules for the three ABIs supported.
Changes to sysdeps/unix/sysv/linux/mips/readelflib.c have been made
following an earlier code quality suggestion made here:
http://sourceware.org/ml/libc-ports/2009-03/msg00036.html
and are therefore a little bit more extensive than the minimum
required.
Finally a new name has been defined for the dynamic linker so that
2008-NaN and legacy-NaN binaries can coexist on a single system that
supports dual-mode operation and that a legacy dynamic linker that
does not support verifying the 2008-NaN ELF file header flag is not
chosen to interpret a 2008-NaN binary by accident.
2. Floating environment support.
IEEE 754-2008 features are controlled in the Floating-Point Control
and Status (FCSR) register and updates are needed to floating
environment support so that the 2008-NaN flag is set correctly and
the kernel default, inferred from the 2008-NaN ELF file header flag
at the time an executable is loaded, respected.
As the NaN encoding format is a property of GCC code generation that is
both a user-selected GCC configuration default and can be overridden
with GCC options, code that needs to know what NaN encoding standard it
has been configured for checks for the __mips_nan2008 macro that is
defined internally by GCC whenever the 2008-NaN mode has been selected.
This mode is determined at the glibc configuration time and therefore a
few consistency checks have been added to catch cases where compilation
flags have been overridden by the user.
The 2008 NaN set of features relies on kernel support as the in-kernel
floating-point emulator needs to be aware of the NaN encoding used even
on hard-float processors and configure the FPU context according to the
value of the 2008 NaN ELF file header flag of the executable being
started. As at this time work on kernel support is still in progress
and the relevant changes have not made their way yet to linux.org master
repository.
Therefore the minimum version supported has been artificially set to
10.0.0 so that 2008-NaN code is not accidentally run on a Linux kernel
that does not suppport it. It is anticipated that the version is
adjusted later on to the actual initial linux.org kernel version to
support this feature. Legacy NaN encoding support is unaffected, older
kernel versions remain supported.
[1] "IEEE Standard for Floating-Point Arithmetic", IEEE Computer
Society, IEEE Std 754-2008, 29 August 2008
[2] "MIPS Architecture For Programmers, Volume I-A: Introduction to the
MIPS32 Architecture", MIPS Technologies, Inc., Document Number:
MD00082, Revision 3.50, September 20, 2012
[3] "MIPS Architecture For Programmers, Volume I-A: Introduction to the
MIPS64 Architecture", MIPS Technologies, Inc., Document Number:
MD00083, Revision 3.50, September 20, 2012
2013-09-18 22:04:27 +02:00
|
|
|
#define _FPU_RESERVED 0xfe840000 /* Reserved bits in cw, incl NAN2008. */
|
1997-06-21 04:02:21 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
/* The fdlibm code requires strict IEEE double precision arithmetic,
|
|
|
|
|
and no interrupts for exceptions, rounding to nearest. */
|
MIPS: IEEE 754-2008 NaN encoding support
It has been a long practice for software using IEEE 754 floating-point
arithmetic run on MIPS processors to use an encoding of Not-a-Number
(NaN) data different to one used by software run on other processors.
And as of IEEE 754-2008 revision [1] this encoding does not follow one
recommended in the standard, as specified in section 6.2.1, where it
is stated that quiet NaNs should have the first bit (d1) of their
significand set to 1 while signalling NaNs should have that bit set to
0, but MIPS software interprets the two bits in the opposite manner.
As from revision 3.50 [2][3] the MIPS Architecture provides for
processors that support the IEEE 754-2008 preferred NaN encoding format.
As the two formats (further referred to as "legacy NaN" and "2008 NaN")
are incompatible to each other, tools have to provide support for the
two formats to help people avoid using incompatible binary modules.
The change is comprised of two functional groups of features, both of
which are required for correct support.
1. Dynamic linker support.
To enforce the NaN encoding requirement in dynamic linking a new ELF
file header flag has been defined. This flag is set for 2008-NaN
shared modules and executables and clear for legacy-NaN ones. The
dynamic linker silently ignores any incompatible modules it
encounters in dependency processing.
To avoid unnecessary processing of incompatible modules in the
presence of a shared module cache, a set of new cache flags has been
defined to mark 2008-NaN modules for the three ABIs supported.
Changes to sysdeps/unix/sysv/linux/mips/readelflib.c have been made
following an earlier code quality suggestion made here:
http://sourceware.org/ml/libc-ports/2009-03/msg00036.html
and are therefore a little bit more extensive than the minimum
required.
Finally a new name has been defined for the dynamic linker so that
2008-NaN and legacy-NaN binaries can coexist on a single system that
supports dual-mode operation and that a legacy dynamic linker that
does not support verifying the 2008-NaN ELF file header flag is not
chosen to interpret a 2008-NaN binary by accident.
2. Floating environment support.
IEEE 754-2008 features are controlled in the Floating-Point Control
and Status (FCSR) register and updates are needed to floating
environment support so that the 2008-NaN flag is set correctly and
the kernel default, inferred from the 2008-NaN ELF file header flag
at the time an executable is loaded, respected.
As the NaN encoding format is a property of GCC code generation that is
both a user-selected GCC configuration default and can be overridden
with GCC options, code that needs to know what NaN encoding standard it
has been configured for checks for the __mips_nan2008 macro that is
defined internally by GCC whenever the 2008-NaN mode has been selected.
This mode is determined at the glibc configuration time and therefore a
few consistency checks have been added to catch cases where compilation
flags have been overridden by the user.
The 2008 NaN set of features relies on kernel support as the in-kernel
floating-point emulator needs to be aware of the NaN encoding used even
on hard-float processors and configure the FPU context according to the
value of the 2008 NaN ELF file header flag of the executable being
started. As at this time work on kernel support is still in progress
and the relevant changes have not made their way yet to linux.org master
repository.
Therefore the minimum version supported has been artificially set to
10.0.0 so that 2008-NaN code is not accidentally run on a Linux kernel
that does not suppport it. It is anticipated that the version is
adjusted later on to the actual initial linux.org kernel version to
support this feature. Legacy NaN encoding support is unaffected, older
kernel versions remain supported.
[1] "IEEE Standard for Floating-Point Arithmetic", IEEE Computer
Society, IEEE Std 754-2008, 29 August 2008
[2] "MIPS Architecture For Programmers, Volume I-A: Introduction to the
MIPS32 Architecture", MIPS Technologies, Inc., Document Number:
MD00082, Revision 3.50, September 20, 2012
[3] "MIPS Architecture For Programmers, Volume I-A: Introduction to the
MIPS64 Architecture", MIPS Technologies, Inc., Document Number:
MD00083, Revision 3.50, September 20, 2012
2013-09-18 22:04:27 +02:00
|
|
|
#ifdef __mips_nan2008
|
|
|
|
|
# define _FPU_DEFAULT 0x00040000
|
|
|
|
|
#else
|
|
|
|
|
# define _FPU_DEFAULT 0x00000000
|
|
|
|
|
#endif
|
1997-06-21 04:02:21 +02:00
|
|
|
|
MIPS: IEEE 754-2008 NaN encoding support
It has been a long practice for software using IEEE 754 floating-point
arithmetic run on MIPS processors to use an encoding of Not-a-Number
(NaN) data different to one used by software run on other processors.
And as of IEEE 754-2008 revision [1] this encoding does not follow one
recommended in the standard, as specified in section 6.2.1, where it
is stated that quiet NaNs should have the first bit (d1) of their
significand set to 1 while signalling NaNs should have that bit set to
0, but MIPS software interprets the two bits in the opposite manner.
As from revision 3.50 [2][3] the MIPS Architecture provides for
processors that support the IEEE 754-2008 preferred NaN encoding format.
As the two formats (further referred to as "legacy NaN" and "2008 NaN")
are incompatible to each other, tools have to provide support for the
two formats to help people avoid using incompatible binary modules.
The change is comprised of two functional groups of features, both of
which are required for correct support.
1. Dynamic linker support.
To enforce the NaN encoding requirement in dynamic linking a new ELF
file header flag has been defined. This flag is set for 2008-NaN
shared modules and executables and clear for legacy-NaN ones. The
dynamic linker silently ignores any incompatible modules it
encounters in dependency processing.
To avoid unnecessary processing of incompatible modules in the
presence of a shared module cache, a set of new cache flags has been
defined to mark 2008-NaN modules for the three ABIs supported.
Changes to sysdeps/unix/sysv/linux/mips/readelflib.c have been made
following an earlier code quality suggestion made here:
http://sourceware.org/ml/libc-ports/2009-03/msg00036.html
and are therefore a little bit more extensive than the minimum
required.
Finally a new name has been defined for the dynamic linker so that
2008-NaN and legacy-NaN binaries can coexist on a single system that
supports dual-mode operation and that a legacy dynamic linker that
does not support verifying the 2008-NaN ELF file header flag is not
chosen to interpret a 2008-NaN binary by accident.
2. Floating environment support.
IEEE 754-2008 features are controlled in the Floating-Point Control
and Status (FCSR) register and updates are needed to floating
environment support so that the 2008-NaN flag is set correctly and
the kernel default, inferred from the 2008-NaN ELF file header flag
at the time an executable is loaded, respected.
As the NaN encoding format is a property of GCC code generation that is
both a user-selected GCC configuration default and can be overridden
with GCC options, code that needs to know what NaN encoding standard it
has been configured for checks for the __mips_nan2008 macro that is
defined internally by GCC whenever the 2008-NaN mode has been selected.
This mode is determined at the glibc configuration time and therefore a
few consistency checks have been added to catch cases where compilation
flags have been overridden by the user.
The 2008 NaN set of features relies on kernel support as the in-kernel
floating-point emulator needs to be aware of the NaN encoding used even
on hard-float processors and configure the FPU context according to the
value of the 2008 NaN ELF file header flag of the executable being
started. As at this time work on kernel support is still in progress
and the relevant changes have not made their way yet to linux.org master
repository.
Therefore the minimum version supported has been artificially set to
10.0.0 so that 2008-NaN code is not accidentally run on a Linux kernel
that does not suppport it. It is anticipated that the version is
adjusted later on to the actual initial linux.org kernel version to
support this feature. Legacy NaN encoding support is unaffected, older
kernel versions remain supported.
[1] "IEEE Standard for Floating-Point Arithmetic", IEEE Computer
Society, IEEE Std 754-2008, 29 August 2008
[2] "MIPS Architecture For Programmers, Volume I-A: Introduction to the
MIPS32 Architecture", MIPS Technologies, Inc., Document Number:
MD00082, Revision 3.50, September 20, 2012
[3] "MIPS Architecture For Programmers, Volume I-A: Introduction to the
MIPS64 Architecture", MIPS Technologies, Inc., Document Number:
MD00083, Revision 3.50, September 20, 2012
2013-09-18 22:04:27 +02:00
|
|
|
/* IEEE: same as above, but exceptions. */
|
|
|
|
|
#ifdef __mips_nan2008
|
|
|
|
|
# define _FPU_IEEE 0x00040F80
|
|
|
|
|
#else
|
|
|
|
|
# define _FPU_IEEE 0x00000F80
|
|
|
|
|
#endif
|
1997-06-21 04:02:21 +02:00
|
|
|
|
|
|
|
|
/* Type of the control word. */
|
2000-07-05 17:37:11 +02:00
|
|
|
typedef unsigned int fpu_control_t __attribute__ ((__mode__ (__SI__)));
|
1997-06-21 04:02:21 +02:00
|
|
|
|
|
|
|
|
/* Macros for accessing the hardware control word. */
|
2013-02-28 00:45:07 +01:00
|
|
|
extern fpu_control_t __mips_fpu_getcw (void) __THROW;
|
|
|
|
|
extern void __mips_fpu_setcw (fpu_control_t) __THROW;
|
|
|
|
|
#ifdef __mips16
|
|
|
|
|
# define _FPU_GETCW(cw) do { (cw) = __mips_fpu_getcw (); } while (0)
|
|
|
|
|
# define _FPU_SETCW(cw) __mips_fpu_setcw (cw)
|
|
|
|
|
#else
|
|
|
|
|
# define _FPU_GETCW(cw) __asm__ volatile ("cfc1 %0,$31" : "=r" (cw))
|
|
|
|
|
# define _FPU_SETCW(cw) __asm__ volatile ("ctc1 %0,$31" : : "r" (cw))
|
|
|
|
|
#endif
|
1997-06-21 04:02:21 +02:00
|
|
|
|
|
|
|
|
/* Default control word set at startup. */
|
|
|
|
|
extern fpu_control_t __fpu_control;
|
|
|
|
|
|
2006-09-21 23:01:02 +02:00
|
|
|
#endif /* __mips_soft_float */
|
|
|
|
|
|
1997-06-21 04:02:21 +02:00
|
|
|
#endif /* fpu_control.h */
|
