The macros va_start(), va_arg(), va_end() and va_copy() are thread safe. Signed-off-by: Peng Haitao <penght@xxxxxxxxxxxxxx> --- man3/stdarg.3 | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/man3/stdarg.3 b/man3/stdarg.3 index fb81772..cc170b5 100644 --- a/man3/stdarg.3 +++ b/man3/stdarg.3 @@ -40,7 +40,7 @@ .\" Converted for Linux, Mon Nov 29 15:11:11 1993, faith@xxxxxxxxxx .\" Additions, 2001-10-14, aeb .\" -.TH STDARG 3 2013-03-15 "" "Linux Programmer's Manual" +.TH STDARG 3 2013-12-10 "" "Linux Programmer's Manual" .SH NAME stdarg, va_start, va_arg, va_end, va_copy \- variable argument lists .SH SYNOPSIS @@ -226,6 +226,15 @@ Some systems that do not supply have .B __va_copy instead, since that was the name used in the draft proposal. +.SH ATTRIBUTES +.SS Multithreading (see pthreads(7)) +The +.BR va_start (), +.BR va_arg (), +.BR va_end (), +and +.BR va_copy () +macros are thread-safe. .SH CONFORMING TO The .BR va_start (), -- 1.8.3.1 -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
