Remove __NO_MATH_INLINES

With fenvinline.h removal the flag is not used anymore.

Checked on x86_64-linux-gnu.

manual/math.texi

@@ -2010,12 +2010,6 @@ might have a reduced precision and/or argument range in comparison with
 the library functions.  The latter inline functions are only available
 if the flag @code{-ffast-math} is given to GNU CC.
 
-In cases where the inline functions and macros are not wanted the symbol
-@code{__NO_MATH_INLINES} should be defined before any system header is
-included.  This will ensure that only library functions are used.  Of
-course, it can be determined for each file in the project whether
-giving this option is preferable or not.
-
 Not all hardware implements the entire @w{IEEE 754} standard, and even
 if it does there may be a substantial performance penalty for using some
 of its features.  For example, enabling traps on some processors forces

math/Makefile

@@ -613,10 +613,6 @@ endef
 object-suffixes-left := $(all-object-suffixes)
 include $(o-iterator)
 
-# We don't want the fdlibm code to use the inline math functions,
-# only the fdlibm code.
-math-CPPFLAGS += -D__NO_MATH_INLINES
-
 ifneq ($(long-double-fcts),yes)
 # The `double' and `long double' types are the same on this machine.
 # We won't compile the `long double' code at all.  Tell the `double' code

math/README.libm-test

@@ -38,11 +38,9 @@ The test drivers "test-double-<func>.c", "test-float-<func>.c", and
 double, float and long double implementation of libm.  Each driver
 selects the desired real floating type to exercise the math functions
 to test with (float, double, or long double) by defining a small set
-of macros just before including the generic "libm-test.c" file.  Each
-driver also either defines or undefines the __NO_MATH_INLINES macro
-just before including "libm-test-<func>.c" to select either the real
-or inline functions, respectively.  Each driver is compiled into a
-single executable test program with the corresponding name.
+of macros just before including the generic "libm-test.c" file. Each
+driver is compiled into a single executable test program with the
+corresponding name.
 
 As mentioned above, the "gen-libm-test.py" script looks for a file
 named "libm-test-ulps" in the platform specific sysdep directory (or

math/math.h

@@ -1257,13 +1257,6 @@ iszero (__T __val)
 # error "M_* values needed for _Float128x"
 #endif
 
-/* When compiling in strict ISO C compatible mode we must not use the
-   inline functions since they, among other things, do not set the
-   `errno' variable correctly.  */
-#if defined __STRICT_ANSI__ && !defined __NO_MATH_INLINES
-# define __NO_MATH_INLINES	1
-#endif
-
 #ifdef __USE_ISOC99
 # if __GNUC_PREREQ (3, 1)
 /* ISO C99 defines some macros to compare number while taking care for

math/test-tgmath.c

@@ -19,8 +19,6 @@
    <https://www.gnu.org/licenses/>.  */
 
 #ifndef HAVE_MAIN
-#undef __NO_MATH_INLINES
-#define __NO_MATH_INLINES 1
 #include <float.h>
 #include <math.h>
 #include <stdint.h>

math/test-tgmath2.c

@@ -18,8 +18,6 @@
    <https://www.gnu.org/licenses/>.  */
 
 #ifndef HAVE_MAIN
-#undef __NO_MATH_INLINES
-#define __NO_MATH_INLINES 1
 #include <float.h>
 #include <math.h>
 #include <complex.h>