signal.7: Note async-signal-safe functions added by POSIX.1-2008 TC1

[thirdparty/man-pages.git] / man3 / ftime.3

diff --git a/man3/ftime.3 b/man3/ftime.3
index 2acdd1aeb8c552dd68d5827aff1370a0f7f01dce..8198552b989ca85965416617ac9fae54abdf2b9e 100644 (file)
--- a/man3/ftime.3
+++ b/man3/ftime.3
@@ -27,7 +27,7 @@
 .\" Modified Sun Oct 18 17:31:43 1998 by Andries Brouwer (aeb@cwi.nl)
 .\" 2008-06-23, mtk, minor rewrites, added some details
 .\"
-.TH FTIME 3 2010-02-25 "GNU" "Linux Programmer's Manual"
+.TH FTIME 3 2015-03-02 "GNU" "Linux Programmer's Manual"
 .SH NAME
 ftime \- return date and time
 .SH SYNOPSIS
@@ -67,6 +67,18 @@ fields are unspecified; avoid relying on them.
 .SH RETURN VALUE
 This function always returns 0.
 (POSIX.1-2001 specifies, and some systems document, a \-1 error return.)
+.SH ATTRIBUTES
+For an explanation of the terms used in this section, see
+.BR attributes (7).
+.TS
+allbox;
+lb lb lb
+l l l.
+Interface      Attribute       Value
+T{
+.BR ftime ()
+T}     Thread safety   MT-Safe
+.TE
 .SH CONFORMING TO
 4.2BSD, POSIX.1-2001.
 POSIX.1-2008 removes the specification of
@@ -84,8 +96,9 @@ gives microseconds;
 gives nanoseconds but is not as widely available.
 .SH BUGS
 .LP
-Under libc4 and libc5 the \fImillitm\fP field is meaningful.
-But early glibc2 is buggy and returns 0 there;
+Early glibc2 is buggy and returns 0 in the
+.I millitm
+field;
 glibc 2.1.1 is correct again.
 .\" .SH HISTORY
 .\" The