]> git.ipfire.org Git - thirdparty/man-pages.git/blob - man3/alloca.3
iconv.1, ldd.1, locale.1, localedef.1, memusage.1, memusagestat.1, mtrace.1, pldd...
[thirdparty/man-pages.git] / man3 / alloca.3
1 .\" Copyright (c) 1980, 1991 Regents of the University of California.
2 .\" All rights reserved.
3 .\"
4 .\" %%%LICENSE_START(BSD_4_CLAUSE_UCB)
5 .\" Redistribution and use in source and binary forms, with or without
6 .\" modification, are permitted provided that the following conditions
7 .\" are met:
8 .\" 1. Redistributions of source code must retain the above copyright
9 .\" notice, this list of conditions and the following disclaimer.
10 .\" 2. Redistributions in binary form must reproduce the above copyright
11 .\" notice, this list of conditions and the following disclaimer in the
12 .\" documentation and/or other materials provided with the distribution.
13 .\" 3. All advertising materials mentioning features or use of this software
14 .\" must display the following acknowledgement:
15 .\" This product includes software developed by the University of
16 .\" California, Berkeley and its contributors.
17 .\" 4. Neither the name of the University nor the names of its contributors
18 .\" may be used to endorse or promote products derived from this software
19 .\" without specific prior written permission.
20 .\"
21 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
22 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
23 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
24 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
25 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
26 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
27 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
28 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
29 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
30 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
31 .\" SUCH DAMAGE.
32 .\" %%%LICENSE_END
33 .\"
34 .\" @(#)alloca.3 5.1 (Berkeley) 5/2/91
35 .\"
36 .\" Converted Mon Nov 29 11:05:55 1993 by Rik Faith <faith@cs.unc.edu>
37 .\" Modified Tue Oct 22 23:41:56 1996 by Eric S. Raymond <esr@thyrsus.com>
38 .\" Modified 2002-07-17, aeb
39 .\" 2008-01-24, mtk:
40 .\" Various rewrites and additions (notes on longjmp() and SIGSEGV).
41 .\" Weaken warning against use of alloca() (as per Debian bug 461100).
42 .\"
43 .TH ALLOCA 3 2017-09-15 "GNU" "Linux Programmer's Manual"
44 .SH NAME
45 alloca \- allocate memory that is automatically freed
46 .SH SYNOPSIS
47 .B #include <alloca.h>
48 .PP
49 .BI "void *alloca(size_t " size );
50 .SH DESCRIPTION
51 The
52 .BR alloca ()
53 function allocates
54 .I size
55 bytes of space in the stack frame of the caller.
56 This temporary space is
57 automatically freed when the function that called
58 .BR alloca ()
59 returns to its caller.
60 .SH RETURN VALUE
61 The
62 .BR alloca ()
63 function returns a pointer to the beginning of the allocated space.
64 If the allocation causes stack overflow, program behavior is undefined.
65 .SH ATTRIBUTES
66 For an explanation of the terms used in this section, see
67 .BR attributes (7).
68 .TS
69 allbox;
70 lb lb lb
71 l l l.
72 Interface Attribute Value
73 T{
74 .BR alloca ()
75 T} Thread safety MT-Safe
76 .TE
77 .SH CONFORMING TO
78 This function is not in POSIX.1.
79 .PP
80 There is evidence that the
81 .BR alloca ()
82 function appeared in 32V, PWB, PWB.2, 3BSD, and 4BSD.
83 There is a man page for it in 4.3BSD.
84 Linux uses the GNU version.
85 .SH NOTES
86 The
87 .BR alloca ()
88 function is machine- and compiler-dependent.
89 For certain applications,
90 its use can improve efficiency compared to the use of
91 .BR malloc (3)
92 plus
93 .BR free (3).
94 In certain cases,
95 it can also simplify memory deallocation in applications that use
96 .BR longjmp (3)
97 or
98 .BR siglongjmp (3).
99 Otherwise, its use is discouraged.
100 .PP
101 Because the space allocated by
102 .BR alloca ()
103 is allocated within the stack frame,
104 that space is automatically freed if the function return
105 is jumped over by a call to
106 .BR longjmp (3)
107 or
108 .BR siglongjmp (3).
109 .PP
110 Do not attempt to
111 .BR free (3)
112 space allocated by
113 .BR alloca ()!
114 .SS Notes on the GNU version
115 Normally,
116 .BR gcc (1)
117 translates calls to
118 .BR alloca ()
119 with inlined code.
120 This is not done when either the
121 .IR "\-ansi" ,
122 .IR "\-std=c89" ,
123 .IR "\-std=c99" ,
124 or the
125 .IR "\-std=c11"
126 option is given
127 .BR and
128 the header
129 .I <alloca.h>
130 is not included.
131 Otherwise, (without an \-ansi or \-std=c* option) the glibc version of
132 .I <stdlib.h>
133 includes
134 .I <alloca.h>
135 and that contains the lines:
136 .PP
137 .in +4n
138 .EX
139 #ifdef __GNUC__
140 #define alloca(size) __builtin_alloca (size)
141 #endif
142 .EE
143 .in
144 .PP
145 with messy consequences if one has a private version of this function.
146 .PP
147 The fact that the code is inlined means that it is impossible
148 to take the address of this function, or to change its behavior
149 by linking with a different library.
150 .PP
151 The inlined code often consists of a single instruction adjusting
152 the stack pointer, and does not check for stack overflow.
153 Thus, there is no NULL error return.
154 .SH BUGS
155 There is no error indication if the stack frame cannot be extended.
156 (However, after a failed allocation, the program is likely to receive a
157 .B SIGSEGV
158 signal if it attempts to access the unallocated space.)
159 .PP
160 On many systems
161 .BR alloca ()
162 cannot be used inside the list of arguments of a function call, because
163 the stack space reserved by
164 .BR alloca ()
165 would appear on the stack in the middle of the space for the
166 function arguments.
167 .SH SEE ALSO
168 .BR brk (2),
169 .BR longjmp (3),
170 .BR malloc (3)