From f1892dd29623739ea1fa8a55705708474738e2eb Mon Sep 17 00:00:00 2001 From: vlefevre Date: Tue, 4 Feb 2020 01:53:02 +0000 Subject: [doc/mpfr.texi] In the paragraph "MPFR internal data such as flags", no longer mention caches as caches may now also be global when MPFR has been compiled as thread safe (locking is used). Caches have been discussed earlier in the section anyway. (merged changeset r13684 from the trunk) git-svn-id: svn://scm.gforge.inria.fr/svn/mpfr/branches/4.0@13686 280ebfd0-de03-0410-8827-d642c229c3f4 --- doc/mpfr.texi | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/doc/mpfr.texi b/doc/mpfr.texi index d7e8cc79e..5f4673ae3 100644 --- a/doc/mpfr.texi +++ b/doc/mpfr.texi @@ -1032,9 +1032,8 @@ Note: For multithreaded applications, the allocator must be valid in all threads where MPFR may be used; data allocated in one thread may be reallocated and/or freed in some other thread. -MPFR internal data such as flags, the exponent range, the default -precision and rounding mode, and caches (i.e., data that are not -accessed via parameters) are either global (if MPFR has not been +MPFR internal data such as flags, the exponent range, the default precision, +and the default rounding mode are either global (if MPFR has not been compiled as thread safe) or per-thread (thread local storage, TLS)@. The initial values of TLS data after a thread is created entirely depend on the compiler and thread implementation (MPFR simply does -- cgit v1.2.1