On 07.10.2013 21:58, Peng Haitao wrote: > The function alloca() is thread safe. Applied. Thanks, Michael > Signed-off-by: Peng Haitao <penght@xxxxxxxxxxxxxx> > --- > man3/alloca.3 | 7 ++++++- > 1 file changed, 6 insertions(+), 1 deletion(-) > > diff --git a/man3/alloca.3 b/man3/alloca.3 > index 0d593ed..7d11c63 100644 > --- a/man3/alloca.3 > +++ b/man3/alloca.3 > @@ -40,7 +40,7 @@ > .\" Various rewrites and additions (notes on longjmp() and SIGSEGV). > .\" Weaken warning against use of alloca() (as per Debian bug 461100). > .\" > -.TH ALLOCA 3 2013-05-12 "GNU" "Linux Programmer's Manual" > +.TH ALLOCA 3 2013-10-07 "GNU" "Linux Programmer's Manual" > .SH NAME > alloca \- allocate memory that is automatically freed > .SH SYNOPSIS > @@ -62,6 +62,11 @@ The > .BR alloca () > function returns a pointer to the beginning of the allocated space. > If the allocation causes stack overflow, program behavior is undefined. > +.SH ATTRIBUTES > +.SS Multithreading (see pthreads(7)) > +The > +.BR alloca () > +function is thread-safe. > .SH CONFORMING TO > This function is not in POSIX.1-2001. > > -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ My next Linux/UNIX system programming course: -- 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
