rename.2: SEE ALSO: add rename(1)

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

diff --git a/man3/alloca.3 b/man3/alloca.3
index f5087ceafbcbdf7b17243c872ce862504592d8d7..9dc7695e8eb326e460874040aad2163e0ecbd15b 100644 (file)
--- 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 2015-03-02 "GNU" "Linux Programmer's Manual"
+.TH ALLOCA 3 2019-03-06 "GNU" "Linux Programmer's Manual"
 .SH NAME
 alloca \- allocate memory that is automatically freed
 .SH SYNOPSIS
@@ -76,7 +76,7 @@ T}    Thread safety   MT-Safe
 .TE
 .SH CONFORMING TO
 This function is not in POSIX.1.
-
+.PP
 There is evidence that the
 .BR alloca ()
 function appeared in 32V, PWB, PWB.2, 3BSD, and 4BSD.
@@ -97,7 +97,7 @@ it can also simplify memory deallocation in applications that use
 or
 .BR siglongjmp (3).
 Otherwise, its use is discouraged.
-
+.PP
 Because the space allocated by
 .BR alloca ()
 is allocated within the stack frame,
@@ -106,7 +106,14 @@ is jumped over by a call to
 .BR longjmp (3)
 or
 .BR siglongjmp (3).
-
+.PP
+The space allocated by
+.BR alloca ()
+is
+.I not
+automatically deallocated if the pointer that refers to it
+simply goes out of scope.
+.PP
 Do not attempt to
 .BR free (3)
 space allocated by
@@ -133,19 +140,21 @@ Otherwise, (without an \-ansi or \-std=c* option) the glibc version of
 includes
 .I <alloca.h>
 and that contains the lines:
-.nf
-
-    #ifdef  __GNUC__
-    #define alloca(size)   __builtin_alloca (size)
-    #endif
-
-.fi
+.PP
+.in +4n
+.EX
+#ifdef  __GNUC__
+#define alloca(size)   __builtin_alloca (size)
+#endif
+.EE
+.in
+.PP
 with messy consequences if one has a private version of this function.
-.LP
+.PP
 The fact that the code is inlined means that it is impossible
 to take the address of this function, or to change its behavior
 by linking with a different library.
-.LP
+.PP
 The inlined code often consists of a single instruction adjusting
 the stack pointer, and does not check for stack overflow.
 Thus, there is no NULL error return.
@@ -154,7 +163,7 @@ There is no error indication if the stack frame cannot be extended.
 (However, after a failed allocation, the program is likely to receive a
 .B SIGSEGV
 signal if it attempts to access the unallocated space.)
-
+.PP
 On many systems
 .BR alloca ()
 cannot be used inside the list of arguments of a function call, because