aboutsummaryrefslogtreecommitdiff
path: root/newlib/libm/libm.texinfo
diff options
context:
space:
mode:
Diffstat (limited to 'newlib/libm/libm.texinfo')
-rw-r--r--newlib/libm/libm.texinfo18
1 files changed, 4 insertions, 14 deletions
diff --git a/newlib/libm/libm.texinfo b/newlib/libm/libm.texinfo
index f55ad72d9..a579a1743 100644
--- a/newlib/libm/libm.texinfo
+++ b/newlib/libm/libm.texinfo
@@ -107,23 +107,13 @@ into another language, under the above conditions for modified versions.
@cindex reentrancy
@cindex @code{matherr} and reentrancy
When a libm function detects an exceptional case, @code{errno} may be
-set, the @code{matherr} function may be called, and a error message
-may be written to the standard error stream. This behavior may not
-be reentrant.
+set.
@c The exact behavior depends on the currently selected error handling
-@c mode (IEEE, POSIX, X/Open, or SVID).
+@c mode (IEEE or POSIX).
-With reentrant C libraries like the Red Hat newlib C library, @code{errno} is
-a macro which expands to the per-thread error value. This makes it thread
-safe.
-
-When the user provides his own @code{matherr} function it must be
-reentrant for the math library as a whole to be reentrant.
-
-In normal debugged programs, there are usually no math subroutine
-errors---and therefore no assignments to @code{errno} and no @code{matherr}
-calls; in that situation, the math functions behave reentrantly.
+@code{errno} is a macro which expands to the per-thread error value.
+This makes it thread safe, and therefore reentrant.
@node Long Double Functions
@chapter The long double function support of @code{libm}