summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPeng Haitao <penght@cn.fujitsu.com>2013-09-02 11:20:58 +0800
committerMichael Kerrisk <mtk.manpages@gmail.com>2013-09-02 07:46:21 +0200
commite132eea1ab66adc317953ff69473bdff89cdcec3 (patch)
treee373439065f9254c1aa35a706d4d95ba05837b11
parent7d082baba688bd0d274baceb79aa8e1e3e19c640 (diff)
nextafter.3: ATTRIBUTES: Note functions that are thread-safe
The functions nextafter(), nextafterf(), nextafterl(), nexttoward(), nexttowardf() and nexttowardl() are thread safe. Signed-off-by: Peng Haitao <penght@cn.fujitsu.com> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
-rw-r--r--man3/nextafter.313
1 files changed, 12 insertions, 1 deletions
diff --git a/man3/nextafter.3 b/man3/nextafter.3
index 7619cc4a..69289d82 100644
--- a/man3/nextafter.3
+++ b/man3/nextafter.3
@@ -8,7 +8,7 @@
.\"
.\" Based on glibc infopages
.\"
-.TH NEXTAFTER 3 2010-09-20 "GNU" "Linux Programmer's Manual"
+.TH NEXTAFTER 3 2013-09-02 "GNU" "Linux Programmer's Manual"
.SH NAME
nextafter, nextafterf, nextafterl, nexttoward, nexttowardf, nexttowardl \-
floating-point number manipulation
@@ -170,6 +170,17 @@ These functions do not set
.IR errno .
.\" FIXME . Is it intentional that these functions do not set errno?
.\" Bug raised: http://sources.redhat.com/bugzilla/show_bug.cgi?id=6799
+.SH ATTRIBUTES
+.SS Multithreading (see pthreads(7))
+The
+.BR nextafter (),
+.BR nextafterf (),
+.BR nextafterl (),
+.BR nexttoward (),
+.BR nexttowardf (),
+and
+.BR nexttowardl ()
+functions are thread-safe.
.SH CONFORMING TO
C99, POSIX.1-2001.
This function is defined in IEC 559 (and the appendix with