]>
Commit | Line | Data |
---|---|---|
448c0fae | 1 | @c Copyright (C) 1988,1989,1992,1993,1994,1996,1998,1999,2000,2001,2002, 2003 |
2 | @c Free Software Foundation, Inc. | |
146ef39f | 3 | @c This is part of the GCC manual. |
4 | @c For copying conditions, see the file gcc.texi. | |
5 | ||
b2bc1722 | 6 | @node C Implementation |
7 | @chapter C Implementation-defined behavior | |
8 | @cindex implementation-defined behavior, C language | |
9 | ||
10 | A conforming implementation of ISO C is required to document its | |
11 | choice of behavior in each of the areas that are designated | |
12 | ``implementation defined.'' The following lists all such areas, | |
13 | along with the section number from the ISO/IEC 9899:1999 standard. | |
14 | ||
15 | @menu | |
16 | * Translation implementation:: | |
17 | * Environment implementation:: | |
18 | * Identifiers implementation:: | |
19 | * Characters implementation:: | |
20 | * Integers implementation:: | |
21 | * Floating point implementation:: | |
22 | * Arrays and pointers implementation:: | |
23 | * Hints implementation:: | |
24 | * Structures unions enumerations and bit-fields implementation:: | |
25 | * Qualifiers implementation:: | |
26 | * Preprocessing directives implementation:: | |
27 | * Library functions implementation:: | |
28 | * Architecture implementation:: | |
29 | * Locale-specific behavior implementation:: | |
30 | @end menu | |
31 | ||
32 | @node Translation implementation | |
33 | @section Translation | |
34 | ||
35 | @itemize @bullet | |
36 | @item | |
37 | @cite{How a diagnostic is identified (3.10, 5.1.1.3).} | |
38 | ||
f191dff6 | 39 | Diagnostics consist of all the output sent to stderr by GCC. |
40 | ||
b2bc1722 | 41 | @item |
42 | @cite{Whether each nonempty sequence of white-space characters other than | |
43 | new-line is retained or replaced by one space character in translation | |
44 | phase 3 (5.1.1.2).} | |
45 | @end itemize | |
46 | ||
47 | @node Environment implementation | |
48 | @section Environment | |
49 | ||
66dbb5a8 | 50 | The behavior of these points are dependent on the implementation |
b2bc1722 | 51 | of the C library, and are not defined by GCC itself. |
52 | ||
53 | @node Identifiers implementation | |
54 | @section Identifiers | |
55 | ||
56 | @itemize @bullet | |
57 | @item | |
58 | @cite{Which additional multibyte characters may appear in identifiers | |
59 | and their correspondence to universal character names (6.4.2).} | |
60 | ||
61 | @item | |
62 | @cite{The number of significant initial characters in an identifier | |
63 | (5.2.4.1, 6.4.2).} | |
f191dff6 | 64 | |
65 | For internal names, all characters are significant. For external names, | |
66 | the number of significant characters are defined by the linker; for | |
67 | almost all targets, all characters are significant. | |
68 | ||
b2bc1722 | 69 | @end itemize |
70 | ||
71 | @node Characters implementation | |
72 | @section Characters | |
73 | ||
74 | @itemize @bullet | |
75 | @item | |
76 | @cite{The number of bits in a byte (3.6).} | |
77 | ||
78 | @item | |
79 | @cite{The values of the members of the execution character set (5.2.1).} | |
80 | ||
81 | @item | |
82 | @cite{The unique value of the member of the execution character set produced | |
83 | for each of the standard alphabetic escape sequences (5.2.2).} | |
84 | ||
85 | @item | |
86 | @cite{The value of a @code{char} object into which has been stored any | |
87 | character other than a member of the basic execution character set (6.2.5).} | |
88 | ||
89 | @item | |
90 | @cite{Which of @code{signed char} or @code{unsigned char} has the same range, | |
32432f22 | 91 | representation, and behavior as ``plain'' @code{char} (6.2.5, 6.3.1.1).} |
b2bc1722 | 92 | |
93 | @item | |
94 | @cite{The mapping of members of the source character set (in character | |
95 | constants and string literals) to members of the execution character | |
96 | set (6.4.4.4, 5.1.1.2).} | |
97 | ||
98 | @item | |
99 | @cite{The value of an integer character constant containing more than one | |
100 | character or containing a character or escape sequence that does not map | |
101 | to a single-byte execution character (6.4.4.4).} | |
102 | ||
103 | @item | |
104 | @cite{The value of a wide character constant containing more than one | |
105 | multibyte character, or containing a multibyte character or escape | |
106 | sequence not represented in the extended execution character set (6.4.4.4).} | |
107 | ||
108 | @item | |
109 | @cite{The current locale used to convert a wide character constant consisting | |
110 | of a single multibyte character that maps to a member of the extended | |
111 | execution character set into a corresponding wide character code (6.4.4.4).} | |
112 | ||
113 | @item | |
114 | @cite{The current locale used to convert a wide string literal into | |
115 | corresponding wide character codes (6.4.5).} | |
116 | ||
117 | @item | |
118 | @cite{The value of a string literal containing a multibyte character or escape | |
119 | sequence not represented in the execution character set (6.4.5).} | |
120 | @end itemize | |
121 | ||
122 | @node Integers implementation | |
123 | @section Integers | |
124 | ||
125 | @itemize @bullet | |
126 | @item | |
127 | @cite{Any extended integer types that exist in the implementation (6.2.5).} | |
128 | ||
129 | @item | |
130 | @cite{Whether signed integer types are represented using sign and magnitude, | |
131 | two's complement, or one's complement, and whether the extraordinary value | |
132 | is a trap representation or an ordinary value (6.2.6.2).} | |
133 | ||
f191dff6 | 134 | GCC supports only two's complement integer types, and all bit patterns |
135 | are ordinary values. | |
136 | ||
b2bc1722 | 137 | @item |
138 | @cite{The rank of any extended integer type relative to another extended | |
139 | integer type with the same precision (6.3.1.1).} | |
140 | ||
141 | @item | |
142 | @cite{The result of, or the signal raised by, converting an integer to a | |
143 | signed integer type when the value cannot be represented in an object of | |
144 | that type (6.3.1.3).} | |
145 | ||
146 | @item | |
147 | @cite{The results of some bitwise operations on signed integers (6.5).} | |
148 | @end itemize | |
149 | ||
150 | @node Floating point implementation | |
151 | @section Floating point | |
152 | ||
153 | @itemize @bullet | |
154 | @item | |
155 | @cite{The accuracy of the floating-point operations and of the library | |
32432f22 | 156 | functions in @code{<math.h>} and @code{<complex.h>} that return floating-point |
b2bc1722 | 157 | results (5.2.4.2.2).} |
158 | ||
159 | @item | |
160 | @cite{The rounding behaviors characterized by non-standard values | |
0fff59be | 161 | of @code{FLT_ROUNDS} @gol |
162 | (5.2.4.2.2).} | |
b2bc1722 | 163 | |
164 | @item | |
165 | @cite{The evaluation methods characterized by non-standard negative | |
166 | values of @code{FLT_EVAL_METHOD} (5.2.4.2.2).} | |
167 | ||
168 | @item | |
169 | @cite{The direction of rounding when an integer is converted to a | |
170 | floating-point number that cannot exactly represent the original | |
171 | value (6.3.1.4).} | |
172 | ||
173 | @item | |
174 | @cite{The direction of rounding when a floating-point number is | |
175 | converted to a narrower floating-point number (6.3.1.5).} | |
176 | ||
177 | @item | |
178 | @cite{How the nearest representable value or the larger or smaller | |
179 | representable value immediately adjacent to the nearest representable | |
180 | value is chosen for certain floating constants (6.4.4.2).} | |
181 | ||
182 | @item | |
183 | @cite{Whether and how floating expressions are contracted when not | |
184 | disallowed by the @code{FP_CONTRACT} pragma (6.5).} | |
185 | ||
186 | @item | |
187 | @cite{The default state for the @code{FENV_ACCESS} pragma (7.6.1).} | |
188 | ||
189 | @item | |
190 | @cite{Additional floating-point exceptions, rounding modes, environments, | |
191 | and classifications, and their macro names (7.6, 7.12).} | |
192 | ||
193 | @item | |
194 | @cite{The default state for the @code{FP_CONTRACT} pragma (7.12.2).} | |
195 | ||
196 | @item | |
197 | @cite{Whether the ``inexact'' floating-point exception can be raised | |
198 | when the rounded result actually does equal the mathematical result | |
199 | in an IEC 60559 conformant implementation (F.9).} | |
200 | ||
201 | @item | |
202 | @cite{Whether the ``underflow'' (and ``inexact'') floating-point | |
203 | exception can be raised when a result is tiny but not inexact in an | |
204 | IEC 60559 conformant implementation (F.9).} | |
205 | ||
206 | @end itemize | |
207 | ||
208 | @node Arrays and pointers implementation | |
209 | @section Arrays and pointers | |
210 | ||
211 | @itemize @bullet | |
212 | @item | |
213 | @cite{The result of converting a pointer to an integer or | |
214 | vice versa (6.3.2.3).} | |
215 | ||
9b2b2b07 | 216 | A cast from pointer to integer discards most-significant bits if the |
23fa08a2 | 217 | pointer representation is larger than the integer type, |
218 | sign-extends@footnote{Future versions of GCC may zero-extend, or use | |
219 | a target-defined @code{ptr_extend} pattern. Do not rely on sign extension.} | |
9b2b2b07 | 220 | if the pointer representation is smaller than the integer type, otherwise |
221 | the bits are unchanged. | |
222 | @c ??? We've always claimed that pointers were unsigned entities. | |
223 | @c Shouldn't we therefore be doing zero-extension? If so, the bug | |
224 | @c is in convert_to_integer, where we call type_for_size and request | |
225 | @c a signed integral type. On the other hand, it might be most useful | |
226 | @c for the target if we extend according to POINTERS_EXTEND_UNSIGNED. | |
227 | ||
228 | A cast from integer to pointer discards most-significant bits if the | |
229 | pointer representation is smaller than the integer type, extends according | |
230 | to the signedness of the integer type if the pointer representation | |
231 | is larger than the integer type, otherwise the bits are unchanged. | |
232 | ||
233 | When casting from pointer to integer and back again, the resulting | |
234 | pointer must reference the same object as the original pointer, otherwise | |
235 | the behavior is undefined. That is, one may not use integer arithmetic to | |
236 | avoid the undefined behavior of pointer arithmetic as proscribed in 6.5.6/8. | |
237 | ||
b2bc1722 | 238 | @item |
239 | @cite{The size of the result of subtracting two pointers to elements | |
240 | of the same array (6.5.6).} | |
241 | ||
242 | @end itemize | |
243 | ||
244 | @node Hints implementation | |
245 | @section Hints | |
246 | ||
247 | @itemize @bullet | |
248 | @item | |
249 | @cite{The extent to which suggestions made by using the @code{register} | |
250 | storage-class specifier are effective (6.7.1).} | |
251 | ||
d89b84b5 | 252 | The @code{register} specifier affects code generation only in these ways: |
253 | ||
254 | @itemize @bullet | |
255 | @item | |
256 | When used as part of the register variable extension, see | |
257 | @ref{Explicit Reg Vars}. | |
258 | ||
259 | @item | |
260 | When @option{-O0} is in use, the compiler allocates distinct stack | |
261 | memory for all variables that do not have the @code{register} | |
262 | storage-class specifier; if @code{register} is specified, the variable | |
263 | may have a shorter lifespan than the code would indicate and may never | |
264 | be placed in memory. | |
265 | ||
266 | @item | |
267 | On some rare x86 targets, @code{setjmp} doesn't save the registers in | |
268 | all circumstances. In those cases, GCC doesn't allocate any variables | |
269 | in registers unless they are marked @code{register}. | |
270 | ||
271 | @end itemize | |
272 | ||
b2bc1722 | 273 | @item |
274 | @cite{The extent to which suggestions made by using the inline function | |
275 | specifier are effective (6.7.4).} | |
276 | ||
f191dff6 | 277 | GCC will not inline any functions if the @option{-fno-inline} option is |
278 | used or if @option{-O0} is used. Otherwise, GCC may still be unable to | |
279 | inline a function for many reasons; the @option{-Winline} option may be | |
280 | used to determine if a function has not been inlined and why not. | |
281 | ||
b2bc1722 | 282 | @end itemize |
283 | ||
284 | @node Structures unions enumerations and bit-fields implementation | |
285 | @section Structures, unions, enumerations, and bit-fields | |
286 | ||
287 | @itemize @bullet | |
288 | @item | |
289 | @cite{Whether a ``plain'' int bit-field is treated as a @code{signed int} | |
290 | bit-field or as an @code{unsigned int} bit-field (6.7.2, 6.7.2.1).} | |
291 | ||
292 | @item | |
293 | @cite{Allowable bit-field types other than @code{_Bool}, @code{signed int}, | |
294 | and @code{unsigned int} (6.7.2.1).} | |
295 | ||
296 | @item | |
297 | @cite{Whether a bit-field can straddle a storage-unit boundary (6.7.2.1).} | |
298 | ||
299 | @item | |
300 | @cite{The order of allocation of bit-fields within a unit (6.7.2.1).} | |
301 | ||
302 | @item | |
303 | @cite{The alignment of non-bit-field members of structures (6.7.2.1).} | |
304 | ||
305 | @item | |
306 | @cite{The integer type compatible with each enumerated type (6.7.2.2).} | |
307 | ||
308 | @end itemize | |
309 | ||
310 | @node Qualifiers implementation | |
311 | @section Qualifiers | |
312 | ||
313 | @itemize @bullet | |
314 | @item | |
315 | @cite{What constitutes an access to an object that has volatile-qualified | |
316 | type (6.7.3).} | |
317 | ||
318 | @end itemize | |
319 | ||
320 | @node Preprocessing directives implementation | |
321 | @section Preprocessing directives | |
322 | ||
323 | @itemize @bullet | |
324 | @item | |
325 | @cite{How sequences in both forms of header names are mapped to headers | |
326 | or external source file names (6.4.7).} | |
327 | ||
328 | @item | |
329 | @cite{Whether the value of a character constant in a constant expression | |
330 | that controls conditional inclusion matches the value of the same character | |
331 | constant in the execution character set (6.10.1).} | |
332 | ||
333 | @item | |
334 | @cite{Whether the value of a single-character character constant in a | |
335 | constant expression that controls conditional inclusion may have a | |
336 | negative value (6.10.1).} | |
337 | ||
338 | @item | |
339 | @cite{The places that are searched for an included @samp{<>} delimited | |
340 | header, and how the places are specified or the header is | |
341 | identified (6.10.2).} | |
342 | ||
343 | @item | |
344 | @cite{How the named source file is searched for in an included @samp{""} | |
345 | delimited header (6.10.2).} | |
346 | ||
347 | @item | |
348 | @cite{The method by which preprocessing tokens (possibly resulting from | |
349 | macro expansion) in a @code{#include} directive are combined into a header | |
350 | name (6.10.2).} | |
351 | ||
352 | @item | |
353 | @cite{The nesting limit for @code{#include} processing (6.10.2).} | |
354 | ||
f191dff6 | 355 | GCC imposes a limit of 200 nested @code{#include}s. |
356 | ||
b2bc1722 | 357 | @item |
358 | @cite{Whether the @samp{#} operator inserts a @samp{\} character before | |
359 | the @samp{\} character that begins a universal character name in a | |
360 | character constant or string literal (6.10.3.2).} | |
361 | ||
362 | @item | |
363 | @cite{The behavior on each recognized non-@code{STDC #pragma} | |
364 | directive (6.10.6).} | |
365 | ||
366 | @item | |
367 | @cite{The definitions for @code{__DATE__} and @code{__TIME__} when | |
368 | respectively, the date and time of translation are not available (6.10.8).} | |
369 | ||
3385506f | 370 | If the date and time are not available, @code{__DATE__} expands to |
371 | @code{@w{"??? ?? ????"}} and @code{__TIME__} expands to | |
372 | @code{"??:??:??"}. | |
f191dff6 | 373 | |
b2bc1722 | 374 | @end itemize |
375 | ||
376 | @node Library functions implementation | |
377 | @section Library functions | |
378 | ||
66dbb5a8 | 379 | The behavior of these points are dependent on the implementation |
b2bc1722 | 380 | of the C library, and are not defined by GCC itself. |
381 | ||
382 | @node Architecture implementation | |
383 | @section Architecture | |
384 | ||
385 | @itemize @bullet | |
386 | @item | |
387 | @cite{The values or expressions assigned to the macros specified in the | |
32432f22 | 388 | headers @code{<float.h>}, @code{<limits.h>}, and @code{<stdint.h>} |
b2bc1722 | 389 | (5.2.4.2, 7.18.2, 7.18.3).} |
390 | ||
391 | @item | |
392 | @cite{The number, order, and encoding of bytes in any object | |
393 | (when not explicitly specified in this International Standard) (6.2.6.1).} | |
394 | ||
395 | @item | |
396 | @cite{The value of the result of the sizeof operator (6.5.3.4).} | |
397 | ||
398 | @end itemize | |
399 | ||
400 | @node Locale-specific behavior implementation | |
401 | @section Locale-specific behavior | |
402 | ||
66dbb5a8 | 403 | The behavior of these points are dependent on the implementation |
b2bc1722 | 404 | of the C library, and are not defined by GCC itself. |
405 | ||
146ef39f | 406 | @node C Extensions |
407 | @chapter Extensions to the C Language Family | |
408 | @cindex extensions, C language | |
409 | @cindex C language extensions | |
410 | ||
67791935 | 411 | @opindex pedantic |
0858e3a2 | 412 | GNU C provides several language features not found in ISO standard C@. |
37744367 | 413 | (The @option{-pedantic} option directs GCC to print a warning message if |
146ef39f | 414 | any of these features is used.) To test for the availability of these |
415 | features in conditional compilation, check for a predefined macro | |
0858e3a2 | 416 | @code{__GNUC__}, which is always defined under GCC@. |
146ef39f | 417 | |
0858e3a2 | 418 | These extensions are available in C and Objective-C@. Most of them are |
146ef39f | 419 | also available in C++. @xref{C++ Extensions,,Extensions to the |
420 | C++ Language}, for extensions that apply @emph{only} to C++. | |
421 | ||
3cfa0cc4 | 422 | Some features that are in ISO C99 but not C89 or C++ are also, as |
423 | extensions, accepted by GCC in C89 mode and in C++. | |
78b1f616 | 424 | |
146ef39f | 425 | @menu |
426 | * Statement Exprs:: Putting statements and declarations inside expressions. | |
bdc33d98 | 427 | * Local Labels:: Labels local to a block. |
146ef39f | 428 | * Labels as Values:: Getting pointers to labels, and computed gotos. |
429 | * Nested Functions:: As in Algol and Pascal, lexical scoping of functions. | |
430 | * Constructing Calls:: Dispatching a call to another function. | |
146ef39f | 431 | * Typeof:: @code{typeof}: referring to the type of an expression. |
432 | * Lvalues:: Using @samp{?:}, @samp{,} and casts in lvalues. | |
433 | * Conditionals:: Omitting the middle operand of a @samp{?:} expression. | |
434 | * Long Long:: Double-word integers---@code{long long int}. | |
435 | * Complex:: Data types for complex numbers. | |
75bd5ada | 436 | * Hex Floats:: Hexadecimal floating-point constants. |
146ef39f | 437 | * Zero Length:: Zero-length arrays. |
438 | * Variable Length:: Arrays whose length is computed at run time. | |
710d60ed | 439 | * Empty Structures:: Structures with no members. |
da825954 | 440 | * Variadic Macros:: Macros with a variable number of arguments. |
441 | * Escaped Newlines:: Slightly looser rules for escaped newlines. | |
146ef39f | 442 | * Subscripting:: Any array can be subscripted, even if not an lvalue. |
443 | * Pointer Arith:: Arithmetic on @code{void}-pointers and function pointers. | |
444 | * Initializers:: Non-constant initializers. | |
3cfa0cc4 | 445 | * Compound Literals:: Compound literals give structures, unions |
146ef39f | 446 | or arrays as values. |
3cfa0cc4 | 447 | * Designated Inits:: Labeling elements of initializers. |
146ef39f | 448 | * Cast to Union:: Casting to union type from any member of the union. |
449 | * Case Ranges:: `case 1 ... 9' and such. | |
3cfa0cc4 | 450 | * Mixed Declarations:: Mixing declarations and code. |
146ef39f | 451 | * Function Attributes:: Declaring that functions have no side effects, |
452 | or that they can never return. | |
b31bfb3f | 453 | * Attribute Syntax:: Formal syntax for attributes. |
146ef39f | 454 | * Function Prototypes:: Prototype declarations and old-style definitions. |
455 | * C++ Comments:: C++ comments are recognized. | |
456 | * Dollar Signs:: Dollar sign is allowed in identifiers. | |
457 | * Character Escapes:: @samp{\e} stands for the character @key{ESC}. | |
458 | * Variable Attributes:: Specifying attributes of variables. | |
459 | * Type Attributes:: Specifying attributes of types. | |
460 | * Alignment:: Inquiring about the alignment of a type or variable. | |
461 | * Inline:: Defining inline functions (as fast as macros). | |
462 | * Extended Asm:: Assembler instructions with C expressions as operands. | |
463 | (With them you can define ``built-in'' functions.) | |
464 | * Constraints:: Constraints for asm operands | |
465 | * Asm Labels:: Specifying the assembler name to use for a C symbol. | |
466 | * Explicit Reg Vars:: Defining variables residing in specified registers. | |
467 | * Alternate Keywords:: @code{__const__}, @code{__asm__}, etc., for header files. | |
468 | * Incomplete Enums:: @code{enum foo;}, with details to follow. | |
469 | * Function Names:: Printable strings which are the name of the current | |
470 | function. | |
471 | * Return Address:: Getting the return or frame address of a function. | |
ee5925ea | 472 | * Vector Extensions:: Using vector instructions through built-in functions. |
7014838c | 473 | * Other Builtins:: Other built-in functions. |
ca5827cf | 474 | * Target Builtins:: Built-in functions specific to particular targets. |
49f45d83 | 475 | * Pragmas:: Pragmas accepted by GCC. |
f5b36051 | 476 | * Unnamed Fields:: Unnamed struct/union fields within structs/unions. |
2a6f0f81 | 477 | * Thread-Local:: Per-thread variables. |
146ef39f | 478 | @end menu |
146ef39f | 479 | |
480 | @node Statement Exprs | |
481 | @section Statements and Declarations in Expressions | |
482 | @cindex statements inside expressions | |
483 | @cindex declarations inside expressions | |
484 | @cindex expressions containing statements | |
485 | @cindex macros, statements in expressions | |
486 | ||
487 | @c the above section title wrapped and causes an underfull hbox.. i | |
488 | @c changed it from "within" to "in". --mew 4feb93 | |
146ef39f | 489 | A compound statement enclosed in parentheses may appear as an expression |
0858e3a2 | 490 | in GNU C@. This allows you to use loops, switches, and local variables |
146ef39f | 491 | within an expression. |
492 | ||
493 | Recall that a compound statement is a sequence of statements surrounded | |
494 | by braces; in this construct, parentheses go around the braces. For | |
495 | example: | |
496 | ||
497 | @example | |
498 | (@{ int y = foo (); int z; | |
499 | if (y > 0) z = y; | |
500 | else z = - y; | |
501 | z; @}) | |
502 | @end example | |
503 | ||
504 | @noindent | |
505 | is a valid (though slightly more complex than necessary) expression | |
506 | for the absolute value of @code{foo ()}. | |
507 | ||
508 | The last thing in the compound statement should be an expression | |
509 | followed by a semicolon; the value of this subexpression serves as the | |
510 | value of the entire construct. (If you use some other kind of statement | |
511 | last within the braces, the construct has type @code{void}, and thus | |
512 | effectively no value.) | |
513 | ||
514 | This feature is especially useful in making macro definitions ``safe'' (so | |
515 | that they evaluate each operand exactly once). For example, the | |
516 | ``maximum'' function is commonly defined as a macro in standard C as | |
517 | follows: | |
518 | ||
519 | @example | |
520 | #define max(a,b) ((a) > (b) ? (a) : (b)) | |
521 | @end example | |
522 | ||
523 | @noindent | |
524 | @cindex side effects, macro argument | |
525 | But this definition computes either @var{a} or @var{b} twice, with bad | |
526 | results if the operand has side effects. In GNU C, if you know the | |
527 | type of the operands (here let's assume @code{int}), you can define | |
528 | the macro safely as follows: | |
529 | ||
530 | @example | |
531 | #define maxint(a,b) \ | |
532 | (@{int _a = (a), _b = (b); _a > _b ? _a : _b; @}) | |
533 | @end example | |
534 | ||
535 | Embedded statements are not allowed in constant expressions, such as | |
8e5fcce7 | 536 | the value of an enumeration constant, the width of a bit-field, or |
146ef39f | 537 | the initial value of a static variable. |
538 | ||
539 | If you don't know the type of the operand, you can still do this, but you | |
f6f89f14 | 540 | must use @code{typeof} (@pxref{Typeof}). |
146ef39f | 541 | |
942ab15b | 542 | In G++, the result value of a statement expression undergoes array and |
543 | function pointer decay, and is returned by value to the enclosing | |
544 | expression. For instance, if @code{A} is a class, then | |
6a50ae27 | 545 | |
942ab15b | 546 | @smallexample |
547 | A a; | |
6a50ae27 | 548 | |
942ab15b | 549 | (@{a;@}).Foo () |
550 | @end smallexample | |
6a50ae27 | 551 | |
552 | @noindent | |
942ab15b | 553 | will construct a temporary @code{A} object to hold the result of the |
554 | statement expression, and that will be used to invoke @code{Foo}. | |
555 | Therefore the @code{this} pointer observed by @code{Foo} will not be the | |
556 | address of @code{a}. | |
557 | ||
558 | Any temporaries created within a statement within a statement expression | |
559 | will be destroyed at the statement's end. This makes statement | |
560 | expressions inside macros slightly different from function calls. In | |
561 | the latter case temporaries introduced during argument evaluation will | |
562 | be destroyed at the end of the statement that includes the function | |
563 | call. In the statement expression case they will be destroyed during | |
564 | the statement expression. For instance, | |
6a50ae27 | 565 | |
942ab15b | 566 | @smallexample |
567 | #define macro(a) (@{__typeof__(a) b = (a); b + 3; @}) | |
568 | template<typename T> T function(T a) @{ T b = a; return b + 3; @} | |
569 | ||
570 | void foo () | |
571 | @{ | |
572 | macro (X ()); | |
573 | function (X ()); | |
574 | @} | |
575 | @end smallexample | |
6a50ae27 | 576 | |
577 | @noindent | |
942ab15b | 578 | will have different places where temporaries are destroyed. For the |
579 | @code{macro} case, the temporary @code{X} will be destroyed just after | |
580 | the initialization of @code{b}. In the @code{function} case that | |
581 | temporary will be destroyed when the function returns. | |
6a50ae27 | 582 | |
583 | These considerations mean that it is probably a bad idea to use | |
584 | statement-expressions of this form in header files that are designed to | |
f12bbcea | 585 | work with C++. (Note that some versions of the GNU C Library contained |
586 | header files using statement-expression that lead to precisely this | |
587 | bug.) | |
6a50ae27 | 588 | |
146ef39f | 589 | @node Local Labels |
590 | @section Locally Declared Labels | |
591 | @cindex local labels | |
592 | @cindex macros, local labels | |
593 | ||
bdc33d98 | 594 | GCC allows you to declare @dfn{local labels} in any nested block |
595 | scope. A local label is just like an ordinary label, but you can | |
596 | only reference it (with a @code{goto} statement, or by taking its | |
597 | address) within the block in which it was declared. | |
146ef39f | 598 | |
599 | A local label declaration looks like this: | |
600 | ||
601 | @example | |
602 | __label__ @var{label}; | |
603 | @end example | |
604 | ||
605 | @noindent | |
606 | or | |
607 | ||
608 | @example | |
4ae74ddd | 609 | __label__ @var{label1}, @var{label2}, /* @r{@dots{}} */; |
146ef39f | 610 | @end example |
611 | ||
bdc33d98 | 612 | Local label declarations must come at the beginning of the block, |
613 | before any ordinary declarations or statements. | |
146ef39f | 614 | |
615 | The label declaration defines the label @emph{name}, but does not define | |
616 | the label itself. You must do this in the usual way, with | |
617 | @code{@var{label}:}, within the statements of the statement expression. | |
618 | ||
bdc33d98 | 619 | The local label feature is useful for complex macros. If a macro |
620 | contains nested loops, a @code{goto} can be useful for breaking out of | |
621 | them. However, an ordinary label whose scope is the whole function | |
622 | cannot be used: if the macro can be expanded several times in one | |
623 | function, the label will be multiply defined in that function. A | |
624 | local label avoids this problem. For example: | |
625 | ||
626 | @example | |
627 | #define SEARCH(value, array, target) \ | |
628 | do @{ \ | |
629 | __label__ found; \ | |
630 | typeof (target) _SEARCH_target = (target); \ | |
631 | typeof (*(array)) *_SEARCH_array = (array); \ | |
632 | int i, j; \ | |
633 | int value; \ | |
634 | for (i = 0; i < max; i++) \ | |
635 | for (j = 0; j < max; j++) \ | |
636 | if (_SEARCH_array[i][j] == _SEARCH_target) \ | |
637 | @{ (value) = i; goto found; @} \ | |
638 | (value) = -1; \ | |
639 | found:; \ | |
640 | @} while (0) | |
641 | @end example | |
642 | ||
643 | This could also be written using a statement-expression: | |
146ef39f | 644 | |
645 | @example | |
646 | #define SEARCH(array, target) \ | |
d90db7dc | 647 | (@{ \ |
146ef39f | 648 | __label__ found; \ |
649 | typeof (target) _SEARCH_target = (target); \ | |
650 | typeof (*(array)) *_SEARCH_array = (array); \ | |
651 | int i, j; \ | |
652 | int value; \ | |
653 | for (i = 0; i < max; i++) \ | |
654 | for (j = 0; j < max; j++) \ | |
655 | if (_SEARCH_array[i][j] == _SEARCH_target) \ | |
d90db7dc | 656 | @{ value = i; goto found; @} \ |
146ef39f | 657 | value = -1; \ |
658 | found: \ | |
659 | value; \ | |
660 | @}) | |
661 | @end example | |
662 | ||
bdc33d98 | 663 | Local label declarations also make the labels they declare visible to |
664 | nested functions, if there are any. @xref{Nested Functions}, for details. | |
665 | ||
146ef39f | 666 | @node Labels as Values |
667 | @section Labels as Values | |
668 | @cindex labels as values | |
669 | @cindex computed gotos | |
670 | @cindex goto with computed label | |
671 | @cindex address of a label | |
672 | ||
673 | You can get the address of a label defined in the current function | |
674 | (or a containing function) with the unary operator @samp{&&}. The | |
675 | value has type @code{void *}. This value is a constant and can be used | |
676 | wherever a constant of that type is valid. For example: | |
677 | ||
678 | @example | |
679 | void *ptr; | |
4ae74ddd | 680 | /* @r{@dots{}} */ |
146ef39f | 681 | ptr = &&foo; |
682 | @end example | |
683 | ||
684 | To use these values, you need to be able to jump to one. This is done | |
685 | with the computed goto statement@footnote{The analogous feature in | |
686 | Fortran is called an assigned goto, but that name seems inappropriate in | |
687 | C, where one can do more than simply store label addresses in label | |
688 | variables.}, @code{goto *@var{exp};}. For example, | |
689 | ||
690 | @example | |
691 | goto *ptr; | |
692 | @end example | |
693 | ||
694 | @noindent | |
695 | Any expression of type @code{void *} is allowed. | |
696 | ||
697 | One way of using these constants is in initializing a static array that | |
698 | will serve as a jump table: | |
699 | ||
700 | @example | |
701 | static void *array[] = @{ &&foo, &&bar, &&hack @}; | |
702 | @end example | |
703 | ||
704 | Then you can select a label with indexing, like this: | |
705 | ||
706 | @example | |
707 | goto *array[i]; | |
708 | @end example | |
709 | ||
710 | @noindent | |
711 | Note that this does not check whether the subscript is in bounds---array | |
712 | indexing in C never does that. | |
713 | ||
714 | Such an array of label values serves a purpose much like that of the | |
715 | @code{switch} statement. The @code{switch} statement is cleaner, so | |
716 | use that rather than an array unless the problem does not fit a | |
717 | @code{switch} statement very well. | |
718 | ||
719 | Another use of label values is in an interpreter for threaded code. | |
720 | The labels within the interpreter function can be stored in the | |
721 | threaded code for super-fast dispatching. | |
722 | ||
3b0848a2 | 723 | You may not use this mechanism to jump to code in a different function. |
56d9dfd0 | 724 | If you do that, totally unpredictable things will happen. The best way to |
146ef39f | 725 | avoid this is to store the label address only in automatic variables and |
726 | never pass it as an argument. | |
727 | ||
56d9dfd0 | 728 | An alternate way to write the above example is |
729 | ||
730 | @example | |
d90db7dc | 731 | static const int array[] = @{ &&foo - &&foo, &&bar - &&foo, |
732 | &&hack - &&foo @}; | |
56d9dfd0 | 733 | goto *(&&foo + array[i]); |
734 | @end example | |
735 | ||
736 | @noindent | |
737 | This is more friendly to code living in shared libraries, as it reduces | |
738 | the number of dynamic relocations that are needed, and by consequence, | |
739 | allows the data to be read-only. | |
740 | ||
146ef39f | 741 | @node Nested Functions |
742 | @section Nested Functions | |
743 | @cindex nested functions | |
744 | @cindex downward funargs | |
745 | @cindex thunks | |
746 | ||
747 | A @dfn{nested function} is a function defined inside another function. | |
748 | (Nested functions are not supported for GNU C++.) The nested function's | |
749 | name is local to the block where it is defined. For example, here we | |
750 | define a nested function named @code{square}, and call it twice: | |
751 | ||
752 | @example | |
753 | @group | |
754 | foo (double a, double b) | |
755 | @{ | |
756 | double square (double z) @{ return z * z; @} | |
757 | ||
758 | return square (a) + square (b); | |
759 | @} | |
760 | @end group | |
761 | @end example | |
762 | ||
763 | The nested function can access all the variables of the containing | |
764 | function that are visible at the point of its definition. This is | |
765 | called @dfn{lexical scoping}. For example, here we show a nested | |
766 | function which uses an inherited variable named @code{offset}: | |
767 | ||
768 | @example | |
70c2c81c | 769 | @group |
146ef39f | 770 | bar (int *array, int offset, int size) |
771 | @{ | |
772 | int access (int *array, int index) | |
773 | @{ return array[index + offset]; @} | |
774 | int i; | |
4ae74ddd | 775 | /* @r{@dots{}} */ |
146ef39f | 776 | for (i = 0; i < size; i++) |
4ae74ddd | 777 | /* @r{@dots{}} */ access (array, i) /* @r{@dots{}} */ |
146ef39f | 778 | @} |
70c2c81c | 779 | @end group |
146ef39f | 780 | @end example |
781 | ||
782 | Nested function definitions are permitted within functions in the places | |
783 | where variable definitions are allowed; that is, in any block, before | |
784 | the first statement in the block. | |
785 | ||
786 | It is possible to call the nested function from outside the scope of its | |
787 | name by storing its address or passing the address to another function: | |
788 | ||
789 | @example | |
790 | hack (int *array, int size) | |
791 | @{ | |
792 | void store (int index, int value) | |
793 | @{ array[index] = value; @} | |
794 | ||
795 | intermediate (store, size); | |
796 | @} | |
797 | @end example | |
798 | ||
799 | Here, the function @code{intermediate} receives the address of | |
800 | @code{store} as an argument. If @code{intermediate} calls @code{store}, | |
801 | the arguments given to @code{store} are used to store into @code{array}. | |
802 | But this technique works only so long as the containing function | |
803 | (@code{hack}, in this example) does not exit. | |
804 | ||
805 | If you try to call the nested function through its address after the | |
806 | containing function has exited, all hell will break loose. If you try | |
807 | to call it after a containing scope level has exited, and if it refers | |
808 | to some of the variables that are no longer in scope, you may be lucky, | |
809 | but it's not wise to take the risk. If, however, the nested function | |
810 | does not refer to anything that has gone out of scope, you should be | |
811 | safe. | |
812 | ||
0fff59be | 813 | GCC implements taking the address of a nested function using a technique |
814 | called @dfn{trampolines}. A paper describing them is available as | |
815 | ||
816 | @noindent | |
457b1f66 | 817 | @uref{http://people.debian.org/~aaronl/Usenix88-lexic.pdf}. |
146ef39f | 818 | |
819 | A nested function can jump to a label inherited from a containing | |
820 | function, provided the label was explicitly declared in the containing | |
821 | function (@pxref{Local Labels}). Such a jump returns instantly to the | |
822 | containing function, exiting the nested function which did the | |
823 | @code{goto} and any intermediate functions as well. Here is an example: | |
824 | ||
825 | @example | |
826 | @group | |
827 | bar (int *array, int offset, int size) | |
828 | @{ | |
829 | __label__ failure; | |
830 | int access (int *array, int index) | |
831 | @{ | |
832 | if (index > size) | |
833 | goto failure; | |
834 | return array[index + offset]; | |
835 | @} | |
836 | int i; | |
4ae74ddd | 837 | /* @r{@dots{}} */ |
146ef39f | 838 | for (i = 0; i < size; i++) |
4ae74ddd | 839 | /* @r{@dots{}} */ access (array, i) /* @r{@dots{}} */ |
840 | /* @r{@dots{}} */ | |
146ef39f | 841 | return 0; |
842 | ||
843 | /* @r{Control comes here from @code{access} | |
844 | if it detects an error.} */ | |
845 | failure: | |
846 | return -1; | |
847 | @} | |
848 | @end group | |
849 | @end example | |
850 | ||
851 | A nested function always has internal linkage. Declaring one with | |
852 | @code{extern} is erroneous. If you need to declare the nested function | |
853 | before its definition, use @code{auto} (which is otherwise meaningless | |
854 | for function declarations). | |
855 | ||
856 | @example | |
857 | bar (int *array, int offset, int size) | |
858 | @{ | |
859 | __label__ failure; | |
860 | auto int access (int *, int); | |
4ae74ddd | 861 | /* @r{@dots{}} */ |
146ef39f | 862 | int access (int *array, int index) |
863 | @{ | |
864 | if (index > size) | |
865 | goto failure; | |
866 | return array[index + offset]; | |
867 | @} | |
4ae74ddd | 868 | /* @r{@dots{}} */ |
146ef39f | 869 | @} |
870 | @end example | |
871 | ||
872 | @node Constructing Calls | |
873 | @section Constructing Function Calls | |
874 | @cindex constructing calls | |
875 | @cindex forwarding calls | |
876 | ||
877 | Using the built-in functions described below, you can record | |
878 | the arguments a function received, and call another function | |
879 | with the same arguments, without knowing the number or types | |
880 | of the arguments. | |
881 | ||
882 | You can also record the return value of that function call, | |
883 | and later return that value, without knowing what data type | |
884 | the function tried to return (as long as your caller expects | |
885 | that data type). | |
886 | ||
67791935 | 887 | @deftypefn {Built-in Function} {void *} __builtin_apply_args () |
888 | This built-in function returns a pointer to data | |
146ef39f | 889 | describing how to perform a call with the same arguments as were passed |
890 | to the current function. | |
891 | ||
892 | The function saves the arg pointer register, structure value address, | |
893 | and all registers that might be used to pass arguments to a function | |
894 | into a block of memory allocated on the stack. Then it returns the | |
895 | address of that block. | |
67791935 | 896 | @end deftypefn |
146ef39f | 897 | |
67791935 | 898 | @deftypefn {Built-in Function} {void *} __builtin_apply (void (*@var{function})(), void *@var{arguments}, size_t @var{size}) |
899 | This built-in function invokes @var{function} | |
900 | with a copy of the parameters described by @var{arguments} | |
901 | and @var{size}. | |
146ef39f | 902 | |
903 | The value of @var{arguments} should be the value returned by | |
904 | @code{__builtin_apply_args}. The argument @var{size} specifies the size | |
905 | of the stack argument data, in bytes. | |
906 | ||
67791935 | 907 | This function returns a pointer to data describing |
146ef39f | 908 | how to return whatever value was returned by @var{function}. The data |
909 | is saved in a block of memory allocated on the stack. | |
910 | ||
911 | It is not always simple to compute the proper value for @var{size}. The | |
912 | value is used by @code{__builtin_apply} to compute the amount of data | |
913 | that should be pushed on the stack and copied from the incoming argument | |
914 | area. | |
67791935 | 915 | @end deftypefn |
146ef39f | 916 | |
67791935 | 917 | @deftypefn {Built-in Function} {void} __builtin_return (void *@var{result}) |
146ef39f | 918 | This built-in function returns the value described by @var{result} from |
919 | the containing function. You should specify, for @var{result}, a value | |
920 | returned by @code{__builtin_apply}. | |
67791935 | 921 | @end deftypefn |
146ef39f | 922 | |
146ef39f | 923 | @node Typeof |
924 | @section Referring to a Type with @code{typeof} | |
925 | @findex typeof | |
926 | @findex sizeof | |
927 | @cindex macros, types of arguments | |
928 | ||
929 | Another way to refer to the type of an expression is with @code{typeof}. | |
930 | The syntax of using of this keyword looks like @code{sizeof}, but the | |
931 | construct acts semantically like a type name defined with @code{typedef}. | |
932 | ||
933 | There are two ways of writing the argument to @code{typeof}: with an | |
934 | expression or with a type. Here is an example with an expression: | |
935 | ||
936 | @example | |
937 | typeof (x[0](1)) | |
938 | @end example | |
939 | ||
940 | @noindent | |
f934d81d | 941 | This assumes that @code{x} is an array of pointers to functions; |
942 | the type described is that of the values of the functions. | |
146ef39f | 943 | |
944 | Here is an example with a typename as the argument: | |
945 | ||
946 | @example | |
947 | typeof (int *) | |
948 | @end example | |
949 | ||
950 | @noindent | |
951 | Here the type described is that of pointers to @code{int}. | |
952 | ||
78b1f616 | 953 | If you are writing a header file that must work when included in ISO C |
146ef39f | 954 | programs, write @code{__typeof__} instead of @code{typeof}. |
955 | @xref{Alternate Keywords}. | |
956 | ||
957 | A @code{typeof}-construct can be used anywhere a typedef name could be | |
958 | used. For example, you can use it in a declaration, in a cast, or inside | |
959 | of @code{sizeof} or @code{typeof}. | |
960 | ||
f6f89f14 | 961 | @code{typeof} is often useful in conjunction with the |
962 | statements-within-expressions feature. Here is how the two together can | |
963 | be used to define a safe ``maximum'' macro that operates on any | |
964 | arithmetic type and evaluates each of its arguments exactly once: | |
965 | ||
966 | @example | |
967 | #define max(a,b) \ | |
968 | (@{ typeof (a) _a = (a); \ | |
969 | typeof (b) _b = (b); \ | |
970 | _a > _b ? _a : _b; @}) | |
971 | @end example | |
972 | ||
2e411f1f | 973 | @cindex underscores in variables in macros |
974 | @cindex @samp{_} in variables in macros | |
975 | @cindex local variables in macros | |
976 | @cindex variables, local, in macros | |
977 | @cindex macros, local variables in | |
978 | ||
979 | The reason for using names that start with underscores for the local | |
980 | variables is to avoid conflicts with variable names that occur within the | |
981 | expressions that are substituted for @code{a} and @code{b}. Eventually we | |
982 | hope to design a new form of declaration syntax that allows you to declare | |
983 | variables whose scopes start only after their initializers; this will be a | |
984 | more reliable way to prevent such conflicts. | |
985 | ||
f6f89f14 | 986 | @noindent |
987 | Some more examples of the use of @code{typeof}: | |
988 | ||
146ef39f | 989 | @itemize @bullet |
990 | @item | |
991 | This declares @code{y} with the type of what @code{x} points to. | |
992 | ||
993 | @example | |
994 | typeof (*x) y; | |
995 | @end example | |
996 | ||
997 | @item | |
998 | This declares @code{y} as an array of such values. | |
999 | ||
1000 | @example | |
1001 | typeof (*x) y[4]; | |
1002 | @end example | |
1003 | ||
1004 | @item | |
1005 | This declares @code{y} as an array of pointers to characters: | |
1006 | ||
1007 | @example | |
1008 | typeof (typeof (char *)[4]) y; | |
1009 | @end example | |
1010 | ||
1011 | @noindent | |
1012 | It is equivalent to the following traditional C declaration: | |
1013 | ||
1014 | @example | |
1015 | char *y[4]; | |
1016 | @end example | |
1017 | ||
1018 | To see the meaning of the declaration using @code{typeof}, and why it | |
1019 | might be a useful way to write, let's rewrite it with these macros: | |
1020 | ||
1021 | @example | |
1022 | #define pointer(T) typeof(T *) | |
1023 | #define array(T, N) typeof(T [N]) | |
1024 | @end example | |
1025 | ||
1026 | @noindent | |
1027 | Now the declaration can be rewritten this way: | |
1028 | ||
1029 | @example | |
1030 | array (pointer (char), 4) y; | |
1031 | @end example | |
1032 | ||
1033 | @noindent | |
1034 | Thus, @code{array (pointer (char), 4)} is the type of arrays of 4 | |
1035 | pointers to @code{char}. | |
1036 | @end itemize | |
1037 | ||
f6f89f14 | 1038 | @emph{Compatibility Note:} In addition to @code{typeof}, GCC 2 supported |
1039 | a more limited extension which permitted one to write | |
1040 | ||
1041 | @example | |
1042 | typedef @var{T} = @var{expr}; | |
1043 | @end example | |
1044 | ||
1045 | @noindent | |
1046 | with the effect of declaring @var{T} to have the type of the expression | |
1047 | @var{expr}. This extension does not work with GCC 3 (versions between | |
1048 | 3.0 and 3.2 will crash; 3.2.1 and later give an error). Code which | |
1049 | relies on it should be rewritten to use @code{typeof}: | |
1050 | ||
1051 | @example | |
1052 | typedef typeof(@var{expr}) @var{T}; | |
1053 | @end example | |
1054 | ||
1055 | @noindent | |
1056 | This will work with all versions of GCC@. | |
1057 | ||
146ef39f | 1058 | @node Lvalues |
1059 | @section Generalized Lvalues | |
1060 | @cindex compound expressions as lvalues | |
1061 | @cindex expressions, compound, as lvalues | |
1062 | @cindex conditional expressions as lvalues | |
1063 | @cindex expressions, conditional, as lvalues | |
1064 | @cindex casts as lvalues | |
1065 | @cindex generalized lvalues | |
1066 | @cindex lvalues, generalized | |
1067 | @cindex extensions, @code{?:} | |
1068 | @cindex @code{?:} extensions | |
cfafa1e9 | 1069 | |
146ef39f | 1070 | Compound expressions, conditional expressions and casts are allowed as |
1071 | lvalues provided their operands are lvalues. This means that you can take | |
1072 | their addresses or store values into them. | |
1073 | ||
29c42daf | 1074 | Standard C++ allows compound expressions and conditional expressions |
1075 | as lvalues, and permits casts to reference type, so use of this | |
1076 | extension is not supported for C++ code. | |
146ef39f | 1077 | |
1078 | For example, a compound expression can be assigned, provided the last | |
1079 | expression in the sequence is an lvalue. These two expressions are | |
1080 | equivalent: | |
1081 | ||
1082 | @example | |
1083 | (a, b) += 5 | |
1084 | a, (b += 5) | |
1085 | @end example | |
1086 | ||
1087 | Similarly, the address of the compound expression can be taken. These two | |
1088 | expressions are equivalent: | |
1089 | ||
1090 | @example | |
1091 | &(a, b) | |
1092 | a, &b | |
1093 | @end example | |
1094 | ||
1095 | A conditional expression is a valid lvalue if its type is not void and the | |
1096 | true and false branches are both valid lvalues. For example, these two | |
1097 | expressions are equivalent: | |
1098 | ||
1099 | @example | |
1100 | (a ? b : c) = 5 | |
1101 | (a ? b = 5 : (c = 5)) | |
1102 | @end example | |
1103 | ||
1104 | A cast is a valid lvalue if its operand is an lvalue. A simple | |
1105 | assignment whose left-hand side is a cast works by converting the | |
1106 | right-hand side first to the specified type, then to the type of the | |
1107 | inner left-hand side expression. After this is stored, the value is | |
1108 | converted back to the specified type to become the value of the | |
1109 | assignment. Thus, if @code{a} has type @code{char *}, the following two | |
1110 | expressions are equivalent: | |
1111 | ||
1112 | @example | |
1113 | (int)a = 5 | |
1114 | (int)(a = (char *)(int)5) | |
1115 | @end example | |
1116 | ||
1117 | An assignment-with-arithmetic operation such as @samp{+=} applied to a cast | |
1118 | performs the arithmetic using the type resulting from the cast, and then | |
1119 | continues as in the previous case. Therefore, these two expressions are | |
1120 | equivalent: | |
1121 | ||
1122 | @example | |
1123 | (int)a += 5 | |
1124 | (int)(a = (char *)(int) ((int)a + 5)) | |
1125 | @end example | |
1126 | ||
1127 | You cannot take the address of an lvalue cast, because the use of its | |
1128 | address would not work out coherently. Suppose that @code{&(int)f} were | |
1129 | permitted, where @code{f} has type @code{float}. Then the following | |
1130 | statement would try to store an integer bit-pattern where a floating | |
1131 | point number belongs: | |
1132 | ||
1133 | @example | |
1134 | *&(int)f = 1; | |
1135 | @end example | |
1136 | ||
1137 | This is quite different from what @code{(int)f = 1} would do---that | |
1138 | would convert 1 to floating point and store it. Rather than cause this | |
1139 | inconsistency, we think it is better to prohibit use of @samp{&} on a cast. | |
1140 | ||
1141 | If you really do want an @code{int *} pointer with the address of | |
1142 | @code{f}, you can simply write @code{(int *)&f}. | |
1143 | ||
1144 | @node Conditionals | |
1145 | @section Conditionals with Omitted Operands | |
1146 | @cindex conditional expressions, extensions | |
1147 | @cindex omitted middle-operands | |
1148 | @cindex middle-operands, omitted | |
1149 | @cindex extensions, @code{?:} | |
1150 | @cindex @code{?:} extensions | |
1151 | ||
1152 | The middle operand in a conditional expression may be omitted. Then | |
1153 | if the first operand is nonzero, its value is the value of the conditional | |
1154 | expression. | |
1155 | ||
1156 | Therefore, the expression | |
1157 | ||
1158 | @example | |
1159 | x ? : y | |
1160 | @end example | |
1161 | ||
1162 | @noindent | |
1163 | has the value of @code{x} if that is nonzero; otherwise, the value of | |
1164 | @code{y}. | |
1165 | ||
1166 | This example is perfectly equivalent to | |
1167 | ||
1168 | @example | |
1169 | x ? x : y | |
1170 | @end example | |
1171 | ||
1172 | @cindex side effect in ?: | |
1173 | @cindex ?: side effect | |
1174 | @noindent | |
1175 | In this simple case, the ability to omit the middle operand is not | |
1176 | especially useful. When it becomes useful is when the first operand does, | |
1177 | or may (if it is a macro argument), contain a side effect. Then repeating | |
1178 | the operand in the middle would perform the side effect twice. Omitting | |
1179 | the middle operand uses the value already computed without the undesirable | |
1180 | effects of recomputing it. | |
1181 | ||
1182 | @node Long Long | |
1183 | @section Double-Word Integers | |
1184 | @cindex @code{long long} data types | |
1185 | @cindex double-word arithmetic | |
1186 | @cindex multiprecision arithmetic | |
3cfa0cc4 | 1187 | @cindex @code{LL} integer suffix |
1188 | @cindex @code{ULL} integer suffix | |
146ef39f | 1189 | |
3cfa0cc4 | 1190 | ISO C99 supports data types for integers that are at least 64 bits wide, |
1191 | and as an extension GCC supports them in C89 mode and in C++. | |
1192 | Simply write @code{long long int} for a signed integer, or | |
146ef39f | 1193 | @code{unsigned long long int} for an unsigned integer. To make an |
67791935 | 1194 | integer constant of type @code{long long int}, add the suffix @samp{LL} |
146ef39f | 1195 | to the integer. To make an integer constant of type @code{unsigned long |
67791935 | 1196 | long int}, add the suffix @samp{ULL} to the integer. |
146ef39f | 1197 | |
1198 | You can use these types in arithmetic like any other integer types. | |
1199 | Addition, subtraction, and bitwise boolean operations on these types | |
1200 | are open-coded on all types of machines. Multiplication is open-coded | |
1201 | if the machine supports fullword-to-doubleword a widening multiply | |
1202 | instruction. Division and shifts are open-coded only on machines that | |
1203 | provide special support. The operations that are not open-coded use | |
0858e3a2 | 1204 | special library routines that come with GCC@. |
146ef39f | 1205 | |
1206 | There may be pitfalls when you use @code{long long} types for function | |
1207 | arguments, unless you declare function prototypes. If a function | |
1208 | expects type @code{int} for its argument, and you pass a value of type | |
1209 | @code{long long int}, confusion will result because the caller and the | |
1210 | subroutine will disagree about the number of bytes for the argument. | |
1211 | Likewise, if the function expects @code{long long int} and you pass | |
1212 | @code{int}. The best way to avoid such problems is to use prototypes. | |
1213 | ||
1214 | @node Complex | |
1215 | @section Complex Numbers | |
1216 | @cindex complex numbers | |
3cfa0cc4 | 1217 | @cindex @code{_Complex} keyword |
1218 | @cindex @code{__complex__} keyword | |
146ef39f | 1219 | |
3cfa0cc4 | 1220 | ISO C99 supports complex floating data types, and as an extension GCC |
1221 | supports them in C89 mode and in C++, and supports complex integer data | |
1222 | types which are not part of ISO C99. You can declare complex types | |
1223 | using the keyword @code{_Complex}. As an extension, the older GNU | |
1224 | keyword @code{__complex__} is also supported. | |
146ef39f | 1225 | |
3cfa0cc4 | 1226 | For example, @samp{_Complex double x;} declares @code{x} as a |
146ef39f | 1227 | variable whose real part and imaginary part are both of type |
3cfa0cc4 | 1228 | @code{double}. @samp{_Complex short int y;} declares @code{y} to |
146ef39f | 1229 | have real and imaginary parts of type @code{short int}; this is not |
1230 | likely to be useful, but it shows that the set of complex types is | |
1231 | complete. | |
1232 | ||
1233 | To write a constant with a complex data type, use the suffix @samp{i} or | |
1234 | @samp{j} (either one; they are equivalent). For example, @code{2.5fi} | |
3cfa0cc4 | 1235 | has type @code{_Complex float} and @code{3i} has type |
1236 | @code{_Complex int}. Such a constant always has a pure imaginary | |
146ef39f | 1237 | value, but you can form any complex value you like by adding one to a |
3cfa0cc4 | 1238 | real constant. This is a GNU extension; if you have an ISO C99 |
1239 | conforming C library (such as GNU libc), and want to construct complex | |
1240 | constants of floating type, you should include @code{<complex.h>} and | |
1241 | use the macros @code{I} or @code{_Complex_I} instead. | |
146ef39f | 1242 | |
3cfa0cc4 | 1243 | @cindex @code{__real__} keyword |
1244 | @cindex @code{__imag__} keyword | |
146ef39f | 1245 | To extract the real part of a complex-valued expression @var{exp}, write |
1246 | @code{__real__ @var{exp}}. Likewise, use @code{__imag__} to | |
3cfa0cc4 | 1247 | extract the imaginary part. This is a GNU extension; for values of |
1248 | floating type, you should use the ISO C99 functions @code{crealf}, | |
1249 | @code{creal}, @code{creall}, @code{cimagf}, @code{cimag} and | |
1250 | @code{cimagl}, declared in @code{<complex.h>} and also provided as | |
0858e3a2 | 1251 | built-in functions by GCC@. |
146ef39f | 1252 | |
3cfa0cc4 | 1253 | @cindex complex conjugation |
146ef39f | 1254 | The operator @samp{~} performs complex conjugation when used on a value |
3cfa0cc4 | 1255 | with a complex type. This is a GNU extension; for values of |
1256 | floating type, you should use the ISO C99 functions @code{conjf}, | |
1257 | @code{conj} and @code{conjl}, declared in @code{<complex.h>} and also | |
0858e3a2 | 1258 | provided as built-in functions by GCC@. |
146ef39f | 1259 | |
37744367 | 1260 | GCC can allocate complex automatic variables in a noncontiguous |
146ef39f | 1261 | fashion; it's even possible for the real part to be in a register while |
1a050f4e | 1262 | the imaginary part is on the stack (or vice-versa). Only the DWARF2 |
1263 | debug info format can represent this, so use of DWARF2 is recommended. | |
1264 | If you are using the stabs debug info format, GCC describes a noncontiguous | |
1265 | complex variable as if it were two separate variables of noncomplex type. | |
146ef39f | 1266 | If the variable's actual name is @code{foo}, the two fictitious |
1267 | variables are named @code{foo$real} and @code{foo$imag}. You can | |
1268 | examine and set these two fictitious variables with your debugger. | |
1269 | ||
75bd5ada | 1270 | @node Hex Floats |
caee732e | 1271 | @section Hex Floats |
1272 | @cindex hex floats | |
7014838c | 1273 | |
3cfa0cc4 | 1274 | ISO C99 supports floating-point numbers written not only in the usual |
75bd5ada | 1275 | decimal notation, such as @code{1.55e1}, but also numbers such as |
3cfa0cc4 | 1276 | @code{0x1.fp3} written in hexadecimal format. As a GNU extension, GCC |
1277 | supports this in C89 mode (except in some cases when strictly | |
1278 | conforming) and in C++. In that format the | |
67791935 | 1279 | @samp{0x} hex introducer and the @samp{p} or @samp{P} exponent field are |
75bd5ada | 1280 | mandatory. The exponent is a decimal number that indicates the power of |
67791935 | 1281 | 2 by which the significant part will be multiplied. Thus @samp{0x1.f} is |
70c2c81c | 1282 | @tex |
1283 | $1 {15\over16}$, | |
1284 | @end tex | |
1285 | @ifnottex | |
1286 | 1 15/16, | |
1287 | @end ifnottex | |
1288 | @samp{p3} multiplies it by 8, and the value of @code{0x1.fp3} | |
75bd5ada | 1289 | is the same as @code{1.55e1}. |
1290 | ||
1291 | Unlike for floating-point numbers in the decimal notation the exponent | |
1292 | is always required in the hexadecimal notation. Otherwise the compiler | |
1293 | would not be able to resolve the ambiguity of, e.g., @code{0x1.f}. This | |
67791935 | 1294 | could mean @code{1.0f} or @code{1.9375} since @samp{f} is also the |
75bd5ada | 1295 | extension for floating-point constants of type @code{float}. |
1296 | ||
146ef39f | 1297 | @node Zero Length |
1298 | @section Arrays of Length Zero | |
1299 | @cindex arrays of length zero | |
1300 | @cindex zero-length arrays | |
1301 | @cindex length-zero arrays | |
21c8999d | 1302 | @cindex flexible array members |
146ef39f | 1303 | |
0858e3a2 | 1304 | Zero-length arrays are allowed in GNU C@. They are very useful as the |
15119d83 | 1305 | last element of a structure which is really a header for a variable-length |
146ef39f | 1306 | object: |
1307 | ||
1308 | @example | |
1309 | struct line @{ | |
1310 | int length; | |
1311 | char contents[0]; | |
1312 | @}; | |
1313 | ||
15119d83 | 1314 | struct line *thisline = (struct line *) |
1315 | malloc (sizeof (struct line) + this_length); | |
1316 | thisline->length = this_length; | |
146ef39f | 1317 | @end example |
1318 | ||
7fb9818b | 1319 | In ISO C90, you would have to give @code{contents} a length of 1, which |
146ef39f | 1320 | means either you waste space or complicate the argument to @code{malloc}. |
1321 | ||
3b0848a2 | 1322 | In ISO C99, you would use a @dfn{flexible array member}, which is |
15119d83 | 1323 | slightly different in syntax and semantics: |
1324 | ||
1325 | @itemize @bullet | |
1326 | @item | |
1327 | Flexible array members are written as @code{contents[]} without | |
1328 | the @code{0}. | |
1329 | ||
1330 | @item | |
1331 | Flexible array members have incomplete type, and so the @code{sizeof} | |
1332 | operator may not be applied. As a quirk of the original implementation | |
1333 | of zero-length arrays, @code{sizeof} evaluates to zero. | |
1334 | ||
1335 | @item | |
1336 | Flexible array members may only appear as the last member of a | |
26877a3f | 1337 | @code{struct} that is otherwise non-empty. |
ce09bc13 | 1338 | |
1339 | @item | |
1340 | A structure containing a flexible array member, or a union containing | |
1341 | such a structure (possibly recursively), may not be a member of a | |
1342 | structure or an element of an array. (However, these uses are | |
1343 | permitted by GCC as extensions.) | |
21c8999d | 1344 | @end itemize |
1b82e858 | 1345 | |
21c8999d | 1346 | GCC versions before 3.0 allowed zero-length arrays to be statically |
26877a3f | 1347 | initialized, as if they were flexible arrays. In addition to those |
1348 | cases that were useful, it also allowed initializations in situations | |
1349 | that would corrupt later data. Non-empty initialization of zero-length | |
1350 | arrays is now treated like any case where there are more initializer | |
1351 | elements than the array holds, in that a suitable warning about "excess | |
1352 | elements in array" is given, and the excess elements (all of them, in | |
1353 | this case) are ignored. | |
21c8999d | 1354 | |
1355 | Instead GCC allows static initialization of flexible array members. | |
1356 | This is equivalent to defining a new structure containing the original | |
1357 | structure followed by an array of sufficient size to contain the data. | |
0858f8a2 | 1358 | I.e.@: in the following, @code{f1} is constructed as if it were declared |
21c8999d | 1359 | like @code{f2}. |
1b82e858 | 1360 | |
1361 | @example | |
21c8999d | 1362 | struct f1 @{ |
1363 | int x; int y[]; | |
1364 | @} f1 = @{ 1, @{ 2, 3, 4 @} @}; | |
1365 | ||
1366 | struct f2 @{ | |
1367 | struct f1 f1; int data[3]; | |
1368 | @} f2 = @{ @{ 1 @}, @{ 2, 3, 4 @} @}; | |
1369 | @end example | |
15119d83 | 1370 | |
21c8999d | 1371 | @noindent |
1372 | The convenience of this extension is that @code{f1} has the desired | |
1373 | type, eliminating the need to consistently refer to @code{f2.f1}. | |
1374 | ||
1375 | This has symmetry with normal static arrays, in that an array of | |
1376 | unknown size is also written with @code{[]}. | |
1b82e858 | 1377 | |
21c8999d | 1378 | Of course, this extension only makes sense if the extra data comes at |
1379 | the end of a top-level object, as otherwise we would be overwriting | |
1380 | data at subsequent offsets. To avoid undue complication and confusion | |
1381 | with initialization of deeply nested arrays, we simply disallow any | |
1382 | non-empty initialization except when the structure is the top-level | |
1383 | object. For example: | |
15119d83 | 1384 | |
21c8999d | 1385 | @example |
1386 | struct foo @{ int x; int y[]; @}; | |
1387 | struct bar @{ struct foo z; @}; | |
1388 | ||
afb00aa2 | 1389 | struct foo a = @{ 1, @{ 2, 3, 4 @} @}; // @r{Valid.} |
1390 | struct bar b = @{ @{ 1, @{ 2, 3, 4 @} @} @}; // @r{Invalid.} | |
1391 | struct bar c = @{ @{ 1, @{ @} @} @}; // @r{Valid.} | |
1392 | struct foo d[1] = @{ @{ 1 @{ 2, 3, 4 @} @} @}; // @r{Invalid.} | |
1b82e858 | 1393 | @end example |
eae914e2 | 1394 | |
710d60ed | 1395 | @node Empty Structures |
1396 | @section Structures With No Members | |
1397 | @cindex empty structures | |
1398 | @cindex zero-size structures | |
1399 | ||
1400 | GCC permits a C structure to have no members: | |
1401 | ||
1402 | @example | |
1403 | struct empty @{ | |
1404 | @}; | |
1405 | @end example | |
1406 | ||
1407 | The structure will have size zero. In C++, empty structures are part | |
907e3369 | 1408 | of the language. G++ treats empty structures as if they had a single |
1409 | member of type @code{char}. | |
710d60ed | 1410 | |
146ef39f | 1411 | @node Variable Length |
1412 | @section Arrays of Variable Length | |
1413 | @cindex variable-length arrays | |
1414 | @cindex arrays of variable length | |
3cfa0cc4 | 1415 | @cindex VLAs |
146ef39f | 1416 | |
3cfa0cc4 | 1417 | Variable-length automatic arrays are allowed in ISO C99, and as an |
1418 | extension GCC accepts them in C89 mode and in C++. (However, GCC's | |
1419 | implementation of variable-length arrays does not yet conform in detail | |
1420 | to the ISO C99 standard.) These arrays are | |
146ef39f | 1421 | declared like any other automatic arrays, but with a length that is not |
1422 | a constant expression. The storage is allocated at the point of | |
1423 | declaration and deallocated when the brace-level is exited. For | |
1424 | example: | |
1425 | ||
1426 | @example | |
1427 | FILE * | |
1428 | concat_fopen (char *s1, char *s2, char *mode) | |
1429 | @{ | |
1430 | char str[strlen (s1) + strlen (s2) + 1]; | |
1431 | strcpy (str, s1); | |
1432 | strcat (str, s2); | |
1433 | return fopen (str, mode); | |
1434 | @} | |
1435 | @end example | |
1436 | ||
1437 | @cindex scope of a variable length array | |
1438 | @cindex variable-length array scope | |
1439 | @cindex deallocating variable length arrays | |
1440 | Jumping or breaking out of the scope of the array name deallocates the | |
1441 | storage. Jumping into the scope is not allowed; you get an error | |
1442 | message for it. | |
1443 | ||
1444 | @cindex @code{alloca} vs variable-length arrays | |
1445 | You can use the function @code{alloca} to get an effect much like | |
1446 | variable-length arrays. The function @code{alloca} is available in | |
1447 | many other C implementations (but not in all). On the other hand, | |
1448 | variable-length arrays are more elegant. | |
1449 | ||
1450 | There are other differences between these two methods. Space allocated | |
1451 | with @code{alloca} exists until the containing @emph{function} returns. | |
1452 | The space for a variable-length array is deallocated as soon as the array | |
1453 | name's scope ends. (If you use both variable-length arrays and | |
1454 | @code{alloca} in the same function, deallocation of a variable-length array | |
1455 | will also deallocate anything more recently allocated with @code{alloca}.) | |
1456 | ||
1457 | You can also use variable-length arrays as arguments to functions: | |
1458 | ||
1459 | @example | |
1460 | struct entry | |
1461 | tester (int len, char data[len][len]) | |
1462 | @{ | |
4ae74ddd | 1463 | /* @r{@dots{}} */ |
146ef39f | 1464 | @} |
1465 | @end example | |
1466 | ||
1467 | The length of an array is computed once when the storage is allocated | |
1468 | and is remembered for the scope of the array in case you access it with | |
1469 | @code{sizeof}. | |
1470 | ||
1471 | If you want to pass the array first and the length afterward, you can | |
1472 | use a forward declaration in the parameter list---another GNU extension. | |
1473 | ||
1474 | @example | |
1475 | struct entry | |
1476 | tester (int len; char data[len][len], int len) | |
1477 | @{ | |
4ae74ddd | 1478 | /* @r{@dots{}} */ |
146ef39f | 1479 | @} |
1480 | @end example | |
1481 | ||
1482 | @cindex parameter forward declaration | |
1483 | The @samp{int len} before the semicolon is a @dfn{parameter forward | |
1484 | declaration}, and it serves the purpose of making the name @code{len} | |
1485 | known when the declaration of @code{data} is parsed. | |
1486 | ||
1487 | You can write any number of such parameter forward declarations in the | |
1488 | parameter list. They can be separated by commas or semicolons, but the | |
1489 | last one must end with a semicolon, which is followed by the ``real'' | |
1490 | parameter declarations. Each forward declaration must match a ``real'' | |
3cfa0cc4 | 1491 | declaration in parameter name and data type. ISO C99 does not support |
1492 | parameter forward declarations. | |
146ef39f | 1493 | |
da825954 | 1494 | @node Variadic Macros |
1495 | @section Macros with a Variable Number of Arguments. | |
146ef39f | 1496 | @cindex variable number of arguments |
1497 | @cindex macro with variable arguments | |
1498 | @cindex rest argument (in macro) | |
da825954 | 1499 | @cindex variadic macros |
146ef39f | 1500 | |
da825954 | 1501 | In the ISO C standard of 1999, a macro can be declared to accept a |
1502 | variable number of arguments much as a function can. The syntax for | |
1503 | defining the macro is similar to that of a function. Here is an | |
1504 | example: | |
146ef39f | 1505 | |
b724fad7 | 1506 | @smallexample |
da825954 | 1507 | #define debug(format, ...) fprintf (stderr, format, __VA_ARGS__) |
b724fad7 | 1508 | @end smallexample |
146ef39f | 1509 | |
da825954 | 1510 | Here @samp{@dots{}} is a @dfn{variable argument}. In the invocation of |
1511 | such a macro, it represents the zero or more tokens until the closing | |
1512 | parenthesis that ends the invocation, including any commas. This set of | |
1513 | tokens replaces the identifier @code{__VA_ARGS__} in the macro body | |
1514 | wherever it appears. See the CPP manual for more information. | |
1515 | ||
1516 | GCC has long supported variadic macros, and used a different syntax that | |
1517 | allowed you to give a name to the variable arguments just like any other | |
1518 | argument. Here is an example: | |
146ef39f | 1519 | |
1520 | @example | |
da825954 | 1521 | #define debug(format, args...) fprintf (stderr, format, args) |
146ef39f | 1522 | @end example |
1523 | ||
da825954 | 1524 | This is in all ways equivalent to the ISO C example above, but arguably |
1525 | more readable and descriptive. | |
146ef39f | 1526 | |
da825954 | 1527 | GNU CPP has two further variadic macro extensions, and permits them to |
1528 | be used with either of the above forms of macro definition. | |
1529 | ||
1530 | In standard C, you are not allowed to leave the variable argument out | |
1531 | entirely; but you are allowed to pass an empty argument. For example, | |
1532 | this invocation is invalid in ISO C, because there is no comma after | |
1533 | the string: | |
146ef39f | 1534 | |
1535 | @example | |
da825954 | 1536 | debug ("A message") |
146ef39f | 1537 | @end example |
1538 | ||
da825954 | 1539 | GNU CPP permits you to completely omit the variable arguments in this |
1540 | way. In the above examples, the compiler would complain, though since | |
1541 | the expansion of the macro still has the extra comma after the format | |
1542 | string. | |
1543 | ||
1544 | To help solve this problem, CPP behaves specially for variable arguments | |
1545 | used with the token paste operator, @samp{##}. If instead you write | |
146ef39f | 1546 | |
b724fad7 | 1547 | @smallexample |
da825954 | 1548 | #define debug(format, ...) fprintf (stderr, format, ## __VA_ARGS__) |
b724fad7 | 1549 | @end smallexample |
146ef39f | 1550 | |
da825954 | 1551 | and if the variable arguments are omitted or empty, the @samp{##} |
1552 | operator causes the preprocessor to remove the comma before it. If you | |
1553 | do provide some variable arguments in your macro invocation, GNU CPP | |
1554 | does not complain about the paste operation and instead places the | |
1555 | variable arguments after the comma. Just like any other pasted macro | |
1556 | argument, these arguments are not macro expanded. | |
1557 | ||
1558 | @node Escaped Newlines | |
1559 | @section Slightly Looser Rules for Escaped Newlines | |
1560 | @cindex escaped newlines | |
1561 | @cindex newlines (escaped) | |
1562 | ||
455730ef | 1563 | Recently, the preprocessor has relaxed its treatment of escaped |
1564 | newlines. Previously, the newline had to immediately follow a | |
ebc03810 | 1565 | backslash. The current implementation allows whitespace in the form |
1566 | of spaces, horizontal and vertical tabs, and form feeds between the | |
da825954 | 1567 | backslash and the subsequent newline. The preprocessor issues a |
1568 | warning, but treats it as a valid escaped newline and combines the two | |
1569 | lines to form a single logical line. This works within comments and | |
ebc03810 | 1570 | tokens, as well as between tokens. Comments are @emph{not} treated as |
1571 | whitespace for the purposes of this relaxation, since they have not | |
1572 | yet been replaced with spaces. | |
146ef39f | 1573 | |
1574 | @node Subscripting | |
1575 | @section Non-Lvalue Arrays May Have Subscripts | |
1576 | @cindex subscripting | |
1577 | @cindex arrays, non-lvalue | |
1578 | ||
1579 | @cindex subscripting and function values | |
62827f44 | 1580 | In ISO C99, arrays that are not lvalues still decay to pointers, and |
1581 | may be subscripted, although they may not be modified or used after | |
1582 | the next sequence point and the unary @samp{&} operator may not be | |
1583 | applied to them. As an extension, GCC allows such arrays to be | |
1584 | subscripted in C89 mode, though otherwise they do not decay to | |
1585 | pointers outside C99 mode. For example, | |
3cfa0cc4 | 1586 | this is valid in GNU C though not valid in C89: |
146ef39f | 1587 | |
1588 | @example | |
1589 | @group | |
1590 | struct foo @{int a[4];@}; | |
1591 | ||
1592 | struct foo f(); | |
1593 | ||
1594 | bar (int index) | |
1595 | @{ | |
1596 | return f().a[index]; | |
1597 | @} | |
1598 | @end group | |
1599 | @end example | |
1600 | ||
1601 | @node Pointer Arith | |
1602 | @section Arithmetic on @code{void}- and Function-Pointers | |
1603 | @cindex void pointers, arithmetic | |
1604 | @cindex void, size of pointer to | |
1605 | @cindex function pointers, arithmetic | |
1606 | @cindex function, size of pointer to | |
1607 | ||
1608 | In GNU C, addition and subtraction operations are supported on pointers to | |
1609 | @code{void} and on pointers to functions. This is done by treating the | |
1610 | size of a @code{void} or of a function as 1. | |
1611 | ||
1612 | A consequence of this is that @code{sizeof} is also allowed on @code{void} | |
1613 | and on function types, and returns 1. | |
1614 | ||
67791935 | 1615 | @opindex Wpointer-arith |
1616 | The option @option{-Wpointer-arith} requests a warning if these extensions | |
146ef39f | 1617 | are used. |
1618 | ||
1619 | @node Initializers | |
1620 | @section Non-Constant Initializers | |
1621 | @cindex initializers, non-constant | |
1622 | @cindex non-constant initializers | |
1623 | ||
3cfa0cc4 | 1624 | As in standard C++ and ISO C99, the elements of an aggregate initializer for an |
0858e3a2 | 1625 | automatic variable are not required to be constant expressions in GNU C@. |
146ef39f | 1626 | Here is an example of an initializer with run-time varying elements: |
1627 | ||
1628 | @example | |
1629 | foo (float f, float g) | |
1630 | @{ | |
1631 | float beat_freqs[2] = @{ f-g, f+g @}; | |
4ae74ddd | 1632 | /* @r{@dots{}} */ |
146ef39f | 1633 | @} |
1634 | @end example | |
1635 | ||
3cfa0cc4 | 1636 | @node Compound Literals |
1637 | @section Compound Literals | |
146ef39f | 1638 | @cindex constructor expressions |
1639 | @cindex initializations in expressions | |
1640 | @cindex structures, constructor expression | |
1641 | @cindex expressions, constructor | |
3cfa0cc4 | 1642 | @cindex compound literals |
1643 | @c The GNU C name for what C99 calls compound literals was "constructor expressions". | |
146ef39f | 1644 | |
3cfa0cc4 | 1645 | ISO C99 supports compound literals. A compound literal looks like |
146ef39f | 1646 | a cast containing an initializer. Its value is an object of the |
1647 | type specified in the cast, containing the elements specified in | |
ec11e38e | 1648 | the initializer; it is an lvalue. As an extension, GCC supports |
1649 | compound literals in C89 mode and in C++. | |
146ef39f | 1650 | |
1651 | Usually, the specified type is a structure. Assume that | |
1652 | @code{struct foo} and @code{structure} are declared as shown: | |
1653 | ||
1654 | @example | |
1655 | struct foo @{int a; char b[2];@} structure; | |
1656 | @end example | |
1657 | ||
1658 | @noindent | |
3cfa0cc4 | 1659 | Here is an example of constructing a @code{struct foo} with a compound literal: |
146ef39f | 1660 | |
1661 | @example | |
1662 | structure = ((struct foo) @{x + y, 'a', 0@}); | |
1663 | @end example | |
1664 | ||
1665 | @noindent | |
1666 | This is equivalent to writing the following: | |
1667 | ||
1668 | @example | |
1669 | @{ | |
1670 | struct foo temp = @{x + y, 'a', 0@}; | |
1671 | structure = temp; | |
1672 | @} | |
1673 | @end example | |
1674 | ||
3cfa0cc4 | 1675 | You can also construct an array. If all the elements of the compound literal |
146ef39f | 1676 | are (made up of) simple constant expressions, suitable for use in |
ec11e38e | 1677 | initializers of objects of static storage duration, then the compound |
1678 | literal can be coerced to a pointer to its first element and used in | |
1679 | such an initializer, as shown here: | |
146ef39f | 1680 | |
1681 | @example | |
1682 | char **foo = (char *[]) @{ "x", "y", "z" @}; | |
1683 | @end example | |
1684 | ||
3cfa0cc4 | 1685 | Compound literals for scalar types and union types are is |
1686 | also allowed, but then the compound literal is equivalent | |
146ef39f | 1687 | to a cast. |
1688 | ||
4619fc15 | 1689 | As a GNU extension, GCC allows initialization of objects with static storage |
1690 | duration by compound literals (which is not possible in ISO C99, because | |
1691 | the initializer is not a constant). | |
1692 | It is handled as if the object was initialized only with the bracket | |
1693 | enclosed list if compound literal's and object types match. | |
1694 | The initializer list of the compound literal must be constant. | |
1695 | If the object being initialized has array type of unknown size, the size is | |
02643ebc | 1696 | determined by compound literal size. |
4619fc15 | 1697 | |
1698 | @example | |
1699 | static struct foo x = (struct foo) @{1, 'a', 'b'@}; | |
1700 | static int y[] = (int []) @{1, 2, 3@}; | |
1701 | static int z[] = (int [3]) @{1@}; | |
1702 | @end example | |
1703 | ||
1704 | @noindent | |
1705 | The above lines are equivalent to the following: | |
1706 | @example | |
1707 | static struct foo x = @{1, 'a', 'b'@}; | |
1708 | static int y[] = @{1, 2, 3@}; | |
02643ebc | 1709 | static int z[] = @{1, 0, 0@}; |
4619fc15 | 1710 | @end example |
1711 | ||
3cfa0cc4 | 1712 | @node Designated Inits |
1713 | @section Designated Initializers | |
146ef39f | 1714 | @cindex initializers with labeled elements |
1715 | @cindex labeled elements in initializers | |
1716 | @cindex case labels in initializers | |
3cfa0cc4 | 1717 | @cindex designated initializers |
146ef39f | 1718 | |
31bd149b | 1719 | Standard C89 requires the elements of an initializer to appear in a fixed |
146ef39f | 1720 | order, the same as the order of the elements in the array or structure |
1721 | being initialized. | |
1722 | ||
31bd149b | 1723 | In ISO C99 you can give the elements in any order, specifying the array |
1724 | indices or structure field names they apply to, and GNU C allows this as | |
1725 | an extension in C89 mode as well. This extension is not | |
146ef39f | 1726 | implemented in GNU C++. |
1727 | ||
31bd149b | 1728 | To specify an array index, write |
146ef39f | 1729 | @samp{[@var{index}] =} before the element value. For example, |
1730 | ||
1731 | @example | |
31bd149b | 1732 | int a[6] = @{ [4] = 29, [2] = 15 @}; |
146ef39f | 1733 | @end example |
1734 | ||
1735 | @noindent | |
1736 | is equivalent to | |
1737 | ||
1738 | @example | |
1739 | int a[6] = @{ 0, 0, 15, 0, 29, 0 @}; | |
1740 | @end example | |
1741 | ||
1742 | @noindent | |
1743 | The index values must be constant expressions, even if the array being | |
1744 | initialized is automatic. | |
1745 | ||
31bd149b | 1746 | An alternative syntax for this which has been obsolete since GCC 2.5 but |
1747 | GCC still accepts is to write @samp{[@var{index}]} before the element | |
1748 | value, with no @samp{=}. | |
1749 | ||
146ef39f | 1750 | To initialize a range of elements to the same value, write |
31bd149b | 1751 | @samp{[@var{first} ... @var{last}] = @var{value}}. This is a GNU |
1752 | extension. For example, | |
146ef39f | 1753 | |
1754 | @example | |
1755 | int widths[] = @{ [0 ... 9] = 1, [10 ... 99] = 2, [100] = 3 @}; | |
1756 | @end example | |
1757 | ||
989bbcfc | 1758 | @noindent |
1759 | If the value in it has side-effects, the side-effects will happen only once, | |
1760 | not for each initialized field by the range initializer. | |
1761 | ||
146ef39f | 1762 | @noindent |
1763 | Note that the length of the array is the highest value specified | |
1764 | plus one. | |
1765 | ||
1766 | In a structure initializer, specify the name of a field to initialize | |
31bd149b | 1767 | with @samp{.@var{fieldname} =} before the element value. For example, |
146ef39f | 1768 | given the following structure, |
1769 | ||
1770 | @example | |
1771 | struct point @{ int x, y; @}; | |
1772 | @end example | |
1773 | ||
1774 | @noindent | |
1775 | the following initialization | |
1776 | ||
1777 | @example | |
31bd149b | 1778 | struct point p = @{ .y = yvalue, .x = xvalue @}; |
146ef39f | 1779 | @end example |
1780 | ||
1781 | @noindent | |
1782 | is equivalent to | |
1783 | ||
1784 | @example | |
1785 | struct point p = @{ xvalue, yvalue @}; | |
1786 | @end example | |
1787 | ||
31bd149b | 1788 | Another syntax which has the same meaning, obsolete since GCC 2.5, is |
1789 | @samp{@var{fieldname}:}, as shown here: | |
146ef39f | 1790 | |
1791 | @example | |
31bd149b | 1792 | struct point p = @{ y: yvalue, x: xvalue @}; |
146ef39f | 1793 | @end example |
1794 | ||
3cfa0cc4 | 1795 | @cindex designators |
1796 | The @samp{[@var{index}]} or @samp{.@var{fieldname}} is known as a | |
1797 | @dfn{designator}. You can also use a designator (or the obsolete colon | |
1798 | syntax) when initializing a union, to specify which element of the union | |
1799 | should be used. For example, | |
146ef39f | 1800 | |
1801 | @example | |
1802 | union foo @{ int i; double d; @}; | |
1803 | ||
31bd149b | 1804 | union foo f = @{ .d = 4 @}; |
146ef39f | 1805 | @end example |
1806 | ||
1807 | @noindent | |
1808 | will convert 4 to a @code{double} to store it in the union using | |
1809 | the second element. By contrast, casting 4 to type @code{union foo} | |
1810 | would store it into the union as the integer @code{i}, since it is | |
1811 | an integer. (@xref{Cast to Union}.) | |
1812 | ||
1813 | You can combine this technique of naming elements with ordinary C | |
1814 | initialization of successive elements. Each initializer element that | |
3cfa0cc4 | 1815 | does not have a designator applies to the next consecutive element of the |
146ef39f | 1816 | array or structure. For example, |
1817 | ||
1818 | @example | |
1819 | int a[6] = @{ [1] = v1, v2, [4] = v4 @}; | |
1820 | @end example | |
1821 | ||
1822 | @noindent | |
1823 | is equivalent to | |
1824 | ||
1825 | @example | |
1826 | int a[6] = @{ 0, v1, v2, 0, v4, 0 @}; | |
1827 | @end example | |
1828 | ||
1829 | Labeling the elements of an array initializer is especially useful | |
1830 | when the indices are characters or belong to an @code{enum} type. | |
1831 | For example: | |
1832 | ||
1833 | @example | |
1834 | int whitespace[256] | |
1835 | = @{ [' '] = 1, ['\t'] = 1, ['\h'] = 1, | |
1836 | ['\f'] = 1, ['\n'] = 1, ['\r'] = 1 @}; | |
1837 | @end example | |
1838 | ||
3cfa0cc4 | 1839 | @cindex designator lists |
31bd149b | 1840 | You can also write a series of @samp{.@var{fieldname}} and |
3cfa0cc4 | 1841 | @samp{[@var{index}]} designators before an @samp{=} to specify a |
31bd149b | 1842 | nested subobject to initialize; the list is taken relative to the |
1843 | subobject corresponding to the closest surrounding brace pair. For | |
1844 | example, with the @samp{struct point} declaration above: | |
1845 | ||
b724fad7 | 1846 | @smallexample |
31bd149b | 1847 | struct point ptarray[10] = @{ [2].y = yv2, [2].x = xv2, [0].x = xv0 @}; |
b724fad7 | 1848 | @end smallexample |
31bd149b | 1849 | |
989bbcfc | 1850 | @noindent |
1851 | If the same field is initialized multiple times, it will have value from | |
1852 | the last initialization. If any such overridden initialization has | |
1853 | side-effect, it is unspecified whether the side-effect happens or not. | |
1854 | Currently, gcc will discard them and issue a warning. | |
1855 | ||
146ef39f | 1856 | @node Case Ranges |
1857 | @section Case Ranges | |
1858 | @cindex case ranges | |
1859 | @cindex ranges in case statements | |
1860 | ||
1861 | You can specify a range of consecutive values in a single @code{case} label, | |
1862 | like this: | |
1863 | ||
1864 | @example | |
1865 | case @var{low} ... @var{high}: | |
1866 | @end example | |
1867 | ||
1868 | @noindent | |
1869 | This has the same effect as the proper number of individual @code{case} | |
1870 | labels, one for each integer value from @var{low} to @var{high}, inclusive. | |
1871 | ||
1872 | This feature is especially useful for ranges of ASCII character codes: | |
1873 | ||
1874 | @example | |
1875 | case 'A' ... 'Z': | |
1876 | @end example | |
1877 | ||
1878 | @strong{Be careful:} Write spaces around the @code{...}, for otherwise | |
1879 | it may be parsed wrong when you use it with integer values. For example, | |
1880 | write this: | |
1881 | ||
1882 | @example | |
1883 | case 1 ... 5: | |
1884 | @end example | |
1885 | ||
1886 | @noindent | |
1887 | rather than this: | |
1888 | ||
1889 | @example | |
1890 | case 1...5: | |
1891 | @end example | |
1892 | ||
1893 | @node Cast to Union | |
1894 | @section Cast to a Union Type | |
1895 | @cindex cast to a union | |
1896 | @cindex union, casting to a | |
1897 | ||
1898 | A cast to union type is similar to other casts, except that the type | |
1899 | specified is a union type. You can specify the type either with | |
1900 | @code{union @var{tag}} or with a typedef name. A cast to union is actually | |
1901 | a constructor though, not a cast, and hence does not yield an lvalue like | |
3cfa0cc4 | 1902 | normal casts. (@xref{Compound Literals}.) |
146ef39f | 1903 | |
1904 | The types that may be cast to the union type are those of the members | |
1905 | of the union. Thus, given the following union and variables: | |
1906 | ||
1907 | @example | |
1908 | union foo @{ int i; double d; @}; | |
1909 | int x; | |
1910 | double y; | |
1911 | @end example | |
1912 | ||
1913 | @noindent | |
70c2c81c | 1914 | both @code{x} and @code{y} can be cast to type @code{union foo}. |
146ef39f | 1915 | |
1916 | Using the cast as the right-hand side of an assignment to a variable of | |
1917 | union type is equivalent to storing in a member of the union: | |
1918 | ||
1919 | @example | |
1920 | union foo u; | |
4ae74ddd | 1921 | /* @r{@dots{}} */ |
146ef39f | 1922 | u = (union foo) x @equiv{} u.i = x |
1923 | u = (union foo) y @equiv{} u.d = y | |
1924 | @end example | |
1925 | ||
1926 | You can also use the union cast as a function argument: | |
1927 | ||
1928 | @example | |
1929 | void hack (union foo); | |
4ae74ddd | 1930 | /* @r{@dots{}} */ |
146ef39f | 1931 | hack ((union foo) x); |
1932 | @end example | |
1933 | ||
3cfa0cc4 | 1934 | @node Mixed Declarations |
1935 | @section Mixed Declarations and Code | |
1936 | @cindex mixed declarations and code | |
1937 | @cindex declarations, mixed with code | |
1938 | @cindex code, mixed with declarations | |
1939 | ||
1940 | ISO C99 and ISO C++ allow declarations and code to be freely mixed | |
1941 | within compound statements. As an extension, GCC also allows this in | |
1942 | C89 mode. For example, you could do: | |
1943 | ||
1944 | @example | |
1945 | int i; | |
4ae74ddd | 1946 | /* @r{@dots{}} */ |
3cfa0cc4 | 1947 | i++; |
1948 | int j = i + 2; | |
1949 | @end example | |
1950 | ||
1951 | Each identifier is visible from where it is declared until the end of | |
1952 | the enclosing block. | |
1953 | ||
146ef39f | 1954 | @node Function Attributes |
1955 | @section Declaring Attributes of Functions | |
1956 | @cindex function attributes | |
1957 | @cindex declaring attributes of functions | |
1958 | @cindex functions that never return | |
1959 | @cindex functions that have no side effects | |
1960 | @cindex functions in arbitrary sections | |
1caefcbd | 1961 | @cindex functions that behave like malloc |
146ef39f | 1962 | @cindex @code{volatile} applied to function |
1963 | @cindex @code{const} applied to function | |
6a87209c | 1964 | @cindex functions with @code{printf}, @code{scanf}, @code{strftime} or @code{strfmon} style arguments |
dbf6c367 | 1965 | @cindex functions with non-null pointer arguments |
146ef39f | 1966 | @cindex functions that are passed arguments in registers on the 386 |
1967 | @cindex functions that pop the argument stack on the 386 | |
1968 | @cindex functions that do not pop the argument stack on the 386 | |
1969 | ||
1970 | In GNU C, you declare certain things about functions called in your program | |
1971 | which help the compiler optimize function calls and check your code more | |
1972 | carefully. | |
1973 | ||
1974 | The keyword @code{__attribute__} allows you to specify special | |
1975 | attributes when making a declaration. This keyword is followed by an | |
93f10b04 | 1976 | attribute specification inside double parentheses. The following |
b28b3cd2 | 1977 | attributes are currently defined for functions on all targets: |
af87ad83 | 1978 | @code{noreturn}, @code{noinline}, @code{always_inline}, |
fa987697 | 1979 | @code{pure}, @code{const}, @code{nothrow}, |
93f10b04 | 1980 | @code{format}, @code{format_arg}, @code{no_instrument_function}, |
1981 | @code{section}, @code{constructor}, @code{destructor}, @code{used}, | |
dbf6c367 | 1982 | @code{unused}, @code{deprecated}, @code{weak}, @code{malloc}, |
1983 | @code{alias}, and @code{nonnull}. Several other attributes are defined | |
1984 | for functions on particular target systems. Other attributes, including | |
1985 | @code{section} are supported for variables declarations | |
1986 | (@pxref{Variable Attributes}) and for types (@pxref{Type Attributes}). | |
146ef39f | 1987 | |
1988 | You may also specify attributes with @samp{__} preceding and following | |
1989 | each keyword. This allows you to use them in header files without | |
1990 | being concerned about a possible macro of the same name. For example, | |
1991 | you may use @code{__noreturn__} instead of @code{noreturn}. | |
1992 | ||
b31bfb3f | 1993 | @xref{Attribute Syntax}, for details of the exact syntax for using |
1994 | attributes. | |
1995 | ||
146ef39f | 1996 | @table @code |
1997 | @cindex @code{noreturn} function attribute | |
1998 | @item noreturn | |
1999 | A few standard library functions, such as @code{abort} and @code{exit}, | |
37744367 | 2000 | cannot return. GCC knows this automatically. Some programs define |
146ef39f | 2001 | their own functions that never return. You can declare them |
2002 | @code{noreturn} to tell the compiler this fact. For example, | |
2003 | ||
2004 | @smallexample | |
70c2c81c | 2005 | @group |
146ef39f | 2006 | void fatal () __attribute__ ((noreturn)); |
2007 | ||
2008 | void | |
4ae74ddd | 2009 | fatal (/* @r{@dots{}} */) |
146ef39f | 2010 | @{ |
4ae74ddd | 2011 | /* @r{@dots{}} */ /* @r{Print error message.} */ /* @r{@dots{}} */ |
146ef39f | 2012 | exit (1); |
2013 | @} | |
70c2c81c | 2014 | @end group |
146ef39f | 2015 | @end smallexample |
2016 | ||
2017 | The @code{noreturn} keyword tells the compiler to assume that | |
2018 | @code{fatal} cannot return. It can then optimize without regard to what | |
2019 | would happen if @code{fatal} ever did return. This makes slightly | |
2020 | better code. More importantly, it helps avoid spurious warnings of | |
2021 | uninitialized variables. | |
2022 | ||
2023 | Do not assume that registers saved by the calling function are | |
2024 | restored before calling the @code{noreturn} function. | |
2025 | ||
2026 | It does not make sense for a @code{noreturn} function to have a return | |
2027 | type other than @code{void}. | |
2028 | ||
37744367 | 2029 | The attribute @code{noreturn} is not implemented in GCC versions |
146ef39f | 2030 | earlier than 2.5. An alternative way to declare that a function does |
2031 | not return, which works in the current version and in some older | |
2032 | versions, is as follows: | |
2033 | ||
2034 | @smallexample | |
2035 | typedef void voidfn (); | |
2036 | ||
2037 | volatile voidfn fatal; | |
2038 | @end smallexample | |
2039 | ||
93f10b04 | 2040 | @cindex @code{noinline} function attribute |
2041 | @item noinline | |
2042 | This function attribute prevents a function from being considered for | |
2043 | inlining. | |
2044 | ||
af87ad83 | 2045 | @cindex @code{always_inline} function attribute |
2046 | @item always_inline | |
2047 | Generally, functions are not inlined unless optimization is specified. | |
2048 | For functions declared inline, this attribute inlines the function even | |
2049 | if no optimization level was specified. | |
2050 | ||
26dfc457 | 2051 | @cindex @code{pure} function attribute |
2052 | @item pure | |
2053 | Many functions have no effects except the return value and their | |
9de464a7 | 2054 | return value depends only on the parameters and/or global variables. |
26dfc457 | 2055 | Such a function can be subject |
146ef39f | 2056 | to common subexpression elimination and loop optimization just as an |
2057 | arithmetic operator would be. These functions should be declared | |
26dfc457 | 2058 | with the attribute @code{pure}. For example, |
146ef39f | 2059 | |
2060 | @smallexample | |
26dfc457 | 2061 | int square (int) __attribute__ ((pure)); |
146ef39f | 2062 | @end smallexample |
2063 | ||
2064 | @noindent | |
2065 | says that the hypothetical function @code{square} is safe to call | |
2066 | fewer times than the program says. | |
2067 | ||
26dfc457 | 2068 | Some of common examples of pure functions are @code{strlen} or @code{memcmp}. |
2069 | Interesting non-pure functions are functions with infinite loops or those | |
2070 | depending on volatile memory or other system resource, that may change between | |
1caefcbd | 2071 | two consecutive calls (such as @code{feof} in a multithreading environment). |
26dfc457 | 2072 | |
37744367 | 2073 | The attribute @code{pure} is not implemented in GCC versions earlier |
26dfc457 | 2074 | than 2.96. |
2075 | @cindex @code{const} function attribute | |
2076 | @item const | |
2077 | Many functions do not examine any values except their arguments, and | |
2078 | have no effects except the return value. Basically this is just slightly | |
67791935 | 2079 | more strict class than the @code{pure} attribute above, since function is not |
1caefcbd | 2080 | allowed to read global memory. |
26dfc457 | 2081 | |
2082 | @cindex pointer arguments | |
2083 | Note that a function that has pointer arguments and examines the data | |
2084 | pointed to must @emph{not} be declared @code{const}. Likewise, a | |
2085 | function that calls a non-@code{const} function usually must not be | |
2086 | @code{const}. It does not make sense for a @code{const} function to | |
2087 | return @code{void}. | |
2088 | ||
37744367 | 2089 | The attribute @code{const} is not implemented in GCC versions earlier |
146ef39f | 2090 | than 2.5. An alternative way to declare that a function has no side |
2091 | effects, which works in the current version and in some older versions, | |
2092 | is as follows: | |
2093 | ||
2094 | @smallexample | |
2095 | typedef int intfn (); | |
2096 | ||
2097 | extern const intfn square; | |
2098 | @end smallexample | |
2099 | ||
2100 | This approach does not work in GNU C++ from 2.6.0 on, since the language | |
2101 | specifies that the @samp{const} must be attached to the return value. | |
2102 | ||
fa987697 | 2103 | @cindex @code{nothrow} function attribute |
2104 | @item nothrow | |
2105 | The @code{nothrow} attribute is used to inform the compiler that a | |
2106 | function cannot throw an exception. For example, most functions in | |
2107 | the standard C library can be guaranteed not to throw an exception | |
2108 | with the notable exceptions of @code{qsort} and @code{bsearch} that | |
2109 | take function pointer arguments. The @code{nothrow} attribute is not | |
2110 | implemented in GCC versions earlier than 3.2. | |
146ef39f | 2111 | |
2112 | @item format (@var{archetype}, @var{string-index}, @var{first-to-check}) | |
2113 | @cindex @code{format} function attribute | |
67791935 | 2114 | @opindex Wformat |
d1f11193 | 2115 | The @code{format} attribute specifies that a function takes @code{printf}, |
6a87209c | 2116 | @code{scanf}, @code{strftime} or @code{strfmon} style arguments which |
2117 | should be type-checked against a format string. For example, the | |
2118 | declaration: | |
146ef39f | 2119 | |
2120 | @smallexample | |
2121 | extern int | |
2122 | my_printf (void *my_object, const char *my_format, ...) | |
2123 | __attribute__ ((format (printf, 2, 3))); | |
2124 | @end smallexample | |
2125 | ||
2126 | @noindent | |
2127 | causes the compiler to check the arguments in calls to @code{my_printf} | |
2128 | for consistency with the @code{printf} style format string argument | |
2129 | @code{my_format}. | |
2130 | ||
2131 | The parameter @var{archetype} determines how the format string is | |
6a87209c | 2132 | interpreted, and should be @code{printf}, @code{scanf}, @code{strftime} |
2133 | or @code{strfmon}. (You can also use @code{__printf__}, | |
2134 | @code{__scanf__}, @code{__strftime__} or @code{__strfmon__}.) The | |
146ef39f | 2135 | parameter @var{string-index} specifies which argument is the format |
2136 | string argument (starting from 1), while @var{first-to-check} is the | |
2137 | number of the first argument to check against the format string. For | |
2138 | functions where the arguments are not available to be checked (such as | |
2139 | @code{vprintf}), specify the third parameter as zero. In this case the | |
0f502901 | 2140 | compiler only checks the format string for consistency. For |
2141 | @code{strftime} formats, the third parameter is required to be zero. | |
6b4b1c7b | 2142 | Since non-static C++ methods have an implicit @code{this} argument, the |
2143 | arguments of such methods should be counted from two, not one, when | |
2144 | giving values for @var{string-index} and @var{first-to-check}. | |
146ef39f | 2145 | |
2146 | In the example above, the format string (@code{my_format}) is the second | |
2147 | argument of the function @code{my_print}, and the arguments to check | |
2148 | start with the third argument, so the correct parameters for the format | |
2149 | attribute are 2 and 3. | |
2150 | ||
67791935 | 2151 | @opindex ffreestanding |
146ef39f | 2152 | The @code{format} attribute allows you to identify your own functions |
37744367 | 2153 | which take format strings as arguments, so that GCC can check the |
0f502901 | 2154 | calls to these functions for errors. The compiler always (unless |
67791935 | 2155 | @option{-ffreestanding} is used) checks formats |
0f502901 | 2156 | for the standard library functions @code{printf}, @code{fprintf}, |
d1f11193 | 2157 | @code{sprintf}, @code{scanf}, @code{fscanf}, @code{sscanf}, @code{strftime}, |
146ef39f | 2158 | @code{vprintf}, @code{vfprintf} and @code{vsprintf} whenever such |
67791935 | 2159 | warnings are requested (using @option{-Wformat}), so there is no need to |
0f502901 | 2160 | modify the header file @file{stdio.h}. In C99 mode, the functions |
2161 | @code{snprintf}, @code{vsnprintf}, @code{vscanf}, @code{vfscanf} and | |
6a87209c | 2162 | @code{vsscanf} are also checked. Except in strictly conforming C |
c013a46e | 2163 | standard modes, the X/Open function @code{strfmon} is also checked as |
2164 | are @code{printf_unlocked} and @code{fprintf_unlocked}. | |
0f502901 | 2165 | @xref{C Dialect Options,,Options Controlling C Dialect}. |
146ef39f | 2166 | |
2167 | @item format_arg (@var{string-index}) | |
2168 | @cindex @code{format_arg} function attribute | |
67791935 | 2169 | @opindex Wformat-nonliteral |
6a87209c | 2170 | The @code{format_arg} attribute specifies that a function takes a format |
2171 | string for a @code{printf}, @code{scanf}, @code{strftime} or | |
2172 | @code{strfmon} style function and modifies it (for example, to translate | |
2173 | it into another language), so the result can be passed to a | |
2174 | @code{printf}, @code{scanf}, @code{strftime} or @code{strfmon} style | |
2175 | function (with the remaining arguments to the format function the same | |
2176 | as they would have been for the unmodified string). For example, the | |
2177 | declaration: | |
146ef39f | 2178 | |
2179 | @smallexample | |
2180 | extern char * | |
2181 | my_dgettext (char *my_domain, const char *my_format) | |
2182 | __attribute__ ((format_arg (2))); | |
2183 | @end smallexample | |
2184 | ||
2185 | @noindent | |
6a87209c | 2186 | causes the compiler to check the arguments in calls to a @code{printf}, |
2187 | @code{scanf}, @code{strftime} or @code{strfmon} type function, whose | |
2188 | format string argument is a call to the @code{my_dgettext} function, for | |
2189 | consistency with the format string argument @code{my_format}. If the | |
2190 | @code{format_arg} attribute had not been specified, all the compiler | |
2191 | could tell in such calls to format functions would be that the format | |
2192 | string argument is not constant; this would generate a warning when | |
67791935 | 2193 | @option{-Wformat-nonliteral} is used, but the calls could not be checked |
6a87209c | 2194 | without the attribute. |
146ef39f | 2195 | |
2196 | The parameter @var{string-index} specifies which argument is the format | |
6b4b1c7b | 2197 | string argument (starting from one). Since non-static C++ methods have |
2198 | an implicit @code{this} argument, the arguments of such methods should | |
2199 | be counted from two. | |
146ef39f | 2200 | |
2201 | The @code{format-arg} attribute allows you to identify your own | |
37744367 | 2202 | functions which modify format strings, so that GCC can check the |
6a87209c | 2203 | calls to @code{printf}, @code{scanf}, @code{strftime} or @code{strfmon} |
2204 | type function whose operands are a call to one of your own function. | |
2205 | The compiler always treats @code{gettext}, @code{dgettext}, and | |
2206 | @code{dcgettext} in this manner except when strict ISO C support is | |
67791935 | 2207 | requested by @option{-ansi} or an appropriate @option{-std} option, or |
2208 | @option{-ffreestanding} is used. @xref{C Dialect Options,,Options | |
6a87209c | 2209 | Controlling C Dialect}. |
146ef39f | 2210 | |
05888bbf | 2211 | @item nonnull (@var{arg-index}, @dots{}) |
dbf6c367 | 2212 | @cindex @code{nonnull} function attribute |
2213 | The @code{nonnull} attribute specifies that some function parameters should | |
2214 | be non-null pointers. For instance, the declaration: | |
2215 | ||
2216 | @smallexample | |
2217 | extern void * | |
2218 | my_memcpy (void *dest, const void *src, size_t len) | |
2219 | __attribute__((nonnull (1, 2))); | |
2220 | @end smallexample | |
2221 | ||
2222 | @noindent | |
2223 | causes the compiler to check that, in calls to @code{my_memcpy}, | |
2224 | arguments @var{dest} and @var{src} are non-null. If the compiler | |
2225 | determines that a null pointer is passed in an argument slot marked | |
2226 | as non-null, and the @option{-Wnonnull} option is enabled, a warning | |
2227 | is issued. The compiler may also choose to make optimizations based | |
2228 | on the knowledge that certain function arguments will not be null. | |
2229 | ||
2230 | If no argument index list is given to the @code{nonnull} attribute, | |
2231 | all pointer arguments are marked as non-null. To illustrate, the | |
2232 | following declaration is equivalent to the previous example: | |
2233 | ||
2234 | @smallexample | |
2235 | extern void * | |
2236 | my_memcpy (void *dest, const void *src, size_t len) | |
2237 | __attribute__((nonnull)); | |
2238 | @end smallexample | |
2239 | ||
abd28cef | 2240 | @item no_instrument_function |
2241 | @cindex @code{no_instrument_function} function attribute | |
67791935 | 2242 | @opindex finstrument-functions |
2243 | If @option{-finstrument-functions} is given, profiling function calls will | |
abd28cef | 2244 | be generated at entry and exit of most user-compiled functions. |
2245 | Functions with this attribute will not be so instrumented. | |
2246 | ||
67791935 | 2247 | @item section ("@var{section-name}") |
146ef39f | 2248 | @cindex @code{section} function attribute |
2249 | Normally, the compiler places the code it generates in the @code{text} section. | |
2250 | Sometimes, however, you need additional sections, or you need certain | |
2251 | particular functions to appear in special sections. The @code{section} | |
2252 | attribute specifies that a function lives in a particular section. | |
2253 | For example, the declaration: | |
2254 | ||
2255 | @smallexample | |
2256 | extern void foobar (void) __attribute__ ((section ("bar"))); | |
2257 | @end smallexample | |
2258 | ||
2259 | @noindent | |
2260 | puts the function @code{foobar} in the @code{bar} section. | |
2261 | ||
2262 | Some file formats do not support arbitrary sections so the @code{section} | |
2263 | attribute is not available on all platforms. | |
2264 | If you need to map the entire contents of a module to a particular | |
2265 | section, consider using the facilities of the linker instead. | |
2266 | ||
2267 | @item constructor | |
2268 | @itemx destructor | |
2269 | @cindex @code{constructor} function attribute | |
2270 | @cindex @code{destructor} function attribute | |
2271 | The @code{constructor} attribute causes the function to be called | |
2272 | automatically before execution enters @code{main ()}. Similarly, the | |
2273 | @code{destructor} attribute causes the function to be called | |
2274 | automatically after @code{main ()} has completed or @code{exit ()} has | |
2275 | been called. Functions with these attributes are useful for | |
2276 | initializing data that will be used implicitly during the execution of | |
2277 | the program. | |
2278 | ||
0858e3a2 | 2279 | These attributes are not currently implemented for Objective-C@. |
146ef39f | 2280 | |
93f10b04 | 2281 | @cindex @code{unused} attribute. |
146ef39f | 2282 | @item unused |
2283 | This attribute, attached to a function, means that the function is meant | |
37744367 | 2284 | to be possibly unused. GCC will not produce a warning for this |
2f215800 | 2285 | function. |
146ef39f | 2286 | |
93f10b04 | 2287 | @cindex @code{used} attribute. |
2288 | @item used | |
2289 | This attribute, attached to a function, means that code must be emitted | |
2290 | for the function even if it appears that the function is not referenced. | |
2291 | This is useful, for example, when the function is referenced only in | |
2292 | inline assembly. | |
2293 | ||
88da234d | 2294 | @cindex @code{deprecated} attribute. |
2295 | @item deprecated | |
2296 | The @code{deprecated} attribute results in a warning if the function | |
2297 | is used anywhere in the source file. This is useful when identifying | |
2298 | functions that are expected to be removed in a future version of a | |
2299 | program. The warning also includes the location of the declaration | |
2300 | of the deprecated function, to enable users to easily find further | |
2301 | information about why the function is deprecated, or what they should | |
2302 | do instead. Note that the warnings only occurs for uses: | |
2303 | ||
2304 | @smallexample | |
2305 | int old_fn () __attribute__ ((deprecated)); | |
2306 | int old_fn (); | |
2307 | int (*fn_ptr)() = old_fn; | |
2308 | @end smallexample | |
2309 | ||
2310 | results in a warning on line 3 but not line 2. | |
2311 | ||
2312 | The @code{deprecated} attribute can also be used for variables and | |
2313 | types (@pxref{Variable Attributes}, @pxref{Type Attributes}.) | |
2314 | ||
146ef39f | 2315 | @item weak |
2316 | @cindex @code{weak} attribute | |
2317 | The @code{weak} attribute causes the declaration to be emitted as a weak | |
2318 | symbol rather than a global. This is primarily useful in defining | |
2319 | library functions which can be overridden in user code, though it can | |
2320 | also be used with non-function declarations. Weak symbols are supported | |
2321 | for ELF targets, and also for a.out targets when using the GNU assembler | |
2322 | and linker. | |
2323 | ||
7259f3f8 | 2324 | @item malloc |
2325 | @cindex @code{malloc} attribute | |
2326 | The @code{malloc} attribute is used to tell the compiler that a function | |
2327 | may be treated as if it were the malloc function. The compiler assumes | |
ea1c20d0 | 2328 | that calls to malloc result in pointers that cannot alias anything. |
7259f3f8 | 2329 | This will often improve optimization. |
2330 | ||
67791935 | 2331 | @item alias ("@var{target}") |
146ef39f | 2332 | @cindex @code{alias} attribute |
2333 | The @code{alias} attribute causes the declaration to be emitted as an | |
2334 | alias for another symbol, which must be specified. For instance, | |
2335 | ||
2336 | @smallexample | |
b4cf9ec1 | 2337 | void __f () @{ /* @r{Do something.} */; @} |
146ef39f | 2338 | void f () __attribute__ ((weak, alias ("__f"))); |
2339 | @end smallexample | |
2340 | ||
2341 | declares @samp{f} to be a weak alias for @samp{__f}. In C++, the | |
2342 | mangled name for the target must be used. | |
2343 | ||
35073234 | 2344 | Not all target machines support this attribute. |
2345 | ||
b4cf9ec1 | 2346 | @item visibility ("@var{visibility_type}") |
2347 | @cindex @code{visibility} attribute | |
2348 | The @code{visibility} attribute on ELF targets causes the declaration | |
2d0ba106 | 2349 | to be emitted with default, hidden, protected or internal visibility. |
b4cf9ec1 | 2350 | |
2351 | @smallexample | |
2352 | void __attribute__ ((visibility ("protected"))) | |
2353 | f () @{ /* @r{Do something.} */; @} | |
2354 | int i __attribute__ ((visibility ("hidden"))); | |
2355 | @end smallexample | |
2356 | ||
0e5c52ed | 2357 | See the ELF gABI for complete details, but the short story is: |
21a24508 | 2358 | |
2359 | @table @dfn | |
2d0ba106 | 2360 | @item default |
2361 | Default visibility is the normal case for ELF. This value is | |
42cc08b5 | 2362 | available for the visibility attribute to override other options |
2d0ba106 | 2363 | that may change the assumed visibility of symbols. |
2364 | ||
21a24508 | 2365 | @item hidden |
2366 | Hidden visibility indicates that the symbol will not be placed into | |
2367 | the dynamic symbol table, so no other @dfn{module} (executable or | |
2368 | shared library) can reference it directly. | |
2369 | ||
2370 | @item protected | |
2371 | Protected visibility indicates that the symbol will be placed in the | |
2372 | dynamic symbol table, but that references within the defining module | |
2373 | will bind to the local symbol. That is, the symbol cannot be overridden | |
2374 | by another module. | |
2375 | ||
2376 | @item internal | |
2377 | Internal visibility is like hidden visibility, but with additional | |
2378 | processor specific semantics. Unless otherwise specified by the psABI, | |
2379 | gcc defines internal visibility to mean that the function is @emph{never} | |
ea1c20d0 | 2380 | called from another module. Note that hidden symbols, while they cannot |
21a24508 | 2381 | be referenced directly by other modules, can be referenced indirectly via |
2382 | function pointers. By indicating that a symbol cannot be called from | |
2383 | outside the module, gcc may for instance omit the load of a PIC register | |
2384 | since it is known that the calling function loaded the correct value. | |
2385 | @end table | |
2386 | ||
b4cf9ec1 | 2387 | Not all ELF targets support this attribute. |
2388 | ||
146ef39f | 2389 | @item regparm (@var{number}) |
3deb1c7e | 2390 | @cindex @code{regparm} attribute |
146ef39f | 2391 | @cindex functions that are passed arguments in registers on the 386 |
2392 | On the Intel 386, the @code{regparm} attribute causes the compiler to | |
67791935 | 2393 | pass up to @var{number} integer arguments in registers EAX, |
2394 | EDX, and ECX instead of on the stack. Functions that take a | |
146ef39f | 2395 | variable number of arguments will continue to be passed all of their |
2396 | arguments on the stack. | |
2397 | ||
3deb1c7e | 2398 | Beware that on some ELF systems this attribute is unsuitable for |
2399 | global functions in shared libraries with lazy binding (which is the | |
2400 | default). Lazy binding will send the first call via resolving code in | |
2401 | the loader, which might assume EAX, EDX and ECX can be clobbered, as | |
2402 | per the standard calling conventions. Solaris 8 is affected by this. | |
2403 | GNU systems with GLIBC 2.1 or higher, and FreeBSD, are believed to be | |
2404 | safe since the loaders there save all registers. (Lazy binding can be | |
2405 | disabled with the linker or the loader if desired, to avoid the | |
2406 | problem.) | |
2407 | ||
146ef39f | 2408 | @item stdcall |
2409 | @cindex functions that pop the argument stack on the 386 | |
2410 | On the Intel 386, the @code{stdcall} attribute causes the compiler to | |
2411 | assume that the called function will pop off the stack space used to | |
2412 | pass arguments, unless it takes a variable number of arguments. | |
2413 | ||
54f917d1 | 2414 | @item fastcall |
2415 | @cindex functions that pop the argument stack on the 386 | |
2416 | On the Intel 386, the @code{fastcall} attribute causes the compiler to | |
2417 | pass the first two arguments in the registers ECX and EDX. Subsequent | |
2418 | arguments are passed on the stack. The called function will pop the | |
2419 | arguments off the stack. If the number of arguments is variable all | |
2420 | arguments are pushed on the stack. | |
2421 | ||
146ef39f | 2422 | @item cdecl |
2423 | @cindex functions that do pop the argument stack on the 386 | |
67791935 | 2424 | @opindex mrtd |
146ef39f | 2425 | On the Intel 386, the @code{cdecl} attribute causes the compiler to |
2426 | assume that the calling function will pop off the stack space used to | |
2427 | pass arguments. This is | |
67791935 | 2428 | useful to override the effects of the @option{-mrtd} switch. |
146ef39f | 2429 | |
edd2f2ae | 2430 | @item longcall/shortcall |
146ef39f | 2431 | @cindex functions called via pointer on the RS/6000 and PowerPC |
2432 | On the RS/6000 and PowerPC, the @code{longcall} attribute causes the | |
edd2f2ae | 2433 | compiler to always call this function via a pointer, just as it would if |
2434 | the @option{-mlongcall} option had been specified. The @code{shortcall} | |
2435 | attribute causes the compiler not to do this. These attributes override | |
2436 | both the @option{-mlongcall} switch and the @code{#pragma longcall} | |
2437 | setting. | |
2438 | ||
ea1c20d0 | 2439 | @xref{RS/6000 and PowerPC Options}, for more information on whether long |
2440 | calls are necessary. | |
146ef39f | 2441 | |
78fe751b | 2442 | @item long_call/short_call |
2443 | @cindex indirect calls on ARM | |
ea1c20d0 | 2444 | This attribute specifies how a particular function is called on |
0858e3a2 | 2445 | ARM@. Both attributes override the @option{-mlong-calls} (@pxref{ARM Options}) |
78fe751b | 2446 | command line switch and @code{#pragma long_calls} settings. The |
2447 | @code{long_call} attribute causes the compiler to always call the | |
2448 | function by first loading its address into a register and then using the | |
2449 | contents of that register. The @code{short_call} attribute always places | |
2450 | the offset to the function from the call site into the @samp{BL} | |
2451 | instruction directly. | |
2452 | ||
146ef39f | 2453 | @item function_vector |
2454 | @cindex calling functions through the function vector on the H8/300 processors | |
eafbc061 | 2455 | Use this attribute on the H8/300 and H8/300H to indicate that the specified |
146ef39f | 2456 | function should be called through the function vector. Calling a |
2457 | function through the function vector will reduce code size, however; | |
2458 | the function vector has a limited size (maximum 128 entries on the H8/300 | |
2459 | and 64 entries on the H8/300H) and shares space with the interrupt vector. | |
2460 | ||
2461 | You must use GAS and GLD from GNU binutils version 2.7 or later for | |
eafbc061 | 2462 | this attribute to work correctly. |
146ef39f | 2463 | |
e27ad2d5 | 2464 | @item interrupt |
2465 | @cindex interrupt handler functions | |
3c8d298d | 2466 | Use this attribute on the ARM, AVR, C4x, M32R/D and Xstormy16 ports to indicate |
565d3099 | 2467 | that the specified function is an interrupt handler. The compiler will |
2468 | generate function entry and exit sequences suitable for use in an | |
2469 | interrupt handler when this attribute is present. | |
e27ad2d5 | 2470 | |
9763338f | 2471 | Note, interrupt handlers for the H8/300, H8/300H and SH processors can |
2472 | be specified via the @code{interrupt_handler} attribute. | |
e27ad2d5 | 2473 | |
ea1c20d0 | 2474 | Note, on the AVR, interrupts will be enabled inside the function. |
e27ad2d5 | 2475 | |
ea1c20d0 | 2476 | Note, for the ARM, you can specify the kind of interrupt to be handled by |
e27ad2d5 | 2477 | adding an optional parameter to the interrupt attribute like this: |
2478 | ||
2479 | @smallexample | |
2480 | void f () __attribute__ ((interrupt ("IRQ"))); | |
2481 | @end smallexample | |
2482 | ||
0858e3a2 | 2483 | Permissible values for this parameter are: IRQ, FIQ, SWI, ABORT and UNDEF@. |
e27ad2d5 | 2484 | |
9763338f | 2485 | @item interrupt_handler |
2486 | @cindex interrupt handler functions on the H8/300 and SH processors | |
eafbc061 | 2487 | Use this attribute on the H8/300, H8/300H and SH to indicate that the |
9763338f | 2488 | specified function is an interrupt handler. The compiler will generate |
2489 | function entry and exit sequences suitable for use in an interrupt | |
2490 | handler when this attribute is present. | |
2491 | ||
2492 | @item sp_switch | |
eafbc061 | 2493 | Use this attribute on the SH to indicate an @code{interrupt_handler} |
9763338f | 2494 | function should switch to an alternate stack. It expects a string |
2495 | argument that names a global variable holding the address of the | |
2496 | alternate stack. | |
2497 | ||
2498 | @smallexample | |
2499 | void *alt_stack; | |
70c2c81c | 2500 | void f () __attribute__ ((interrupt_handler, |
2501 | sp_switch ("alt_stack"))); | |
9763338f | 2502 | @end smallexample |
2503 | ||
2504 | @item trap_exit | |
eafbc061 | 2505 | Use this attribute on the SH for an @code{interrupt_handle} to return using |
9763338f | 2506 | @code{trapa} instead of @code{rte}. This attribute expects an integer |
2507 | argument specifying the trap number to be used. | |
2508 | ||
146ef39f | 2509 | @item eightbit_data |
2510 | @cindex eight bit data on the H8/300 and H8/300H | |
eafbc061 | 2511 | Use this attribute on the H8/300 and H8/300H to indicate that the specified |
146ef39f | 2512 | variable should be placed into the eight bit data section. |
2513 | The compiler will generate more efficient code for certain operations | |
2514 | on data in the eight bit data area. Note the eight bit data area is limited to | |
2515 | 256 bytes of data. | |
2516 | ||
2517 | You must use GAS and GLD from GNU binutils version 2.7 or later for | |
eafbc061 | 2518 | this attribute to work correctly. |
146ef39f | 2519 | |
2520 | @item tiny_data | |
2521 | @cindex tiny data section on the H8/300H | |
eafbc061 | 2522 | Use this attribute on the H8/300H to indicate that the specified |
146ef39f | 2523 | variable should be placed into the tiny data section. |
2524 | The compiler will generate more efficient code for loads and stores | |
2525 | on data in the tiny data section. Note the tiny data area is limited to | |
2526 | slightly under 32kbytes of data. | |
097cea9f | 2527 | |
97bbc51b | 2528 | @item signal |
2529 | @cindex signal handler functions on the AVR processors | |
eafbc061 | 2530 | Use this attribute on the AVR to indicate that the specified |
ea1c20d0 | 2531 | function is a signal handler. The compiler will generate function |
2532 | entry and exit sequences suitable for use in a signal handler when this | |
2533 | attribute is present. Interrupts will be disabled inside the function. | |
97bbc51b | 2534 | |
2535 | @item naked | |
e27ad2d5 | 2536 | @cindex function without a prologue/epilogue code |
3c8d298d | 2537 | Use this attribute on the ARM, AVR, C4x and IP2K ports to indicate that the |
ea1c20d0 | 2538 | specified function does not need prologue/epilogue sequences generated by |
770a909a | 2539 | the compiler. It is up to the programmer to provide these sequences. |
97bbc51b | 2540 | |
097cea9f | 2541 | @item model (@var{model-name}) |
2542 | @cindex function addressability on the M32R/D | |
b8629bcb | 2543 | @cindex variable addressability on the IA-64 |
2544 | ||
2545 | On the M32R/D, use this attribute to set the addressability of an | |
2546 | object, and of the code generated for a function. The identifier | |
2547 | @var{model-name} is one of @code{small}, @code{medium}, or | |
2548 | @code{large}, representing each of the code models. | |
097cea9f | 2549 | |
2550 | Small model objects live in the lower 16MB of memory (so that their | |
2551 | addresses can be loaded with the @code{ld24} instruction), and are | |
2552 | callable with the @code{bl} instruction. | |
2553 | ||
3b0848a2 | 2554 | Medium model objects may live anywhere in the 32-bit address space (the |
097cea9f | 2555 | compiler will generate @code{seth/add3} instructions to load their addresses), |
2556 | and are callable with the @code{bl} instruction. | |
2557 | ||
3b0848a2 | 2558 | Large model objects may live anywhere in the 32-bit address space (the |
097cea9f | 2559 | compiler will generate @code{seth/add3} instructions to load their addresses), |
2560 | and may not be reachable with the @code{bl} instruction (the compiler will | |
2561 | generate the much slower @code{seth/add3/jl} instruction sequence). | |
2562 | ||
b8629bcb | 2563 | On IA-64, use this attribute to set the addressability of an object. |
2564 | At present, the only supported identifier for @var{model-name} is | |
2565 | @code{small}, indicating addressability via ``small'' (22-bit) | |
2566 | addresses (so that their addresses can be loaded with the @code{addl} | |
2567 | instruction). Caveat: such addressing is by definition not position | |
2568 | independent and hence this attribute must not be used for objects | |
2569 | defined by shared libraries. | |
2570 | ||
76b9b5f9 | 2571 | @item far |
2572 | @cindex functions which handle memory bank switching | |
2573 | On 68HC11 and 68HC12 the @code{far} attribute causes the compiler to | |
2574 | use a calling convention that takes care of switching memory banks when | |
2575 | entering and leaving a function. This calling convention is also the | |
2576 | default when using the @option{-mlong-calls} option. | |
2577 | ||
2578 | On 68HC12 the compiler will use the @code{call} and @code{rtc} instructions | |
2579 | to call and return from a function. | |
2580 | ||
2581 | On 68HC11 the compiler will generate a sequence of instructions | |
2582 | to invoke a board-specific routine to switch the memory bank and call the | |
2583 | real function. The board-specific routine simulates a @code{call}. | |
2584 | At the end of a function, it will jump to a board-specific routine | |
2585 | instead of using @code{rts}. The board-specific return routine simulates | |
2586 | the @code{rtc}. | |
2587 | ||
2588 | @item near | |
2589 | @cindex functions which do not handle memory bank switching on 68HC11/68HC12 | |
2590 | On 68HC11 and 68HC12 the @code{near} attribute causes the compiler to | |
2591 | use the normal calling convention based on @code{jsr} and @code{rts}. | |
2592 | This attribute can be used to cancel the effect of the @option{-mlong-calls} | |
2593 | option. | |
2594 | ||
195d932a | 2595 | @item dllimport |
2596 | @cindex @code{__declspec(dllimport)} | |
2597 | On Windows targets, the @code{dllimport} attribute causes the compiler | |
2598 | to reference a function or variable via a global pointer to a pointer | |
2599 | that is set up by the Windows dll library. The pointer name is formed by | |
2600 | combining @code{_imp__} and the function or variable name. The attribute | |
2601 | implies @code{extern} storage. | |
2602 | ||
2603 | Currently, the attribute is ignored for inlined functions. If the | |
2604 | attribute is applied to a symbol @emph{definition}, an error is reported. | |
2605 | If a symbol previously declared @code{dllimport} is later defined, the | |
2606 | attribute is ignored in subsequent references, and a warning is emitted. | |
2607 | The attribute is also overriden by a subsequent declaration as | |
2608 | @code{dllexport}. | |
2609 | ||
2610 | When applied to C++ classes, the attribute marks non-inlined | |
2611 | member functions and static data members as imports. However, the | |
2612 | attribute is ignored for virtual methods to allow creation of vtables | |
2613 | using thunks. | |
2614 | ||
2615 | On cygwin, mingw and arm-pe targets, @code{__declspec(dllimport)} is | |
2616 | recognized as a synonym for @code{__attribute__ ((dllimport))} for | |
2617 | compatibility with other Windows compilers. | |
2618 | ||
2619 | The use of the @code{dllimport} attribute on functions is not necessary, | |
2620 | but provides a small performance benefit by eliminating a thunk in the | |
2621 | dll. The use of the @code{dllimport} attribute on imported variables was | |
2622 | required on older versions of GNU ld, but can now be avoided by passing | |
2623 | the @option{--enable-auto-import} switch to ld. As with functions, using | |
2624 | the attribute for a variable eliminates a thunk in the dll. | |
2625 | ||
2626 | One drawback to using this attribute is that a pointer to a function or | |
2627 | variable marked as dllimport cannot be used as a constant address. The | |
2628 | attribute can be disabled for functions by setting the | |
2629 | @option{-mnop-fun-dllimport} flag. | |
2630 | ||
2631 | @item dllexport | |
2632 | @cindex @code{__declspec(dllexport)} | |
2633 | On Windows targets the @code{dllexport} attribute causes the compiler to | |
2634 | provide a global pointer to a pointer in a dll, so that it can be | |
2635 | referenced with the @code{dllimport} attribute. The pointer name is | |
2636 | formed by combining @code{_imp__} and the function or variable name. | |
2637 | ||
2638 | Currently, the @code{dllexport}attribute is ignored for inlined | |
2639 | functions, but export can be forced by using the | |
2640 | @option{-fkeep-inline-functions} flag. The attribute is also ignored for | |
2641 | undefined symbols. | |
2642 | ||
2643 | When applied to C++ classes. the attribute marks defined non-inlined | |
2644 | member functions and static data members as exports. Static consts | |
2645 | initialized in-class are not marked unless they are also defined | |
2646 | out-of-class. | |
2647 | ||
2648 | On cygwin, mingw and arm-pe targets, @code{__declspec(dllexport)} is | |
2649 | recognized as a synonym for @code{__attribute__ ((dllexport))} for | |
2650 | compatibility with other Windows compilers. | |
2651 | ||
2652 | Alternative methods for including the symbol in the dll's export table | |
2653 | are to use a .def file with an @code{EXPORTS} section or, with GNU ld, | |
2654 | using the @option{--export-all} linker flag. | |
2655 | ||
146ef39f | 2656 | @end table |
2657 | ||
2658 | You can specify multiple attributes in a declaration by separating them | |
2659 | by commas within the double parentheses or by immediately following an | |
2660 | attribute declaration with another attribute declaration. | |
2661 | ||
2662 | @cindex @code{#pragma}, reason for not using | |
2663 | @cindex pragma, reason for not using | |
4449f3e0 | 2664 | Some people object to the @code{__attribute__} feature, suggesting that |
2665 | ISO C's @code{#pragma} should be used instead. At the time | |
2666 | @code{__attribute__} was designed, there were two reasons for not doing | |
2667 | this. | |
146ef39f | 2668 | |
2669 | @enumerate | |
2670 | @item | |
2671 | It is impossible to generate @code{#pragma} commands from a macro. | |
2672 | ||
2673 | @item | |
2674 | There is no telling what the same @code{#pragma} might mean in another | |
2675 | compiler. | |
2676 | @end enumerate | |
2677 | ||
4449f3e0 | 2678 | These two reasons applied to almost any application that might have been |
2679 | proposed for @code{#pragma}. It was basically a mistake to use | |
2680 | @code{#pragma} for @emph{anything}. | |
2681 | ||
2682 | The ISO C99 standard includes @code{_Pragma}, which now allows pragmas | |
2683 | to be generated from macros. In addition, a @code{#pragma GCC} | |
2684 | namespace is now in use for GCC-specific pragmas. However, it has been | |
2685 | found convenient to use @code{__attribute__} to achieve a natural | |
2686 | attachment of attributes to their corresponding declarations, whereas | |
2687 | @code{#pragma GCC} is of use for constructs that do not naturally form | |
2688 | part of the grammar. @xref{Other Directives,,Miscellaneous | |
2689 | Preprocessing Directives, cpp, The C Preprocessor}. | |
146ef39f | 2690 | |
b31bfb3f | 2691 | @node Attribute Syntax |
2692 | @section Attribute Syntax | |
2693 | @cindex attribute syntax | |
2694 | ||
2695 | This section describes the syntax with which @code{__attribute__} may be | |
2696 | used, and the constructs to which attribute specifiers bind, for the C | |
0858e3a2 | 2697 | language. Some details may vary for C++ and Objective-C@. Because of |
b31bfb3f | 2698 | infelicities in the grammar for attributes, some forms described here |
2699 | may not be successfully parsed in all cases. | |
2700 | ||
e3c541f0 | 2701 | There are some problems with the semantics of attributes in C++. For |
2702 | example, there are no manglings for attributes, although they may affect | |
2703 | code generation, so problems may arise when attributed types are used in | |
2704 | conjunction with templates or overloading. Similarly, @code{typeid} | |
2705 | does not distinguish between types with different attributes. Support | |
2706 | for attributes in C++ may be restricted in future to attributes on | |
2707 | declarations only, but not on nested declarators. | |
2708 | ||
b31bfb3f | 2709 | @xref{Function Attributes}, for details of the semantics of attributes |
2710 | applying to functions. @xref{Variable Attributes}, for details of the | |
2711 | semantics of attributes applying to variables. @xref{Type Attributes}, | |
2712 | for details of the semantics of attributes applying to structure, union | |
2713 | and enumerated types. | |
2714 | ||
2715 | An @dfn{attribute specifier} is of the form | |
2716 | @code{__attribute__ ((@var{attribute-list}))}. An @dfn{attribute list} | |
2717 | is a possibly empty comma-separated sequence of @dfn{attributes}, where | |
2718 | each attribute is one of the following: | |
2719 | ||
2720 | @itemize @bullet | |
2721 | @item | |
2722 | Empty. Empty attributes are ignored. | |
2723 | ||
2724 | @item | |
2725 | A word (which may be an identifier such as @code{unused}, or a reserved | |
2726 | word such as @code{const}). | |
2727 | ||
2728 | @item | |
2729 | A word, followed by, in parentheses, parameters for the attribute. | |
2730 | These parameters take one of the following forms: | |
2731 | ||
2732 | @itemize @bullet | |
2733 | @item | |
2734 | An identifier. For example, @code{mode} attributes use this form. | |
2735 | ||
2736 | @item | |
2737 | An identifier followed by a comma and a non-empty comma-separated list | |
2738 | of expressions. For example, @code{format} attributes use this form. | |
2739 | ||
2740 | @item | |
2741 | A possibly empty comma-separated list of expressions. For example, | |
2742 | @code{format_arg} attributes use this form with the list being a single | |
2743 | integer constant expression, and @code{alias} attributes use this form | |
2744 | with the list being a single string constant. | |
2745 | @end itemize | |
2746 | @end itemize | |
2747 | ||
2748 | An @dfn{attribute specifier list} is a sequence of one or more attribute | |
2749 | specifiers, not separated by any other tokens. | |
2750 | ||
2f215800 | 2751 | In GNU C, an attribute specifier list may appear after the colon following a |
b31bfb3f | 2752 | label, other than a @code{case} or @code{default} label. The only |
2753 | attribute it makes sense to use after a label is @code{unused}. This | |
2754 | feature is intended for code generated by programs which contains labels | |
2755 | that may be unused but which is compiled with @option{-Wall}. It would | |
2756 | not normally be appropriate to use in it human-written code, though it | |
2757 | could be useful in cases where the code that jumps to the label is | |
2f215800 | 2758 | contained within an @code{#ifdef} conditional. GNU C++ does not permit |
2759 | such placement of attribute lists, as it is permissible for a | |
2760 | declaration, which could begin with an attribute list, to be labelled in | |
2761 | C++. Declarations cannot be labelled in C90 or C99, so the ambiguity | |
2762 | does not arise there. | |
b31bfb3f | 2763 | |
2764 | An attribute specifier list may appear as part of a @code{struct}, | |
2765 | @code{union} or @code{enum} specifier. It may go either immediately | |
2766 | after the @code{struct}, @code{union} or @code{enum} keyword, or after | |
2767 | the closing brace. It is ignored if the content of the structure, union | |
2768 | or enumerated type is not defined in the specifier in which the | |
2769 | attribute specifier list is used---that is, in usages such as | |
2770 | @code{struct __attribute__((foo)) bar} with no following opening brace. | |
2771 | Where attribute specifiers follow the closing brace, they are considered | |
2772 | to relate to the structure, union or enumerated type defined, not to any | |
2773 | enclosing declaration the type specifier appears in, and the type | |
2774 | defined is not complete until after the attribute specifiers. | |
2775 | @c Otherwise, there would be the following problems: a shift/reduce | |
20dd417a | 2776 | @c conflict between attributes binding the struct/union/enum and |
b31bfb3f | 2777 | @c binding to the list of specifiers/qualifiers; and "aligned" |
2778 | @c attributes could use sizeof for the structure, but the size could be | |
2779 | @c changed later by "packed" attributes. | |
2780 | ||
2781 | Otherwise, an attribute specifier appears as part of a declaration, | |
2782 | counting declarations of unnamed parameters and type names, and relates | |
2783 | to that declaration (which may be nested in another declaration, for | |
e3c541f0 | 2784 | example in the case of a parameter declaration), or to a particular declarator |
2785 | within a declaration. Where an | |
d193f25f | 2786 | attribute specifier is applied to a parameter declared as a function or |
2787 | an array, it should apply to the function or array rather than the | |
2788 | pointer to which the parameter is implicitly converted, but this is not | |
2789 | yet correctly implemented. | |
b31bfb3f | 2790 | |
2791 | Any list of specifiers and qualifiers at the start of a declaration may | |
2792 | contain attribute specifiers, whether or not such a list may in that | |
2793 | context contain storage class specifiers. (Some attributes, however, | |
2794 | are essentially in the nature of storage class specifiers, and only make | |
2795 | sense where storage class specifiers may be used; for example, | |
2796 | @code{section}.) There is one necessary limitation to this syntax: the | |
2797 | first old-style parameter declaration in a function definition cannot | |
2798 | begin with an attribute specifier, because such an attribute applies to | |
2799 | the function instead by syntax described below (which, however, is not | |
2800 | yet implemented in this case). In some other cases, attribute | |
2801 | specifiers are permitted by this grammar but not yet supported by the | |
2802 | compiler. All attribute specifiers in this place relate to the | |
8e5fcce7 | 2803 | declaration as a whole. In the obsolescent usage where a type of |
b31bfb3f | 2804 | @code{int} is implied by the absence of type specifiers, such a list of |
2805 | specifiers and qualifiers may be an attribute specifier list with no | |
2806 | other specifiers or qualifiers. | |
2807 | ||
2808 | An attribute specifier list may appear immediately before a declarator | |
2809 | (other than the first) in a comma-separated list of declarators in a | |
2810 | declaration of more than one identifier using a single list of | |
ecb4f65e | 2811 | specifiers and qualifiers. Such attribute specifiers apply |
0fff59be | 2812 | only to the identifier before whose declarator they appear. For |
2813 | example, in | |
2814 | ||
2815 | @smallexample | |
2816 | __attribute__((noreturn)) void d0 (void), | |
2817 | __attribute__((format(printf, 1, 2))) d1 (const char *, ...), | |
2818 | d2 (void) | |
2819 | @end smallexample | |
2820 | ||
2821 | @noindent | |
2822 | the @code{noreturn} attribute applies to all the functions | |
ecb4f65e | 2823 | declared; the @code{format} attribute only applies to @code{d1}. |
b31bfb3f | 2824 | |
2825 | An attribute specifier list may appear immediately before the comma, | |
2826 | @code{=} or semicolon terminating the declaration of an identifier other | |
2827 | than a function definition. At present, such attribute specifiers apply | |
2828 | to the declared object or function, but in future they may attach to the | |
2829 | outermost adjacent declarator. In simple cases there is no difference, | |
228c5b30 | 2830 | but, for example, in |
0fff59be | 2831 | |
2832 | @smallexample | |
2833 | void (****f)(void) __attribute__((noreturn)); | |
2834 | @end smallexample | |
2835 | ||
2836 | @noindent | |
2837 | at present the @code{noreturn} attribute applies to @code{f}, which | |
2838 | causes a warning since @code{f} is not a function, but in future it may | |
2839 | apply to the function @code{****f}. The precise semantics of what | |
2840 | attributes in such cases will apply to are not yet specified. Where an | |
2841 | assembler name for an object or function is specified (@pxref{Asm | |
2842 | Labels}), at present the attribute must follow the @code{asm} | |
2843 | specification; in future, attributes before the @code{asm} specification | |
2844 | may apply to the adjacent declarator, and those after it to the declared | |
2845 | object or function. | |
b31bfb3f | 2846 | |
2847 | An attribute specifier list may, in future, be permitted to appear after | |
2848 | the declarator in a function definition (before any old-style parameter | |
2849 | declarations or the function body). | |
2850 | ||
1fd94215 | 2851 | Attribute specifiers may be mixed with type qualifiers appearing inside |
2852 | the @code{[]} of a parameter array declarator, in the C99 construct by | |
2853 | which such qualifiers are applied to the pointer to which the array is | |
2854 | implicitly converted. Such attribute specifiers apply to the pointer, | |
2855 | not to the array, but at present this is not implemented and they are | |
2856 | ignored. | |
2857 | ||
b31bfb3f | 2858 | An attribute specifier list may appear at the start of a nested |
2859 | declarator. At present, there are some limitations in this usage: the | |
e3c541f0 | 2860 | attributes correctly apply to the declarator, but for most individual |
2861 | attributes the semantics this implies are not implemented. | |
2862 | When attribute specifiers follow the @code{*} of a pointer | |
ecb4f65e | 2863 | declarator, they may be mixed with any type qualifiers present. |
e3c541f0 | 2864 | The following describes the formal semantics of this syntax. It will make the |
b31bfb3f | 2865 | most sense if you are familiar with the formal specification of |
2866 | declarators in the ISO C standard. | |
2867 | ||
2868 | Consider (as in C99 subclause 6.7.5 paragraph 4) a declaration @code{T | |
2869 | D1}, where @code{T} contains declaration specifiers that specify a type | |
2870 | @var{Type} (such as @code{int}) and @code{D1} is a declarator that | |
2871 | contains an identifier @var{ident}. The type specified for @var{ident} | |
2872 | for derived declarators whose type does not include an attribute | |
2873 | specifier is as in the ISO C standard. | |
2874 | ||
2875 | If @code{D1} has the form @code{( @var{attribute-specifier-list} D )}, | |
2876 | and the declaration @code{T D} specifies the type | |
2877 | ``@var{derived-declarator-type-list} @var{Type}'' for @var{ident}, then | |
2878 | @code{T D1} specifies the type ``@var{derived-declarator-type-list} | |
2879 | @var{attribute-specifier-list} @var{Type}'' for @var{ident}. | |
2880 | ||
2881 | If @code{D1} has the form @code{* | |
2882 | @var{type-qualifier-and-attribute-specifier-list} D}, and the | |
2883 | declaration @code{T D} specifies the type | |
2884 | ``@var{derived-declarator-type-list} @var{Type}'' for @var{ident}, then | |
2885 | @code{T D1} specifies the type ``@var{derived-declarator-type-list} | |
2886 | @var{type-qualifier-and-attribute-specifier-list} @var{Type}'' for | |
2887 | @var{ident}. | |
2888 | ||
228c5b30 | 2889 | For example, |
0fff59be | 2890 | |
2891 | @smallexample | |
2892 | void (__attribute__((noreturn)) ****f) (void); | |
2893 | @end smallexample | |
2894 | ||
2895 | @noindent | |
2896 | specifies the type ``pointer to pointer to pointer to pointer to | |
2897 | non-returning function returning @code{void}''. As another example, | |
2898 | ||
2899 | @smallexample | |
2900 | char *__attribute__((aligned(8))) *f; | |
2901 | @end smallexample | |
2902 | ||
2903 | @noindent | |
2904 | specifies the type ``pointer to 8-byte-aligned pointer to @code{char}''. | |
e3c541f0 | 2905 | Note again that this does not work with most attributes; for example, |
2906 | the usage of @samp{aligned} and @samp{noreturn} attributes given above | |
2907 | is not yet supported. | |
2908 | ||
2909 | For compatibility with existing code written for compiler versions that | |
2910 | did not implement attributes on nested declarators, some laxity is | |
2911 | allowed in the placing of attributes. If an attribute that only applies | |
2912 | to types is applied to a declaration, it will be treated as applying to | |
2913 | the type of that declaration. If an attribute that only applies to | |
2914 | declarations is applied to the type of a declaration, it will be treated | |
2915 | as applying to that declaration; and, for compatibility with code | |
2916 | placing the attributes immediately before the identifier declared, such | |
2917 | an attribute applied to a function return type will be treated as | |
2918 | applying to the function type, and such an attribute applied to an array | |
2919 | element type will be treated as applying to the array type. If an | |
2920 | attribute that only applies to function types is applied to a | |
2921 | pointer-to-function type, it will be treated as applying to the pointer | |
2922 | target type; if such an attribute is applied to a function return type | |
2923 | that is not a pointer-to-function type, it will be treated as applying | |
2924 | to the function type. | |
b31bfb3f | 2925 | |
146ef39f | 2926 | @node Function Prototypes |
2927 | @section Prototypes and Old-Style Function Definitions | |
2928 | @cindex function prototype declarations | |
2929 | @cindex old-style function definitions | |
2930 | @cindex promotion of formal parameters | |
2931 | ||
78b1f616 | 2932 | GNU C extends ISO C to allow a function prototype to override a later |
146ef39f | 2933 | old-style non-prototype definition. Consider the following example: |
2934 | ||
2935 | @example | |
2936 | /* @r{Use prototypes unless the compiler is old-fashioned.} */ | |
7223a120 | 2937 | #ifdef __STDC__ |
146ef39f | 2938 | #define P(x) x |
2939 | #else | |
2940 | #define P(x) () | |
2941 | #endif | |
2942 | ||
2943 | /* @r{Prototype function declaration.} */ | |
2944 | int isroot P((uid_t)); | |
2945 | ||
2946 | /* @r{Old-style function definition.} */ | |
2947 | int | |
2948 | isroot (x) /* ??? lossage here ??? */ | |
2949 | uid_t x; | |
2950 | @{ | |
2951 | return x == 0; | |
2952 | @} | |
2953 | @end example | |
2954 | ||
78b1f616 | 2955 | Suppose the type @code{uid_t} happens to be @code{short}. ISO C does |
146ef39f | 2956 | not allow this example, because subword arguments in old-style |
2957 | non-prototype definitions are promoted. Therefore in this example the | |
2958 | function definition's argument is really an @code{int}, which does not | |
2959 | match the prototype argument type of @code{short}. | |
2960 | ||
78b1f616 | 2961 | This restriction of ISO C makes it hard to write code that is portable |
146ef39f | 2962 | to traditional C compilers, because the programmer does not know |
2963 | whether the @code{uid_t} type is @code{short}, @code{int}, or | |
2964 | @code{long}. Therefore, in cases like these GNU C allows a prototype | |
2965 | to override a later old-style definition. More precisely, in GNU C, a | |
2966 | function prototype argument type overrides the argument type specified | |
2967 | by a later old-style definition if the former type is the same as the | |
2968 | latter type before promotion. Thus in GNU C the above example is | |
2969 | equivalent to the following: | |
2970 | ||
2971 | @example | |
2972 | int isroot (uid_t); | |
2973 | ||
2974 | int | |
2975 | isroot (uid_t x) | |
2976 | @{ | |
2977 | return x == 0; | |
2978 | @} | |
2979 | @end example | |
2980 | ||
0fff59be | 2981 | @noindent |
146ef39f | 2982 | GNU C++ does not support old-style function definitions, so this |
2983 | extension is irrelevant. | |
2984 | ||
2985 | @node C++ Comments | |
2986 | @section C++ Style Comments | |
2987 | @cindex // | |
2988 | @cindex C++ comments | |
2989 | @cindex comments, C++ style | |
2990 | ||
2991 | In GNU C, you may use C++ style comments, which start with @samp{//} and | |
2992 | continue until the end of the line. Many other C implementations allow | |
455730ef | 2993 | such comments, and they are included in the 1999 C standard. However, |
2994 | C++ style comments are not recognized if you specify an @option{-std} | |
2995 | option specifying a version of ISO C before C99, or @option{-ansi} | |
2996 | (equivalent to @option{-std=c89}). | |
146ef39f | 2997 | |
2998 | @node Dollar Signs | |
2999 | @section Dollar Signs in Identifier Names | |
3000 | @cindex $ | |
3001 | @cindex dollar signs in identifier names | |
3002 | @cindex identifier names, dollar signs in | |
3003 | ||
fae2383c | 3004 | In GNU C, you may normally use dollar signs in identifier names. |
3005 | This is because many traditional C implementations allow such identifiers. | |
3006 | However, dollar signs in identifiers are not supported on a few target | |
3007 | machines, typically because the target assembler does not allow them. | |
146ef39f | 3008 | |
3009 | @node Character Escapes | |
3010 | @section The Character @key{ESC} in Constants | |
3011 | ||
3012 | You can use the sequence @samp{\e} in a string or character constant to | |
3013 | stand for the ASCII character @key{ESC}. | |
3014 | ||
3015 | @node Alignment | |
3016 | @section Inquiring on Alignment of Types or Variables | |
3017 | @cindex alignment | |
3018 | @cindex type alignment | |
3019 | @cindex variable alignment | |
3020 | ||
3021 | The keyword @code{__alignof__} allows you to inquire about how an object | |
3022 | is aligned, or the minimum alignment usually required by a type. Its | |
3023 | syntax is just like @code{sizeof}. | |
3024 | ||
3025 | For example, if the target machine requires a @code{double} value to be | |
3026 | aligned on an 8-byte boundary, then @code{__alignof__ (double)} is 8. | |
3027 | This is true on many RISC machines. On more traditional machine | |
3028 | designs, @code{__alignof__ (double)} is 4 or even 2. | |
3029 | ||
3030 | Some machines never actually require alignment; they allow reference to any | |
ea1c20d0 | 3031 | data type even at an odd address. For these machines, @code{__alignof__} |
146ef39f | 3032 | reports the @emph{recommended} alignment of a type. |
3033 | ||
d3200805 | 3034 | If the operand of @code{__alignof__} is an lvalue rather than a type, |
3035 | its value is the required alignment for its type, taking into account | |
3036 | any minimum alignment specified with GCC's @code{__attribute__} | |
3037 | extension (@pxref{Variable Attributes}). For example, after this | |
3038 | declaration: | |
146ef39f | 3039 | |
3040 | @example | |
3041 | struct foo @{ int x; char y; @} foo1; | |
3042 | @end example | |
3043 | ||
3044 | @noindent | |
d3200805 | 3045 | the value of @code{__alignof__ (foo1.y)} is 1, even though its actual |
3046 | alignment is probably 2 or 4, the same as @code{__alignof__ (int)}. | |
146ef39f | 3047 | |
c0272e26 | 3048 | It is an error to ask for the alignment of an incomplete type. |
3049 | ||
146ef39f | 3050 | @node Variable Attributes |
3051 | @section Specifying Attributes of Variables | |
3052 | @cindex attribute of variables | |
3053 | @cindex variable attributes | |
3054 | ||
3055 | The keyword @code{__attribute__} allows you to specify special | |
3056 | attributes of variables or structure fields. This keyword is followed | |
e7d1f980 | 3057 | by an attribute specification inside double parentheses. Some |
3058 | attributes are currently defined generically for variables. | |
3059 | Other attributes are defined for variables on particular target | |
3060 | systems. Other attributes are available for functions | |
3061 | (@pxref{Function Attributes}) and for types (@pxref{Type Attributes}). | |
3062 | Other front ends might define more attributes | |
3063 | (@pxref{C++ Extensions,,Extensions to the C++ Language}). | |
146ef39f | 3064 | |
3065 | You may also specify attributes with @samp{__} preceding and following | |
3066 | each keyword. This allows you to use them in header files without | |
3067 | being concerned about a possible macro of the same name. For example, | |
3068 | you may use @code{__aligned__} instead of @code{aligned}. | |
3069 | ||
b31bfb3f | 3070 | @xref{Attribute Syntax}, for details of the exact syntax for using |
3071 | attributes. | |
3072 | ||
146ef39f | 3073 | @table @code |
3074 | @cindex @code{aligned} attribute | |
3075 | @item aligned (@var{alignment}) | |
3076 | This attribute specifies a minimum alignment for the variable or | |
3077 | structure field, measured in bytes. For example, the declaration: | |
3078 | ||
3079 | @smallexample | |
3080 | int x __attribute__ ((aligned (16))) = 0; | |
3081 | @end smallexample | |
3082 | ||
3083 | @noindent | |
3084 | causes the compiler to allocate the global variable @code{x} on a | |
3085 | 16-byte boundary. On a 68040, this could be used in conjunction with | |
3086 | an @code{asm} expression to access the @code{move16} instruction which | |
3087 | requires 16-byte aligned operands. | |
3088 | ||
3089 | You can also specify the alignment of structure fields. For example, to | |
3090 | create a double-word aligned @code{int} pair, you could write: | |
3091 | ||
3092 | @smallexample | |
3093 | struct foo @{ int x[2] __attribute__ ((aligned (8))); @}; | |
3094 | @end smallexample | |
3095 | ||
3096 | @noindent | |
3097 | This is an alternative to creating a union with a @code{double} member | |
3098 | that forces the union to be double-word aligned. | |
3099 | ||
146ef39f | 3100 | As in the preceding examples, you can explicitly specify the alignment |
3101 | (in bytes) that you wish the compiler to use for a given variable or | |
3102 | structure field. Alternatively, you can leave out the alignment factor | |
3103 | and just ask the compiler to align a variable or field to the maximum | |
3104 | useful alignment for the target machine you are compiling for. For | |
3105 | example, you could write: | |
3106 | ||
3107 | @smallexample | |
3108 | short array[3] __attribute__ ((aligned)); | |
3109 | @end smallexample | |
3110 | ||
3111 | Whenever you leave out the alignment factor in an @code{aligned} attribute | |
3112 | specification, the compiler automatically sets the alignment for the declared | |
3113 | variable or field to the largest alignment which is ever used for any data | |
3114 | type on the target machine you are compiling for. Doing this can often make | |
3115 | copy operations more efficient, because the compiler can use whatever | |
3116 | instructions copy the biggest chunks of memory when performing copies to | |
3117 | or from the variables or fields that you have aligned this way. | |
3118 | ||
3119 | The @code{aligned} attribute can only increase the alignment; but you | |
3120 | can decrease it by specifying @code{packed} as well. See below. | |
3121 | ||
3122 | Note that the effectiveness of @code{aligned} attributes may be limited | |
3123 | by inherent limitations in your linker. On many systems, the linker is | |
3124 | only able to arrange for variables to be aligned up to a certain maximum | |
3125 | alignment. (For some linkers, the maximum supported alignment may | |
3126 | be very very small.) If your linker is only able to align variables | |
3127 | up to a maximum of 8 byte alignment, then specifying @code{aligned(16)} | |
3128 | in an @code{__attribute__} will still only provide you with 8 byte | |
3129 | alignment. See your linker documentation for further information. | |
3130 | ||
7acb29a3 | 3131 | @item cleanup (@var{cleanup_function}) |
3132 | @cindex @code{cleanup} attribute | |
3133 | The @code{cleanup} attribute runs a function when the variable goes | |
3134 | out of scope. This attribute can only be applied to auto function | |
3135 | scope variables; it may not be applied to parameters or variables | |
3136 | with static storage duration. The function must take one parameter, | |
3137 | a pointer to a type compatible with the variable. The return value | |
3138 | of the function (if any) is ignored. | |
3139 | ||
3140 | If @option{-fexceptions} is enabled, then @var{cleanup_function} | |
3141 | will be run during the stack unwinding that happens during the | |
3142 | processing of the exception. Note that the @code{cleanup} attribute | |
3143 | does not allow the exception to be caught, only to perform an action. | |
3144 | It is undefined what happens if @var{cleanup_function} does not | |
3145 | return normally. | |
3146 | ||
e7d1f980 | 3147 | @item common |
3148 | @itemx nocommon | |
3149 | @cindex @code{common} attribute | |
3150 | @cindex @code{nocommon} attribute | |
3151 | @opindex fcommon | |
3152 | @opindex fno-common | |
3153 | The @code{common} attribute requests GCC to place a variable in | |
3154 | ``common'' storage. The @code{nocommon} attribute requests the | |
3155 | opposite -- to allocate space for it directly. | |
3156 | ||
3157 | These attributes override the default chosen by the | |
3158 | @option{-fno-common} and @option{-fcommon} flags respectively. | |
3159 | ||
3160 | @item deprecated | |
3161 | @cindex @code{deprecated} attribute | |
3162 | The @code{deprecated} attribute results in a warning if the variable | |
3163 | is used anywhere in the source file. This is useful when identifying | |
3164 | variables that are expected to be removed in a future version of a | |
3165 | program. The warning also includes the location of the declaration | |
3166 | of the deprecated variable, to enable users to easily find further | |
3167 | information about why the variable is deprecated, or what they should | |
ea1c20d0 | 3168 | do instead. Note that the warning only occurs for uses: |
e7d1f980 | 3169 | |
3170 | @smallexample | |
3171 | extern int old_var __attribute__ ((deprecated)); | |
3172 | extern int old_var; | |
3173 | int new_fn () @{ return old_var; @} | |
3174 | @end smallexample | |
3175 | ||
3176 | results in a warning on line 3 but not line 2. | |
3177 | ||
3178 | The @code{deprecated} attribute can also be used for functions and | |
3179 | types (@pxref{Function Attributes}, @pxref{Type Attributes}.) | |
3180 | ||
146ef39f | 3181 | @item mode (@var{mode}) |
3182 | @cindex @code{mode} attribute | |
3183 | This attribute specifies the data type for the declaration---whichever | |
3184 | type corresponds to the mode @var{mode}. This in effect lets you | |
3185 | request an integer or floating point type according to its width. | |
3186 | ||
3187 | You may also specify a mode of @samp{byte} or @samp{__byte__} to | |
3188 | indicate the mode corresponding to a one-byte integer, @samp{word} or | |
3189 | @samp{__word__} for the mode of a one-word integer, and @samp{pointer} | |
3190 | or @samp{__pointer__} for the mode used to represent pointers. | |
3191 | ||
146ef39f | 3192 | @item packed |
3193 | @cindex @code{packed} attribute | |
3194 | The @code{packed} attribute specifies that a variable or structure field | |
3195 | should have the smallest possible alignment---one byte for a variable, | |
3196 | and one bit for a field, unless you specify a larger value with the | |
3197 | @code{aligned} attribute. | |
3198 | ||
3199 | Here is a structure in which the field @code{x} is packed, so that it | |
3200 | immediately follows @code{a}: | |
3201 | ||
3202 | @example | |
3203 | struct foo | |
3204 | @{ | |
3205 | char a; | |
3206 | int x[2] __attribute__ ((packed)); | |
3207 | @}; | |
3208 | @end example | |
3209 | ||
67791935 | 3210 | @item section ("@var{section-name}") |
146ef39f | 3211 | @cindex @code{section} variable attribute |
3212 | Normally, the compiler places the objects it generates in sections like | |
3213 | @code{data} and @code{bss}. Sometimes, however, you need additional sections, | |
3214 | or you need certain particular variables to appear in special sections, | |
3215 | for example to map to special hardware. The @code{section} | |
3216 | attribute specifies that a variable (or function) lives in a particular | |
3217 | section. For example, this small program uses several specific section names: | |
3218 | ||
3219 | @smallexample | |
3220 | struct duart a __attribute__ ((section ("DUART_A"))) = @{ 0 @}; | |
3221 | struct duart b __attribute__ ((section ("DUART_B"))) = @{ 0 @}; | |
3222 | char stack[10000] __attribute__ ((section ("STACK"))) = @{ 0 @}; | |
3223 | int init_data __attribute__ ((section ("INITDATA"))) = 0; | |
3224 | ||
3225 | main() | |
3226 | @{ | |
3227 | /* Initialize stack pointer */ | |
3228 | init_sp (stack + sizeof (stack)); | |
3229 | ||
3230 | /* Initialize initialized data */ | |
3231 | memcpy (&init_data, &data, &edata - &data); | |
3232 | ||
3233 | /* Turn on the serial ports */ | |
3234 | init_duart (&a); | |
3235 | init_duart (&b); | |
3236 | @} | |
3237 | @end smallexample | |
3238 | ||
3239 | @noindent | |
3240 | Use the @code{section} attribute with an @emph{initialized} definition | |
37744367 | 3241 | of a @emph{global} variable, as shown in the example. GCC issues |
146ef39f | 3242 | a warning and otherwise ignores the @code{section} attribute in |
3243 | uninitialized variable declarations. | |
3244 | ||
3245 | You may only use the @code{section} attribute with a fully initialized | |
3246 | global definition because of the way linkers work. The linker requires | |
3247 | each object be defined once, with the exception that uninitialized | |
3248 | variables tentatively go in the @code{common} (or @code{bss}) section | |
67791935 | 3249 | and can be multiply ``defined''. You can force a variable to be |
3250 | initialized with the @option{-fno-common} flag or the @code{nocommon} | |
146ef39f | 3251 | attribute. |
3252 | ||
3253 | Some file formats do not support arbitrary sections so the @code{section} | |
3254 | attribute is not available on all platforms. | |
3255 | If you need to map the entire contents of a module to a particular | |
3256 | section, consider using the facilities of the linker instead. | |
3257 | ||
87135be0 | 3258 | @item shared |
3259 | @cindex @code{shared} variable attribute | |
195d932a | 3260 | On Windows, in addition to putting variable definitions in a named |
3b0848a2 | 3261 | section, the section can also be shared among all running copies of an |
0858e3a2 | 3262 | executable or DLL@. For example, this small program defines shared data |
67791935 | 3263 | by putting it in a named section @code{shared} and marking the section |
87135be0 | 3264 | shareable: |
3265 | ||
3266 | @smallexample | |
3267 | int foo __attribute__((section ("shared"), shared)) = 0; | |
3268 | ||
3269 | int | |
3270 | main() | |
3271 | @{ | |
d90db7dc | 3272 | /* Read and write foo. All running |
3273 | copies see the same value. */ | |
87135be0 | 3274 | return 0; |
3275 | @} | |
3276 | @end smallexample | |
3277 | ||
3278 | @noindent | |
3279 | You may only use the @code{shared} attribute along with @code{section} | |
3b0848a2 | 3280 | attribute with a fully initialized global definition because of the way |
87135be0 | 3281 | linkers work. See @code{section} attribute for more information. |
3282 | ||
195d932a | 3283 | The @code{shared} attribute is only available on Windows@. |
87135be0 | 3284 | |
e7d1f980 | 3285 | @item tls_model ("@var{tls_model}") |
3286 | @cindex @code{tls_model} attribute | |
3287 | The @code{tls_model} attribute sets thread-local storage model | |
3288 | (@pxref{Thread-Local}) of a particular @code{__thread} variable, | |
3289 | overriding @code{-ftls-model=} command line switch on a per-variable | |
3290 | basis. | |
3291 | The @var{tls_model} argument should be one of @code{global-dynamic}, | |
3292 | @code{local-dynamic}, @code{initial-exec} or @code{local-exec}. | |
3293 | ||
3294 | Not all targets support this attribute. | |
3295 | ||
146ef39f | 3296 | @item transparent_union |
3297 | This attribute, attached to a function parameter which is a union, means | |
3298 | that the corresponding argument may have the type of any union member, | |
3299 | but the argument is passed as if its type were that of the first union | |
3300 | member. For more details see @xref{Type Attributes}. You can also use | |
3301 | this attribute on a @code{typedef} for a union data type; then it | |
3302 | applies to all function parameters with that type. | |
3303 | ||
3304 | @item unused | |
3305 | This attribute, attached to a variable, means that the variable is meant | |
37744367 | 3306 | to be possibly unused. GCC will not produce a warning for this |
146ef39f | 3307 | variable. |
3308 | ||
ae4718db | 3309 | @item vector_size (@var{bytes}) |
3310 | This attribute specifies the vector size for the variable, measured in | |
3311 | bytes. For example, the declaration: | |
3312 | ||
3313 | @smallexample | |
3314 | int foo __attribute__ ((vector_size (16))); | |
3315 | @end smallexample | |
3316 | ||
3317 | @noindent | |
3318 | causes the compiler to set the mode for @code{foo}, to be 16 bytes, | |
3319 | divided into @code{int} sized units. Assuming a 32-bit int (a vector of | |
3320 | 4 units of 4 bytes), the corresponding mode of @code{foo} will be V4SI@. | |
3321 | ||
3322 | This attribute is only applicable to integral and float scalars, | |
3323 | although arrays, pointers, and function return values are allowed in | |
3324 | conjunction with this construct. | |
3325 | ||
3326 | Aggregates with this attribute are invalid, even if they are of the same | |
3327 | size as a corresponding scalar. For example, the declaration: | |
3328 | ||
3329 | @smallexample | |
6bdacb9b | 3330 | struct S @{ int a; @}; |
ae4718db | 3331 | struct S __attribute__ ((vector_size (16))) foo; |
3332 | @end smallexample | |
3333 | ||
3334 | @noindent | |
3335 | is invalid even if the size of the structure is the same as the size of | |
3336 | the @code{int}. | |
3337 | ||
146ef39f | 3338 | @item weak |
3339 | The @code{weak} attribute is described in @xref{Function Attributes}. | |
195d932a | 3340 | |
3341 | @item dllimport | |
3342 | The @code{dllimport} attribute is described in @xref{Function Attributes}. | |
3343 | ||
3344 | @item dlexport | |
3345 | The @code{dllexport} attribute is described in @xref{Function Attributes}. | |
3346 | ||
e7d1f980 | 3347 | @end table |
3348 | ||
3349 | @subsection M32R/D Variable Attributes | |
097cea9f | 3350 | |
e7d1f980 | 3351 | One attribute is currently defined for the M32R/D. |
3352 | ||
3353 | @table @code | |
097cea9f | 3354 | @item model (@var{model-name}) |
3355 | @cindex variable addressability on the M32R/D | |
3356 | Use this attribute on the M32R/D to set the addressability of an object. | |
3357 | The identifier @var{model-name} is one of @code{small}, @code{medium}, | |
3358 | or @code{large}, representing each of the code models. | |
3359 | ||
3360 | Small model objects live in the lower 16MB of memory (so that their | |
3361 | addresses can be loaded with the @code{ld24} instruction). | |
3362 | ||
3b0848a2 | 3363 | Medium and large model objects may live anywhere in the 32-bit address space |
097cea9f | 3364 | (the compiler will generate @code{seth/add3} instructions to load their |
3365 | addresses). | |
e7d1f980 | 3366 | @end table |
097cea9f | 3367 | |
b09c5db2 | 3368 | @subsection i386 Variable Attributes |
3369 | ||
3370 | Two attributes are currently defined for i386 configurations: | |
3371 | @code{ms_struct} and @code{gcc_struct} | |
3372 | ||
e7d1f980 | 3373 | @table @code |
b09c5db2 | 3374 | @item ms_struct |
3375 | @itemx gcc_struct | |
e7d1f980 | 3376 | @cindex @code{ms_struct} attribute |
3377 | @cindex @code{gcc_struct} attribute | |
b09c5db2 | 3378 | |
3379 | If @code{packed} is used on a structure, or if bit-fields are used | |
3380 | it may be that the Microsoft ABI packs them differently | |
3381 | than GCC would normally pack them. Particularly when moving packed | |
3382 | data between functions compiled with GCC and the native Microsoft compiler | |
3383 | (either via function call or as data in a file), it may be necessary to access | |
3384 | either format. | |
3385 | ||
3386 | Currently @option{-m[no-]ms-bitfields} is provided for the Windows X86 | |
3387 | compilers to match the native Microsoft compiler. | |
146ef39f | 3388 | @end table |
3389 | ||
146ef39f | 3390 | @node Type Attributes |
3391 | @section Specifying Attributes of Types | |
3392 | @cindex attribute of types | |
3393 | @cindex type attributes | |
3394 | ||
3395 | The keyword @code{__attribute__} allows you to specify special | |
3396 | attributes of @code{struct} and @code{union} types when you define such | |
3397 | types. This keyword is followed by an attribute specification inside | |
cb59f969 | 3398 | double parentheses. Six attributes are currently defined for types: |
88da234d | 3399 | @code{aligned}, @code{packed}, @code{transparent_union}, @code{unused}, |
cb59f969 | 3400 | @code{deprecated} and @code{may_alias}. Other attributes are defined for |
3401 | functions (@pxref{Function Attributes}) and for variables | |
3402 | (@pxref{Variable Attributes}). | |
146ef39f | 3403 | |
3404 | You may also specify any one of these attributes with @samp{__} | |
3405 | preceding and following its keyword. This allows you to use these | |
3406 | attributes in header files without being concerned about a possible | |
3407 | macro of the same name. For example, you may use @code{__aligned__} | |
3408 | instead of @code{aligned}. | |
3409 | ||
3410 | You may specify the @code{aligned} and @code{transparent_union} | |
3411 | attributes either in a @code{typedef} declaration or just past the | |
3412 | closing curly brace of a complete enum, struct or union type | |
3413 | @emph{definition} and the @code{packed} attribute only past the closing | |
3414 | brace of a definition. | |
3415 | ||
257b057a | 3416 | You may also specify attributes between the enum, struct or union |
3417 | tag and the name of the type rather than after the closing brace. | |
3418 | ||
b31bfb3f | 3419 | @xref{Attribute Syntax}, for details of the exact syntax for using |
3420 | attributes. | |
3421 | ||
146ef39f | 3422 | @table @code |
3423 | @cindex @code{aligned} attribute | |
3424 | @item aligned (@var{alignment}) | |
3425 | This attribute specifies a minimum alignment (in bytes) for variables | |
3426 | of the specified type. For example, the declarations: | |
3427 | ||
3428 | @smallexample | |
c8b8ebd3 | 3429 | struct S @{ short f[3]; @} __attribute__ ((aligned (8))); |
3430 | typedef int more_aligned_int __attribute__ ((aligned (8))); | |
146ef39f | 3431 | @end smallexample |
3432 | ||
3433 | @noindent | |
7223a120 | 3434 | force the compiler to insure (as far as it can) that each variable whose |
146ef39f | 3435 | type is @code{struct S} or @code{more_aligned_int} will be allocated and |
7800959d | 3436 | aligned @emph{at least} on a 8-byte boundary. On a SPARC, having all |
146ef39f | 3437 | variables of type @code{struct S} aligned to 8-byte boundaries allows |
3438 | the compiler to use the @code{ldd} and @code{std} (doubleword load and | |
3439 | store) instructions when copying one variable of type @code{struct S} to | |
3440 | another, thus improving run-time efficiency. | |
3441 | ||
3442 | Note that the alignment of any given @code{struct} or @code{union} type | |
78b1f616 | 3443 | is required by the ISO C standard to be at least a perfect multiple of |
146ef39f | 3444 | the lowest common multiple of the alignments of all of the members of |
3445 | the @code{struct} or @code{union} in question. This means that you @emph{can} | |
3446 | effectively adjust the alignment of a @code{struct} or @code{union} | |
3447 | type by attaching an @code{aligned} attribute to any one of the members | |
3448 | of such a type, but the notation illustrated in the example above is a | |
3449 | more obvious, intuitive, and readable way to request the compiler to | |
3450 | adjust the alignment of an entire @code{struct} or @code{union} type. | |
3451 | ||
3452 | As in the preceding example, you can explicitly specify the alignment | |
3453 | (in bytes) that you wish the compiler to use for a given @code{struct} | |
3454 | or @code{union} type. Alternatively, you can leave out the alignment factor | |
3455 | and just ask the compiler to align a type to the maximum | |
3456 | useful alignment for the target machine you are compiling for. For | |
3457 | example, you could write: | |
3458 | ||
3459 | @smallexample | |
3460 | struct S @{ short f[3]; @} __attribute__ ((aligned)); | |
3461 | @end smallexample | |
3462 | ||
3463 | Whenever you leave out the alignment factor in an @code{aligned} | |
3464 | attribute specification, the compiler automatically sets the alignment | |
3465 | for the type to the largest alignment which is ever used for any data | |
3466 | type on the target machine you are compiling for. Doing this can often | |
3467 | make copy operations more efficient, because the compiler can use | |
3468 | whatever instructions copy the biggest chunks of memory when performing | |
3469 | copies to or from the variables which have types that you have aligned | |
3470 | this way. | |
3471 | ||
3472 | In the example above, if the size of each @code{short} is 2 bytes, then | |
3473 | the size of the entire @code{struct S} type is 6 bytes. The smallest | |
3474 | power of two which is greater than or equal to that is 8, so the | |
3475 | compiler sets the alignment for the entire @code{struct S} type to 8 | |
3476 | bytes. | |
3477 | ||
3478 | Note that although you can ask the compiler to select a time-efficient | |
3479 | alignment for a given type and then declare only individual stand-alone | |
3480 | objects of that type, the compiler's ability to select a time-efficient | |
3481 | alignment is primarily useful only when you plan to create arrays of | |
3482 | variables having the relevant (efficiently aligned) type. If you | |
3483 | declare or use arrays of variables of an efficiently-aligned type, then | |
3484 | it is likely that your program will also be doing pointer arithmetic (or | |
3485 | subscripting, which amounts to the same thing) on pointers to the | |
3486 | relevant type, and the code that the compiler generates for these | |
3487 | pointer arithmetic operations will often be more efficient for | |
3488 | efficiently-aligned types than for other types. | |
3489 | ||
3490 | The @code{aligned} attribute can only increase the alignment; but you | |
3491 | can decrease it by specifying @code{packed} as well. See below. | |
3492 | ||
3493 | Note that the effectiveness of @code{aligned} attributes may be limited | |
3494 | by inherent limitations in your linker. On many systems, the linker is | |
3495 | only able to arrange for variables to be aligned up to a certain maximum | |
3496 | alignment. (For some linkers, the maximum supported alignment may | |
3497 | be very very small.) If your linker is only able to align variables | |
3498 | up to a maximum of 8 byte alignment, then specifying @code{aligned(16)} | |
3499 | in an @code{__attribute__} will still only provide you with 8 byte | |
3500 | alignment. See your linker documentation for further information. | |
3501 | ||
3502 | @item packed | |
942ab15b | 3503 | This attribute, attached to @code{struct} or @code{union} type |
3504 | definition, specifies that each member of the structure or union is | |
3505 | placed to minimize the memory required. When attached to an @code{enum} | |
3506 | definition, it indicates that the smallest integral type should be used. | |
146ef39f | 3507 | |
67791935 | 3508 | @opindex fshort-enums |
146ef39f | 3509 | Specifying this attribute for @code{struct} and @code{union} types is |
3510 | equivalent to specifying the @code{packed} attribute on each of the | |
67791935 | 3511 | structure or union members. Specifying the @option{-fshort-enums} |
146ef39f | 3512 | flag on the line is equivalent to specifying the @code{packed} |
3513 | attribute on all @code{enum} definitions. | |
3514 | ||
942ab15b | 3515 | In the following example @code{struct my_packed_struct}'s members are |
3516 | packed closely together, but the internal layout of its @code{s} member | |
3517 | is not packed -- to do that, @code{struct my_unpacked_struct} would need to | |
3518 | be packed too. | |
3519 | ||
3520 | @smallexample | |
3521 | struct my_unpacked_struct | |
3522 | @{ | |
3523 | char c; | |
3524 | int i; | |
3525 | @}; | |
3526 | ||
3527 | struct my_packed_struct __attribute__ ((__packed__)) | |
3528 | @{ | |
3529 | char c; | |
3530 | int i; | |
3531 | struct my_unpacked_struct s; | |
3532 | @}; | |
3533 | @end smallexample | |
3534 | ||
3535 | You may only specify this attribute on the definition of a @code{enum}, | |
3536 | @code{struct} or @code{union}, not on a @code{typedef} which does not | |
3537 | also define the enumerated type, structure or union. | |
146ef39f | 3538 | |
3539 | @item transparent_union | |
3540 | This attribute, attached to a @code{union} type definition, indicates | |
3541 | that any function parameter having that union type causes calls to that | |
3542 | function to be treated in a special way. | |
3543 | ||
3544 | First, the argument corresponding to a transparent union type can be of | |
3545 | any type in the union; no cast is required. Also, if the union contains | |
3546 | a pointer type, the corresponding argument can be a null pointer | |
3547 | constant or a void pointer expression; and if the union contains a void | |
3548 | pointer type, the corresponding argument can be any pointer expression. | |
3549 | If the union member type is a pointer, qualifiers like @code{const} on | |
3550 | the referenced type must be respected, just as with normal pointer | |
3551 | conversions. | |
3552 | ||
3553 | Second, the argument is passed to the function using the calling | |
ea1c20d0 | 3554 | conventions of the first member of the transparent union, not the calling |
146ef39f | 3555 | conventions of the union itself. All members of the union must have the |
3556 | same machine representation; this is necessary for this argument passing | |
3557 | to work properly. | |
3558 | ||
3559 | Transparent unions are designed for library functions that have multiple | |
3560 | interfaces for compatibility reasons. For example, suppose the | |
3561 | @code{wait} function must accept either a value of type @code{int *} to | |
3562 | comply with Posix, or a value of type @code{union wait *} to comply with | |
3563 | the 4.1BSD interface. If @code{wait}'s parameter were @code{void *}, | |
3564 | @code{wait} would accept both kinds of arguments, but it would also | |
3565 | accept any other pointer type and this would make argument type checking | |
3566 | less useful. Instead, @code{<sys/wait.h>} might define the interface | |
3567 | as follows: | |
3568 | ||
3569 | @smallexample | |
3570 | typedef union | |
3571 | @{ | |
3572 | int *__ip; | |
3573 | union wait *__up; | |
3574 | @} wait_status_ptr_t __attribute__ ((__transparent_union__)); | |
3575 | ||
3576 | pid_t wait (wait_status_ptr_t); | |
3577 | @end smallexample | |
3578 | ||
3579 | This interface allows either @code{int *} or @code{union wait *} | |
3580 | arguments to be passed, using the @code{int *} calling convention. | |
3581 | The program can call @code{wait} with arguments of either type: | |
3582 | ||
3583 | @example | |
3584 | int w1 () @{ int w; return wait (&w); @} | |
3585 | int w2 () @{ union wait w; return wait (&w); @} | |
3586 | @end example | |
3587 | ||
3588 | With this interface, @code{wait}'s implementation might look like this: | |
3589 | ||
3590 | @example | |
3591 | pid_t wait (wait_status_ptr_t p) | |
3592 | @{ | |
3593 | return waitpid (-1, p.__ip, 0); | |
3594 | @} | |
3595 | @end example | |
7223a120 | 3596 | |
3597 | @item unused | |
3598 | When attached to a type (including a @code{union} or a @code{struct}), | |
3599 | this attribute means that variables of that type are meant to appear | |
37744367 | 3600 | possibly unused. GCC will not produce a warning for any variables of |
7223a120 | 3601 | that type, even if the variable appears to do nothing. This is often |
3602 | the case with lock or thread classes, which are usually defined and then | |
3603 | not referenced, but contain constructors and destructors that have | |
ad87de1e | 3604 | nontrivial bookkeeping functions. |
7223a120 | 3605 | |
88da234d | 3606 | @item deprecated |
3607 | The @code{deprecated} attribute results in a warning if the type | |
3608 | is used anywhere in the source file. This is useful when identifying | |
3609 | types that are expected to be removed in a future version of a program. | |
3610 | If possible, the warning also includes the location of the declaration | |
3611 | of the deprecated type, to enable users to easily find further | |
3612 | information about why the type is deprecated, or what they should do | |
3613 | instead. Note that the warnings only occur for uses and then only | |
6831447b | 3614 | if the type is being applied to an identifier that itself is not being |
88da234d | 3615 | declared as deprecated. |
3616 | ||
3617 | @smallexample | |
3618 | typedef int T1 __attribute__ ((deprecated)); | |
3619 | T1 x; | |
3620 | typedef T1 T2; | |
3621 | T2 y; | |
3622 | typedef T1 T3 __attribute__ ((deprecated)); | |
3623 | T3 z __attribute__ ((deprecated)); | |
3624 | @end smallexample | |
3625 | ||
3626 | results in a warning on line 2 and 3 but not lines 4, 5, or 6. No | |
3627 | warning is issued for line 4 because T2 is not explicitly | |
3628 | deprecated. Line 5 has no warning because T3 is explicitly | |
3629 | deprecated. Similarly for line 6. | |
3630 | ||
3631 | The @code{deprecated} attribute can also be used for functions and | |
3632 | variables (@pxref{Function Attributes}, @pxref{Variable Attributes}.) | |
3633 | ||
cb59f969 | 3634 | @item may_alias |
3635 | Accesses to objects with types with this attribute are not subjected to | |
3636 | type-based alias analysis, but are instead assumed to be able to alias | |
3637 | any other type of objects, just like the @code{char} type. See | |
3638 | @option{-fstrict-aliasing} for more information on aliasing issues. | |
3639 | ||
3640 | Example of use: | |
3641 | ||
b724fad7 | 3642 | @smallexample |
cb59f969 | 3643 | typedef short __attribute__((__may_alias__)) short_a; |
3644 | ||
3645 | int | |
3646 | main (void) | |
3647 | @{ | |
3648 | int a = 0x12345678; | |
3649 | short_a *b = (short_a *) &a; | |
3650 | ||
3651 | b[1] = 0; | |
3652 | ||
3653 | if (a == 0x12345678) | |
3654 | abort(); | |
3655 | ||
3656 | exit(0); | |
3657 | @} | |
b724fad7 | 3658 | @end smallexample |
cb59f969 | 3659 | |
3660 | If you replaced @code{short_a} with @code{short} in the variable | |
3661 | declaration, the above program would abort when compiled with | |
3662 | @option{-fstrict-aliasing}, which is on by default at @option{-O2} or | |
3663 | above in recent GCC versions. | |
b09c5db2 | 3664 | |
3665 | @subsection i386 Type Attributes | |
3666 | ||
3667 | Two attributes are currently defined for i386 configurations: | |
3668 | @code{ms_struct} and @code{gcc_struct} | |
3669 | ||
3670 | @item ms_struct | |
3671 | @itemx gcc_struct | |
3672 | @cindex @code{ms_struct} | |
3673 | @cindex @code{gcc_struct} | |
3674 | ||
3675 | If @code{packed} is used on a structure, or if bit-fields are used | |
3676 | it may be that the Microsoft ABI packs them differently | |
3677 | than GCC would normally pack them. Particularly when moving packed | |
3678 | data between functions compiled with GCC and the native Microsoft compiler | |
3679 | (either via function call or as data in a file), it may be necessary to access | |
3680 | either format. | |
3681 | ||
3682 | Currently @option{-m[no-]ms-bitfields} is provided for the Windows X86 | |
3683 | compilers to match the native Microsoft compiler. | |
146ef39f | 3684 | @end table |
3685 | ||
3686 | To specify multiple attributes, separate them by commas within the | |
3687 | double parentheses: for example, @samp{__attribute__ ((aligned (16), | |
3688 | packed))}. | |
3689 | ||
3690 | @node Inline | |
3691 | @section An Inline Function is As Fast As a Macro | |
3692 | @cindex inline functions | |
3693 | @cindex integrating function code | |
3694 | @cindex open coding | |
3695 | @cindex macros, inline alternative | |
3696 | ||
37744367 | 3697 | By declaring a function @code{inline}, you can direct GCC to |
146ef39f | 3698 | integrate that function's code into the code for its callers. This |
3699 | makes execution faster by eliminating the function-call overhead; in | |
3700 | addition, if any of the actual argument values are constant, their known | |
3701 | values may permit simplifications at compile time so that not all of the | |
3702 | inline function's code needs to be included. The effect on code size is | |
3703 | less predictable; object code may be larger or smaller with function | |
3704 | inlining, depending on the particular case. Inlining of functions is an | |
3705 | optimization and it really ``works'' only in optimizing compilation. If | |
67791935 | 3706 | you don't use @option{-O}, no function is really inline. |
146ef39f | 3707 | |
3cfa0cc4 | 3708 | Inline functions are included in the ISO C99 standard, but there are |
3709 | currently substantial differences between what GCC implements and what | |
3710 | the ISO C99 standard requires. | |
3711 | ||
146ef39f | 3712 | To declare a function inline, use the @code{inline} keyword in its |
3713 | declaration, like this: | |
3714 | ||
3715 | @example | |
3716 | inline int | |
3717 | inc (int *a) | |
3718 | @{ | |
3719 | (*a)++; | |
3720 | @} | |
3721 | @end example | |
3722 | ||
78b1f616 | 3723 | (If you are writing a header file to be included in ISO C programs, write |
146ef39f | 3724 | @code{__inline__} instead of @code{inline}. @xref{Alternate Keywords}.) |
146ef39f | 3725 | You can also make all ``simple enough'' functions inline with the option |
67791935 | 3726 | @option{-finline-functions}. |
5a967f61 | 3727 | |
67791935 | 3728 | @opindex Winline |
5a967f61 | 3729 | Note that certain usages in a function definition can make it unsuitable |
3730 | for inline substitution. Among these usages are: use of varargs, use of | |
3731 | alloca, use of variable sized data types (@pxref{Variable Length}), | |
3732 | use of computed goto (@pxref{Labels as Values}), use of nonlocal goto, | |
67791935 | 3733 | and nested functions (@pxref{Nested Functions}). Using @option{-Winline} |
5a967f61 | 3734 | will warn when a function marked @code{inline} could not be substituted, |
3735 | and will give the reason for the failure. | |
146ef39f | 3736 | |
3db5236b | 3737 | Note that in C and Objective-C, unlike C++, the @code{inline} keyword |
146ef39f | 3738 | does not affect the linkage of the function. |
3739 | ||
3740 | @cindex automatic @code{inline} for C++ member fns | |
3741 | @cindex @code{inline} automatic for C++ member fns | |
3742 | @cindex member fns, automatically @code{inline} | |
3743 | @cindex C++ member fns, automatically @code{inline} | |
67791935 | 3744 | @opindex fno-default-inline |
37744367 | 3745 | GCC automatically inlines member functions defined within the class |
146ef39f | 3746 | body of C++ programs even if they are not explicitly declared |
67791935 | 3747 | @code{inline}. (You can override this with @option{-fno-default-inline}; |
146ef39f | 3748 | @pxref{C++ Dialect Options,,Options Controlling C++ Dialect}.) |
3749 | ||
3750 | @cindex inline functions, omission of | |
67791935 | 3751 | @opindex fkeep-inline-functions |
146ef39f | 3752 | When a function is both inline and @code{static}, if all calls to the |
3753 | function are integrated into the caller, and the function's address is | |
3754 | never used, then the function's own assembler code is never referenced. | |
37744367 | 3755 | In this case, GCC does not actually output assembler code for the |
67791935 | 3756 | function, unless you specify the option @option{-fkeep-inline-functions}. |
146ef39f | 3757 | Some calls cannot be integrated for various reasons (in particular, |
3758 | calls that precede the function's definition cannot be integrated, and | |
3759 | neither can recursive calls within the definition). If there is a | |
3760 | nonintegrated call, then the function is compiled to assembler code as | |
3761 | usual. The function must also be compiled as usual if the program | |
3762 | refers to its address, because that can't be inlined. | |
3763 | ||
3764 | @cindex non-static inline function | |
3765 | When an inline function is not @code{static}, then the compiler must assume | |
3766 | that there may be calls from other source files; since a global symbol can | |
3767 | be defined only once in any program, the function must not be defined in | |
3768 | the other source files, so the calls therein cannot be integrated. | |
3769 | Therefore, a non-@code{static} inline function is always compiled on its | |
3770 | own in the usual fashion. | |
3771 | ||
3772 | If you specify both @code{inline} and @code{extern} in the function | |
3773 | definition, then the definition is used only for inlining. In no case | |
3774 | is the function compiled on its own, not even if you refer to its | |
3775 | address explicitly. Such an address becomes an external reference, as | |
3776 | if you had only declared the function, and had not defined it. | |
3777 | ||
3778 | This combination of @code{inline} and @code{extern} has almost the | |
3779 | effect of a macro. The way to use it is to put a function definition in | |
3780 | a header file with these keywords, and put another copy of the | |
3781 | definition (lacking @code{inline} and @code{extern}) in a library file. | |
3782 | The definition in the header file will cause most calls to the function | |
3783 | to be inlined. If any uses of the function remain, they will refer to | |
3784 | the single copy in the library. | |
3785 | ||
ea1c20d0 | 3786 | Since GCC eventually will implement ISO C99 semantics for |
3787 | inline functions, it is best to use @code{static inline} only | |
3788 | to guarentee compatibility. (The | |
3cfa0cc4 | 3789 | existing semantics will remain available when @option{-std=gnu89} is |
3790 | specified, but eventually the default will be @option{-std=gnu99} and | |
3791 | that will implement the C99 semantics, though it does not do so yet.) | |
3792 | ||
af87ad83 | 3793 | GCC does not inline any functions when not optimizing unless you specify |
3794 | the @samp{always_inline} attribute for the function, like this: | |
3795 | ||
3796 | @example | |
3797 | /* Prototype. */ | |
3798 | inline void foo (const char) __attribute__((always_inline)); | |
3799 | @end example | |
146ef39f | 3800 | |
3801 | @node Extended Asm | |
3802 | @section Assembler Instructions with C Expression Operands | |
3803 | @cindex extended @code{asm} | |
3804 | @cindex @code{asm} expressions | |
3805 | @cindex assembler instructions | |
3806 | @cindex registers | |
3807 | ||
220345e0 | 3808 | In an assembler instruction using @code{asm}, you can specify the |
3809 | operands of the instruction using C expressions. This means you need not | |
3810 | guess which registers or memory locations will contain the data you want | |
146ef39f | 3811 | to use. |
3812 | ||
220345e0 | 3813 | You must specify an assembler instruction template much like what |
3814 | appears in a machine description, plus an operand constraint string for | |
3815 | each operand. | |
146ef39f | 3816 | |
3817 | For example, here is how to use the 68881's @code{fsinx} instruction: | |
3818 | ||
3819 | @example | |
3820 | asm ("fsinx %1,%0" : "=f" (result) : "f" (angle)); | |
3821 | @end example | |
3822 | ||
3823 | @noindent | |
3824 | Here @code{angle} is the C expression for the input operand while | |
3825 | @code{result} is that of the output operand. Each has @samp{"f"} as its | |
220345e0 | 3826 | operand constraint, saying that a floating point register is required. |
3827 | The @samp{=} in @samp{=f} indicates that the operand is an output; all | |
3828 | output operands' constraints must use @samp{=}. The constraints use the | |
3829 | same language used in the machine description (@pxref{Constraints}). | |
3830 | ||
3831 | Each operand is described by an operand-constraint string followed by | |
3832 | the C expression in parentheses. A colon separates the assembler | |
3833 | template from the first output operand and another separates the last | |
3834 | output operand from the first input, if any. Commas separate the | |
2c7f203c | 3835 | operands within each group. The total number of operands is currently |
3836 | limited to 30; this limitation may be lifted in some future version of | |
3837 | GCC. | |
220345e0 | 3838 | |
3839 | If there are no output operands but there are input operands, you must | |
3840 | place two consecutive colons surrounding the place where the output | |
146ef39f | 3841 | operands would go. |
3842 | ||
2c7f203c | 3843 | As of GCC version 3.1, it is also possible to specify input and output |
3844 | operands using symbolic names which can be referenced within the | |
3845 | assembler code. These names are specified inside square brackets | |
3846 | preceding the constraint string, and can be referenced inside the | |
3847 | assembler code using @code{%[@var{name}]} instead of a percentage sign | |
3848 | followed by the operand number. Using named operands the above example | |
3849 | could look like: | |
3850 | ||
3851 | @example | |
3852 | asm ("fsinx %[angle],%[output]" | |
3853 | : [output] "=f" (result) | |
3854 | : [angle] "f" (angle)); | |
3855 | @end example | |
3856 | ||
3857 | @noindent | |
3858 | Note that the symbolic operand names have no relation whatsoever to | |
3859 | other C identifiers. You may use any name you like, even those of | |
ea1c20d0 | 3860 | existing C symbols, but you must ensure that no two operands within the same |
2c7f203c | 3861 | assembler construct use the same symbolic name. |
3862 | ||
146ef39f | 3863 | Output operand expressions must be lvalues; the compiler can check this. |
220345e0 | 3864 | The input operands need not be lvalues. The compiler cannot check |
3865 | whether the operands have data types that are reasonable for the | |
3866 | instruction being executed. It does not parse the assembler instruction | |
3867 | template and does not know what it means or even whether it is valid | |
3868 | assembler input. The extended @code{asm} feature is most often used for | |
3869 | machine instructions the compiler itself does not know exist. If | |
3870 | the output expression cannot be directly addressed (for example, it is a | |
37744367 | 3871 | bit-field), your constraint must allow a register. In that case, GCC |
220345e0 | 3872 | will use the register as the output of the @code{asm}, and then store |
3873 | that register into the output. | |
3874 | ||
37744367 | 3875 | The ordinary output operands must be write-only; GCC will assume that |
220345e0 | 3876 | the values in these operands before the instruction are dead and need |
3877 | not be generated. Extended asm supports input-output or read-write | |
3878 | operands. Use the constraint character @samp{+} to indicate such an | |
3879 | operand and list it with the output operands. | |
3880 | ||
3881 | When the constraints for the read-write operand (or the operand in which | |
3882 | only some of the bits are to be changed) allows a register, you may, as | |
3883 | an alternative, logically split its function into two separate operands, | |
3884 | one input operand and one write-only output operand. The connection | |
3885 | between them is expressed by constraints which say they need to be in | |
3886 | the same location when the instruction executes. You can use the same C | |
3887 | expression for both operands, or different expressions. For example, | |
3888 | here we write the (fictitious) @samp{combine} instruction with | |
3889 | @code{bar} as its read-only source operand and @code{foo} as its | |
3890 | read-write destination: | |
146ef39f | 3891 | |
3892 | @example | |
3893 | asm ("combine %2,%0" : "=r" (foo) : "0" (foo), "g" (bar)); | |
3894 | @end example | |
3895 | ||
3896 | @noindent | |
220345e0 | 3897 | The constraint @samp{"0"} for operand 1 says that it must occupy the |
2c7f203c | 3898 | same location as operand 0. A number in constraint is allowed only in |
3899 | an input operand and it must refer to an output operand. | |
146ef39f | 3900 | |
2c7f203c | 3901 | Only a number in the constraint can guarantee that one operand will be in |
220345e0 | 3902 | the same place as another. The mere fact that @code{foo} is the value |
3903 | of both operands is not enough to guarantee that they will be in the | |
3904 | same place in the generated assembler code. The following would not | |
3905 | work reliably: | |
146ef39f | 3906 | |
3907 | @example | |
3908 | asm ("combine %2,%0" : "=r" (foo) : "r" (foo), "g" (bar)); | |
3909 | @end example | |
3910 | ||
3911 | Various optimizations or reloading could cause operands 0 and 1 to be in | |
37744367 | 3912 | different registers; GCC knows no reason not to do so. For example, the |
146ef39f | 3913 | compiler might find a copy of the value of @code{foo} in one register and |
3914 | use it for operand 1, but generate the output operand 0 in a different | |
3915 | register (copying it afterward to @code{foo}'s own address). Of course, | |
3916 | since the register for operand 1 is not even mentioned in the assembler | |
37744367 | 3917 | code, the result will not work, but GCC can't tell that. |
146ef39f | 3918 | |
2c7f203c | 3919 | As of GCC version 3.1, one may write @code{[@var{name}]} instead of |
3920 | the operand number for a matching constraint. For example: | |
3921 | ||
3922 | @example | |
3923 | asm ("cmoveq %1,%2,%[result]" | |
3924 | : [result] "=r"(result) | |
3925 | : "r" (test), "r"(new), "[result]"(old)); | |
3926 | @end example | |
3927 | ||
220345e0 | 3928 | Some instructions clobber specific hard registers. To describe this, |
3929 | write a third colon after the input operands, followed by the names of | |
3930 | the clobbered hard registers (given as strings). Here is a realistic | |
3931 | example for the VAX: | |
146ef39f | 3932 | |
3933 | @example | |
3934 | asm volatile ("movc3 %0,%1,%2" | |
3935 | : /* no outputs */ | |
3936 | : "g" (from), "g" (to), "g" (count) | |
3937 | : "r0", "r1", "r2", "r3", "r4", "r5"); | |
3938 | @end example | |
3939 | ||
7014838c | 3940 | You may not write a clobber description in a way that overlaps with an |
3941 | input or output operand. For example, you may not have an operand | |
3942 | describing a register class with one member if you mention that register | |
3d52d305 | 3943 | in the clobber list. Variables declared to live in specific registers |
3944 | (@pxref{Explicit Reg Vars}), and used as asm input or output operands must | |
3945 | have no part mentioned in the clobber description. | |
3946 | There is no way for you to specify that an input | |
7014838c | 3947 | operand is modified without also specifying it as an output |
3948 | operand. Note that if all the output operands you specify are for this | |
3949 | purpose (and hence unused), you will then also need to specify | |
3950 | @code{volatile} for the @code{asm} construct, as described below, to | |
37744367 | 3951 | prevent GCC from deleting the @code{asm} statement as unused. |
abd6a9dd | 3952 | |
146ef39f | 3953 | If you refer to a particular hardware register from the assembler code, |
220345e0 | 3954 | you will probably have to list the register after the third colon to |
3955 | tell the compiler the register's value is modified. In some assemblers, | |
3956 | the register names begin with @samp{%}; to produce one @samp{%} in the | |
3957 | assembler code, you must write @samp{%%} in the input. | |
3958 | ||
3959 | If your assembler instruction can alter the condition code register, add | |
37744367 | 3960 | @samp{cc} to the list of clobbered registers. GCC on some machines |
220345e0 | 3961 | represents the condition codes as a specific hardware register; |
3962 | @samp{cc} serves to name this register. On other machines, the | |
3963 | condition code is handled differently, and specifying @samp{cc} has no | |
3964 | effect. But it is valid no matter what the machine. | |
146ef39f | 3965 | |
3966 | If your assembler instruction modifies memory in an unpredictable | |
220345e0 | 3967 | fashion, add @samp{memory} to the list of clobbered registers. This |
37744367 | 3968 | will cause GCC to not keep memory values cached in registers across |
61bcb403 | 3969 | the assembler instruction. You will also want to add the |
3970 | @code{volatile} keyword if the memory affected is not listed in the | |
3971 | inputs or outputs of the @code{asm}, as the @samp{memory} clobber does | |
3972 | not count as a side-effect of the @code{asm}. | |
146ef39f | 3973 | |
220345e0 | 3974 | You can put multiple assembler instructions together in a single |
4cd470f2 | 3975 | @code{asm} template, separated by the characters normally used in assembly |
3976 | code for the system. A combination that works in most places is a newline | |
3977 | to break the line, plus a tab character to move to the instruction field | |
3978 | (written as @samp{\n\t}). Sometimes semicolons can be used, if the | |
3979 | assembler allows semicolons as a line-breaking character. Note that some | |
3980 | assembler dialects use semicolons to start a comment. | |
3981 | The input operands are guaranteed not to use any of the clobbered | |
220345e0 | 3982 | registers, and neither will the output operands' addresses, so you can |
3983 | read and write the clobbered registers as many times as you like. Here | |
3984 | is an example of multiple instructions in a template; it assumes the | |
3985 | subroutine @code{_foo} accepts arguments in registers 9 and 10: | |
146ef39f | 3986 | |
3987 | @example | |
4cd470f2 | 3988 | asm ("movl %0,r9\n\tmovl %1,r10\n\tcall _foo" |
146ef39f | 3989 | : /* no outputs */ |
3990 | : "g" (from), "g" (to) | |
3991 | : "r9", "r10"); | |
3992 | @end example | |
3993 | ||
37744367 | 3994 | Unless an output operand has the @samp{&} constraint modifier, GCC |
220345e0 | 3995 | may allocate it in the same register as an unrelated input operand, on |
3996 | the assumption the inputs are consumed before the outputs are produced. | |
146ef39f | 3997 | This assumption may be false if the assembler code actually consists of |
3998 | more than one instruction. In such a case, use @samp{&} for each output | |
220345e0 | 3999 | operand that may not overlap an input. @xref{Modifiers}. |
146ef39f | 4000 | |
220345e0 | 4001 | If you want to test the condition code produced by an assembler |
4002 | instruction, you must include a branch and a label in the @code{asm} | |
4003 | construct, as follows: | |
146ef39f | 4004 | |
4005 | @example | |
4cd470f2 | 4006 | asm ("clr %0\n\tfrob %1\n\tbeq 0f\n\tmov #1,%0\n0:" |
146ef39f | 4007 | : "g" (result) |
4008 | : "g" (input)); | |
4009 | @end example | |
4010 | ||
4011 | @noindent | |
4012 | This assumes your assembler supports local labels, as the GNU assembler | |
4013 | and most Unix assemblers do. | |
4014 | ||
4015 | Speaking of labels, jumps from one @code{asm} to another are not | |
220345e0 | 4016 | supported. The compiler's optimizers do not know about these jumps, and |
4017 | therefore they cannot take account of them when deciding how to | |
146ef39f | 4018 | optimize. |
4019 | ||
4020 | @cindex macros containing @code{asm} | |
4021 | Usually the most convenient way to use these @code{asm} instructions is to | |
4022 | encapsulate them in macros that look like functions. For example, | |
4023 | ||
4024 | @example | |
4025 | #define sin(x) \ | |
4026 | (@{ double __value, __arg = (x); \ | |
4027 | asm ("fsinx %1,%0": "=f" (__value): "f" (__arg)); \ | |
4028 | __value; @}) | |
4029 | @end example | |
4030 | ||
4031 | @noindent | |
4032 | Here the variable @code{__arg} is used to make sure that the instruction | |
4033 | operates on a proper @code{double} value, and to accept only those | |
4034 | arguments @code{x} which can convert automatically to a @code{double}. | |
4035 | ||
220345e0 | 4036 | Another way to make sure the instruction operates on the correct data |
4037 | type is to use a cast in the @code{asm}. This is different from using a | |
146ef39f | 4038 | variable @code{__arg} in that it converts more different types. For |
4039 | example, if the desired type were @code{int}, casting the argument to | |
4040 | @code{int} would accept a pointer with no complaint, while assigning the | |
4041 | argument to an @code{int} variable named @code{__arg} would warn about | |
4042 | using a pointer unless the caller explicitly casts it. | |
4043 | ||
37744367 | 4044 | If an @code{asm} has output operands, GCC assumes for optimization |
220345e0 | 4045 | purposes the instruction has no side effects except to change the output |
4046 | operands. This does not mean instructions with a side effect cannot be | |
4047 | used, but you must be careful, because the compiler may eliminate them | |
4048 | if the output operands aren't used, or move them out of loops, or | |
4049 | replace two with one if they constitute a common subexpression. Also, | |
4050 | if your instruction does have a side effect on a variable that otherwise | |
4051 | appears not to change, the old value of the variable may be reused later | |
4052 | if it happens to be found in a register. | |
146ef39f | 4053 | |
4054 | You can prevent an @code{asm} instruction from being deleted, moved | |
4055 | significantly, or combined, by writing the keyword @code{volatile} after | |
4056 | the @code{asm}. For example: | |
4057 | ||
4058 | @example | |
d90db7dc | 4059 | #define get_and_set_priority(new) \ |
4060 | (@{ int __old; \ | |
4061 | asm volatile ("get_and_set_priority %0, %1" \ | |
4062 | : "=g" (__old) : "g" (new)); \ | |
220345e0 | 4063 | __old; @}) |
a4f62784 | 4064 | @end example |
146ef39f | 4065 | |
4066 | @noindent | |
37744367 | 4067 | If you write an @code{asm} instruction with no outputs, GCC will know |
220345e0 | 4068 | the instruction has side-effects and will not delete the instruction or |
90f960d5 | 4069 | move it outside of loops. |
220345e0 | 4070 | |
90f960d5 | 4071 | The @code{volatile} keyword indicates that the instruction has |
4072 | important side-effects. GCC will not delete a volatile @code{asm} if | |
4073 | it is reachable. (The instruction can still be deleted if GCC can | |
4074 | prove that control-flow will never reach the location of the | |
4075 | instruction.) In addition, GCC will not reschedule instructions | |
4076 | across a volatile @code{asm} instruction. For example: | |
4077 | ||
4078 | @example | |
9149051d | 4079 | *(volatile int *)addr = foo; |
90f960d5 | 4080 | asm volatile ("eieio" : : ); |
4081 | @end example | |
4082 | ||
77f71523 | 4083 | @noindent |
90f960d5 | 4084 | Assume @code{addr} contains the address of a memory mapped device |
4085 | register. The PowerPC @code{eieio} instruction (Enforce In-order | |
70c2c81c | 4086 | Execution of I/O) tells the CPU to make sure that the store to that |
0858e3a2 | 4087 | device register happens before it issues any other I/O@. |
146ef39f | 4088 | |
4089 | Note that even a volatile @code{asm} instruction can be moved in ways | |
4090 | that appear insignificant to the compiler, such as across jump | |
4091 | instructions. You can't expect a sequence of volatile @code{asm} | |
4092 | instructions to remain perfectly consecutive. If you want consecutive | |
90f960d5 | 4093 | output, use a single @code{asm}. Also, GCC will perform some |
4094 | optimizations across a volatile @code{asm} instruction; GCC does not | |
4095 | ``forget everything'' when it encounters a volatile @code{asm} | |
4096 | instruction the way some other compilers do. | |
4097 | ||
4098 | An @code{asm} instruction without any operands or clobbers (an ``old | |
4099 | style'' @code{asm}) will be treated identically to a volatile | |
4100 | @code{asm} instruction. | |
146ef39f | 4101 | |
4102 | It is a natural idea to look for a way to give access to the condition | |
4103 | code left by the assembler instruction. However, when we attempted to | |
4104 | implement this, we found no way to make it work reliably. The problem | |
4105 | is that output operands might need reloading, which would result in | |
4106 | additional following ``store'' instructions. On most machines, these | |
4107 | instructions would alter the condition code before there was time to | |
4108 | test it. This problem doesn't arise for ordinary ``test'' and | |
4109 | ``compare'' instructions because they don't have any output operands. | |
4110 | ||
356ed71f | 4111 | For reasons similar to those described above, it is not possible to give |
4112 | an assembler instruction access to the condition code left by previous | |
4113 | instructions. | |
4114 | ||
78b1f616 | 4115 | If you are writing a header file that should be includable in ISO C |
146ef39f | 4116 | programs, write @code{__asm__} instead of @code{asm}. @xref{Alternate |
4117 | Keywords}. | |
4118 | ||
53ae8f59 | 4119 | @subsection i386 floating point asm operands |
4120 | ||
4121 | There are several rules on the usage of stack-like regs in | |
4122 | asm_operands insns. These rules apply only to the operands that are | |
4123 | stack-like regs: | |
4124 | ||
4125 | @enumerate | |
4126 | @item | |
4127 | Given a set of input regs that die in an asm_operands, it is | |
4128 | necessary to know which are implicitly popped by the asm, and | |
4129 | which must be explicitly popped by gcc. | |
4130 | ||
4131 | An input reg that is implicitly popped by the asm must be | |
4132 | explicitly clobbered, unless it is constrained to match an | |
4133 | output operand. | |
4134 | ||
4135 | @item | |
4136 | For any input reg that is implicitly popped by an asm, it is | |
4137 | necessary to know how to adjust the stack to compensate for the pop. | |
4138 | If any non-popped input is closer to the top of the reg-stack than | |
4139 | the implicitly popped reg, it would not be possible to know what the | |
67791935 | 4140 | stack looked like---it's not clear how the rest of the stack ``slides |
53ae8f59 | 4141 | up''. |
4142 | ||
4143 | All implicitly popped input regs must be closer to the top of | |
4144 | the reg-stack than any input that is not implicitly popped. | |
4145 | ||
4146 | It is possible that if an input dies in an insn, reload might | |
4147 | use the input reg for an output reload. Consider this example: | |
4148 | ||
4149 | @example | |
4150 | asm ("foo" : "=t" (a) : "f" (b)); | |
4151 | @end example | |
4152 | ||
4153 | This asm says that input B is not popped by the asm, and that | |
8e5fcce7 | 4154 | the asm pushes a result onto the reg-stack, i.e., the stack is one |
53ae8f59 | 4155 | deeper after the asm than it was before. But, it is possible that |
4156 | reload will think that it can use the same reg for both the input and | |
4157 | the output, if input B dies in this insn. | |
4158 | ||
4159 | If any input operand uses the @code{f} constraint, all output reg | |
4160 | constraints must use the @code{&} earlyclobber. | |
4161 | ||
4162 | The asm above would be written as | |
4163 | ||
4164 | @example | |
4165 | asm ("foo" : "=&t" (a) : "f" (b)); | |
4166 | @end example | |
4167 | ||
4168 | @item | |
4169 | Some operands need to be in particular places on the stack. All | |
67791935 | 4170 | output operands fall in this category---there is no other way to |
53ae8f59 | 4171 | know which regs the outputs appear in unless the user indicates |
4172 | this in the constraints. | |
4173 | ||
4174 | Output operands must specifically indicate which reg an output | |
4175 | appears in after an asm. @code{=f} is not allowed: the operand | |
4176 | constraints must select a class with a single reg. | |
4177 | ||
4178 | @item | |
4179 | Output operands may not be ``inserted'' between existing stack regs. | |
4180 | Since no 387 opcode uses a read/write operand, all output operands | |
4181 | are dead before the asm_operands, and are pushed by the asm_operands. | |
4182 | It makes no sense to push anywhere but the top of the reg-stack. | |
4183 | ||
4184 | Output operands must start at the top of the reg-stack: output | |
4185 | operands may not ``skip'' a reg. | |
4186 | ||
4187 | @item | |
4188 | Some asm statements may need extra stack space for internal | |
4189 | calculations. This can be guaranteed by clobbering stack registers | |
4190 | unrelated to the inputs and outputs. | |
4191 | ||
4192 | @end enumerate | |
4193 | ||
4194 | Here are a couple of reasonable asms to want to write. This asm | |
4195 | takes one input, which is internally popped, and produces two outputs. | |
4196 | ||
4197 | @example | |
4198 | asm ("fsincos" : "=t" (cos), "=u" (sin) : "0" (inp)); | |
4199 | @end example | |
4200 | ||
4201 | This asm takes two inputs, which are popped by the @code{fyl2xp1} opcode, | |
4202 | and replaces them with one output. The user must code the @code{st(1)} | |
4203 | clobber for reg-stack.c to know that @code{fyl2xp1} pops both inputs. | |
4204 | ||
4205 | @example | |
4206 | asm ("fyl2xp1" : "=t" (result) : "0" (x), "u" (y) : "st(1)"); | |
4207 | @end example | |
4208 | ||
146ef39f | 4209 | @include md.texi |
146ef39f | 4210 | |
4211 | @node Asm Labels | |
4212 | @section Controlling Names Used in Assembler Code | |
4213 | @cindex assembler names for identifiers | |
4214 | @cindex names used in assembler code | |
4215 | @cindex identifiers, names in assembler code | |
4216 | ||
4217 | You can specify the name to be used in the assembler code for a C | |
4218 | function or variable by writing the @code{asm} (or @code{__asm__}) | |
4219 | keyword after the declarator as follows: | |
4220 | ||
4221 | @example | |
4222 | int foo asm ("myfoo") = 2; | |
4223 | @end example | |
4224 | ||
4225 | @noindent | |
4226 | This specifies that the name to be used for the variable @code{foo} in | |
4227 | the assembler code should be @samp{myfoo} rather than the usual | |
4228 | @samp{_foo}. | |
4229 | ||
4230 | On systems where an underscore is normally prepended to the name of a C | |
4231 | function or variable, this feature allows you to define names for the | |
4232 | linker that do not start with an underscore. | |
4233 | ||
cd5abf58 | 4234 | It does not make sense to use this feature with a non-static local |
4235 | variable since such variables do not have assembler names. If you are | |
4236 | trying to put the variable in a particular register, see @ref{Explicit | |
4237 | Reg Vars}. GCC presently accepts such code with a warning, but will | |
4238 | probably be changed to issue an error, rather than a warning, in the | |
4239 | future. | |
4240 | ||
146ef39f | 4241 | You cannot use @code{asm} in this way in a function @emph{definition}; but |
4242 | you can get the same effect by writing a declaration for the function | |
4243 | before its definition and putting @code{asm} there, like this: | |
4244 | ||
4245 | @example | |
4246 | extern func () asm ("FUNC"); | |
4247 | ||
4248 | func (x, y) | |
4249 | int x, y; | |
4ae74ddd | 4250 | /* @r{@dots{}} */ |
146ef39f | 4251 | @end example |
4252 | ||
4253 | It is up to you to make sure that the assembler names you choose do not | |
4254 | conflict with any other assembler symbols. Also, you must not use a | |
37744367 | 4255 | register name; that would produce completely invalid assembler code. GCC |
4256 | does not as yet have the ability to store static variables in registers. | |
146ef39f | 4257 | Perhaps that will be added. |
4258 | ||
4259 | @node Explicit Reg Vars | |
4260 | @section Variables in Specified Registers | |
4261 | @cindex explicit register variables | |
4262 | @cindex variables in specified registers | |
4263 | @cindex specified registers | |
4264 | @cindex registers, global allocation | |
4265 | ||
4266 | GNU C allows you to put a few global variables into specified hardware | |
4267 | registers. You can also specify the register in which an ordinary | |
4268 | register variable should be allocated. | |
4269 | ||
4270 | @itemize @bullet | |
4271 | @item | |
4272 | Global register variables reserve registers throughout the program. | |
4273 | This may be useful in programs such as programming language | |
4274 | interpreters which have a couple of global variables that are accessed | |
4275 | very often. | |
4276 | ||
4277 | @item | |
4278 | Local register variables in specific registers do not reserve the | |
4279 | registers. The compiler's data flow analysis is capable of determining | |
4280 | where the specified registers contain live values, and where they are | |
dcb61f7f | 4281 | available for other uses. Stores into local register variables may be deleted |
d2763590 | 4282 | when they appear to be dead according to dataflow analysis. References |
4283 | to local register variables may be deleted or moved or simplified. | |
146ef39f | 4284 | |
4285 | These local variables are sometimes convenient for use with the extended | |
4286 | @code{asm} feature (@pxref{Extended Asm}), if you want to write one | |
4287 | output of the assembler instruction directly into a particular register. | |
4288 | (This will work provided the register you specify fits the constraints | |
4289 | specified for that operand in the @code{asm}.) | |
4290 | @end itemize | |
4291 | ||
4292 | @menu | |
4293 | * Global Reg Vars:: | |
4294 | * Local Reg Vars:: | |
4295 | @end menu | |
4296 | ||
4297 | @node Global Reg Vars | |
4298 | @subsection Defining Global Register Variables | |
4299 | @cindex global register variables | |
4300 | @cindex registers, global variables in | |
4301 | ||
4302 | You can define a global register variable in GNU C like this: | |
4303 | ||
4304 | @example | |
4305 | register int *foo asm ("a5"); | |
4306 | @end example | |
4307 | ||
4308 | @noindent | |
4309 | Here @code{a5} is the name of the register which should be used. Choose a | |
4310 | register which is normally saved and restored by function calls on your | |
4311 | machine, so that library routines will not clobber it. | |
4312 | ||
4313 | Naturally the register name is cpu-dependent, so you would need to | |
4314 | conditionalize your program according to cpu type. The register | |
4315 | @code{a5} would be a good choice on a 68000 for a variable of pointer | |
4316 | type. On machines with register windows, be sure to choose a ``global'' | |
4317 | register that is not affected magically by the function call mechanism. | |
4318 | ||
4319 | In addition, operating systems on one type of cpu may differ in how they | |
4320 | name the registers; then you would need additional conditionals. For | |
4321 | example, some 68000 operating systems call this register @code{%a5}. | |
4322 | ||
4323 | Eventually there may be a way of asking the compiler to choose a register | |
4324 | automatically, but first we need to figure out how it should choose and | |
4325 | how to enable you to guide the choice. No solution is evident. | |
4326 | ||
4327 | Defining a global register variable in a certain register reserves that | |
4328 | register entirely for this use, at least within the current compilation. | |
4329 | The register will not be allocated for any other purpose in the functions | |
4330 | in the current compilation. The register will not be saved and restored by | |
4331 | these functions. Stores into this register are never deleted even if they | |
4332 | would appear to be dead, but references may be deleted or moved or | |
4333 | simplified. | |
4334 | ||
4335 | It is not safe to access the global register variables from signal | |
4336 | handlers, or from more than one thread of control, because the system | |
4337 | library routines may temporarily use the register for other things (unless | |
4338 | you recompile them specially for the task at hand). | |
4339 | ||
4340 | @cindex @code{qsort}, and global register variables | |
4341 | It is not safe for one function that uses a global register variable to | |
4342 | call another such function @code{foo} by way of a third function | |
0858f8a2 | 4343 | @code{lose} that was compiled without knowledge of this variable (i.e.@: in a |
146ef39f | 4344 | different source file in which the variable wasn't declared). This is |
4345 | because @code{lose} might save the register and put some other value there. | |
4346 | For example, you can't expect a global register variable to be available in | |
4347 | the comparison-function that you pass to @code{qsort}, since @code{qsort} | |
4348 | might have put something else in that register. (If you are prepared to | |
4349 | recompile @code{qsort} with the same global register variable, you can | |
4350 | solve this problem.) | |
4351 | ||
4352 | If you want to recompile @code{qsort} or other source files which do not | |
4353 | actually use your global register variable, so that they will not use that | |
4354 | register for any other purpose, then it suffices to specify the compiler | |
67791935 | 4355 | option @option{-ffixed-@var{reg}}. You need not actually add a global |
146ef39f | 4356 | register declaration to their source code. |
4357 | ||
4358 | A function which can alter the value of a global register variable cannot | |
4359 | safely be called from a function compiled without this variable, because it | |
4360 | could clobber the value the caller expects to find there on return. | |
4361 | Therefore, the function which is the entry point into the part of the | |
4362 | program that uses the global register variable must explicitly save and | |
4363 | restore the value which belongs to its caller. | |
4364 | ||
4365 | @cindex register variable after @code{longjmp} | |
4366 | @cindex global register after @code{longjmp} | |
4367 | @cindex value after @code{longjmp} | |
4368 | @findex longjmp | |
4369 | @findex setjmp | |
4370 | On most machines, @code{longjmp} will restore to each global register | |
4371 | variable the value it had at the time of the @code{setjmp}. On some | |
4372 | machines, however, @code{longjmp} will not change the value of global | |
4373 | register variables. To be portable, the function that called @code{setjmp} | |
4374 | should make other arrangements to save the values of the global register | |
4375 | variables, and to restore them in a @code{longjmp}. This way, the same | |
4376 | thing will happen regardless of what @code{longjmp} does. | |
4377 | ||
4378 | All global register variable declarations must precede all function | |
4379 | definitions. If such a declaration could appear after function | |
4380 | definitions, the declaration would be too late to prevent the register from | |
4381 | being used for other purposes in the preceding functions. | |
4382 | ||
4383 | Global register variables may not have initial values, because an | |
4384 | executable file has no means to supply initial contents for a register. | |
4385 | ||
7800959d | 4386 | On the SPARC, there are reports that g3 @dots{} g7 are suitable |
146ef39f | 4387 | registers, but certain library functions, such as @code{getwd}, as well |
4388 | as the subroutines for division and remainder, modify g3 and g4. g1 and | |
4389 | g2 are local temporaries. | |
4390 | ||
4391 | On the 68000, a2 @dots{} a5 should be suitable, as should d2 @dots{} d7. | |
4392 | Of course, it will not do to use more than a few of those. | |
4393 | ||
4394 | @node Local Reg Vars | |
4395 | @subsection Specifying Registers for Local Variables | |
4396 | @cindex local variables, specifying registers | |
4397 | @cindex specifying registers for local variables | |
4398 | @cindex registers for local variables | |
4399 | ||
4400 | You can define a local register variable with a specified register | |
4401 | like this: | |
4402 | ||
4403 | @example | |
4404 | register int *foo asm ("a5"); | |
4405 | @end example | |
4406 | ||
4407 | @noindent | |
4408 | Here @code{a5} is the name of the register which should be used. Note | |
4409 | that this is the same syntax used for defining global register | |
4410 | variables, but for a local variable it would appear within a function. | |
4411 | ||
4412 | Naturally the register name is cpu-dependent, but this is not a | |
4413 | problem, since specific registers are most often useful with explicit | |
4414 | assembler instructions (@pxref{Extended Asm}). Both of these things | |
4415 | generally require that you conditionalize your program according to | |
4416 | cpu type. | |
4417 | ||
4418 | In addition, operating systems on one type of cpu may differ in how they | |
4419 | name the registers; then you would need additional conditionals. For | |
4420 | example, some 68000 operating systems call this register @code{%a5}. | |
4421 | ||
146ef39f | 4422 | Defining such a register variable does not reserve the register; it |
4423 | remains available for other uses in places where flow control determines | |
4424 | the variable's value is not live. However, these registers are made | |
997d68fe | 4425 | unavailable for use in the reload pass; excessive use of this feature |
4426 | leaves the compiler too few available registers to compile certain | |
4427 | functions. | |
4428 | ||
37744367 | 4429 | This option does not guarantee that GCC will generate code that has |
997d68fe | 4430 | this variable in the register you specify at all times. You may not |
4431 | code an explicit reference to this register in an @code{asm} statement | |
4432 | and assume it will always refer to this variable. | |
146ef39f | 4433 | |
dcb61f7f | 4434 | Stores into local register variables may be deleted when they appear to be dead |
d2763590 | 4435 | according to dataflow analysis. References to local register variables may |
4436 | be deleted or moved or simplified. | |
4437 | ||
146ef39f | 4438 | @node Alternate Keywords |
4439 | @section Alternate Keywords | |
4440 | @cindex alternate keywords | |
4441 | @cindex keywords, alternate | |
4442 | ||
78b1f616 | 4443 | @option{-ansi} and the various @option{-std} options disable certain |
455730ef | 4444 | keywords. This causes trouble when you want to use GNU C extensions, or |
4445 | a general-purpose header file that should be usable by all programs, | |
4446 | including ISO C programs. The keywords @code{asm}, @code{typeof} and | |
4447 | @code{inline} are not available in programs compiled with | |
4448 | @option{-ansi} or @option{-std} (although @code{inline} can be used in a | |
4449 | program compiled with @option{-std=c99}). The ISO C99 keyword | |
78b1f616 | 4450 | @code{restrict} is only available when @option{-std=gnu99} (which will |
4451 | eventually be the default) or @option{-std=c99} (or the equivalent | |
f36eeacd | 4452 | @option{-std=iso9899:1999}) is used. |
146ef39f | 4453 | |
4454 | The way to solve these problems is to put @samp{__} at the beginning and | |
4455 | end of each problematical keyword. For example, use @code{__asm__} | |
455730ef | 4456 | instead of @code{asm}, and @code{__inline__} instead of @code{inline}. |
146ef39f | 4457 | |
4458 | Other C compilers won't accept these alternative keywords; if you want to | |
4459 | compile with another compiler, you can define the alternate keywords as | |
4460 | macros to replace them with the customary keywords. It looks like this: | |
4461 | ||
4462 | @example | |
4463 | #ifndef __GNUC__ | |
4464 | #define __asm__ asm | |
4465 | #endif | |
4466 | @end example | |
4467 | ||
d4303d2a | 4468 | @findex __extension__ |
67791935 | 4469 | @opindex pedantic |
4470 | @option{-pedantic} and other options cause warnings for many GNU C extensions. | |
6b88ddb7 | 4471 | You can |
146ef39f | 4472 | prevent such warnings within one expression by writing |
4473 | @code{__extension__} before the expression. @code{__extension__} has no | |
4474 | effect aside from this. | |
4475 | ||
4476 | @node Incomplete Enums | |
4477 | @section Incomplete @code{enum} Types | |
4478 | ||
4479 | You can define an @code{enum} tag without specifying its possible values. | |
4480 | This results in an incomplete type, much like what you get if you write | |
4481 | @code{struct foo} without describing the elements. A later declaration | |
4482 | which does specify the possible values completes the type. | |
4483 | ||
4484 | You can't allocate variables or storage using the type while it is | |
4485 | incomplete. However, you can work with pointers to that type. | |
4486 | ||
4487 | This extension may not be very useful, but it makes the handling of | |
4488 | @code{enum} more consistent with the way @code{struct} and @code{union} | |
4489 | are handled. | |
4490 | ||
4491 | This extension is not supported by GNU C++. | |
4492 | ||
4493 | @node Function Names | |
4494 | @section Function Names as Strings | |
ebc03810 | 4495 | @cindex @code{__func__} identifier |
3cfa0cc4 | 4496 | @cindex @code{__FUNCTION__} identifier |
4497 | @cindex @code{__PRETTY_FUNCTION__} identifier | |
146ef39f | 4498 | |
ebc03810 | 4499 | GCC provides three magic variables which hold the name of the current |
4500 | function, as a string. The first of these is @code{__func__}, which | |
4501 | is part of the C99 standard: | |
4502 | ||
4503 | @display | |
4504 | The identifier @code{__func__} is implicitly declared by the translator | |
4505 | as if, immediately following the opening brace of each function | |
4506 | definition, the declaration | |
4507 | ||
4508 | @smallexample | |
4509 | static const char __func__[] = "function-name"; | |
4510 | @end smallexample | |
146ef39f | 4511 | |
ebc03810 | 4512 | appeared, where function-name is the name of the lexically-enclosing |
4513 | function. This name is the unadorned name of the function. | |
4514 | @end display | |
4515 | ||
4516 | @code{__FUNCTION__} is another name for @code{__func__}. Older | |
4517 | versions of GCC recognize only this name. However, it is not | |
4518 | standardized. For maximum portability, we recommend you use | |
4519 | @code{__func__}, but provide a fallback definition with the | |
4520 | preprocessor: | |
4521 | ||
4522 | @smallexample | |
4523 | #if __STDC_VERSION__ < 199901L | |
4524 | # if __GNUC__ >= 2 | |
4525 | # define __func__ __FUNCTION__ | |
4526 | # else | |
4527 | # define __func__ "<unknown>" | |
4528 | # endif | |
4529 | #endif | |
4530 | @end smallexample | |
4531 | ||
4532 | In C, @code{__PRETTY_FUNCTION__} is yet another name for | |
4533 | @code{__func__}. However, in C++, @code{__PRETTY_FUNCTION__} contains | |
4534 | the type signature of the function as well as its bare name. For | |
4535 | example, this program: | |
146ef39f | 4536 | |
4537 | @smallexample | |
4538 | extern "C" @{ | |
4539 | extern int printf (char *, ...); | |
4540 | @} | |
4541 | ||
4542 | class a @{ | |
4543 | public: | |
20a69fd5 | 4544 | void sub (int i) |
146ef39f | 4545 | @{ |
4546 | printf ("__FUNCTION__ = %s\n", __FUNCTION__); | |
4547 | printf ("__PRETTY_FUNCTION__ = %s\n", __PRETTY_FUNCTION__); | |
4548 | @} | |
4549 | @}; | |
4550 | ||
4551 | int | |
4552 | main (void) | |
4553 | @{ | |
4554 | a ax; | |
4555 | ax.sub (0); | |
4556 | return 0; | |
4557 | @} | |
4558 | @end smallexample | |
4559 | ||
4560 | @noindent | |
4561 | gives this output: | |
4562 | ||
4563 | @smallexample | |
4564 | __FUNCTION__ = sub | |
ebc03810 | 4565 | __PRETTY_FUNCTION__ = void a::sub(int) |
b082e8af | 4566 | @end smallexample |
4567 | ||
ebc03810 | 4568 | These identifiers are not preprocessor macros. In GCC 3.3 and |
4569 | earlier, in C only, @code{__FUNCTION__} and @code{__PRETTY_FUNCTION__} | |
4570 | were treated as string literals; they could be used to initialize | |
4571 | @code{char} arrays, and they could be concatenated with other string | |
4572 | literals. GCC 3.4 and later treat them as variables, like | |
4573 | @code{__func__}. In C++, @code{__FUNCTION__} and | |
4574 | @code{__PRETTY_FUNCTION__} have always been variables. | |
b082e8af | 4575 | |
146ef39f | 4576 | @node Return Address |
4577 | @section Getting the Return or Frame Address of a Function | |
4578 | ||
4579 | These functions may be used to get information about the callers of a | |
4580 | function. | |
4581 | ||
67791935 | 4582 | @deftypefn {Built-in Function} {void *} __builtin_return_address (unsigned int @var{level}) |
146ef39f | 4583 | This function returns the return address of the current function, or of |
4584 | one of its callers. The @var{level} argument is number of frames to | |
4585 | scan up the call stack. A value of @code{0} yields the return address | |
4586 | of the current function, a value of @code{1} yields the return address | |
85456819 | 4587 | of the caller of the current function, and so forth. When inlining |
4588 | the expected behavior is that the function will return the address of | |
4589 | the function that will be returned to. To work around this behavior use | |
4590 | the @code{noinline} function attribute. | |
146ef39f | 4591 | |
4592 | The @var{level} argument must be a constant integer. | |
4593 | ||
4594 | On some machines it may be impossible to determine the return address of | |
4595 | any function other than the current one; in such cases, or when the top | |
1288313e | 4596 | of the stack has been reached, this function will return @code{0} or a |
4597 | random value. In addition, @code{__builtin_frame_address} may be used | |
4598 | to determine if the top of the stack has been reached. | |
146ef39f | 4599 | |
f45856ef | 4600 | This function should only be used with a nonzero argument for debugging |
146ef39f | 4601 | purposes. |
67791935 | 4602 | @end deftypefn |
146ef39f | 4603 | |
67791935 | 4604 | @deftypefn {Built-in Function} {void *} __builtin_frame_address (unsigned int @var{level}) |
146ef39f | 4605 | This function is similar to @code{__builtin_return_address}, but it |
4606 | returns the address of the function frame rather than the return address | |
4607 | of the function. Calling @code{__builtin_frame_address} with a value of | |
4608 | @code{0} yields the frame address of the current function, a value of | |
4609 | @code{1} yields the frame address of the caller of the current function, | |
4610 | and so forth. | |
4611 | ||
4612 | The frame is the area on the stack which holds local variables and saved | |
4613 | registers. The frame address is normally the address of the first word | |
4614 | pushed on to the stack by the function. However, the exact definition | |
4615 | depends upon the processor and the calling convention. If the processor | |
4616 | has a dedicated frame pointer register, and the function has a frame, | |
4617 | then @code{__builtin_frame_address} will return the value of the frame | |
4618 | pointer register. | |
4619 | ||
1288313e | 4620 | On some machines it may be impossible to determine the frame address of |
4621 | any function other than the current one; in such cases, or when the top | |
4622 | of the stack has been reached, this function will return @code{0} if | |
4623 | the first frame pointer is properly initialized by the startup code. | |
4624 | ||
f45856ef | 4625 | This function should only be used with a nonzero argument for debugging |
1288313e | 4626 | purposes. |
67791935 | 4627 | @end deftypefn |
146ef39f | 4628 | |
ee5925ea | 4629 | @node Vector Extensions |
4630 | @section Using vector instructions through built-in functions | |
4631 | ||
4632 | On some targets, the instruction set contains SIMD vector instructions that | |
4633 | operate on multiple values contained in one large register at the same time. | |
4634 | For example, on the i386 the MMX, 3Dnow! and SSE extensions can be used | |
4635 | this way. | |
4636 | ||
4637 | The first step in using these extensions is to provide the necessary data | |
4638 | types. This should be done using an appropriate @code{typedef}: | |
4639 | ||
4640 | @example | |
4641 | typedef int v4si __attribute__ ((mode(V4SI))); | |
4642 | @end example | |
4643 | ||
4644 | The base type @code{int} is effectively ignored by the compiler, the | |
4645 | actual properties of the new type @code{v4si} are defined by the | |
4646 | @code{__attribute__}. It defines the machine mode to be used; for vector | |
ce901d78 | 4647 | types these have the form @code{V@var{n}@var{B}}; @var{n} should be the |
4648 | number of elements in the vector, and @var{B} should be the base mode of the | |
ee5925ea | 4649 | individual elements. The following can be used as base modes: |
4650 | ||
4651 | @table @code | |
4652 | @item QI | |
4653 | An integer that is as wide as the smallest addressable unit, usually 8 bits. | |
4654 | @item HI | |
4655 | An integer, twice as wide as a QI mode integer, usually 16 bits. | |
4656 | @item SI | |
4657 | An integer, four times as wide as a QI mode integer, usually 32 bits. | |
4658 | @item DI | |
4659 | An integer, eight times as wide as a QI mode integer, usually 64 bits. | |
4660 | @item SF | |
4661 | A floating point value, as wide as a SI mode integer, usually 32 bits. | |
4662 | @item DF | |
4663 | A floating point value, as wide as a DI mode integer, usually 64 bits. | |
4664 | @end table | |
4665 | ||
ead34f59 | 4666 | Specifying a combination that is not valid for the current architecture |
4667 | will cause gcc to synthesize the instructions using a narrower mode. | |
4668 | For example, if you specify a variable of type @code{V4SI} and your | |
4669 | architecture does not allow for this specific SIMD type, gcc will | |
4670 | produce code that uses 4 @code{SIs}. | |
4671 | ||
4672 | The types defined in this manner can be used with a subset of normal C | |
4673 | operations. Currently, gcc will allow using the following operators on | |
4674 | these types: @code{+, -, *, /, unary minus}@. | |
4675 | ||
4676 | The operations behave like C++ @code{valarrays}. Addition is defined as | |
4677 | the addition of the corresponding elements of the operands. For | |
4678 | example, in the code below, each of the 4 elements in @var{a} will be | |
4679 | added to the corresponding 4 elements in @var{b} and the resulting | |
4680 | vector will be stored in @var{c}. | |
4681 | ||
4682 | @example | |
4683 | typedef int v4si __attribute__ ((mode(V4SI))); | |
4684 | ||
4685 | v4si a, b, c; | |
4686 | ||
4687 | c = a + b; | |
4688 | @end example | |
4689 | ||
4690 | Subtraction, multiplication, and division operate in a similar manner. | |
4691 | Likewise, the result of using the unary minus operator on a vector type | |
4692 | is a vector whose elements are the negative value of the corresponding | |
4693 | elements in the operand. | |
4694 | ||
4695 | You can declare variables and use them in function calls and returns, as | |
4696 | well as in assignments and some casts. You can specify a vector type as | |
4697 | a return type for a function. Vector types can also be used as function | |
4698 | arguments. It is possible to cast from one vector type to another, | |
4699 | provided they are of the same size (in fact, you can also cast vectors | |
4700 | to and from other datatypes of the same size). | |
4701 | ||
4702 | You cannot operate between vectors of different lengths or different | |
d835d5ce | 4703 | signedness without a cast. |
ead34f59 | 4704 | |
4705 | A port that supports hardware vector operations, usually provides a set | |
4706 | of built-in functions that can be used to operate on vectors. For | |
4707 | example, a function to add two vectors and multiply the result by a | |
4708 | third could look like this: | |
ee5925ea | 4709 | |
4710 | @example | |
4711 | v4si f (v4si a, v4si b, v4si c) | |
4712 | @{ | |
4713 | v4si tmp = __builtin_addv4si (a, b); | |
4714 | return __builtin_mulv4si (tmp, c); | |
4715 | @} | |
4716 | ||
4717 | @end example | |
4718 | ||
2c776a54 | 4719 | @node Other Builtins |
37744367 | 4720 | @section Other built-in functions provided by GCC |
8e5fcce7 | 4721 | @cindex built-in functions |
1f4e0dac | 4722 | @findex __builtin_isgreater |
4723 | @findex __builtin_isgreaterequal | |
4724 | @findex __builtin_isless | |
4725 | @findex __builtin_islessequal | |
4726 | @findex __builtin_islessgreater | |
4727 | @findex __builtin_isunordered | |
e88e2794 | 4728 | @findex _Exit |
4729 | @findex _exit | |
1f4e0dac | 4730 | @findex abort |
4731 | @findex abs | |
e88e2794 | 4732 | @findex acos |
4733 | @findex acosf | |
4734 | @findex acosh | |
4735 | @findex acoshf | |
4736 | @findex acoshl | |
4737 | @findex acosl | |
1f4e0dac | 4738 | @findex alloca |
e88e2794 | 4739 | @findex asin |
4740 | @findex asinf | |
4741 | @findex asinh | |
4742 | @findex asinhf | |
4743 | @findex asinhl | |
4744 | @findex asinl | |
a2246f84 | 4745 | @findex atan |
fa426235 | 4746 | @findex atan2 |
4747 | @findex atan2f | |
4748 | @findex atan2l | |
a2246f84 | 4749 | @findex atanf |
e88e2794 | 4750 | @findex atanh |
4751 | @findex atanhf | |
4752 | @findex atanhl | |
a2246f84 | 4753 | @findex atanl |
1f4e0dac | 4754 | @findex bcmp |
4755 | @findex bzero | |
78a74442 | 4756 | @findex cabs |
4757 | @findex cabsf | |
4758 | @findex cabsl | |
61b922e7 | 4759 | @findex cacos |
4760 | @findex cacosf | |
4761 | @findex cacosh | |
4762 | @findex cacoshf | |
4763 | @findex cacoshl | |
4764 | @findex cacosl | |
32ef1cd2 | 4765 | @findex calloc |
61b922e7 | 4766 | @findex carg |
4767 | @findex cargf | |
4768 | @findex cargl | |
4769 | @findex casin | |
4770 | @findex casinf | |
4771 | @findex casinh | |
4772 | @findex casinhf | |
4773 | @findex casinhl | |
4774 | @findex casinl | |
4775 | @findex catan | |
4776 | @findex catanf | |
4777 | @findex catanh | |
4778 | @findex catanhf | |
4779 | @findex catanhl | |
4780 | @findex catanl | |
e88e2794 | 4781 | @findex cbrt |
4782 | @findex cbrtf | |
4783 | @findex cbrtl | |
61b922e7 | 4784 | @findex ccos |
4785 | @findex ccosf | |
4786 | @findex ccosh | |
4787 | @findex ccoshf | |
4788 | @findex ccoshl | |
4789 | @findex ccosl | |
982c684c | 4790 | @findex ceil |
4791 | @findex ceilf | |
4792 | @findex ceill | |
61b922e7 | 4793 | @findex cexp |
4794 | @findex cexpf | |
4795 | @findex cexpl | |
d30e4d04 | 4796 | @findex cimag |
4797 | @findex cimagf | |
4798 | @findex cimagl | |
4799 | @findex conj | |
4800 | @findex conjf | |
4801 | @findex conjl | |
e88e2794 | 4802 | @findex copysign |
4803 | @findex copysignf | |
4804 | @findex copysignl | |
1f4e0dac | 4805 | @findex cos |
4806 | @findex cosf | |
e88e2794 | 4807 | @findex cosh |
4808 | @findex coshf | |
4809 | @findex coshl | |
1f4e0dac | 4810 | @findex cosl |
61b922e7 | 4811 | @findex cpow |
4812 | @findex cpowf | |
4813 | @findex cpowl | |
4814 | @findex cproj | |
4815 | @findex cprojf | |
4816 | @findex cprojl | |
d30e4d04 | 4817 | @findex creal |
4818 | @findex crealf | |
4819 | @findex creall | |
61b922e7 | 4820 | @findex csin |
4821 | @findex csinf | |
4822 | @findex csinh | |
4823 | @findex csinhf | |
4824 | @findex csinhl | |
4825 | @findex csinl | |
4826 | @findex csqrt | |
4827 | @findex csqrtf | |
4828 | @findex csqrtl | |
4829 | @findex ctan | |
4830 | @findex ctanf | |
4831 | @findex ctanh | |
4832 | @findex ctanhf | |
4833 | @findex ctanhl | |
4834 | @findex ctanl | |
b9b15671 | 4835 | @findex dcgettext |
4836 | @findex dgettext | |
e88e2794 | 4837 | @findex drem |
4838 | @findex dremf | |
4839 | @findex dreml | |
847749e5 | 4840 | @findex erf |
4841 | @findex erfc | |
4842 | @findex erfcf | |
4843 | @findex erfcl | |
4844 | @findex erff | |
4845 | @findex erfl | |
1f4e0dac | 4846 | @findex exit |
42721db0 | 4847 | @findex exp |
e88e2794 | 4848 | @findex exp10 |
4849 | @findex exp10f | |
4850 | @findex exp10l | |
4851 | @findex exp2 | |
4852 | @findex exp2f | |
4853 | @findex exp2l | |
42721db0 | 4854 | @findex expf |
4855 | @findex expl | |
e88e2794 | 4856 | @findex expm1 |
4857 | @findex expm1f | |
4858 | @findex expm1l | |
1f4e0dac | 4859 | @findex fabs |
4860 | @findex fabsf | |
4861 | @findex fabsl | |
e88e2794 | 4862 | @findex fdim |
4863 | @findex fdimf | |
4864 | @findex fdiml | |
1f4e0dac | 4865 | @findex ffs |
982c684c | 4866 | @findex floor |
4867 | @findex floorf | |
4868 | @findex floorl | |
e88e2794 | 4869 | @findex fma |
4870 | @findex fmaf | |
4871 | @findex fmal | |
4872 | @findex fmax | |
4873 | @findex fmaxf | |
4874 | @findex fmaxl | |
4875 | @findex fmin | |
4876 | @findex fminf | |
4877 | @findex fminl | |
982c684c | 4878 | @findex fmod |
4879 | @findex fmodf | |
4880 | @findex fmodl | |
96df8b77 | 4881 | @findex fprintf |
c013a46e | 4882 | @findex fprintf_unlocked |
1f4e0dac | 4883 | @findex fputs |
c013a46e | 4884 | @findex fputs_unlocked |
4070bd43 | 4885 | @findex frexp |
4886 | @findex frexpf | |
4887 | @findex frexpl | |
b9b15671 | 4888 | @findex fscanf |
847749e5 | 4889 | @findex gamma |
4890 | @findex gammaf | |
4891 | @findex gammal | |
b9b15671 | 4892 | @findex gettext |
e88e2794 | 4893 | @findex hypot |
4894 | @findex hypotf | |
4895 | @findex hypotl | |
4896 | @findex ilogb | |
4897 | @findex ilogbf | |
4898 | @findex ilogbl | |
1dfa965e | 4899 | @findex imaxabs |
398aae36 | 4900 | @findex index |
847749e5 | 4901 | @findex j0 |
4902 | @findex j0f | |
4903 | @findex j0l | |
4904 | @findex j1 | |
4905 | @findex j1f | |
4906 | @findex j1l | |
4907 | @findex jn | |
4908 | @findex jnf | |
4909 | @findex jnl | |
1f4e0dac | 4910 | @findex labs |
e88e2794 | 4911 | @findex ldexp |
4912 | @findex ldexpf | |
4913 | @findex ldexpl | |
847749e5 | 4914 | @findex lgamma |
4915 | @findex lgammaf | |
4916 | @findex lgammal | |
1f4e0dac | 4917 | @findex llabs |
e88e2794 | 4918 | @findex llrint |
4919 | @findex llrintf | |
4920 | @findex llrintl | |
4921 | @findex llround | |
4922 | @findex llroundf | |
4923 | @findex llroundl | |
42721db0 | 4924 | @findex log |
e88e2794 | 4925 | @findex log10 |
4926 | @findex log10f | |
4927 | @findex log10l | |
4928 | @findex log1p | |
4929 | @findex log1pf | |
4930 | @findex log1pl | |
4931 | @findex log2 | |
4932 | @findex log2f | |
4933 | @findex log2l | |
4934 | @findex logb | |
4935 | @findex logbf | |
4936 | @findex logbl | |
42721db0 | 4937 | @findex logf |
4938 | @findex logl | |
e88e2794 | 4939 | @findex lrint |
4940 | @findex lrintf | |
4941 | @findex lrintl | |
4942 | @findex lround | |
4943 | @findex lroundf | |
4944 | @findex lroundl | |
32ef1cd2 | 4945 | @findex malloc |
1f4e0dac | 4946 | @findex memcmp |
4947 | @findex memcpy | |
3b824fa6 | 4948 | @findex mempcpy |
1f4e0dac | 4949 | @findex memset |
4070bd43 | 4950 | @findex modf |
4951 | @findex modff | |
4952 | @findex modfl | |
982c684c | 4953 | @findex nearbyint |
4954 | @findex nearbyintf | |
4955 | @findex nearbyintl | |
e88e2794 | 4956 | @findex nextafter |
4957 | @findex nextafterf | |
4958 | @findex nextafterl | |
4959 | @findex nexttoward | |
4960 | @findex nexttowardf | |
4961 | @findex nexttowardl | |
fa426235 | 4962 | @findex pow |
e88e2794 | 4963 | @findex pow10 |
4964 | @findex pow10f | |
4965 | @findex pow10l | |
fa426235 | 4966 | @findex powf |
4967 | @findex powl | |
1f4e0dac | 4968 | @findex printf |
c013a46e | 4969 | @findex printf_unlocked |
03901330 | 4970 | @findex putchar |
4971 | @findex puts | |
e88e2794 | 4972 | @findex remainder |
4973 | @findex remainderf | |
4974 | @findex remainderl | |
4070bd43 | 4975 | @findex remquo |
4976 | @findex remquof | |
4977 | @findex remquol | |
398aae36 | 4978 | @findex rindex |
e88e2794 | 4979 | @findex rint |
4980 | @findex rintf | |
4981 | @findex rintl | |
982c684c | 4982 | @findex round |
4983 | @findex roundf | |
4984 | @findex roundl | |
e88e2794 | 4985 | @findex scalb |
4986 | @findex scalbf | |
4987 | @findex scalbl | |
4988 | @findex scalbln | |
4989 | @findex scalblnf | |
4990 | @findex scalblnf | |
4991 | @findex scalbn | |
4992 | @findex scalbnf | |
4993 | @findex scanfnl | |
847749e5 | 4994 | @findex significand |
4995 | @findex significandf | |
4996 | @findex significandl | |
1f4e0dac | 4997 | @findex sin |
4070bd43 | 4998 | @findex sincos |
4999 | @findex sincosf | |
5000 | @findex sincosl | |
1f4e0dac | 5001 | @findex sinf |
e88e2794 | 5002 | @findex sinh |
5003 | @findex sinhf | |
5004 | @findex sinhl | |
1f4e0dac | 5005 | @findex sinl |
03901330 | 5006 | @findex snprintf |
5007 | @findex sprintf | |
1f4e0dac | 5008 | @findex sqrt |
5009 | @findex sqrtf | |
5010 | @findex sqrtl | |
03901330 | 5011 | @findex sscanf |
3b824fa6 | 5012 | @findex stpcpy |
49f0327b | 5013 | @findex strcat |
1f4e0dac | 5014 | @findex strchr |
5015 | @findex strcmp | |
5016 | @findex strcpy | |
49f0327b | 5017 | @findex strcspn |
32ef1cd2 | 5018 | @findex strdup |
b9b15671 | 5019 | @findex strfmon |
5020 | @findex strftime | |
1f4e0dac | 5021 | @findex strlen |
49f0327b | 5022 | @findex strncat |
ed09096d | 5023 | @findex strncmp |
5024 | @findex strncpy | |
1f4e0dac | 5025 | @findex strpbrk |
5026 | @findex strrchr | |
49f0327b | 5027 | @findex strspn |
1f4e0dac | 5028 | @findex strstr |
a2246f84 | 5029 | @findex tan |
5030 | @findex tanf | |
e88e2794 | 5031 | @findex tanh |
5032 | @findex tanhf | |
5033 | @findex tanhl | |
a2246f84 | 5034 | @findex tanl |
847749e5 | 5035 | @findex tgamma |
5036 | @findex tgammaf | |
5037 | @findex tgammal | |
805e22b2 | 5038 | @findex trunc |
5039 | @findex truncf | |
5040 | @findex truncl | |
b9b15671 | 5041 | @findex vfprintf |
5042 | @findex vfscanf | |
03901330 | 5043 | @findex vprintf |
5044 | @findex vscanf | |
5045 | @findex vsnprintf | |
5046 | @findex vsprintf | |
5047 | @findex vsscanf | |
847749e5 | 5048 | @findex y0 |
5049 | @findex y0f | |
5050 | @findex y0l | |
5051 | @findex y1 | |
5052 | @findex y1f | |
5053 | @findex y1l | |
5054 | @findex yn | |
5055 | @findex ynf | |
5056 | @findex ynl | |
2c776a54 | 5057 | |
37744367 | 5058 | GCC provides a large number of built-in functions other than the ones |
2c776a54 | 5059 | mentioned above. Some of these are for internal use in the processing |
5060 | of exceptions or variable-length argument lists and will not be | |
5061 | documented here because they may change from time to time; we do not | |
5062 | recommend general use of these functions. | |
5063 | ||
5064 | The remaining functions are provided for optimization purposes. | |
5065 | ||
67791935 | 5066 | @opindex fno-builtin |
0fff59be | 5067 | GCC includes built-in versions of many of the functions in the standard |
5068 | C library. The versions prefixed with @code{__builtin_} will always be | |
5069 | treated as having the same meaning as the C library function even if you | |
5070 | specify the @option{-fno-builtin} option. (@pxref{C Dialect Options}) | |
5071 | Many of these functions are only optimized in certain cases; if they are | |
1f4e0dac | 5072 | not optimized in a particular case, a call to the library function will |
5073 | be emitted. | |
5074 | ||
67791935 | 5075 | @opindex ansi |
5076 | @opindex std | |
982c684c | 5077 | Outside strict ISO C mode (@option{-ansi}, @option{-std=c89} or |
e88e2794 | 5078 | @option{-std=c99}), the functions |
5079 | @code{_exit}, @code{alloca}, @code{bcmp}, @code{bzero}, | |
5080 | @code{dcgettext}, @code{dgettext}, @code{dremf}, @code{dreml}, | |
5081 | @code{drem}, @code{exp10f}, @code{exp10l}, @code{exp10}, @code{ffsll}, | |
5082 | @code{ffsl}, @code{ffs}, @code{fprintf_unlocked}, @code{fputs_unlocked}, | |
847749e5 | 5083 | @code{gammaf}, @code{gammal}, @code{gamma}, @code{gettext}, |
5084 | @code{index}, @code{j0f}, @code{j0l}, @code{j0}, @code{j1f}, @code{j1l}, | |
5085 | @code{j1}, @code{jnf}, @code{jnl}, @code{jn}, @code{mempcpy}, | |
5086 | @code{pow10f}, @code{pow10l}, @code{pow10}, @code{printf_unlocked}, | |
5087 | @code{rindex}, @code{scalbf}, @code{scalbl}, @code{scalb}, | |
5088 | @code{significandf}, @code{significandl}, @code{significand}, | |
4070bd43 | 5089 | @code{sincosf}, @code{sincosl}, @code{sincos}, @code{stpcpy}, |
5090 | @code{strdup}, @code{strfmon}, @code{y0f}, @code{y0l}, @code{y0}, | |
5091 | @code{y1f}, @code{y1l}, @code{y1}, @code{ynf}, @code{ynl} and @code{yn} | |
32ef1cd2 | 5092 | may be handled as built-in functions. |
982c684c | 5093 | All these functions have corresponding versions |
0fff59be | 5094 | prefixed with @code{__builtin_}, which may be used even in strict C89 |
5095 | mode. | |
1f4e0dac | 5096 | |
78a74442 | 5097 | The ISO C99 functions |
e88e2794 | 5098 | @code{_Exit}, @code{acoshf}, @code{acoshl}, @code{acosh}, @code{asinhf}, |
5099 | @code{asinhl}, @code{asinh}, @code{atanhf}, @code{atanhl}, @code{atanh}, | |
61b922e7 | 5100 | @code{cabsf}, @code{cabsl}, @code{cabs}, @code{cacosf}, @code{cacoshf}, |
5101 | @code{cacoshl}, @code{cacosh}, @code{cacosl}, @code{cacos}, | |
5102 | @code{cargf}, @code{cargl}, @code{carg}, @code{casinf}, @code{casinhf}, | |
5103 | @code{casinhl}, @code{casinh}, @code{casinl}, @code{casin}, | |
5104 | @code{catanf}, @code{catanhf}, @code{catanhl}, @code{catanh}, | |
5105 | @code{catanl}, @code{catan}, @code{cbrtf}, @code{cbrtl}, @code{cbrt}, | |
5106 | @code{ccosf}, @code{ccoshf}, @code{ccoshl}, @code{ccosh}, @code{ccosl}, | |
5107 | @code{ccos}, @code{cexpf}, @code{cexpl}, @code{cexp}, @code{cimagf}, | |
5108 | @code{cimagl}, @code{cimag}, | |
5109 | @code{conjf}, @code{conjl}, @code{conj}, @code{copysignf}, | |
5110 | @code{copysignl}, @code{copysign}, @code{cpowf}, @code{cpowl}, | |
5111 | @code{cpow}, @code{cprojf}, @code{cprojl}, @code{cproj}, @code{crealf}, | |
5112 | @code{creall}, @code{creal}, @code{csinf}, @code{csinhf}, @code{csinhl}, | |
5113 | @code{csinh}, @code{csinl}, @code{csin}, @code{csqrtf}, @code{csqrtl}, | |
5114 | @code{csqrt}, @code{ctanf}, @code{ctanhf}, @code{ctanhl}, @code{ctanh}, | |
5115 | @code{ctanl}, @code{ctan}, @code{erfcf}, @code{erfcl}, @code{erfc}, | |
5116 | @code{erff}, @code{erfl}, @code{erf}, @code{exp2f}, @code{exp2l}, | |
5117 | @code{exp2}, @code{expm1f}, @code{expm1l}, @code{expm1}, @code{fdimf}, | |
5118 | @code{fdiml}, @code{fdim}, @code{fmaf}, @code{fmal}, @code{fmaxf}, | |
5119 | @code{fmaxl}, @code{fmax}, @code{fma}, @code{fminf}, @code{fminl}, | |
5120 | @code{fmin}, @code{hypotf}, @code{hypotl}, @code{hypot}, @code{ilogbf}, | |
5121 | @code{ilogbl}, @code{ilogb}, @code{imaxabs}, @code{lgammaf}, | |
5122 | @code{lgammal}, @code{lgamma}, @code{llabs}, @code{llrintf}, | |
5123 | @code{llrintl}, @code{llrint}, @code{llroundf}, @code{llroundl}, | |
5124 | @code{llround}, @code{log1pf}, @code{log1pl}, @code{log1p}, | |
5125 | @code{log2f}, @code{log2l}, @code{log2}, @code{logbf}, @code{logbl}, | |
5126 | @code{logb}, @code{lrintf}, @code{lrintl}, @code{lrint}, @code{lroundf}, | |
5127 | @code{lroundl}, @code{lround}, @code{nearbyintf}, @code{nearbyintl}, | |
5128 | @code{nearbyint}, @code{nextafterf}, @code{nextafterl}, | |
5129 | @code{nextafter}, @code{nexttowardf}, @code{nexttowardl}, | |
5130 | @code{nexttoward}, @code{remainderf}, @code{remainderl}, | |
5131 | @code{remainder}, @code{remquof}, @code{remquol}, @code{remquo}, | |
5132 | @code{rintf}, @code{rintl}, @code{rint}, @code{roundf}, @code{roundl}, | |
5133 | @code{round}, @code{scalblnf}, @code{scalblnl}, @code{scalbln}, | |
5134 | @code{scalbnf}, @code{scalbnl}, @code{scalbn}, @code{snprintf}, | |
5135 | @code{tgammaf}, @code{tgammal}, @code{tgamma}, @code{truncf}, | |
5136 | @code{truncl}, @code{trunc}, @code{vfscanf}, @code{vscanf}, | |
5137 | @code{vsnprintf} and @code{vsscanf} | |
03901330 | 5138 | are handled as built-in functions |
982c684c | 5139 | except in strict ISO C90 mode (@option{-ansi} or @option{-std=c89}). |
fa426235 | 5140 | |
e88e2794 | 5141 | There are also built-in versions of the ISO C99 functions |
5142 | @code{acosf}, @code{acosl}, @code{asinf}, @code{asinl}, @code{atan2f}, | |
a2246f84 | 5143 | @code{atan2l}, @code{atanf}, @code{atanl}, @code{ceilf}, @code{ceill}, |
e88e2794 | 5144 | @code{cosf}, @code{coshf}, @code{coshl}, @code{cosl}, @code{expf}, |
5145 | @code{expl}, @code{fabsf}, @code{fabsl}, @code{floorf}, @code{floorl}, | |
4070bd43 | 5146 | @code{fmodf}, @code{fmodl}, @code{frexpf}, @code{frexpl}, @code{ldexpf}, |
5147 | @code{ldexpl}, @code{log10f}, @code{log10l}, @code{logf}, @code{logl}, | |
5148 | @code{modfl}, @code{modf}, @code{powf}, @code{powl}, @code{sinf}, | |
5149 | @code{sinhf}, @code{sinhl}, @code{sinl}, @code{sqrtf}, @code{sqrtl}, | |
5150 | @code{tanf}, @code{tanhf}, @code{tanhl} and @code{tanl} | |
fa426235 | 5151 | that are recognized in any mode since ISO C90 reserves these names for |
5152 | the purpose to which ISO C99 puts them. All these functions have | |
5153 | corresponding versions prefixed with @code{__builtin_}. | |
5154 | ||
e88e2794 | 5155 | The ISO C90 functions |
5156 | @code{abort}, @code{abs}, @code{acos}, @code{asin}, @code{atan2}, | |
5157 | @code{atan}, @code{calloc}, @code{ceil}, @code{cosh}, @code{cos}, | |
5158 | @code{exit}, @code{exp}, @code{fabs}, @code{floor}, @code{fmod}, | |
4070bd43 | 5159 | @code{fprintf}, @code{fputs}, @code{frexp}, @code{fscanf}, @code{labs}, |
5160 | @code{ldexp}, @code{log10}, @code{log}, @code{malloc}, @code{memcmp}, | |
5161 | @code{memcpy}, @code{memset}, @code{modf}, @code{pow}, @code{printf}, | |
5162 | @code{putchar}, @code{puts}, @code{scanf}, @code{sinh}, @code{sin}, | |
5163 | @code{snprintf}, @code{sprintf}, @code{sqrt}, @code{sscanf}, | |
5164 | @code{strcat}, @code{strchr}, @code{strcmp}, @code{strcpy}, | |
5165 | @code{strcspn}, @code{strlen}, @code{strncat}, @code{strncmp}, | |
5166 | @code{strncpy}, @code{strpbrk}, @code{strrchr}, @code{strspn}, | |
5167 | @code{strstr}, @code{tanh}, @code{tan}, @code{vfprintf}, @code{vprintf} | |
5168 | and @code{vsprintf} | |
03901330 | 5169 | are all recognized as built-in functions unless |
fa426235 | 5170 | @option{-fno-builtin} is specified (or @option{-fno-builtin-@var{function}} |
5171 | is specified for an individual function). All of these functions have | |
805e22b2 | 5172 | corresponding versions prefixed with @code{__builtin_}. |
0fff59be | 5173 | |
5174 | GCC provides built-in versions of the ISO C99 floating point comparison | |
5175 | macros that avoid raising exceptions for unordered operands. They have | |
5176 | the same names as the standard macros ( @code{isgreater}, | |
5177 | @code{isgreaterequal}, @code{isless}, @code{islessequal}, | |
5178 | @code{islessgreater}, and @code{isunordered}) , with @code{__builtin_} | |
5179 | prefixed. We intend for a library implementor to be able to simply | |
5180 | @code{#define} each standard macro to its built-in equivalent. | |
2c776a54 | 5181 | |
acb6974b | 5182 | @deftypefn {Built-in Function} int __builtin_types_compatible_p (@var{type1}, @var{type2}) |
5183 | ||
5184 | You can use the built-in function @code{__builtin_types_compatible_p} to | |
5185 | determine whether two types are the same. | |
5186 | ||
5187 | This built-in function returns 1 if the unqualified versions of the | |
5188 | types @var{type1} and @var{type2} (which are types, not expressions) are | |
5189 | compatible, 0 otherwise. The result of this built-in function can be | |
5190 | used in integer constant expressions. | |
5191 | ||
5192 | This built-in function ignores top level qualifiers (e.g., @code{const}, | |
5193 | @code{volatile}). For example, @code{int} is equivalent to @code{const | |
5194 | int}. | |
5195 | ||
5196 | The type @code{int[]} and @code{int[5]} are compatible. On the other | |
5197 | hand, @code{int} and @code{char *} are not compatible, even if the size | |
5198 | of their types, on the particular architecture are the same. Also, the | |
5199 | amount of pointer indirection is taken into account when determining | |
5200 | similarity. Consequently, @code{short *} is not similar to | |
5201 | @code{short **}. Furthermore, two types that are typedefed are | |
5202 | considered compatible if their underlying types are compatible. | |
5203 | ||
5204 | An @code{enum} type is considered to be compatible with another | |
5205 | @code{enum} type. For example, @code{enum @{foo, bar@}} is similar to | |
5206 | @code{enum @{hot, dog@}}. | |
5207 | ||
5208 | You would typically use this function in code whose execution varies | |
5209 | depending on the arguments' types. For example: | |
5210 | ||
5211 | @smallexample | |
8e1103d3 | 5212 | #define foo(x) \ |
5213 | (@{ \ | |
5214 | typeof (x) tmp; \ | |
5215 | if (__builtin_types_compatible_p (typeof (x), long double)) \ | |
5216 | tmp = foo_long_double (tmp); \ | |
5217 | else if (__builtin_types_compatible_p (typeof (x), double)) \ | |
5218 | tmp = foo_double (tmp); \ | |
5219 | else if (__builtin_types_compatible_p (typeof (x), float)) \ | |
5220 | tmp = foo_float (tmp); \ | |
5221 | else \ | |
5222 | abort (); \ | |
5223 | tmp; \ | |
acb6974b | 5224 | @}) |
5225 | @end smallexample | |
5226 | ||
5227 | @emph{Note:} This construct is only available for C. | |
5228 | ||
5229 | @end deftypefn | |
5230 | ||
5231 | @deftypefn {Built-in Function} @var{type} __builtin_choose_expr (@var{const_exp}, @var{exp1}, @var{exp2}) | |
5232 | ||
5233 | You can use the built-in function @code{__builtin_choose_expr} to | |
5234 | evaluate code depending on the value of a constant expression. This | |
5235 | built-in function returns @var{exp1} if @var{const_exp}, which is a | |
5236 | constant expression that must be able to be determined at compile time, | |
5237 | is nonzero. Otherwise it returns 0. | |
5238 | ||
5239 | This built-in function is analogous to the @samp{? :} operator in C, | |
5240 | except that the expression returned has its type unaltered by promotion | |
5241 | rules. Also, the built-in function does not evaluate the expression | |
5242 | that was not chosen. For example, if @var{const_exp} evaluates to true, | |
5243 | @var{exp2} is not evaluated even if it has side-effects. | |
5244 | ||
5245 | This built-in function can return an lvalue if the chosen argument is an | |
5246 | lvalue. | |
5247 | ||
5248 | If @var{exp1} is returned, the return type is the same as @var{exp1}'s | |
5249 | type. Similarly, if @var{exp2} is returned, its return type is the same | |
5250 | as @var{exp2}. | |
5251 | ||
5252 | Example: | |
5253 | ||
5254 | @smallexample | |
b724fad7 | 5255 | #define foo(x) \ |
5256 | __builtin_choose_expr ( \ | |
5257 | __builtin_types_compatible_p (typeof (x), double), \ | |
5258 | foo_double (x), \ | |
5259 | __builtin_choose_expr ( \ | |
5260 | __builtin_types_compatible_p (typeof (x), float), \ | |
5261 | foo_float (x), \ | |
5262 | /* @r{The void expression results in a compile-time error} \ | |
5263 | @r{when assigning the result to something.} */ \ | |
acb6974b | 5264 | (void)0)) |
5265 | @end smallexample | |
5266 | ||
5267 | @emph{Note:} This construct is only available for C. Furthermore, the | |
5268 | unused expression (@var{exp1} or @var{exp2} depending on the value of | |
5269 | @var{const_exp}) may still generate syntax errors. This may change in | |
5270 | future revisions. | |
5271 | ||
5272 | @end deftypefn | |
5273 | ||
67791935 | 5274 | @deftypefn {Built-in Function} int __builtin_constant_p (@var{exp}) |
5275 | You can use the built-in function @code{__builtin_constant_p} to | |
2c776a54 | 5276 | determine if a value is known to be constant at compile-time and hence |
37744367 | 5277 | that GCC can perform constant-folding on expressions involving that |
2c776a54 | 5278 | value. The argument of the function is the value to test. The function |
5279 | returns the integer 1 if the argument is known to be a compile-time | |
5280 | constant and 0 if it is not known to be a compile-time constant. A | |
5281 | return of 0 does not indicate that the value is @emph{not} a constant, | |
37744367 | 5282 | but merely that GCC cannot prove it is a constant with the specified |
67791935 | 5283 | value of the @option{-O} option. |
2c776a54 | 5284 | |
5285 | You would typically use this function in an embedded application where | |
5286 | memory was a critical resource. If you have some complex calculation, | |
5287 | you may want it to be folded if it involves constants, but need to call | |
5288 | a function if it does not. For example: | |
5289 | ||
6e894357 | 5290 | @smallexample |
d90db7dc | 5291 | #define Scale_Value(X) \ |
5292 | (__builtin_constant_p (X) \ | |
5293 | ? ((X) * SCALE + OFFSET) : Scale (X)) | |
2c776a54 | 5294 | @end smallexample |
5295 | ||
67791935 | 5296 | You may use this built-in function in either a macro or an inline |
2c776a54 | 5297 | function. However, if you use it in an inlined function and pass an |
37744367 | 5298 | argument of the function as the argument to the built-in, GCC will |
2c776a54 | 5299 | never return 1 when you call the inline function with a string constant |
3cfa0cc4 | 5300 | or compound literal (@pxref{Compound Literals}) and will not return 1 |
2c776a54 | 5301 | when you pass a constant numeric value to the inline function unless you |
67791935 | 5302 | specify the @option{-O} option. |
f97c71a1 | 5303 | |
5304 | You may also use @code{__builtin_constant_p} in initializers for static | |
5305 | data. For instance, you can write | |
5306 | ||
5307 | @smallexample | |
c371393a | 5308 | static const int table[] = @{ |
f97c71a1 | 5309 | __builtin_constant_p (EXPRESSION) ? (EXPRESSION) : -1, |
4ae74ddd | 5310 | /* @r{@dots{}} */ |
c371393a | 5311 | @}; |
f97c71a1 | 5312 | @end smallexample |
5313 | ||
5314 | @noindent | |
5315 | This is an acceptable initializer even if @var{EXPRESSION} is not a | |
5316 | constant expression. GCC must be more conservative about evaluating the | |
5317 | built-in in this case, because it has no opportunity to perform | |
5318 | optimization. | |
5319 | ||
5320 | Previous versions of GCC did not accept this built-in in data | |
5321 | initializers. The earliest version where it is completely safe is | |
5322 | 3.0.1. | |
67791935 | 5323 | @end deftypefn |
2c776a54 | 5324 | |
67791935 | 5325 | @deftypefn {Built-in Function} long __builtin_expect (long @var{exp}, long @var{c}) |
5326 | @opindex fprofile-arcs | |
3b0848a2 | 5327 | You may use @code{__builtin_expect} to provide the compiler with |
89cfe6e5 | 5328 | branch prediction information. In general, you should prefer to |
67791935 | 5329 | use actual profile feedback for this (@option{-fprofile-arcs}), as |
89cfe6e5 | 5330 | programmers are notoriously bad at predicting how their programs |
def8652b | 5331 | actually perform. However, there are applications in which this |
89cfe6e5 | 5332 | data is hard to collect. |
5333 | ||
5334 | The return value is the value of @var{exp}, which should be an | |
5335 | integral expression. The value of @var{c} must be a compile-time | |
67791935 | 5336 | constant. The semantics of the built-in are that it is expected |
89cfe6e5 | 5337 | that @var{exp} == @var{c}. For example: |
5338 | ||
5339 | @smallexample | |
5340 | if (__builtin_expect (x, 0)) | |
5341 | foo (); | |
5342 | @end smallexample | |
5343 | ||
5344 | @noindent | |
5345 | would indicate that we do not expect to call @code{foo}, since | |
5346 | we expect @code{x} to be zero. Since you are limited to integral | |
5347 | expressions for @var{exp}, you should use constructions such as | |
5348 | ||
5349 | @smallexample | |
5350 | if (__builtin_expect (ptr != NULL, 1)) | |
5351 | error (); | |
5352 | @end smallexample | |
5353 | ||
5354 | @noindent | |
5355 | when testing pointer or floating-point values. | |
67791935 | 5356 | @end deftypefn |
89cfe6e5 | 5357 | |
82086392 | 5358 | @deftypefn {Built-in Function} void __builtin_prefetch (const void *@var{addr}, ...) |
5e3608d8 | 5359 | This function is used to minimize cache-miss latency by moving data into |
5360 | a cache before it is accessed. | |
5361 | You can insert calls to @code{__builtin_prefetch} into code for which | |
5362 | you know addresses of data in memory that is likely to be accessed soon. | |
5363 | If the target supports them, data prefetch instructions will be generated. | |
5364 | If the prefetch is done early enough before the access then the data will | |
5365 | be in the cache by the time it is accessed. | |
5366 | ||
5367 | The value of @var{addr} is the address of the memory to prefetch. | |
26a5cadb | 5368 | There are two optional arguments, @var{rw} and @var{locality}. |
5e3608d8 | 5369 | The value of @var{rw} is a compile-time constant one or zero; one |
26a5cadb | 5370 | means that the prefetch is preparing for a write to the memory address |
5371 | and zero, the default, means that the prefetch is preparing for a read. | |
5e3608d8 | 5372 | The value @var{locality} must be a compile-time constant integer between |
5373 | zero and three. A value of zero means that the data has no temporal | |
5374 | locality, so it need not be left in the cache after the access. A value | |
5375 | of three means that the data has a high degree of temporal locality and | |
5376 | should be left in all levels of cache possible. Values of one and two | |
26a5cadb | 5377 | mean, respectively, a low or moderate degree of temporal locality. The |
5378 | default is three. | |
5e3608d8 | 5379 | |
5380 | @smallexample | |
5381 | for (i = 0; i < n; i++) | |
5382 | @{ | |
5383 | a[i] = a[i] + b[i]; | |
5384 | __builtin_prefetch (&a[i+j], 1, 1); | |
5385 | __builtin_prefetch (&b[i+j], 0, 1); | |
4ae74ddd | 5386 | /* @r{@dots{}} */ |
5e3608d8 | 5387 | @} |
5388 | @end smallexample | |
5389 | ||
228c5b30 | 5390 | Data prefetch does not generate faults if @var{addr} is invalid, but |
5e3608d8 | 5391 | the address expression itself must be valid. For example, a prefetch |
5392 | of @code{p->next} will not fault if @code{p->next} is not a valid | |
5393 | address, but evaluation will fault if @code{p} is not a valid address. | |
5394 | ||
5395 | If the target does not support data prefetch, the address expression | |
5396 | is evaluated if it includes side effects but no other code is generated | |
5397 | and GCC does not issue a warning. | |
5398 | @end deftypefn | |
5399 | ||
92c43e3c | 5400 | @deftypefn {Built-in Function} double __builtin_huge_val (void) |
5401 | Returns a positive infinity, if supported by the floating-point format, | |
5402 | else @code{DBL_MAX}. This function is suitable for implementing the | |
5403 | ISO C macro @code{HUGE_VAL}. | |
5404 | @end deftypefn | |
5405 | ||
5406 | @deftypefn {Built-in Function} float __builtin_huge_valf (void) | |
5407 | Similar to @code{__builtin_huge_val}, except the return type is @code{float}. | |
5408 | @end deftypefn | |
5409 | ||
a5285cd3 | 5410 | @deftypefn {Built-in Function} {long double} __builtin_huge_vall (void) |
92c43e3c | 5411 | Similar to @code{__builtin_huge_val}, except the return |
5412 | type is @code{long double}. | |
5413 | @end deftypefn | |
5414 | ||
5415 | @deftypefn {Built-in Function} double __builtin_inf (void) | |
5416 | Similar to @code{__builtin_huge_val}, except a warning is generated | |
5417 | if the target floating-point format does not support infinities. | |
5418 | This function is suitable for implementing the ISO C99 macro @code{INFINITY}. | |
5419 | @end deftypefn | |
5420 | ||
5421 | @deftypefn {Built-in Function} float __builtin_inff (void) | |
5422 | Similar to @code{__builtin_inf}, except the return type is @code{float}. | |
5423 | @end deftypefn | |
5424 | ||
a5285cd3 | 5425 | @deftypefn {Built-in Function} {long double} __builtin_infl (void) |
92c43e3c | 5426 | Similar to @code{__builtin_inf}, except the return |
5427 | type is @code{long double}. | |
5428 | @end deftypefn | |
5429 | ||
b0db7939 | 5430 | @deftypefn {Built-in Function} double __builtin_nan (const char *str) |
5431 | This is an implementation of the ISO C99 function @code{nan}. | |
5432 | ||
5433 | Since ISO C99 defines this function in terms of @code{strtod}, which we | |
a99e98db | 5434 | do not implement, a description of the parsing is in order. The string |
b0db7939 | 5435 | is parsed as by @code{strtol}; that is, the base is recognized by |
5436 | leading @samp{0} or @samp{0x} prefixes. The number parsed is placed | |
5437 | in the significand such that the least significant bit of the number | |
5438 | is at the least significant bit of the significand. The number is | |
5439 | truncated to fit the significand field provided. The significand is | |
5440 | forced to be a quiet NaN. | |
5441 | ||
5442 | This function, if given a string literal, is evaluated early enough | |
5443 | that it is considered a compile-time constant. | |
5444 | @end deftypefn | |
5445 | ||
5446 | @deftypefn {Built-in Function} float __builtin_nanf (const char *str) | |
5447 | Similar to @code{__builtin_nan}, except the return type is @code{float}. | |
5448 | @end deftypefn | |
5449 | ||
a5285cd3 | 5450 | @deftypefn {Built-in Function} {long double} __builtin_nanl (const char *str) |
b0db7939 | 5451 | Similar to @code{__builtin_nan}, except the return type is @code{long double}. |
5452 | @end deftypefn | |
5453 | ||
5454 | @deftypefn {Built-in Function} double __builtin_nans (const char *str) | |
5455 | Similar to @code{__builtin_nan}, except the significand is forced | |
5456 | to be a signaling NaN. The @code{nans} function is proposed by | |
9f83c26a | 5457 | @uref{http://std.dkuug.dk/JTC1/SC22/WG14/www/docs/n965.htm,,WG14 N965}. |
b0db7939 | 5458 | @end deftypefn |
5459 | ||
5460 | @deftypefn {Built-in Function} float __builtin_nansf (const char *str) | |
5461 | Similar to @code{__builtin_nans}, except the return type is @code{float}. | |
5462 | @end deftypefn | |
5463 | ||
a5285cd3 | 5464 | @deftypefn {Built-in Function} {long double} __builtin_nansl (const char *str) |
b0db7939 | 5465 | Similar to @code{__builtin_nans}, except the return type is @code{long double}. |
5466 | @end deftypefn | |
5467 | ||
6a08d0ab | 5468 | @deftypefn {Built-in Function} int __builtin_ffs (unsigned int x) |
5469 | Returns one plus the index of the least significant 1-bit of @var{x}, or | |
5470 | if @var{x} is zero, returns zero. | |
5471 | @end deftypefn | |
5472 | ||
5473 | @deftypefn {Built-in Function} int __builtin_clz (unsigned int x) | |
5474 | Returns the number of leading 0-bits in @var{x}, starting at the most | |
5475 | significant bit position. If @var{x} is 0, the result is undefined. | |
5476 | @end deftypefn | |
5477 | ||
5478 | @deftypefn {Built-in Function} int __builtin_ctz (unsigned int x) | |
5479 | Returns the number of trailing 0-bits in @var{x}, starting at the least | |
5480 | significant bit position. If @var{x} is 0, the result is undefined. | |
5481 | @end deftypefn | |
5482 | ||
5483 | @deftypefn {Built-in Function} int __builtin_popcount (unsigned int x) | |
5484 | Returns the number of 1-bits in @var{x}. | |
5485 | @end deftypefn | |
5486 | ||
5487 | @deftypefn {Built-in Function} int __builtin_parity (unsigned int x) | |
5488 | Returns the parity of @var{x}, i.@:e. the number of 1-bits in @var{x} | |
5489 | modulo 2. | |
5490 | @end deftypefn | |
5491 | ||
5492 | @deftypefn {Built-in Function} int __builtin_ffsl (unsigned long) | |
5493 | Similar to @code{__builtin_ffs}, except the argument type is | |
5494 | @code{unsigned long}. | |
5495 | @end deftypefn | |
5496 | ||
5497 | @deftypefn {Built-in Function} int __builtin_clzl (unsigned long) | |
5498 | Similar to @code{__builtin_clz}, except the argument type is | |
5499 | @code{unsigned long}. | |
5500 | @end deftypefn | |
5501 | ||
5502 | @deftypefn {Built-in Function} int __builtin_ctzl (unsigned long) | |
5503 | Similar to @code{__builtin_ctz}, except the argument type is | |
5504 | @code{unsigned long}. | |
5505 | @end deftypefn | |
5506 | ||
5507 | @deftypefn {Built-in Function} int __builtin_popcountl (unsigned long) | |
5508 | Similar to @code{__builtin_popcount}, except the argument type is | |
5509 | @code{unsigned long}. | |
5510 | @end deftypefn | |
5511 | ||
5512 | @deftypefn {Built-in Function} int __builtin_parityl (unsigned long) | |
5513 | Similar to @code{__builtin_parity}, except the argument type is | |
5514 | @code{unsigned long}. | |
5515 | @end deftypefn | |
5516 | ||
5517 | @deftypefn {Built-in Function} int __builtin_ffsll (unsigned long long) | |
5518 | Similar to @code{__builtin_ffs}, except the argument type is | |
5519 | @code{unsigned long long}. | |
5520 | @end deftypefn | |
5521 | ||
5522 | @deftypefn {Built-in Function} int __builtin_clzll (unsigned long long) | |
5523 | Similar to @code{__builtin_clz}, except the argument type is | |
5524 | @code{unsigned long long}. | |
5525 | @end deftypefn | |
5526 | ||
5527 | @deftypefn {Built-in Function} int __builtin_ctzll (unsigned long long) | |
5528 | Similar to @code{__builtin_ctz}, except the argument type is | |
5529 | @code{unsigned long long}. | |
5530 | @end deftypefn | |
5531 | ||
5532 | @deftypefn {Built-in Function} int __builtin_popcountll (unsigned long long) | |
5533 | Similar to @code{__builtin_popcount}, except the argument type is | |
5534 | @code{unsigned long long}. | |
5535 | @end deftypefn | |
5536 | ||
5537 | @deftypefn {Built-in Function} int __builtin_parityll (unsigned long long) | |
5538 | Similar to @code{__builtin_parity}, except the argument type is | |
5539 | @code{unsigned long long}. | |
5540 | @end deftypefn | |
5541 | ||
5542 | ||
ca5827cf | 5543 | @node Target Builtins |
5544 | @section Built-in Functions Specific to Particular Target Machines | |
5545 | ||
5546 | On some target machines, GCC supports many built-in functions specific | |
5547 | to those machines. Generally these generate calls to specific machine | |
5548 | instructions, but allow the compiler to schedule those calls. | |
5549 | ||
5550 | @menu | |
f2cc13dc | 5551 | * Alpha Built-in Functions:: |
af72d7d6 | 5552 | * ARM Built-in Functions:: |
ca5827cf | 5553 | * X86 Built-in Functions:: |
0ae4308e | 5554 | * PowerPC AltiVec Built-in Functions:: |
ca5827cf | 5555 | @end menu |
5556 | ||
f2cc13dc | 5557 | @node Alpha Built-in Functions |
5558 | @subsection Alpha Built-in Functions | |
5559 | ||
5560 | These built-in functions are available for the Alpha family of | |
5561 | processors, depending on the command-line switches used. | |
5562 | ||
85456819 | 5563 | The following built-in functions are always available. They |
f2cc13dc | 5564 | all generate the machine instruction that is part of the name. |
5565 | ||
5566 | @example | |
5567 | long __builtin_alpha_implver (void) | |
5568 | long __builtin_alpha_rpcc (void) | |
5569 | long __builtin_alpha_amask (long) | |
5570 | long __builtin_alpha_cmpbge (long, long) | |
ae4cd3a5 | 5571 | long __builtin_alpha_extbl (long, long) |
5572 | long __builtin_alpha_extwl (long, long) | |
5573 | long __builtin_alpha_extll (long, long) | |
f2cc13dc | 5574 | long __builtin_alpha_extql (long, long) |
ae4cd3a5 | 5575 | long __builtin_alpha_extwh (long, long) |
5576 | long __builtin_alpha_extlh (long, long) | |
f2cc13dc | 5577 | long __builtin_alpha_extqh (long, long) |
ae4cd3a5 | 5578 | long __builtin_alpha_insbl (long, long) |
5579 | long __builtin_alpha_inswl (long, long) | |
5580 | long __builtin_alpha_insll (long, long) | |
5581 | long __builtin_alpha_insql (long, long) | |
5582 | long __builtin_alpha_inswh (long, long) | |
5583 | long __builtin_alpha_inslh (long, long) | |
5584 | long __builtin_alpha_insqh (long, long) | |
5585 | long __builtin_alpha_mskbl (long, long) | |
5586 | long __builtin_alpha_mskwl (long, long) | |
5587 | long __builtin_alpha_mskll (long, long) | |
5588 | long __builtin_alpha_mskql (long, long) | |
5589 | long __builtin_alpha_mskwh (long, long) | |
5590 | long __builtin_alpha_msklh (long, long) | |
5591 | long __builtin_alpha_mskqh (long, long) | |
5592 | long __builtin_alpha_umulh (long, long) | |
f2cc13dc | 5593 | long __builtin_alpha_zap (long, long) |
5594 | long __builtin_alpha_zapnot (long, long) | |
5595 | @end example | |
5596 | ||
5597 | The following built-in functions are always with @option{-mmax} | |
5598 | or @option{-mcpu=@var{cpu}} where @var{cpu} is @code{pca56} or | |
5599 | later. They all generate the machine instruction that is part | |
5600 | of the name. | |
5601 | ||
5602 | @example | |
5603 | long __builtin_alpha_pklb (long) | |
5604 | long __builtin_alpha_pkwb (long) | |
5605 | long __builtin_alpha_unpkbl (long) | |
5606 | long __builtin_alpha_unpkbw (long) | |
5607 | long __builtin_alpha_minub8 (long, long) | |
5608 | long __builtin_alpha_minsb8 (long, long) | |
5609 | long __builtin_alpha_minuw4 (long, long) | |
5610 | long __builtin_alpha_minsw4 (long, long) | |
5611 | long __builtin_alpha_maxub8 (long, long) | |
5612 | long __builtin_alpha_maxsb8 (long, long) | |
5613 | long __builtin_alpha_maxuw4 (long, long) | |
5614 | long __builtin_alpha_maxsw4 (long, long) | |
5615 | long __builtin_alpha_perr (long, long) | |
5616 | @end example | |
5617 | ||
ae4cd3a5 | 5618 | The following built-in functions are always with @option{-mcix} |
5619 | or @option{-mcpu=@var{cpu}} where @var{cpu} is @code{ev67} or | |
5620 | later. They all generate the machine instruction that is part | |
5621 | of the name. | |
5622 | ||
5623 | @example | |
5624 | long __builtin_alpha_cttz (long) | |
5625 | long __builtin_alpha_ctlz (long) | |
5626 | long __builtin_alpha_ctpop (long) | |
5627 | @end example | |
5628 | ||
938e069b | 5629 | The following builtins are available on systems that use the OSF/1 |
5630 | PALcode. Normally they invoke the @code{rduniq} and @code{wruniq} | |
5631 | PAL calls, but when invoked with @option{-mtls-kernel}, they invoke | |
5632 | @code{rdval} and @code{wrval}. | |
5633 | ||
5634 | @example | |
5635 | void *__builtin_thread_pointer (void) | |
5636 | void __builtin_set_thread_pointer (void *) | |
5637 | @end example | |
5638 | ||
af72d7d6 | 5639 | @node ARM Built-in Functions |
5640 | @subsection ARM Built-in Functions | |
5641 | ||
5642 | These built-in functions are available for the ARM family of | |
5643 | processors, when the @option{-mcpu=iwmmxt} switch is used: | |
5644 | ||
5645 | @example | |
5646 | typedef int __v2si __attribute__ ((__mode__ (__V2SI__))) | |
5647 | ||
5648 | v2si __builtin_arm_waddw (v2si, v2si) | |
5649 | v2si __builtin_arm_waddw (v2si, v2si) | |
5650 | v2si __builtin_arm_wsubw (v2si, v2si) | |
5651 | v2si __builtin_arm_wsubw (v2si, v2si) | |
5652 | v2si __builtin_arm_waddwss (v2si, v2si) | |
5653 | v2si __builtin_arm_wsubwss (v2si, v2si) | |
5654 | v2si __builtin_arm_wsubwss (v2si, v2si) | |
5655 | v2si __builtin_arm_wsubwss (v2si, v2si) | |
5656 | v2si __builtin_arm_wsubwss (v2si, v2si) | |
5657 | v2si __builtin_arm_waddwus (v2si, v2si) | |
5658 | v2si __builtin_arm_wsubwus (v2si, v2si) | |
5659 | v2si __builtin_arm_wsubwus (v2si, v2si) | |
5660 | v2si __builtin_arm_wmaxuw (v2si, v2si) | |
5661 | v2si __builtin_arm_wmaxsw (v2si, v2si) | |
5662 | v2si __builtin_arm_wavg2br (v2si, v2si) | |
5663 | v2si __builtin_arm_wavg2hr (v2si, v2si) | |
5664 | v2si __builtin_arm_wavg2b (v2si, v2si) | |
5665 | v2si __builtin_arm_wavg2h (v2si, v2si) | |
5666 | v2si __builtin_arm_waccb (v2si) | |
5667 | v2si __builtin_arm_wacch (v2si) | |
5668 | v2si __builtin_arm_waccw (v2si) | |
5669 | v2si __builtin_arm_wmacs (v2si, v2si, v2si) | |
5670 | v2si __builtin_arm_wmacsz (v2si, v2si, v2si) | |
5671 | v2si __builtin_arm_wmacu (v2si, v2si, v2si) | |
5672 | v2si __builtin_arm_wmacuz (v2si, v2si) | |
5673 | v2si __builtin_arm_wsadb (v2si, v2si) | |
5674 | v2si __builtin_arm_wsadbz (v2si, v2si) | |
5675 | v2si __builtin_arm_wsadh (v2si, v2si) | |
5676 | v2si __builtin_arm_wsadhz (v2si, v2si) | |
5677 | v2si __builtin_arm_walign (v2si, v2si) | |
5678 | v2si __builtin_arm_tmia (v2si, int, int) | |
5679 | v2si __builtin_arm_tmiaph (v2si, int, int) | |
5680 | v2si __builtin_arm_tmiabb (v2si, int, int) | |
5681 | v2si __builtin_arm_tmiabt (v2si, int, int) | |
5682 | v2si __builtin_arm_tmiatb (v2si, int, int) | |
5683 | v2si __builtin_arm_tmiatt (v2si, int, int) | |
5684 | int __builtin_arm_tmovmskb (v2si) | |
5685 | int __builtin_arm_tmovmskh (v2si) | |
5686 | int __builtin_arm_tmovmskw (v2si) | |
5687 | v2si __builtin_arm_wmadds (v2si, v2si) | |
5688 | v2si __builtin_arm_wmaddu (v2si, v2si) | |
5689 | v2si __builtin_arm_wpackhss (v2si, v2si) | |
5690 | v2si __builtin_arm_wpackwss (v2si, v2si) | |
5691 | v2si __builtin_arm_wpackdss (v2si, v2si) | |
5692 | v2si __builtin_arm_wpackhus (v2si, v2si) | |
5693 | v2si __builtin_arm_wpackwus (v2si, v2si) | |
5694 | v2si __builtin_arm_wpackdus (v2si, v2si) | |
5695 | v2si __builtin_arm_waddb (v2si, v2si) | |
5696 | v2si __builtin_arm_waddh (v2si, v2si) | |
5697 | v2si __builtin_arm_waddw (v2si, v2si) | |
5698 | v2si __builtin_arm_waddbss (v2si, v2si) | |
5699 | v2si __builtin_arm_waddhss (v2si, v2si) | |
5700 | v2si __builtin_arm_waddwss (v2si, v2si) | |
5701 | v2si __builtin_arm_waddbus (v2si, v2si) | |
5702 | v2si __builtin_arm_waddhus (v2si, v2si) | |
5703 | v2si __builtin_arm_waddwus (v2si, v2si) | |
5704 | v2si __builtin_arm_wsubb (v2si, v2si) | |
5705 | v2si __builtin_arm_wsubh (v2si, v2si) | |
5706 | v2si __builtin_arm_wsubw (v2si, v2si) | |
5707 | v2si __builtin_arm_wsubbss (v2si, v2si) | |
5708 | v2si __builtin_arm_wsubhss (v2si, v2si) | |
5709 | v2si __builtin_arm_wsubwss (v2si, v2si) | |
5710 | v2si __builtin_arm_wsubbus (v2si, v2si) | |
5711 | v2si __builtin_arm_wsubhus (v2si, v2si) | |
5712 | v2si __builtin_arm_wsubwus (v2si, v2si) | |
5713 | v2si __builtin_arm_wand (v2si, v2si) | |
5714 | v2si __builtin_arm_wandn (v2si, v2si) | |
5715 | v2si __builtin_arm_wor (v2si, v2si) | |
5716 | v2si __builtin_arm_wxor (v2si, v2si) | |
5717 | v2si __builtin_arm_wcmpeqb (v2si, v2si) | |
5718 | v2si __builtin_arm_wcmpeqh (v2si, v2si) | |
5719 | v2si __builtin_arm_wcmpeqw (v2si, v2si) | |
5720 | v2si __builtin_arm_wcmpgtub (v2si, v2si) | |
5721 | v2si __builtin_arm_wcmpgtuh (v2si, v2si) | |
5722 | v2si __builtin_arm_wcmpgtuw (v2si, v2si) | |
5723 | v2si __builtin_arm_wcmpgtsb (v2si, v2si) | |
5724 | v2si __builtin_arm_wcmpgtsh (v2si, v2si) | |
5725 | v2si __builtin_arm_wcmpgtsw (v2si, v2si) | |
5726 | int __builtin_arm_textrmsb (v2si, int) | |
5727 | int __builtin_arm_textrmsh (v2si, int) | |
5728 | int __builtin_arm_textrmsw (v2si, int) | |
5729 | int __builtin_arm_textrmub (v2si, int) | |
5730 | int __builtin_arm_textrmuh (v2si, int) | |
5731 | int __builtin_arm_textrmuw (v2si, int) | |
5732 | v2si __builtin_arm_tinsrb (v2si, int, int) | |
5733 | v2si __builtin_arm_tinsrh (v2si, int, int) | |
5734 | v2si __builtin_arm_tinsrw (v2si, int, int) | |
5735 | v2si __builtin_arm_wmaxsw (v2si, v2si) | |
5736 | v2si __builtin_arm_wmaxsh (v2si, v2si) | |
5737 | v2si __builtin_arm_wmaxsb (v2si, v2si) | |
5738 | v2si __builtin_arm_wmaxuw (v2si, v2si) | |
5739 | v2si __builtin_arm_wmaxuh (v2si, v2si) | |
5740 | v2si __builtin_arm_wmaxub (v2si, v2si) | |
5741 | v2si __builtin_arm_wminsw (v2si, v2si) | |
5742 | v2si __builtin_arm_wminsh (v2si, v2si) | |
5743 | v2si __builtin_arm_wminsb (v2si, v2si) | |
5744 | v2si __builtin_arm_wminuw (v2si, v2si) | |
5745 | v2si __builtin_arm_wminuh (v2si, v2si) | |
5746 | v2si __builtin_arm_wminub (v2si, v2si) | |
5747 | v2si __builtin_arm_wmuluh (v2si, v2si) | |
5748 | v2si __builtin_arm_wmulsh (v2si, v2si) | |
5749 | v2si __builtin_arm_wmulul (v2si, v2si) | |
5750 | v2si __builtin_arm_wshufh (v2si, int) | |
5751 | v2si __builtin_arm_wsllh (v2si, v2si) | |
5752 | v2si __builtin_arm_wsllw (v2si, v2si) | |
5753 | v2si __builtin_arm_wslld (v2si, v2si) | |
5754 | v2si __builtin_arm_wsrah (v2si, v2si) | |
5755 | v2si __builtin_arm_wsraw (v2si, v2si) | |
5756 | v2si __builtin_arm_wsrad (v2si, v2si) | |
5757 | v2si __builtin_arm_wsrlh (v2si, v2si) | |
5758 | v2si __builtin_arm_wsrlw (v2si, v2si) | |
5759 | v2si __builtin_arm_wsrld (v2si, v2si) | |
5760 | v2si __builtin_arm_wrorh (v2si, v2si) | |
5761 | v2si __builtin_arm_wrorw (v2si, v2si) | |
5762 | v2si __builtin_arm_wrord (v2si, v2si) | |
5763 | v2si __builtin_arm_wsllhi (v2si, int) | |
5764 | v2si __builtin_arm_wsllwi (v2si, int) | |
5765 | v2si __builtin_arm_wslldi (v2si, v2si) | |
5766 | v2si __builtin_arm_wsrahi (v2si, int) | |
5767 | v2si __builtin_arm_wsrawi (v2si, int) | |
5768 | v2si __builtin_arm_wsradi (v2si, v2si) | |
5769 | v2si __builtin_arm_wsrlwi (v2si, int) | |
5770 | v2si __builtin_arm_wsrldi (v2si, int) | |
5771 | v2si __builtin_arm_wrorhi (v2si, int) | |
5772 | v2si __builtin_arm_wrorwi (v2si, int) | |
5773 | v2si __builtin_arm_wrordi (v2si, int) | |
5774 | v2si __builtin_arm_wunpckihb (v2si, v2si) | |
5775 | v2si __builtin_arm_wunpckihh (v2si, v2si) | |
5776 | v2si __builtin_arm_wunpckihw (v2si, v2si) | |
5777 | v2si __builtin_arm_wunpckilb (v2si, v2si) | |
5778 | v2si __builtin_arm_wunpckilh (v2si, v2si) | |
5779 | v2si __builtin_arm_wunpckilw (v2si, v2si) | |
5780 | v2si __builtin_arm_wunpckehsb (v2si) | |
5781 | v2si __builtin_arm_wunpckehsh (v2si) | |
5782 | v2si __builtin_arm_wunpckehsw (v2si) | |
5783 | v2si __builtin_arm_wunpckehub (v2si) | |
5784 | v2si __builtin_arm_wunpckehuh (v2si) | |
5785 | v2si __builtin_arm_wunpckehuw (v2si) | |
5786 | v2si __builtin_arm_wunpckelsb (v2si) | |
5787 | v2si __builtin_arm_wunpckelsh (v2si) | |
5788 | v2si __builtin_arm_wunpckelsw (v2si) | |
5789 | v2si __builtin_arm_wunpckelub (v2si) | |
5790 | v2si __builtin_arm_wunpckeluh (v2si) | |
5791 | v2si __builtin_arm_wunpckeluw (v2si) | |
5792 | v2si __builtin_arm_wsubwss (v2si, v2si) | |
5793 | v2si __builtin_arm_wsraw (v2si, v2si) | |
5794 | v2si __builtin_arm_wsrad (v2si, v2si) | |
5795 | @end example | |
5796 | ||
ca5827cf | 5797 | @node X86 Built-in Functions |
5798 | @subsection X86 Built-in Functions | |
5799 | ||
5800 | These built-in functions are available for the i386 and x86-64 family | |
5801 | of computers, depending on the command-line switches used. | |
5802 | ||
5803 | The following machine modes are available for use with MMX built-in functions | |
0ae4308e | 5804 | (@pxref{Vector Extensions}): @code{V2SI} for a vector of two 32-bit integers, |
5805 | @code{V4HI} for a vector of four 16-bit integers, and @code{V8QI} for a | |
5806 | vector of eight 8-bit integers. Some of the built-in functions operate on | |
5807 | MMX registers as a whole 64-bit entity, these use @code{DI} as their mode. | |
ca5827cf | 5808 | |
5809 | If 3Dnow extensions are enabled, @code{V2SF} is used as a mode for a vector | |
0ae4308e | 5810 | of two 32-bit floating point values. |
ca5827cf | 5811 | |
0ae4308e | 5812 | If SSE extensions are enabled, @code{V4SF} is used for a vector of four 32-bit |
5813 | floating point values. Some instructions use a vector of four 32-bit | |
ca5827cf | 5814 | integers, these use @code{V4SI}. Finally, some instructions operate on an |
0ae4308e | 5815 | entire vector register, interpreting it as a 128-bit integer, these use mode |
ca5827cf | 5816 | @code{TI}. |
5817 | ||
5818 | The following built-in functions are made available by @option{-mmmx}. | |
5819 | All of them generate the machine instruction that is part of the name. | |
5820 | ||
5821 | @example | |
5822 | v8qi __builtin_ia32_paddb (v8qi, v8qi) | |
5823 | v4hi __builtin_ia32_paddw (v4hi, v4hi) | |
5824 | v2si __builtin_ia32_paddd (v2si, v2si) | |
5825 | v8qi __builtin_ia32_psubb (v8qi, v8qi) | |
5826 | v4hi __builtin_ia32_psubw (v4hi, v4hi) | |
5827 | v2si __builtin_ia32_psubd (v2si, v2si) | |
5828 | v8qi __builtin_ia32_paddsb (v8qi, v8qi) | |
5829 | v4hi __builtin_ia32_paddsw (v4hi, v4hi) | |
5830 | v8qi __builtin_ia32_psubsb (v8qi, v8qi) | |
5831 | v4hi __builtin_ia32_psubsw (v4hi, v4hi) | |
5832 | v8qi __builtin_ia32_paddusb (v8qi, v8qi) | |
5833 | v4hi __builtin_ia32_paddusw (v4hi, v4hi) | |
5834 | v8qi __builtin_ia32_psubusb (v8qi, v8qi) | |
5835 | v4hi __builtin_ia32_psubusw (v4hi, v4hi) | |
5836 | v4hi __builtin_ia32_pmullw (v4hi, v4hi) | |
5837 | v4hi __builtin_ia32_pmulhw (v4hi, v4hi) | |
5838 | di __builtin_ia32_pand (di, di) | |
5839 | di __builtin_ia32_pandn (di,di) | |
5840 | di __builtin_ia32_por (di, di) | |
5841 | di __builtin_ia32_pxor (di, di) | |
5842 | v8qi __builtin_ia32_pcmpeqb (v8qi, v8qi) | |
5843 | v4hi __builtin_ia32_pcmpeqw (v4hi, v4hi) | |
5844 | v2si __builtin_ia32_pcmpeqd (v2si, v2si) | |
5845 | v8qi __builtin_ia32_pcmpgtb (v8qi, v8qi) | |
5846 | v4hi __builtin_ia32_pcmpgtw (v4hi, v4hi) | |
5847 | v2si __builtin_ia32_pcmpgtd (v2si, v2si) | |
5848 | v8qi __builtin_ia32_punpckhbw (v8qi, v8qi) | |
5849 | v4hi __builtin_ia32_punpckhwd (v4hi, v4hi) | |
5850 | v2si __builtin_ia32_punpckhdq (v2si, v2si) | |
5851 | v8qi __builtin_ia32_punpcklbw (v8qi, v8qi) | |
5852 | v4hi __builtin_ia32_punpcklwd (v4hi, v4hi) | |
5853 | v2si __builtin_ia32_punpckldq (v2si, v2si) | |
5854 | v8qi __builtin_ia32_packsswb (v4hi, v4hi) | |
5855 | v4hi __builtin_ia32_packssdw (v2si, v2si) | |
5856 | v8qi __builtin_ia32_packuswb (v4hi, v4hi) | |
5857 | @end example | |
5858 | ||
5859 | The following built-in functions are made available either with | |
5860 | @option{-msse}, or with a combination of @option{-m3dnow} and | |
5861 | @option{-march=athlon}. All of them generate the machine | |
5862 | instruction that is part of the name. | |
5863 | ||
5864 | @example | |
5865 | v4hi __builtin_ia32_pmulhuw (v4hi, v4hi) | |
5866 | v8qi __builtin_ia32_pavgb (v8qi, v8qi) | |
5867 | v4hi __builtin_ia32_pavgw (v4hi, v4hi) | |
5868 | v4hi __builtin_ia32_psadbw (v8qi, v8qi) | |
5869 | v8qi __builtin_ia32_pmaxub (v8qi, v8qi) | |
5870 | v4hi __builtin_ia32_pmaxsw (v4hi, v4hi) | |
5871 | v8qi __builtin_ia32_pminub (v8qi, v8qi) | |
5872 | v4hi __builtin_ia32_pminsw (v4hi, v4hi) | |
5873 | int __builtin_ia32_pextrw (v4hi, int) | |
5874 | v4hi __builtin_ia32_pinsrw (v4hi, int, int) | |
5875 | int __builtin_ia32_pmovmskb (v8qi) | |
5876 | void __builtin_ia32_maskmovq (v8qi, v8qi, char *) | |
5877 | void __builtin_ia32_movntq (di *, di) | |
5878 | void __builtin_ia32_sfence (void) | |
5879 | @end example | |
5880 | ||
5881 | The following built-in functions are available when @option{-msse} is used. | |
5882 | All of them generate the machine instruction that is part of the name. | |
5883 | ||
5884 | @example | |
5885 | int __builtin_ia32_comieq (v4sf, v4sf) | |
5886 | int __builtin_ia32_comineq (v4sf, v4sf) | |
5887 | int __builtin_ia32_comilt (v4sf, v4sf) | |
5888 | int __builtin_ia32_comile (v4sf, v4sf) | |
5889 | int __builtin_ia32_comigt (v4sf, v4sf) | |
5890 | int __builtin_ia32_comige (v4sf, v4sf) | |
5891 | int __builtin_ia32_ucomieq (v4sf, v4sf) | |
5892 | int __builtin_ia32_ucomineq (v4sf, v4sf) | |
5893 | int __builtin_ia32_ucomilt (v4sf, v4sf) | |
5894 | int __builtin_ia32_ucomile (v4sf, v4sf) | |
5895 | int __builtin_ia32_ucomigt (v4sf, v4sf) | |
5896 | int __builtin_ia32_ucomige (v4sf, v4sf) | |
5897 | v4sf __builtin_ia32_addps (v4sf, v4sf) | |
5898 | v4sf __builtin_ia32_subps (v4sf, v4sf) | |
5899 | v4sf __builtin_ia32_mulps (v4sf, v4sf) | |
5900 | v4sf __builtin_ia32_divps (v4sf, v4sf) | |
5901 | v4sf __builtin_ia32_addss (v4sf, v4sf) | |
5902 | v4sf __builtin_ia32_subss (v4sf, v4sf) | |
5903 | v4sf __builtin_ia32_mulss (v4sf, v4sf) | |
5904 | v4sf __builtin_ia32_divss (v4sf, v4sf) | |
5905 | v4si __builtin_ia32_cmpeqps (v4sf, v4sf) | |
5906 | v4si __builtin_ia32_cmpltps (v4sf, v4sf) | |
5907 | v4si __builtin_ia32_cmpleps (v4sf, v4sf) | |
5908 | v4si __builtin_ia32_cmpgtps (v4sf, v4sf) | |
5909 | v4si __builtin_ia32_cmpgeps (v4sf, v4sf) | |
5910 | v4si __builtin_ia32_cmpunordps (v4sf, v4sf) | |
5911 | v4si __builtin_ia32_cmpneqps (v4sf, v4sf) | |
5912 | v4si __builtin_ia32_cmpnltps (v4sf, v4sf) | |
5913 | v4si __builtin_ia32_cmpnleps (v4sf, v4sf) | |
5914 | v4si __builtin_ia32_cmpngtps (v4sf, v4sf) | |
5915 | v4si __builtin_ia32_cmpngeps (v4sf, v4sf) | |
5916 | v4si __builtin_ia32_cmpordps (v4sf, v4sf) | |
5917 | v4si __builtin_ia32_cmpeqss (v4sf, v4sf) | |
5918 | v4si __builtin_ia32_cmpltss (v4sf, v4sf) | |
5919 | v4si __builtin_ia32_cmpless (v4sf, v4sf) | |
ca5827cf | 5920 | v4si __builtin_ia32_cmpunordss (v4sf, v4sf) |
5921 | v4si __builtin_ia32_cmpneqss (v4sf, v4sf) | |
5922 | v4si __builtin_ia32_cmpnlts (v4sf, v4sf) | |
5923 | v4si __builtin_ia32_cmpnless (v4sf, v4sf) | |
ca5827cf | 5924 | v4si __builtin_ia32_cmpordss (v4sf, v4sf) |
5925 | v4sf __builtin_ia32_maxps (v4sf, v4sf) | |
5926 | v4sf __builtin_ia32_maxss (v4sf, v4sf) | |
5927 | v4sf __builtin_ia32_minps (v4sf, v4sf) | |
5928 | v4sf __builtin_ia32_minss (v4sf, v4sf) | |
5929 | v4sf __builtin_ia32_andps (v4sf, v4sf) | |
5930 | v4sf __builtin_ia32_andnps (v4sf, v4sf) | |
5931 | v4sf __builtin_ia32_orps (v4sf, v4sf) | |
5932 | v4sf __builtin_ia32_xorps (v4sf, v4sf) | |
5933 | v4sf __builtin_ia32_movss (v4sf, v4sf) | |
5934 | v4sf __builtin_ia32_movhlps (v4sf, v4sf) | |
5935 | v4sf __builtin_ia32_movlhps (v4sf, v4sf) | |
5936 | v4sf __builtin_ia32_unpckhps (v4sf, v4sf) | |
5937 | v4sf __builtin_ia32_unpcklps (v4sf, v4sf) | |
5938 | v4sf __builtin_ia32_cvtpi2ps (v4sf, v2si) | |
5939 | v4sf __builtin_ia32_cvtsi2ss (v4sf, int) | |
5940 | v2si __builtin_ia32_cvtps2pi (v4sf) | |
5941 | int __builtin_ia32_cvtss2si (v4sf) | |
5942 | v2si __builtin_ia32_cvttps2pi (v4sf) | |
5943 | int __builtin_ia32_cvttss2si (v4sf) | |
5944 | v4sf __builtin_ia32_rcpps (v4sf) | |
5945 | v4sf __builtin_ia32_rsqrtps (v4sf) | |
5946 | v4sf __builtin_ia32_sqrtps (v4sf) | |
5947 | v4sf __builtin_ia32_rcpss (v4sf) | |
5948 | v4sf __builtin_ia32_rsqrtss (v4sf) | |
5949 | v4sf __builtin_ia32_sqrtss (v4sf) | |
5950 | v4sf __builtin_ia32_shufps (v4sf, v4sf, int) | |
5951 | void __builtin_ia32_movntps (float *, v4sf) | |
5952 | int __builtin_ia32_movmskps (v4sf) | |
5953 | @end example | |
5954 | ||
5955 | The following built-in functions are available when @option{-msse} is used. | |
5956 | ||
5957 | @table @code | |
5958 | @item v4sf __builtin_ia32_loadaps (float *) | |
5959 | Generates the @code{movaps} machine instruction as a load from memory. | |
5960 | @item void __builtin_ia32_storeaps (float *, v4sf) | |
5961 | Generates the @code{movaps} machine instruction as a store to memory. | |
5962 | @item v4sf __builtin_ia32_loadups (float *) | |
5963 | Generates the @code{movups} machine instruction as a load from memory. | |
5964 | @item void __builtin_ia32_storeups (float *, v4sf) | |
5965 | Generates the @code{movups} machine instruction as a store to memory. | |
5966 | @item v4sf __builtin_ia32_loadsss (float *) | |
5967 | Generates the @code{movss} machine instruction as a load from memory. | |
5968 | @item void __builtin_ia32_storess (float *, v4sf) | |
5969 | Generates the @code{movss} machine instruction as a store to memory. | |
5970 | @item v4sf __builtin_ia32_loadhps (v4sf, v2si *) | |
5971 | Generates the @code{movhps} machine instruction as a load from memory. | |
5972 | @item v4sf __builtin_ia32_loadlps (v4sf, v2si *) | |
5973 | Generates the @code{movlps} machine instruction as a load from memory | |
5974 | @item void __builtin_ia32_storehps (v4sf, v2si *) | |
5975 | Generates the @code{movhps} machine instruction as a store to memory. | |
5976 | @item void __builtin_ia32_storelps (v4sf, v2si *) | |
5977 | Generates the @code{movlps} machine instruction as a store to memory. | |
5978 | @end table | |
5979 | ||
754c06ac | 5980 | The following built-in functions are available when @option{-mpni} is used. |
5981 | All of them generate the machine instruction that is part of the name. | |
5982 | ||
5983 | @example | |
5984 | v2df __builtin_ia32_addsubpd (v2df, v2df) | |
5985 | v2df __builtin_ia32_addsubps (v2df, v2df) | |
5986 | v2df __builtin_ia32_haddpd (v2df, v2df) | |
5987 | v2df __builtin_ia32_haddps (v2df, v2df) | |
5988 | v2df __builtin_ia32_hsubpd (v2df, v2df) | |
5989 | v2df __builtin_ia32_hsubps (v2df, v2df) | |
5990 | v16qi __builtin_ia32_lddqu (char const *) | |
5991 | void __builtin_ia32_monitor (void *, unsigned int, unsigned int) | |
5992 | v2df __builtin_ia32_movddup (v2df) | |
5993 | v4sf __builtin_ia32_movshdup (v4sf) | |
5994 | v4sf __builtin_ia32_movsldup (v4sf) | |
5995 | void __builtin_ia32_mwait (unsigned int, unsigned int) | |
5996 | @end example | |
5997 | ||
5998 | The following built-in functions are available when @option{-mpni} is used. | |
5999 | ||
6000 | @table @code | |
6001 | @item v2df __builtin_ia32_loadddup (double const *) | |
6002 | Generates the @code{movddup} machine instruction as a load from memory. | |
6003 | @end table | |
6004 | ||
ca5827cf | 6005 | The following built-in functions are available when @option{-m3dnow} is used. |
6006 | All of them generate the machine instruction that is part of the name. | |
6007 | ||
6008 | @example | |
6009 | void __builtin_ia32_femms (void) | |
6010 | v8qi __builtin_ia32_pavgusb (v8qi, v8qi) | |
6011 | v2si __builtin_ia32_pf2id (v2sf) | |
6012 | v2sf __builtin_ia32_pfacc (v2sf, v2sf) | |
6013 | v2sf __builtin_ia32_pfadd (v2sf, v2sf) | |
6014 | v2si __builtin_ia32_pfcmpeq (v2sf, v2sf) | |
6015 | v2si __builtin_ia32_pfcmpge (v2sf, v2sf) | |
6016 | v2si __builtin_ia32_pfcmpgt (v2sf, v2sf) | |
6017 | v2sf __builtin_ia32_pfmax (v2sf, v2sf) | |
6018 | v2sf __builtin_ia32_pfmin (v2sf, v2sf) | |
6019 | v2sf __builtin_ia32_pfmul (v2sf, v2sf) | |
6020 | v2sf __builtin_ia32_pfrcp (v2sf) | |
6021 | v2sf __builtin_ia32_pfrcpit1 (v2sf, v2sf) | |
6022 | v2sf __builtin_ia32_pfrcpit2 (v2sf, v2sf) | |
6023 | v2sf __builtin_ia32_pfrsqrt (v2sf) | |
6024 | v2sf __builtin_ia32_pfrsqrtit1 (v2sf, v2sf) | |
6025 | v2sf __builtin_ia32_pfsub (v2sf, v2sf) | |
6026 | v2sf __builtin_ia32_pfsubr (v2sf, v2sf) | |
6027 | v2sf __builtin_ia32_pi2fd (v2si) | |
6028 | v4hi __builtin_ia32_pmulhrw (v4hi, v4hi) | |
6029 | @end example | |
6030 | ||
6031 | The following built-in functions are available when both @option{-m3dnow} | |
6032 | and @option{-march=athlon} are used. All of them generate the machine | |
6033 | instruction that is part of the name. | |
6034 | ||
6035 | @example | |
6036 | v2si __builtin_ia32_pf2iw (v2sf) | |
6037 | v2sf __builtin_ia32_pfnacc (v2sf, v2sf) | |
6038 | v2sf __builtin_ia32_pfpnacc (v2sf, v2sf) | |
6039 | v2sf __builtin_ia32_pi2fw (v2si) | |
6040 | v2sf __builtin_ia32_pswapdsf (v2sf) | |
6041 | v2si __builtin_ia32_pswapdsi (v2si) | |
6042 | @end example | |
6043 | ||
0ae4308e | 6044 | @node PowerPC AltiVec Built-in Functions |
6045 | @subsection PowerPC AltiVec Built-in Functions | |
6046 | ||
6047 | These built-in functions are available for the PowerPC family | |
6048 | of computers, depending on the command-line switches used. | |
6049 | ||
6050 | The following machine modes are available for use with AltiVec built-in | |
6051 | functions (@pxref{Vector Extensions}): @code{V4SI} for a vector of four | |
6052 | 32-bit integers, @code{V4SF} for a vector of four 32-bit floating point | |
6053 | numbers, @code{V8HI} for a vector of eight 16-bit integers, and | |
6054 | @code{V16QI} for a vector of sixteen 8-bit integers. | |
6055 | ||
6056 | The following functions are made available by including | |
6057 | @code{<altivec.h>} and using @option{-maltivec} and | |
6058 | @option{-mabi=altivec}. The functions implement the functionality | |
6059 | described in Motorola's AltiVec Programming Interface Manual. | |
6060 | ||
af08769f | 6061 | There are a few differences from Motorola's documentation and GCC's |
6062 | implementation. Vector constants are done with curly braces (not | |
6063 | parentheses). Vector initializers require no casts if the vector | |
6064 | constant is of the same type as the variable it is initializing. The | |
6065 | @code{vector bool} type is deprecated and will be discontinued in | |
6066 | further revisions. Use @code{vector signed} instead. If @code{signed} | |
6067 | or @code{unsigned} is omitted, the vector type will default to | |
17e01dc5 | 6068 | @code{signed}. Lastly, all overloaded functions are implemented with macros |
af08769f | 6069 | for the C implementation. So code the following example will not work: |
6070 | ||
6071 | @smallexample | |
17e01dc5 | 6072 | vec_add ((vector signed int)@{1, 2, 3, 4@}, foo); |
af08769f | 6073 | @end smallexample |
6074 | ||
6075 | Since vec_add is a macro, the vector constant in the above example will | |
6076 | be treated as four different arguments. Wrap the entire argument in | |
6077 | parentheses for this to work. The C++ implementation does not use | |
6078 | macros. | |
6079 | ||
15e5a1c8 | 6080 | @emph{Note:} Only the @code{<altivec.h>} interface is supported. |
6081 | Internally, GCC uses built-in functions to achieve the functionality in | |
6082 | the aforementioned header file, but they are not supported and are | |
6083 | subject to change without notice. | |
6084 | ||
0ae4308e | 6085 | @smallexample |
6086 | vector signed char vec_abs (vector signed char, vector signed char); | |
6087 | vector signed short vec_abs (vector signed short, vector signed short); | |
6088 | vector signed int vec_abs (vector signed int, vector signed int); | |
6089 | vector signed float vec_abs (vector signed float, vector signed float); | |
6090 | ||
6091 | vector signed char vec_abss (vector signed char, vector signed char); | |
6092 | vector signed short vec_abss (vector signed short, vector signed short); | |
6093 | ||
6094 | vector signed char vec_add (vector signed char, vector signed char); | |
6095 | vector unsigned char vec_add (vector signed char, vector unsigned char); | |
6096 | ||
6097 | vector unsigned char vec_add (vector unsigned char, vector signed char); | |
6098 | ||
8bdbaccf | 6099 | vector unsigned char vec_add (vector unsigned char, |
6100 | vector unsigned char); | |
0ae4308e | 6101 | vector signed short vec_add (vector signed short, vector signed short); |
8bdbaccf | 6102 | vector unsigned short vec_add (vector signed short, |
6103 | vector unsigned short); | |
6104 | vector unsigned short vec_add (vector unsigned short, | |
6105 | vector signed short); | |
8e1103d3 | 6106 | vector unsigned short vec_add (vector unsigned short, |
6107 | vector unsigned short); | |
0ae4308e | 6108 | vector signed int vec_add (vector signed int, vector signed int); |
6109 | vector unsigned int vec_add (vector signed int, vector unsigned int); | |
6110 | vector unsigned int vec_add (vector unsigned int, vector signed int); | |
6111 | vector unsigned int vec_add (vector unsigned int, vector unsigned int); | |
6112 | vector float vec_add (vector float, vector float); | |
6113 | ||
6114 | vector unsigned int vec_addc (vector unsigned int, vector unsigned int); | |
6115 | ||
8bdbaccf | 6116 | vector unsigned char vec_adds (vector signed char, |
6117 | vector unsigned char); | |
6118 | vector unsigned char vec_adds (vector unsigned char, | |
6119 | vector signed char); | |
6120 | vector unsigned char vec_adds (vector unsigned char, | |
6121 | vector unsigned char); | |
0ae4308e | 6122 | vector signed char vec_adds (vector signed char, vector signed char); |
8bdbaccf | 6123 | vector unsigned short vec_adds (vector signed short, |
6124 | vector unsigned short); | |
6125 | vector unsigned short vec_adds (vector unsigned short, | |
6126 | vector signed short); | |
8e1103d3 | 6127 | vector unsigned short vec_adds (vector unsigned short, |
6128 | vector unsigned short); | |
0ae4308e | 6129 | vector signed short vec_adds (vector signed short, vector signed short); |
6130 | ||
6131 | vector unsigned int vec_adds (vector signed int, vector unsigned int); | |
6132 | vector unsigned int vec_adds (vector unsigned int, vector signed int); | |
6133 | vector unsigned int vec_adds (vector unsigned int, vector unsigned int); | |
6134 | ||
6135 | vector signed int vec_adds (vector signed int, vector signed int); | |
6136 | ||
6137 | vector float vec_and (vector float, vector float); | |
6138 | vector float vec_and (vector float, vector signed int); | |
6139 | vector float vec_and (vector signed int, vector float); | |
6140 | vector signed int vec_and (vector signed int, vector signed int); | |
6141 | vector unsigned int vec_and (vector signed int, vector unsigned int); | |
6142 | vector unsigned int vec_and (vector unsigned int, vector signed int); | |
6143 | vector unsigned int vec_and (vector unsigned int, vector unsigned int); | |
6144 | vector signed short vec_and (vector signed short, vector signed short); | |
8bdbaccf | 6145 | vector unsigned short vec_and (vector signed short, |
6146 | vector unsigned short); | |
6147 | vector unsigned short vec_and (vector unsigned short, | |
6148 | vector signed short); | |
8e1103d3 | 6149 | vector unsigned short vec_and (vector unsigned short, |
6150 | vector unsigned short); | |
0ae4308e | 6151 | vector signed char vec_and (vector signed char, vector signed char); |
6152 | vector unsigned char vec_and (vector signed char, vector unsigned char); | |
6153 | ||
6154 | vector unsigned char vec_and (vector unsigned char, vector signed char); | |
6155 | ||
8bdbaccf | 6156 | vector unsigned char vec_and (vector unsigned char, |
6157 | vector unsigned char); | |
0ae4308e | 6158 | |
6159 | vector float vec_andc (vector float, vector float); | |
6160 | vector float vec_andc (vector float, vector signed int); | |
6161 | vector float vec_andc (vector signed int, vector float); | |
6162 | vector signed int vec_andc (vector signed int, vector signed int); | |
6163 | vector unsigned int vec_andc (vector signed int, vector unsigned int); | |
6164 | vector unsigned int vec_andc (vector unsigned int, vector signed int); | |
6165 | vector unsigned int vec_andc (vector unsigned int, vector unsigned int); | |
6166 | ||
6167 | vector signed short vec_andc (vector signed short, vector signed short); | |
6168 | ||
8bdbaccf | 6169 | vector unsigned short vec_andc (vector signed short, |
6170 | vector unsigned short); | |
6171 | vector unsigned short vec_andc (vector unsigned short, | |
6172 | vector signed short); | |
8e1103d3 | 6173 | vector unsigned short vec_andc (vector unsigned short, |
6174 | vector unsigned short); | |
0ae4308e | 6175 | vector signed char vec_andc (vector signed char, vector signed char); |
8bdbaccf | 6176 | vector unsigned char vec_andc (vector signed char, |
6177 | vector unsigned char); | |
6178 | vector unsigned char vec_andc (vector unsigned char, | |
6179 | vector signed char); | |
6180 | vector unsigned char vec_andc (vector unsigned char, | |
6181 | vector unsigned char); | |
0ae4308e | 6182 | |
8bdbaccf | 6183 | vector unsigned char vec_avg (vector unsigned char, |
6184 | vector unsigned char); | |
0ae4308e | 6185 | vector signed char vec_avg (vector signed char, vector signed char); |
8e1103d3 | 6186 | vector unsigned short vec_avg (vector unsigned short, |
6187 | vector unsigned short); | |
0ae4308e | 6188 | vector signed short vec_avg (vector signed short, vector signed short); |
6189 | vector unsigned int vec_avg (vector unsigned int, vector unsigned int); | |
6190 | vector signed int vec_avg (vector signed int, vector signed int); | |
6191 | ||
6192 | vector float vec_ceil (vector float); | |
6193 | ||
6194 | vector signed int vec_cmpb (vector float, vector float); | |
6195 | ||
6196 | vector signed char vec_cmpeq (vector signed char, vector signed char); | |
8bdbaccf | 6197 | vector signed char vec_cmpeq (vector unsigned char, |
6198 | vector unsigned char); | |
6199 | vector signed short vec_cmpeq (vector signed short, | |
6200 | vector signed short); | |
8e1103d3 | 6201 | vector signed short vec_cmpeq (vector unsigned short, |
6202 | vector unsigned short); | |
0ae4308e | 6203 | vector signed int vec_cmpeq (vector signed int, vector signed int); |
6204 | vector signed int vec_cmpeq (vector unsigned int, vector unsigned int); | |
6205 | vector signed int vec_cmpeq (vector float, vector float); | |
6206 | ||
6207 | vector signed int vec_cmpge (vector float, vector float); | |
6208 | ||
8bdbaccf | 6209 | vector signed char vec_cmpgt (vector unsigned char, |
6210 | vector unsigned char); | |
0ae4308e | 6211 | vector signed char vec_cmpgt (vector signed char, vector signed char); |
8e1103d3 | 6212 | vector signed short vec_cmpgt (vector unsigned short, |
6213 | vector unsigned short); | |
8bdbaccf | 6214 | vector signed short vec_cmpgt (vector signed short, |
6215 | vector signed short); | |
0ae4308e | 6216 | vector signed int vec_cmpgt (vector unsigned int, vector unsigned int); |
6217 | vector signed int vec_cmpgt (vector signed int, vector signed int); | |
6218 | vector signed int vec_cmpgt (vector float, vector float); | |
6219 | ||
6220 | vector signed int vec_cmple (vector float, vector float); | |
6221 | ||
8bdbaccf | 6222 | vector signed char vec_cmplt (vector unsigned char, |
6223 | vector unsigned char); | |
0ae4308e | 6224 | vector signed char vec_cmplt (vector signed char, vector signed char); |
8e1103d3 | 6225 | vector signed short vec_cmplt (vector unsigned short, |
6226 | vector unsigned short); | |
8bdbaccf | 6227 | vector signed short vec_cmplt (vector signed short, |
6228 | vector signed short); | |
0ae4308e | 6229 | vector signed int vec_cmplt (vector unsigned int, vector unsigned int); |
6230 | vector signed int vec_cmplt (vector signed int, vector signed int); | |
6231 | vector signed int vec_cmplt (vector float, vector float); | |
6232 | ||
6233 | vector float vec_ctf (vector unsigned int, const char); | |
6234 | vector float vec_ctf (vector signed int, const char); | |
6235 | ||
6236 | vector signed int vec_cts (vector float, const char); | |
6237 | ||
6238 | vector unsigned int vec_ctu (vector float, const char); | |
6239 | ||
6240 | void vec_dss (const char); | |
6241 | ||
6242 | void vec_dssall (void); | |
6243 | ||
6244 | void vec_dst (void *, int, const char); | |
6245 | ||
6246 | void vec_dstst (void *, int, const char); | |
6247 | ||
6248 | void vec_dststt (void *, int, const char); | |
6249 | ||
6250 | void vec_dstt (void *, int, const char); | |
6251 | ||
6252 | vector float vec_expte (vector float, vector float); | |
6253 | ||
6254 | vector float vec_floor (vector float, vector float); | |
6255 | ||
6256 | vector float vec_ld (int, vector float *); | |
6257 | vector float vec_ld (int, float *): | |
6258 | vector signed int vec_ld (int, int *); | |
6259 | vector signed int vec_ld (int, vector signed int *); | |
6260 | vector unsigned int vec_ld (int, vector unsigned int *); | |
6261 | vector unsigned int vec_ld (int, unsigned int *); | |
6262 | vector signed short vec_ld (int, short *, vector signed short *); | |
8e1103d3 | 6263 | vector unsigned short vec_ld (int, unsigned short *, |
6264 | vector unsigned short *); | |
0ae4308e | 6265 | vector signed char vec_ld (int, signed char *); |
6266 | vector signed char vec_ld (int, vector signed char *); | |
6267 | vector unsigned char vec_ld (int, unsigned char *); | |
6268 | vector unsigned char vec_ld (int, vector unsigned char *); | |
6269 | ||
6270 | vector signed char vec_lde (int, signed char *); | |
6271 | vector unsigned char vec_lde (int, unsigned char *); | |
6272 | vector signed short vec_lde (int, short *); | |
6273 | vector unsigned short vec_lde (int, unsigned short *); | |
6274 | vector float vec_lde (int, float *); | |
6275 | vector signed int vec_lde (int, int *); | |
6276 | vector unsigned int vec_lde (int, unsigned int *); | |
6277 | ||
6278 | void float vec_ldl (int, float *); | |
6279 | void float vec_ldl (int, vector float *); | |
6280 | void signed int vec_ldl (int, vector signed int *); | |
6281 | void signed int vec_ldl (int, int *); | |
6282 | void unsigned int vec_ldl (int, unsigned int *); | |
6283 | void unsigned int vec_ldl (int, vector unsigned int *); | |
6284 | void signed short vec_ldl (int, vector signed short *); | |
6285 | void signed short vec_ldl (int, short *); | |
6286 | void unsigned short vec_ldl (int, vector unsigned short *); | |
6287 | void unsigned short vec_ldl (int, unsigned short *); | |
6288 | void signed char vec_ldl (int, vector signed char *); | |
6289 | void signed char vec_ldl (int, signed char *); | |
6290 | void unsigned char vec_ldl (int, vector unsigned char *); | |
6291 | void unsigned char vec_ldl (int, unsigned char *); | |
6292 | ||
6293 | vector float vec_loge (vector float); | |
6294 | ||
6295 | vector unsigned char vec_lvsl (int, void *, int *); | |
6296 | ||
6297 | vector unsigned char vec_lvsr (int, void *, int *); | |
6298 | ||
6299 | vector float vec_madd (vector float, vector float, vector float); | |
6300 | ||
8e1103d3 | 6301 | vector signed short vec_madds (vector signed short, vector signed short, |
6302 | vector signed short); | |
0ae4308e | 6303 | |
6304 | vector unsigned char vec_max (vector signed char, vector unsigned char); | |
6305 | ||
6306 | vector unsigned char vec_max (vector unsigned char, vector signed char); | |
6307 | ||
8bdbaccf | 6308 | vector unsigned char vec_max (vector unsigned char, |
6309 | vector unsigned char); | |
0ae4308e | 6310 | vector signed char vec_max (vector signed char, vector signed char); |
8bdbaccf | 6311 | vector unsigned short vec_max (vector signed short, |
6312 | vector unsigned short); | |
6313 | vector unsigned short vec_max (vector unsigned short, | |
6314 | vector signed short); | |
8e1103d3 | 6315 | vector unsigned short vec_max (vector unsigned short, |
6316 | vector unsigned short); | |
0ae4308e | 6317 | vector signed short vec_max (vector signed short, vector signed short); |
6318 | vector unsigned int vec_max (vector signed int, vector unsigned int); | |
6319 | vector unsigned int vec_max (vector unsigned int, vector signed int); | |
6320 | vector unsigned int vec_max (vector unsigned int, vector unsigned int); | |
6321 | vector signed int vec_max (vector signed int, vector signed int); | |
6322 | vector float vec_max (vector float, vector float); | |
6323 | ||
6324 | vector signed char vec_mergeh (vector signed char, vector signed char); | |
8e1103d3 | 6325 | vector unsigned char vec_mergeh (vector unsigned char, |
6326 | vector unsigned char); | |
8bdbaccf | 6327 | vector signed short vec_mergeh (vector signed short, |
6328 | vector signed short); | |
8e1103d3 | 6329 | vector unsigned short vec_mergeh (vector unsigned short, |
6330 | vector unsigned short); | |
0ae4308e | 6331 | vector float vec_mergeh (vector float, vector float); |
6332 | vector signed int vec_mergeh (vector signed int, vector signed int); | |
8bdbaccf | 6333 | vector unsigned int vec_mergeh (vector unsigned int, |
6334 | vector unsigned int); | |
0ae4308e | 6335 | |
6336 | vector signed char vec_mergel (vector signed char, vector signed char); | |
8e1103d3 | 6337 | vector unsigned char vec_mergel (vector unsigned char, |
6338 | vector unsigned char); | |
8bdbaccf | 6339 | vector signed short vec_mergel (vector signed short, |
6340 | vector signed short); | |
8e1103d3 | 6341 | vector unsigned short vec_mergel (vector unsigned short, |
6342 | vector unsigned short); | |
0ae4308e | 6343 | vector float vec_mergel (vector float, vector float); |
6344 | vector signed int vec_mergel (vector signed int, vector signed int); | |
8bdbaccf | 6345 | vector unsigned int vec_mergel (vector unsigned int, |
6346 | vector unsigned int); | |
0ae4308e | 6347 | |
6348 | vector unsigned short vec_mfvscr (void); | |
6349 | ||
6350 | vector unsigned char vec_min (vector signed char, vector unsigned char); | |
6351 | ||
6352 | vector unsigned char vec_min (vector unsigned char, vector signed char); | |
6353 | ||
8bdbaccf | 6354 | vector unsigned char vec_min (vector unsigned char, |
6355 | vector unsigned char); | |
0ae4308e | 6356 | vector signed char vec_min (vector signed char, vector signed char); |
8bdbaccf | 6357 | vector unsigned short vec_min (vector signed short, |
6358 | vector unsigned short); | |
6359 | vector unsigned short vec_min (vector unsigned short, | |
6360 | vector signed short); | |
8e1103d3 | 6361 | vector unsigned short vec_min (vector unsigned short, |
6362 | vector unsigned short); | |
0ae4308e | 6363 | vector signed short vec_min (vector signed short, vector signed short); |
6364 | vector unsigned int vec_min (vector signed int, vector unsigned int); | |
6365 | vector unsigned int vec_min (vector unsigned int, vector signed int); | |
6366 | vector unsigned int vec_min (vector unsigned int, vector unsigned int); | |
6367 | vector signed int vec_min (vector signed int, vector signed int); | |
6368 | vector float vec_min (vector float, vector float); | |
6369 | ||
8e1103d3 | 6370 | vector signed short vec_mladd (vector signed short, vector signed short, |
6371 | vector signed short); | |
8bdbaccf | 6372 | vector signed short vec_mladd (vector signed short, |
6373 | vector unsigned short, | |
8e1103d3 | 6374 | vector unsigned short); |
8bdbaccf | 6375 | vector signed short vec_mladd (vector unsigned short, |
6376 | vector signed short, | |
8e1103d3 | 6377 | vector signed short); |
6378 | vector unsigned short vec_mladd (vector unsigned short, | |
6379 | vector unsigned short, | |
6380 | vector unsigned short); | |
6381 | ||
8bdbaccf | 6382 | vector signed short vec_mradds (vector signed short, |
6383 | vector signed short, | |
8e1103d3 | 6384 | vector signed short); |
6385 | ||
8bdbaccf | 6386 | vector unsigned int vec_msum (vector unsigned char, |
6387 | vector unsigned char, | |
8e1103d3 | 6388 | vector unsigned int); |
6389 | vector signed int vec_msum (vector signed char, vector unsigned char, | |
6390 | vector signed int); | |
8bdbaccf | 6391 | vector unsigned int vec_msum (vector unsigned short, |
6392 | vector unsigned short, | |
8e1103d3 | 6393 | vector unsigned int); |
6394 | vector signed int vec_msum (vector signed short, vector signed short, | |
6395 | vector signed int); | |
6396 | ||
6397 | vector unsigned int vec_msums (vector unsigned short, | |
8bdbaccf | 6398 | vector unsigned short, |
6399 | vector unsigned int); | |
8e1103d3 | 6400 | vector signed int vec_msums (vector signed short, vector signed short, |
6401 | vector signed int); | |
0ae4308e | 6402 | |
6403 | void vec_mtvscr (vector signed int); | |
6404 | void vec_mtvscr (vector unsigned int); | |
6405 | void vec_mtvscr (vector signed short); | |
6406 | void vec_mtvscr (vector unsigned short); | |
6407 | void vec_mtvscr (vector signed char); | |
6408 | void vec_mtvscr (vector unsigned char); | |
6409 | ||
8bdbaccf | 6410 | vector unsigned short vec_mule (vector unsigned char, |
6411 | vector unsigned char); | |
0ae4308e | 6412 | vector signed short vec_mule (vector signed char, vector signed char); |
8bdbaccf | 6413 | vector unsigned int vec_mule (vector unsigned short, |
6414 | vector unsigned short); | |
0ae4308e | 6415 | vector signed int vec_mule (vector signed short, vector signed short); |
6416 | ||
8bdbaccf | 6417 | vector unsigned short vec_mulo (vector unsigned char, |
6418 | vector unsigned char); | |
0ae4308e | 6419 | vector signed short vec_mulo (vector signed char, vector signed char); |
8bdbaccf | 6420 | vector unsigned int vec_mulo (vector unsigned short, |
6421 | vector unsigned short); | |
0ae4308e | 6422 | vector signed int vec_mulo (vector signed short, vector signed short); |
6423 | ||
6424 | vector float vec_nmsub (vector float, vector float, vector float); | |
6425 | ||
6426 | vector float vec_nor (vector float, vector float); | |
6427 | vector signed int vec_nor (vector signed int, vector signed int); | |
6428 | vector unsigned int vec_nor (vector unsigned int, vector unsigned int); | |
6429 | vector signed short vec_nor (vector signed short, vector signed short); | |
8e1103d3 | 6430 | vector unsigned short vec_nor (vector unsigned short, |
6431 | vector unsigned short); | |
0ae4308e | 6432 | vector signed char vec_nor (vector signed char, vector signed char); |
8bdbaccf | 6433 | vector unsigned char vec_nor (vector unsigned char, |
6434 | vector unsigned char); | |
0ae4308e | 6435 | |
6436 | vector float vec_or (vector float, vector float); | |
6437 | vector float vec_or (vector float, vector signed int); | |
6438 | vector float vec_or (vector signed int, vector float); | |
6439 | vector signed int vec_or (vector signed int, vector signed int); | |
6440 | vector unsigned int vec_or (vector signed int, vector unsigned int); | |
6441 | vector unsigned int vec_or (vector unsigned int, vector signed int); | |
6442 | vector unsigned int vec_or (vector unsigned int, vector unsigned int); | |
6443 | vector signed short vec_or (vector signed short, vector signed short); | |
8bdbaccf | 6444 | vector unsigned short vec_or (vector signed short, |
6445 | vector unsigned short); | |
6446 | vector unsigned short vec_or (vector unsigned short, | |
6447 | vector signed short); | |
6448 | vector unsigned short vec_or (vector unsigned short, | |
6449 | vector unsigned short); | |
0ae4308e | 6450 | vector signed char vec_or (vector signed char, vector signed char); |
6451 | vector unsigned char vec_or (vector signed char, vector unsigned char); | |
6452 | vector unsigned char vec_or (vector unsigned char, vector signed char); | |
8bdbaccf | 6453 | vector unsigned char vec_or (vector unsigned char, |
6454 | vector unsigned char); | |
0ae4308e | 6455 | |
6456 | vector signed char vec_pack (vector signed short, vector signed short); | |
8e1103d3 | 6457 | vector unsigned char vec_pack (vector unsigned short, |
6458 | vector unsigned short); | |
0ae4308e | 6459 | vector signed short vec_pack (vector signed int, vector signed int); |
8bdbaccf | 6460 | vector unsigned short vec_pack (vector unsigned int, |
6461 | vector unsigned int); | |
0ae4308e | 6462 | |
8bdbaccf | 6463 | vector signed short vec_packpx (vector unsigned int, |
6464 | vector unsigned int); | |
0ae4308e | 6465 | |
8e1103d3 | 6466 | vector unsigned char vec_packs (vector unsigned short, |
6467 | vector unsigned short); | |
0ae4308e | 6468 | vector signed char vec_packs (vector signed short, vector signed short); |
6469 | ||
8bdbaccf | 6470 | vector unsigned short vec_packs (vector unsigned int, |
6471 | vector unsigned int); | |
0ae4308e | 6472 | vector signed short vec_packs (vector signed int, vector signed int); |
6473 | ||
8e1103d3 | 6474 | vector unsigned char vec_packsu (vector unsigned short, |
6475 | vector unsigned short); | |
8bdbaccf | 6476 | vector unsigned char vec_packsu (vector signed short, |
6477 | vector signed short); | |
6478 | vector unsigned short vec_packsu (vector unsigned int, | |
6479 | vector unsigned int); | |
0ae4308e | 6480 | vector unsigned short vec_packsu (vector signed int, vector signed int); |
6481 | ||
8bdbaccf | 6482 | vector float vec_perm (vector float, vector float, |
6483 | vector unsigned char); | |
8e1103d3 | 6484 | vector signed int vec_perm (vector signed int, vector signed int, |
6485 | vector unsigned char); | |
6486 | vector unsigned int vec_perm (vector unsigned int, vector unsigned int, | |
6487 | vector unsigned char); | |
6488 | vector signed short vec_perm (vector signed short, vector signed short, | |
6489 | vector unsigned char); | |
6490 | vector unsigned short vec_perm (vector unsigned short, | |
6491 | vector unsigned short, | |
6492 | vector unsigned char); | |
6493 | vector signed char vec_perm (vector signed char, vector signed char, | |
6494 | vector unsigned char); | |
8bdbaccf | 6495 | vector unsigned char vec_perm (vector unsigned char, |
6496 | vector unsigned char, | |
8e1103d3 | 6497 | vector unsigned char); |
0ae4308e | 6498 | |
6499 | vector float vec_re (vector float); | |
6500 | ||
6501 | vector signed char vec_rl (vector signed char, vector unsigned char); | |
8bdbaccf | 6502 | vector unsigned char vec_rl (vector unsigned char, |
6503 | vector unsigned char); | |
0ae4308e | 6504 | vector signed short vec_rl (vector signed short, vector unsigned short); |
6505 | ||
8bdbaccf | 6506 | vector unsigned short vec_rl (vector unsigned short, |
6507 | vector unsigned short); | |
0ae4308e | 6508 | vector signed int vec_rl (vector signed int, vector unsigned int); |
6509 | vector unsigned int vec_rl (vector unsigned int, vector unsigned int); | |
6510 | ||
6511 | vector float vec_round (vector float); | |
6512 | ||
6513 | vector float vec_rsqrte (vector float); | |
6514 | ||
6515 | vector float vec_sel (vector float, vector float, vector signed int); | |
6516 | vector float vec_sel (vector float, vector float, vector unsigned int); | |
8e1103d3 | 6517 | vector signed int vec_sel (vector signed int, vector signed int, |
6518 | vector signed int); | |
6519 | vector signed int vec_sel (vector signed int, vector signed int, | |
6520 | vector unsigned int); | |
6521 | vector unsigned int vec_sel (vector unsigned int, vector unsigned int, | |
6522 | vector signed int); | |
6523 | vector unsigned int vec_sel (vector unsigned int, vector unsigned int, | |
6524 | vector unsigned int); | |
6525 | vector signed short vec_sel (vector signed short, vector signed short, | |
6526 | vector signed short); | |
6527 | vector signed short vec_sel (vector signed short, vector signed short, | |
6528 | vector unsigned short); | |
6529 | vector unsigned short vec_sel (vector unsigned short, | |
8bdbaccf | 6530 | vector unsigned short, |
6531 | vector signed short); | |
8e1103d3 | 6532 | vector unsigned short vec_sel (vector unsigned short, |
6533 | vector unsigned short, | |
6534 | vector unsigned short); | |
6535 | vector signed char vec_sel (vector signed char, vector signed char, | |
6536 | vector signed char); | |
6537 | vector signed char vec_sel (vector signed char, vector signed char, | |
6538 | vector unsigned char); | |
8bdbaccf | 6539 | vector unsigned char vec_sel (vector unsigned char, |
6540 | vector unsigned char, | |
8e1103d3 | 6541 | vector signed char); |
8bdbaccf | 6542 | vector unsigned char vec_sel (vector unsigned char, |
6543 | vector unsigned char, | |
8e1103d3 | 6544 | vector unsigned char); |
0ae4308e | 6545 | |
6546 | vector signed char vec_sl (vector signed char, vector unsigned char); | |
8bdbaccf | 6547 | vector unsigned char vec_sl (vector unsigned char, |
6548 | vector unsigned char); | |
0ae4308e | 6549 | vector signed short vec_sl (vector signed short, vector unsigned short); |
6550 | ||
8bdbaccf | 6551 | vector unsigned short vec_sl (vector unsigned short, |
6552 | vector unsigned short); | |
0ae4308e | 6553 | vector signed int vec_sl (vector signed int, vector unsigned int); |
6554 | vector unsigned int vec_sl (vector unsigned int, vector unsigned int); | |
6555 | ||
6556 | vector float vec_sld (vector float, vector float, const char); | |
8e1103d3 | 6557 | vector signed int vec_sld (vector signed int, vector signed int, |
6558 | const char); | |
6559 | vector unsigned int vec_sld (vector unsigned int, vector unsigned int, | |
6560 | const char); | |
6561 | vector signed short vec_sld (vector signed short, vector signed short, | |
6562 | const char); | |
6563 | vector unsigned short vec_sld (vector unsigned short, | |
6564 | vector unsigned short, const char); | |
6565 | vector signed char vec_sld (vector signed char, vector signed char, | |
6566 | const char); | |
8bdbaccf | 6567 | vector unsigned char vec_sld (vector unsigned char, |
6568 | vector unsigned char, | |
8e1103d3 | 6569 | const char); |
0ae4308e | 6570 | |
6571 | vector signed int vec_sll (vector signed int, vector unsigned int); | |
6572 | vector signed int vec_sll (vector signed int, vector unsigned short); | |
6573 | vector signed int vec_sll (vector signed int, vector unsigned char); | |
6574 | vector unsigned int vec_sll (vector unsigned int, vector unsigned int); | |
8bdbaccf | 6575 | vector unsigned int vec_sll (vector unsigned int, |
6576 | vector unsigned short); | |
0ae4308e | 6577 | vector unsigned int vec_sll (vector unsigned int, vector unsigned char); |
6578 | ||
6579 | vector signed short vec_sll (vector signed short, vector unsigned int); | |
8bdbaccf | 6580 | vector signed short vec_sll (vector signed short, |
6581 | vector unsigned short); | |
0ae4308e | 6582 | vector signed short vec_sll (vector signed short, vector unsigned char); |
6583 | ||
8bdbaccf | 6584 | vector unsigned short vec_sll (vector unsigned short, |
6585 | vector unsigned int); | |
8e1103d3 | 6586 | vector unsigned short vec_sll (vector unsigned short, |
6587 | vector unsigned short); | |
8bdbaccf | 6588 | vector unsigned short vec_sll (vector unsigned short, |
6589 | vector unsigned char); | |
0ae4308e | 6590 | vector signed char vec_sll (vector signed char, vector unsigned int); |
6591 | vector signed char vec_sll (vector signed char, vector unsigned short); | |
6592 | vector signed char vec_sll (vector signed char, vector unsigned char); | |
8bdbaccf | 6593 | vector unsigned char vec_sll (vector unsigned char, |
6594 | vector unsigned int); | |
6595 | vector unsigned char vec_sll (vector unsigned char, | |
6596 | vector unsigned short); | |
6597 | vector unsigned char vec_sll (vector unsigned char, | |
6598 | vector unsigned char); | |
0ae4308e | 6599 | |
6600 | vector float vec_slo (vector float, vector signed char); | |
6601 | vector float vec_slo (vector float, vector unsigned char); | |
6602 | vector signed int vec_slo (vector signed int, vector signed char); | |
6603 | vector signed int vec_slo (vector signed int, vector unsigned char); | |
6604 | vector unsigned int vec_slo (vector unsigned int, vector signed char); | |
6605 | vector unsigned int vec_slo (vector unsigned int, vector unsigned char); | |
6606 | ||
6607 | vector signed short vec_slo (vector signed short, vector signed char); | |
6608 | vector signed short vec_slo (vector signed short, vector unsigned char); | |
6609 | ||
8bdbaccf | 6610 | vector unsigned short vec_slo (vector unsigned short, |
6611 | vector signed char); | |
6612 | vector unsigned short vec_slo (vector unsigned short, | |
6613 | vector unsigned char); | |
0ae4308e | 6614 | vector signed char vec_slo (vector signed char, vector signed char); |
6615 | vector signed char vec_slo (vector signed char, vector unsigned char); | |
6616 | vector unsigned char vec_slo (vector unsigned char, vector signed char); | |
6617 | ||
8bdbaccf | 6618 | vector unsigned char vec_slo (vector unsigned char, |
6619 | vector unsigned char); | |
0ae4308e | 6620 | |
6621 | vector signed char vec_splat (vector signed char, const char); | |
6622 | vector unsigned char vec_splat (vector unsigned char, const char); | |
6623 | vector signed short vec_splat (vector signed short, const char); | |
6624 | vector unsigned short vec_splat (vector unsigned short, const char); | |
6625 | vector float vec_splat (vector float, const char); | |
6626 | vector signed int vec_splat (vector signed int, const char); | |
6627 | vector unsigned int vec_splat (vector unsigned int, const char); | |
6628 | ||
6629 | vector signed char vec_splat_s8 (const char); | |
6630 | ||
6631 | vector signed short vec_splat_s16 (const char); | |
6632 | ||
6633 | vector signed int vec_splat_s32 (const char); | |
6634 | ||
6635 | vector unsigned char vec_splat_u8 (const char); | |
6636 | ||
6637 | vector unsigned short vec_splat_u16 (const char); | |
6638 | ||
6639 | vector unsigned int vec_splat_u32 (const char); | |
6640 | ||
6641 | vector signed char vec_sr (vector signed char, vector unsigned char); | |
8bdbaccf | 6642 | vector unsigned char vec_sr (vector unsigned char, |
6643 | vector unsigned char); | |
0ae4308e | 6644 | vector signed short vec_sr (vector signed short, vector unsigned short); |
6645 | ||
8bdbaccf | 6646 | vector unsigned short vec_sr (vector unsigned short, |
6647 | vector unsigned short); | |
0ae4308e | 6648 | vector signed int vec_sr (vector signed int, vector unsigned int); |
6649 | vector unsigned int vec_sr (vector unsigned int, vector unsigned int); | |
6650 | ||
6651 | vector signed char vec_sra (vector signed char, vector unsigned char); | |
8bdbaccf | 6652 | vector unsigned char vec_sra (vector unsigned char, |
6653 | vector unsigned char); | |
6654 | vector signed short vec_sra (vector signed short, | |
6655 | vector unsigned short); | |
8e1103d3 | 6656 | vector unsigned short vec_sra (vector unsigned short, |
6657 | vector unsigned short); | |
0ae4308e | 6658 | vector signed int vec_sra (vector signed int, vector unsigned int); |
6659 | vector unsigned int vec_sra (vector unsigned int, vector unsigned int); | |
6660 | ||
6661 | vector signed int vec_srl (vector signed int, vector unsigned int); | |
6662 | vector signed int vec_srl (vector signed int, vector unsigned short); | |
6663 | vector signed int vec_srl (vector signed int, vector unsigned char); | |
6664 | vector unsigned int vec_srl (vector unsigned int, vector unsigned int); | |
8bdbaccf | 6665 | vector unsigned int vec_srl (vector unsigned int, |
6666 | vector unsigned short); | |
0ae4308e | 6667 | vector unsigned int vec_srl (vector unsigned int, vector unsigned char); |
6668 | ||
6669 | vector signed short vec_srl (vector signed short, vector unsigned int); | |
8bdbaccf | 6670 | vector signed short vec_srl (vector signed short, |
6671 | vector unsigned short); | |
0ae4308e | 6672 | vector signed short vec_srl (vector signed short, vector unsigned char); |
6673 | ||
8bdbaccf | 6674 | vector unsigned short vec_srl (vector unsigned short, |
6675 | vector unsigned int); | |
8e1103d3 | 6676 | vector unsigned short vec_srl (vector unsigned short, |
6677 | vector unsigned short); | |
8bdbaccf | 6678 | vector unsigned short vec_srl (vector unsigned short, |
6679 | vector unsigned char); | |
0ae4308e | 6680 | vector signed char vec_srl (vector signed char, vector unsigned int); |
6681 | vector signed char vec_srl (vector signed char, vector unsigned short); | |
6682 | vector signed char vec_srl (vector signed char, vector unsigned char); | |
8bdbaccf | 6683 | vector unsigned char vec_srl (vector unsigned char, |
6684 | vector unsigned int); | |
6685 | vector unsigned char vec_srl (vector unsigned char, | |
6686 | vector unsigned short); | |
6687 | vector unsigned char vec_srl (vector unsigned char, | |
6688 | vector unsigned char); | |
0ae4308e | 6689 | |
6690 | vector float vec_sro (vector float, vector signed char); | |
6691 | vector float vec_sro (vector float, vector unsigned char); | |
6692 | vector signed int vec_sro (vector signed int, vector signed char); | |
6693 | vector signed int vec_sro (vector signed int, vector unsigned char); | |
6694 | vector unsigned int vec_sro (vector unsigned int, vector signed char); | |
6695 | vector unsigned int vec_sro (vector unsigned int, vector unsigned char); | |
6696 | ||
6697 | vector signed short vec_sro (vector signed short, vector signed char); | |
6698 | vector signed short vec_sro (vector signed short, vector unsigned char); | |
6699 | ||
8bdbaccf | 6700 | vector unsigned short vec_sro (vector unsigned short, |
6701 | vector signed char); | |
6702 | vector unsigned short vec_sro (vector unsigned short, | |
6703 | vector unsigned char); | |
0ae4308e | 6704 | vector signed char vec_sro (vector signed char, vector signed char); |
6705 | vector signed char vec_sro (vector signed char, vector unsigned char); | |
6706 | vector unsigned char vec_sro (vector unsigned char, vector signed char); | |
6707 | ||
8bdbaccf | 6708 | vector unsigned char vec_sro (vector unsigned char, |
6709 | vector unsigned char); | |
0ae4308e | 6710 | |
6711 | void vec_st (vector float, int, float *); | |
6712 | void vec_st (vector float, int, vector float *); | |
6713 | void vec_st (vector signed int, int, int *); | |
6714 | void vec_st (vector signed int, int, unsigned int *); | |
6715 | void vec_st (vector unsigned int, int, unsigned int *); | |
6716 | void vec_st (vector unsigned int, int, vector unsigned int *); | |
6717 | void vec_st (vector signed short, int, short *); | |
6718 | void vec_st (vector signed short, int, vector unsigned short *); | |
6719 | void vec_st (vector signed short, int, vector signed short *); | |
6720 | void vec_st (vector unsigned short, int, unsigned short *); | |
6721 | void vec_st (vector unsigned short, int, vector unsigned short *); | |
6722 | void vec_st (vector signed char, int, signed char *); | |
6723 | void vec_st (vector signed char, int, unsigned char *); | |
6724 | void vec_st (vector signed char, int, vector signed char *); | |
6725 | void vec_st (vector unsigned char, int, unsigned char *); | |
6726 | void vec_st (vector unsigned char, int, vector unsigned char *); | |
6727 | ||
6728 | void vec_ste (vector signed char, int, unsigned char *); | |
6729 | void vec_ste (vector signed char, int, signed char *); | |
6730 | void vec_ste (vector unsigned char, int, unsigned char *); | |
6731 | void vec_ste (vector signed short, int, short *); | |
6732 | void vec_ste (vector signed short, int, unsigned short *); | |
6733 | void vec_ste (vector unsigned short, int, void *); | |
6734 | void vec_ste (vector signed int, int, unsigned int *); | |
6735 | void vec_ste (vector signed int, int, int *); | |
6736 | void vec_ste (vector unsigned int, int, unsigned int *); | |
6737 | void vec_ste (vector float, int, float *); | |
6738 | ||
6739 | void vec_stl (vector float, int, vector float *); | |
6740 | void vec_stl (vector float, int, float *); | |
6741 | void vec_stl (vector signed int, int, vector signed int *); | |
6742 | void vec_stl (vector signed int, int, int *); | |
6743 | void vec_stl (vector signed int, int, unsigned int *); | |
6744 | void vec_stl (vector unsigned int, int, vector unsigned int *); | |
6745 | void vec_stl (vector unsigned int, int, unsigned int *); | |
6746 | void vec_stl (vector signed short, int, short *); | |
6747 | void vec_stl (vector signed short, int, unsigned short *); | |
6748 | void vec_stl (vector signed short, int, vector signed short *); | |
6749 | void vec_stl (vector unsigned short, int, unsigned short *); | |
6750 | void vec_stl (vector unsigned short, int, vector signed short *); | |
6751 | void vec_stl (vector signed char, int, signed char *); | |
6752 | void vec_stl (vector signed char, int, unsigned char *); | |
6753 | void vec_stl (vector signed char, int, vector signed char *); | |
6754 | void vec_stl (vector unsigned char, int, unsigned char *); | |
6755 | void vec_stl (vector unsigned char, int, vector unsigned char *); | |
6756 | ||
6757 | vector signed char vec_sub (vector signed char, vector signed char); | |
6758 | vector unsigned char vec_sub (vector signed char, vector unsigned char); | |
6759 | ||
6760 | vector unsigned char vec_sub (vector unsigned char, vector signed char); | |
6761 | ||
8bdbaccf | 6762 | vector unsigned char vec_sub (vector unsigned char, |
6763 | vector unsigned char); | |
0ae4308e | 6764 | vector signed short vec_sub (vector signed short, vector signed short); |
8bdbaccf | 6765 | vector unsigned short vec_sub (vector signed short, |
6766 | vector unsigned short); | |
6767 | vector unsigned short vec_sub (vector unsigned short, | |
6768 | vector signed short); | |
8e1103d3 | 6769 | vector unsigned short vec_sub (vector unsigned short, |
6770 | vector unsigned short); | |
0ae4308e | 6771 | vector signed int vec_sub (vector signed int, vector signed int); |
6772 | vector unsigned int vec_sub (vector signed int, vector unsigned int); | |
6773 | vector unsigned int vec_sub (vector unsigned int, vector signed int); | |
6774 | vector unsigned int vec_sub (vector unsigned int, vector unsigned int); | |
6775 | vector float vec_sub (vector float, vector float); | |
6776 | ||
6777 | vector unsigned int vec_subc (vector unsigned int, vector unsigned int); | |
6778 | ||
8bdbaccf | 6779 | vector unsigned char vec_subs (vector signed char, |
6780 | vector unsigned char); | |
6781 | vector unsigned char vec_subs (vector unsigned char, | |
6782 | vector signed char); | |
6783 | vector unsigned char vec_subs (vector unsigned char, | |
6784 | vector unsigned char); | |
0ae4308e | 6785 | vector signed char vec_subs (vector signed char, vector signed char); |
8bdbaccf | 6786 | vector unsigned short vec_subs (vector signed short, |
6787 | vector unsigned short); | |
6788 | vector unsigned short vec_subs (vector unsigned short, | |
6789 | vector signed short); | |
8e1103d3 | 6790 | vector unsigned short vec_subs (vector unsigned short, |
6791 | vector unsigned short); | |
0ae4308e | 6792 | vector signed short vec_subs (vector signed short, vector signed short); |
6793 | ||
6794 | vector unsigned int vec_subs (vector signed int, vector unsigned int); | |
6795 | vector unsigned int vec_subs (vector unsigned int, vector signed int); | |
6796 | vector unsigned int vec_subs (vector unsigned int, vector unsigned int); | |
6797 | ||
6798 | vector signed int vec_subs (vector signed int, vector signed int); | |
6799 | ||
8bdbaccf | 6800 | vector unsigned int vec_sum4s (vector unsigned char, |
6801 | vector unsigned int); | |
0ae4308e | 6802 | vector signed int vec_sum4s (vector signed char, vector signed int); |
6803 | vector signed int vec_sum4s (vector signed short, vector signed int); | |
6804 | ||
6805 | vector signed int vec_sum2s (vector signed int, vector signed int); | |
6806 | ||
6807 | vector signed int vec_sums (vector signed int, vector signed int); | |
6808 | ||
6809 | vector float vec_trunc (vector float); | |
6810 | ||
6811 | vector signed short vec_unpackh (vector signed char); | |
6812 | vector unsigned int vec_unpackh (vector signed short); | |
6813 | vector signed int vec_unpackh (vector signed short); | |
6814 | ||
6815 | vector signed short vec_unpackl (vector signed char); | |
6816 | vector unsigned int vec_unpackl (vector signed short); | |
6817 | vector signed int vec_unpackl (vector signed short); | |
6818 | ||
6819 | vector float vec_xor (vector float, vector float); | |
6820 | vector float vec_xor (vector float, vector signed int); | |
6821 | vector float vec_xor (vector signed int, vector float); | |
6822 | vector signed int vec_xor (vector signed int, vector signed int); | |
6823 | vector unsigned int vec_xor (vector signed int, vector unsigned int); | |
6824 | vector unsigned int vec_xor (vector unsigned int, vector signed int); | |
6825 | vector unsigned int vec_xor (vector unsigned int, vector unsigned int); | |
6826 | vector signed short vec_xor (vector signed short, vector signed short); | |
8bdbaccf | 6827 | vector unsigned short vec_xor (vector signed short, |
6828 | vector unsigned short); | |
6829 | vector unsigned short vec_xor (vector unsigned short, | |
6830 | vector signed short); | |
8e1103d3 | 6831 | vector unsigned short vec_xor (vector unsigned short, |
6832 | vector unsigned short); | |
0ae4308e | 6833 | vector signed char vec_xor (vector signed char, vector signed char); |
6834 | vector unsigned char vec_xor (vector signed char, vector unsigned char); | |
6835 | ||
6836 | vector unsigned char vec_xor (vector unsigned char, vector signed char); | |
6837 | ||
8bdbaccf | 6838 | vector unsigned char vec_xor (vector unsigned char, |
6839 | vector unsigned char); | |
0ae4308e | 6840 | |
6841 | vector signed int vec_all_eq (vector signed char, vector unsigned char); | |
6842 | ||
6843 | vector signed int vec_all_eq (vector signed char, vector signed char); | |
6844 | vector signed int vec_all_eq (vector unsigned char, vector signed char); | |
6845 | ||
8bdbaccf | 6846 | vector signed int vec_all_eq (vector unsigned char, |
6847 | vector unsigned char); | |
6848 | vector signed int vec_all_eq (vector signed short, | |
6849 | vector unsigned short); | |
0ae4308e | 6850 | vector signed int vec_all_eq (vector signed short, vector signed short); |
6851 | ||
8bdbaccf | 6852 | vector signed int vec_all_eq (vector unsigned short, |
6853 | vector signed short); | |
6854 | vector signed int vec_all_eq (vector unsigned short, | |
6855 | vector unsigned short); | |
0ae4308e | 6856 | vector signed int vec_all_eq (vector signed int, vector unsigned int); |
6857 | vector signed int vec_all_eq (vector signed int, vector signed int); | |
6858 | vector signed int vec_all_eq (vector unsigned int, vector signed int); | |
6859 | vector signed int vec_all_eq (vector unsigned int, vector unsigned int); | |
6860 | ||
6861 | vector signed int vec_all_eq (vector float, vector float); | |
6862 | ||
6863 | vector signed int vec_all_ge (vector signed char, vector unsigned char); | |
6864 | ||
6865 | vector signed int vec_all_ge (vector unsigned char, vector signed char); | |
6866 | ||
8bdbaccf | 6867 | vector signed int vec_all_ge (vector unsigned char, |
6868 | vector unsigned char); | |
0ae4308e | 6869 | vector signed int vec_all_ge (vector signed char, vector signed char); |
8bdbaccf | 6870 | vector signed int vec_all_ge (vector signed short, |
6871 | vector unsigned short); | |
6872 | vector signed int vec_all_ge (vector unsigned short, | |
6873 | vector signed short); | |
6874 | vector signed int vec_all_ge (vector unsigned short, | |
6875 | vector unsigned short); | |
0ae4308e | 6876 | vector signed int vec_all_ge (vector signed short, vector signed short); |
6877 | ||
6878 | vector signed int vec_all_ge (vector signed int, vector unsigned int); | |
6879 | vector signed int vec_all_ge (vector unsigned int, vector signed int); | |
6880 | vector signed int vec_all_ge (vector unsigned int, vector unsigned int); | |
6881 | ||
6882 | vector signed int vec_all_ge (vector signed int, vector signed int); | |
6883 | vector signed int vec_all_ge (vector float, vector float); | |
6884 | ||
6885 | vector signed int vec_all_gt (vector signed char, vector unsigned char); | |
6886 | ||
6887 | vector signed int vec_all_gt (vector unsigned char, vector signed char); | |
6888 | ||
8bdbaccf | 6889 | vector signed int vec_all_gt (vector unsigned char, |
6890 | vector unsigned char); | |
0ae4308e | 6891 | vector signed int vec_all_gt (vector signed char, vector signed char); |
8bdbaccf | 6892 | vector signed int vec_all_gt (vector signed short, |
6893 | vector unsigned short); | |
228c5b30 | 6894 | vector signed int vec_all_gt (vector unsigned short, |
8bdbaccf | 6895 | vector signed short); |
6896 | vector signed int vec_all_gt (vector unsigned short, | |
6897 | vector unsigned short); | |
0ae4308e | 6898 | vector signed int vec_all_gt (vector signed short, vector signed short); |
6899 | ||
6900 | vector signed int vec_all_gt (vector signed int, vector unsigned int); | |
6901 | vector signed int vec_all_gt (vector unsigned int, vector signed int); | |
6902 | vector signed int vec_all_gt (vector unsigned int, vector unsigned int); | |
6903 | ||
6904 | vector signed int vec_all_gt (vector signed int, vector signed int); | |
6905 | vector signed int vec_all_gt (vector float, vector float); | |
6906 | ||
6907 | vector signed int vec_all_in (vector float, vector float); | |
6908 | ||
6909 | vector signed int vec_all_le (vector signed char, vector unsigned char); | |
6910 | ||
6911 | vector signed int vec_all_le (vector unsigned char, vector signed char); | |
6912 | ||
8bdbaccf | 6913 | vector signed int vec_all_le (vector unsigned char, |
6914 | vector unsigned char); | |
0ae4308e | 6915 | vector signed int vec_all_le (vector signed char, vector signed char); |
8bdbaccf | 6916 | vector signed int vec_all_le (vector signed short, |
6917 | vector unsigned short); | |
6918 | vector signed int vec_all_le (vector unsigned short, | |
6919 | vector signed short); | |
6920 | vector signed int vec_all_le (vector unsigned short, | |
6921 | vector unsigned short); | |
0ae4308e | 6922 | vector signed int vec_all_le (vector signed short, vector signed short); |
6923 | ||
6924 | vector signed int vec_all_le (vector signed int, vector unsigned int); | |
6925 | vector signed int vec_all_le (vector unsigned int, vector signed int); | |
6926 | vector signed int vec_all_le (vector unsigned int, vector unsigned int); | |
6927 | ||
6928 | vector signed int vec_all_le (vector signed int, vector signed int); | |
6929 | vector signed int vec_all_le (vector float, vector float); | |
6930 | ||
6931 | vector signed int vec_all_lt (vector signed char, vector unsigned char); | |
6932 | ||
6933 | vector signed int vec_all_lt (vector unsigned char, vector signed char); | |
6934 | ||
8bdbaccf | 6935 | vector signed int vec_all_lt (vector unsigned char, |
6936 | vector unsigned char); | |
0ae4308e | 6937 | vector signed int vec_all_lt (vector signed char, vector signed char); |
8bdbaccf | 6938 | vector signed int vec_all_lt (vector signed short, |
6939 | vector unsigned short); | |
6940 | vector signed int vec_all_lt (vector unsigned short, | |
6941 | vector signed short); | |
6942 | vector signed int vec_all_lt (vector unsigned short, | |
6943 | vector unsigned short); | |
0ae4308e | 6944 | vector signed int vec_all_lt (vector signed short, vector signed short); |
6945 | ||
6946 | vector signed int vec_all_lt (vector signed int, vector unsigned int); | |
6947 | vector signed int vec_all_lt (vector unsigned int, vector signed int); | |
6948 | vector signed int vec_all_lt (vector unsigned int, vector unsigned int); | |
6949 | ||
6950 | vector signed int vec_all_lt (vector signed int, vector signed int); | |
6951 | vector signed int vec_all_lt (vector float, vector float); | |
6952 | ||
6953 | vector signed int vec_all_nan (vector float); | |
6954 | ||
6955 | vector signed int vec_all_ne (vector signed char, vector unsigned char); | |
6956 | ||
6957 | vector signed int vec_all_ne (vector signed char, vector signed char); | |
6958 | vector signed int vec_all_ne (vector unsigned char, vector signed char); | |
6959 | ||
8bdbaccf | 6960 | vector signed int vec_all_ne (vector unsigned char, |
6961 | vector unsigned char); | |
6962 | vector signed int vec_all_ne (vector signed short, | |
6963 | vector unsigned short); | |
0ae4308e | 6964 | vector signed int vec_all_ne (vector signed short, vector signed short); |
6965 | ||
8bdbaccf | 6966 | vector signed int vec_all_ne (vector unsigned short, |
6967 | vector signed short); | |
6968 | vector signed int vec_all_ne (vector unsigned short, | |
6969 | vector unsigned short); | |
0ae4308e | 6970 | vector signed int vec_all_ne (vector signed int, vector unsigned int); |
6971 | vector signed int vec_all_ne (vector signed int, vector signed int); | |
6972 | vector signed int vec_all_ne (vector unsigned int, vector signed int); | |
6973 | vector signed int vec_all_ne (vector unsigned int, vector unsigned int); | |
6974 | ||
6975 | vector signed int vec_all_ne (vector float, vector float); | |
6976 | ||
6977 | vector signed int vec_all_nge (vector float, vector float); | |
6978 | ||
6979 | vector signed int vec_all_ngt (vector float, vector float); | |
6980 | ||
6981 | vector signed int vec_all_nle (vector float, vector float); | |
6982 | ||
6983 | vector signed int vec_all_nlt (vector float, vector float); | |
6984 | ||
6985 | vector signed int vec_all_numeric (vector float); | |
6986 | ||
6987 | vector signed int vec_any_eq (vector signed char, vector unsigned char); | |
6988 | ||
6989 | vector signed int vec_any_eq (vector signed char, vector signed char); | |
6990 | vector signed int vec_any_eq (vector unsigned char, vector signed char); | |
6991 | ||
8bdbaccf | 6992 | vector signed int vec_any_eq (vector unsigned char, |
6993 | vector unsigned char); | |
6994 | vector signed int vec_any_eq (vector signed short, | |
6995 | vector unsigned short); | |
0ae4308e | 6996 | vector signed int vec_any_eq (vector signed short, vector signed short); |
6997 | ||
8bdbaccf | 6998 | vector signed int vec_any_eq (vector unsigned short, |
6999 | vector signed short); | |
7000 | vector signed int vec_any_eq (vector unsigned short, | |
7001 | vector unsigned short); | |
0ae4308e | 7002 | vector signed int vec_any_eq (vector signed int, vector unsigned int); |
7003 | vector signed int vec_any_eq (vector signed int, vector signed int); | |
7004 | vector signed int vec_any_eq (vector unsigned int, vector signed int); | |
7005 | vector signed int vec_any_eq (vector unsigned int, vector unsigned int); | |
7006 | ||
7007 | vector signed int vec_any_eq (vector float, vector float); | |
7008 | ||
7009 | vector signed int vec_any_ge (vector signed char, vector unsigned char); | |
7010 | ||
7011 | vector signed int vec_any_ge (vector unsigned char, vector signed char); | |
7012 | ||
8bdbaccf | 7013 | vector signed int vec_any_ge (vector unsigned char, |
7014 | vector unsigned char); | |
0ae4308e | 7015 | vector signed int vec_any_ge (vector signed char, vector signed char); |
8bdbaccf | 7016 | vector signed int vec_any_ge (vector signed short, |
7017 | vector unsigned short); | |
7018 | vector signed int vec_any_ge (vector unsigned short, | |
7019 | vector signed short); | |
7020 | vector signed int vec_any_ge (vector unsigned short, | |
7021 | vector unsigned short); | |
0ae4308e | 7022 | vector signed int vec_any_ge (vector signed short, vector signed short); |
7023 | ||
7024 | vector signed int vec_any_ge (vector signed int, vector unsigned int); | |
7025 | vector signed int vec_any_ge (vector unsigned int, vector signed int); | |
7026 | vector signed int vec_any_ge (vector unsigned int, vector unsigned int); | |
7027 | ||
7028 | vector signed int vec_any_ge (vector signed int, vector signed int); | |
7029 | vector signed int vec_any_ge (vector float, vector float); | |
7030 | ||
7031 | vector signed int vec_any_gt (vector signed char, vector unsigned char); | |
7032 | ||
7033 | vector signed int vec_any_gt (vector unsigned char, vector signed char); | |
7034 | ||
8bdbaccf | 7035 | vector signed int vec_any_gt (vector unsigned char, |
7036 | vector unsigned char); | |
0ae4308e | 7037 | vector signed int vec_any_gt (vector signed char, vector signed char); |
8bdbaccf | 7038 | vector signed int vec_any_gt (vector signed short, |
7039 | vector unsigned short); | |
7040 | vector signed int vec_any_gt (vector unsigned short, | |
7041 | vector signed short); | |
7042 | vector signed int vec_any_gt (vector unsigned short, | |
7043 | vector unsigned short); | |
0ae4308e | 7044 | vector signed int vec_any_gt (vector signed short, vector signed short); |
7045 | ||
7046 | vector signed int vec_any_gt (vector signed int, vector unsigned int); | |
7047 | vector signed int vec_any_gt (vector unsigned int, vector signed int); | |
7048 | vector signed int vec_any_gt (vector unsigned int, vector unsigned int); | |
7049 | ||
7050 | vector signed int vec_any_gt (vector signed int, vector signed int); | |
7051 | vector signed int vec_any_gt (vector float, vector float); | |
7052 | ||
7053 | vector signed int vec_any_le (vector signed char, vector unsigned char); | |
7054 | ||
7055 | vector signed int vec_any_le (vector unsigned char, vector signed char); | |
7056 | ||
8bdbaccf | 7057 | vector signed int vec_any_le (vector unsigned char, |
7058 | vector unsigned char); | |
0ae4308e | 7059 | vector signed int vec_any_le (vector signed char, vector signed char); |
8bdbaccf | 7060 | vector signed int vec_any_le (vector signed short, |
7061 | vector unsigned short); | |
7062 | vector signed int vec_any_le (vector unsigned short, | |
7063 | vector signed short); | |
7064 | vector signed int vec_any_le (vector unsigned short, | |
7065 | vector unsigned short); | |
0ae4308e | 7066 | vector signed int vec_any_le (vector signed short, vector signed short); |
7067 | ||
7068 | vector signed int vec_any_le (vector signed int, vector unsigned int); | |
7069 | vector signed int vec_any_le (vector unsigned int, vector signed int); | |
7070 | vector signed int vec_any_le (vector unsigned int, vector unsigned int); | |
7071 | ||
7072 | vector signed int vec_any_le (vector signed int, vector signed int); | |
7073 | vector signed int vec_any_le (vector float, vector float); | |
7074 | ||
7075 | vector signed int vec_any_lt (vector signed char, vector unsigned char); | |
7076 | ||
7077 | vector signed int vec_any_lt (vector unsigned char, vector signed char); | |
7078 | ||
8bdbaccf | 7079 | vector signed int vec_any_lt (vector unsigned char, |
7080 | vector unsigned char); | |
0ae4308e | 7081 | vector signed int vec_any_lt (vector signed char, vector signed char); |
8bdbaccf | 7082 | vector signed int vec_any_lt (vector signed short, |
7083 | vector unsigned short); | |
7084 | vector signed int vec_any_lt (vector unsigned short, | |
7085 | vector signed short); | |
7086 | vector signed int vec_any_lt (vector unsigned short, | |
7087 | vector unsigned short); | |
0ae4308e | 7088 | vector signed int vec_any_lt (vector signed short, vector signed short); |
7089 | ||
7090 | vector signed int vec_any_lt (vector signed int, vector unsigned int); | |
7091 | vector signed int vec_any_lt (vector unsigned int, vector signed int); | |
7092 | vector signed int vec_any_lt (vector unsigned int, vector unsigned int); | |
7093 | ||
7094 | vector signed int vec_any_lt (vector signed int, vector signed int); | |
7095 | vector signed int vec_any_lt (vector float, vector float); | |
7096 | ||
7097 | vector signed int vec_any_nan (vector float); | |
7098 | ||
7099 | vector signed int vec_any_ne (vector signed char, vector unsigned char); | |
7100 | ||
7101 | vector signed int vec_any_ne (vector signed char, vector signed char); | |
7102 | vector signed int vec_any_ne (vector unsigned char, vector signed char); | |
7103 | ||
8bdbaccf | 7104 | vector signed int vec_any_ne (vector unsigned char, |
7105 | vector unsigned char); | |
7106 | vector signed int vec_any_ne (vector signed short, | |
7107 | vector unsigned short); | |
0ae4308e | 7108 | vector signed int vec_any_ne (vector signed short, vector signed short); |
7109 | ||
8bdbaccf | 7110 | vector signed int vec_any_ne (vector unsigned short, |
7111 | vector signed short); | |
7112 | vector signed int vec_any_ne (vector unsigned short, | |
7113 | vector unsigned short); | |
0ae4308e | 7114 | vector signed int vec_any_ne (vector signed int, vector unsigned int); |
7115 | vector signed int vec_any_ne (vector signed int, vector signed int); | |
7116 | vector signed int vec_any_ne (vector unsigned int, vector signed int); | |
7117 | vector signed int vec_any_ne (vector unsigned int, vector unsigned int); | |
7118 | ||
7119 | vector signed int vec_any_ne (vector float, vector float); | |
7120 | ||
7121 | vector signed int vec_any_nge (vector float, vector float); | |
7122 | ||
7123 | vector signed int vec_any_ngt (vector float, vector float); | |
7124 | ||
7125 | vector signed int vec_any_nle (vector float, vector float); | |
7126 | ||
7127 | vector signed int vec_any_nlt (vector float, vector float); | |
7128 | ||
7129 | vector signed int vec_any_numeric (vector float); | |
7130 | ||
7131 | vector signed int vec_any_out (vector float, vector float); | |
7132 | @end smallexample | |
7133 | ||
49f45d83 | 7134 | @node Pragmas |
7135 | @section Pragmas Accepted by GCC | |
7136 | @cindex pragmas | |
7137 | @cindex #pragma | |
7138 | ||
7139 | GCC supports several types of pragmas, primarily in order to compile | |
7140 | code originally written for other compilers. Note that in general | |
7141 | we do not recommend the use of pragmas; @xref{Function Attributes}, | |
7142 | for further explanation. | |
7143 | ||
7144 | @menu | |
7145 | * ARM Pragmas:: | |
edd2f2ae | 7146 | * RS/6000 and PowerPC Pragmas:: |
49f45d83 | 7147 | * Darwin Pragmas:: |
ea42c4de | 7148 | * Solaris Pragmas:: |
7149 | * Tru64 Pragmas:: | |
49f45d83 | 7150 | @end menu |
7151 | ||
7152 | @node ARM Pragmas | |
7153 | @subsection ARM Pragmas | |
7154 | ||
7155 | The ARM target defines pragmas for controlling the default addition of | |
7156 | @code{long_call} and @code{short_call} attributes to functions. | |
7157 | @xref{Function Attributes}, for information about the effects of these | |
7158 | attributes. | |
7159 | ||
7160 | @table @code | |
7161 | @item long_calls | |
7162 | @cindex pragma, long_calls | |
7163 | Set all subsequent functions to have the @code{long_call} attribute. | |
7164 | ||
7165 | @item no_long_calls | |
7166 | @cindex pragma, no_long_calls | |
7167 | Set all subsequent functions to have the @code{short_call} attribute. | |
7168 | ||
7169 | @item long_calls_off | |
7170 | @cindex pragma, long_calls_off | |
7171 | Do not affect the @code{long_call} or @code{short_call} attributes of | |
7172 | subsequent functions. | |
7173 | @end table | |
7174 | ||
edd2f2ae | 7175 | @node RS/6000 and PowerPC Pragmas |
7176 | @subsection RS/6000 and PowerPC Pragmas | |
7177 | ||
7178 | The RS/6000 and PowerPC targets define one pragma for controlling | |
7179 | whether or not the @code{longcall} attribute is added to function | |
7180 | declarations by default. This pragma overrides the @option{-mlongcall} | |
85456819 | 7181 | option, but not the @code{longcall} and @code{shortcall} attributes. |
edd2f2ae | 7182 | @xref{RS/6000 and PowerPC Options}, for more information about when long |
7183 | calls are and are not necessary. | |
7184 | ||
7185 | @table @code | |
7186 | @item longcall (1) | |
7187 | @cindex pragma, longcall | |
7188 | Apply the @code{longcall} attribute to all subsequent function | |
7189 | declarations. | |
7190 | ||
7191 | @item longcall (0) | |
7192 | Do not apply the @code{longcall} attribute to subsequent function | |
7193 | declarations. | |
7194 | @end table | |
7195 | ||
49f45d83 | 7196 | @c Describe c4x pragmas here. |
7197 | @c Describe h8300 pragmas here. | |
7198 | @c Describe i370 pragmas here. | |
7199 | @c Describe i960 pragmas here. | |
7200 | @c Describe sh pragmas here. | |
7201 | @c Describe v850 pragmas here. | |
7202 | ||
7203 | @node Darwin Pragmas | |
7204 | @subsection Darwin Pragmas | |
7205 | ||
7206 | The following pragmas are available for all architectures running the | |
7207 | Darwin operating system. These are useful for compatibility with other | |
1c95bb8d | 7208 | Mac OS compilers. |
49f45d83 | 7209 | |
7210 | @table @code | |
7211 | @item mark @var{tokens}@dots{} | |
7212 | @cindex pragma, mark | |
7213 | This pragma is accepted, but has no effect. | |
7214 | ||
7215 | @item options align=@var{alignment} | |
7216 | @cindex pragma, options align | |
7217 | This pragma sets the alignment of fields in structures. The values of | |
7218 | @var{alignment} may be @code{mac68k}, to emulate m68k alignment, or | |
7219 | @code{power}, to emulate PowerPC alignment. Uses of this pragma nest | |
7220 | properly; to restore the previous setting, use @code{reset} for the | |
7221 | @var{alignment}. | |
7222 | ||
7223 | @item segment @var{tokens}@dots{} | |
7224 | @cindex pragma, segment | |
7225 | This pragma is accepted, but has no effect. | |
7226 | ||
7227 | @item unused (@var{var} [, @var{var}]@dots{}) | |
7228 | @cindex pragma, unused | |
7229 | This pragma declares variables to be possibly unused. GCC will not | |
7230 | produce warnings for the listed variables. The effect is similar to | |
7231 | that of the @code{unused} attribute, except that this pragma may appear | |
7232 | anywhere within the variables' scopes. | |
7233 | @end table | |
7234 | ||
ea42c4de | 7235 | @node Solaris Pragmas |
7236 | @subsection Solaris Pragmas | |
7237 | ||
7238 | For compatibility with the SunPRO compiler, the following pragma | |
7239 | is supported. | |
7240 | ||
7241 | @table @code | |
7242 | @item redefine_extname @var{oldname} @var{newname} | |
7243 | @cindex pragma, redefine_extname | |
7244 | ||
7245 | This pragma gives the C function @var{oldname} the assembler label | |
7246 | @var{newname}. The pragma must appear before the function declaration. | |
7247 | This pragma is equivalent to the asm labels extension (@pxref{Asm | |
7248 | Labels}). The preprocessor defines @code{__PRAGMA_REDEFINE_EXTNAME} | |
7249 | if the pragma is available. | |
7250 | @end table | |
7251 | ||
7252 | @node Tru64 Pragmas | |
7253 | @subsection Tru64 Pragmas | |
7254 | ||
7255 | For compatibility with the Compaq C compiler, the following pragma | |
7256 | is supported. | |
7257 | ||
7258 | @table @code | |
7259 | @item extern_prefix @var{string} | |
7260 | @cindex pragma, extern_prefix | |
7261 | ||
7262 | This pragma renames all subsequent function and variable declarations | |
7263 | such that @var{string} is prepended to the name. This effect may be | |
85456819 | 7264 | terminated by using another @code{extern_prefix} pragma with the |
ea42c4de | 7265 | empty string. |
7266 | ||
7267 | This pragma is similar in intent to to the asm labels extension | |
7268 | (@pxref{Asm Labels}) in that the system programmer wants to change | |
7269 | the assembly-level ABI without changing the source-level API. The | |
219cff1b | 7270 | preprocessor defines @code{__PRAGMA_EXTERN_PREFIX} if the pragma is |
7271 | available. | |
ea42c4de | 7272 | @end table |
7273 | ||
7cb6c162 | 7274 | @node Unnamed Fields |
7275 | @section Unnamed struct/union fields within structs/unions. | |
7276 | @cindex struct | |
7277 | @cindex union | |
7278 | ||
7279 | For compatibility with other compilers, GCC allows you to define | |
7280 | a structure or union that contains, as fields, structures and unions | |
7281 | without names. For example: | |
7282 | ||
7283 | @example | |
7284 | struct @{ | |
7285 | int a; | |
7286 | union @{ | |
7287 | int b; | |
7288 | float c; | |
7289 | @}; | |
7290 | int d; | |
7291 | @} foo; | |
7292 | @end example | |
7293 | ||
7294 | In this example, the user would be able to access members of the unnamed | |
7295 | union with code like @samp{foo.b}. Note that only unnamed structs and | |
7296 | unions are allowed, you may not have, for example, an unnamed | |
7297 | @code{int}. | |
7298 | ||
7299 | You must never create such structures that cause ambiguous field definitions. | |
7300 | For example, this structure: | |
7301 | ||
7302 | @example | |
7303 | struct @{ | |
7304 | int a; | |
7305 | struct @{ | |
7306 | int a; | |
7307 | @}; | |
7308 | @} foo; | |
7309 | @end example | |
7310 | ||
7311 | It is ambiguous which @code{a} is being referred to with @samp{foo.a}. | |
7312 | Such constructs are not supported and must be avoided. In the future, | |
7313 | such constructs may be detected and treated as compilation errors. | |
7314 | ||
2a6f0f81 | 7315 | @node Thread-Local |
7316 | @section Thread-Local Storage | |
7317 | @cindex Thread-Local Storage | |
abf68e10 | 7318 | @cindex @acronym{TLS} |
2a6f0f81 | 7319 | @cindex __thread |
7320 | ||
abf68e10 | 7321 | Thread-local storage (@acronym{TLS}) is a mechanism by which variables |
7322 | are allocated such that there is one instance of the variable per extant | |
2a6f0f81 | 7323 | thread. The run-time model GCC uses to implement this originates |
7324 | in the IA-64 processor-specific ABI, but has since been migrated | |
7325 | to other processors as well. It requires significant support from | |
7326 | the linker (@command{ld}), dynamic linker (@command{ld.so}), and | |
7327 | system libraries (@file{libc.so} and @file{libpthread.so}), so it | |
abf68e10 | 7328 | is not available everywhere. |
2a6f0f81 | 7329 | |
7330 | At the user level, the extension is visible with a new storage | |
7331 | class keyword: @code{__thread}. For example: | |
7332 | ||
7333 | @example | |
7334 | __thread int i; | |
7335 | extern __thread struct state s; | |
7336 | static __thread char *p; | |
7337 | @end example | |
7338 | ||
7339 | The @code{__thread} specifier may be used alone, with the @code{extern} | |
7340 | or @code{static} specifiers, but with no other storage class specifier. | |
7341 | When used with @code{extern} or @code{static}, @code{__thread} must appear | |
7342 | immediately after the other storage class specifier. | |
7343 | ||
7344 | The @code{__thread} specifier may be applied to any global, file-scoped | |
4facf21c | 7345 | static, function-scoped static, or static data member of a class. It may |
7346 | not be applied to block-scoped automatic or non-static data member. | |
2a6f0f81 | 7347 | |
7348 | When the address-of operator is applied to a thread-local variable, it is | |
7349 | evaluated at run-time and returns the address of the current thread's | |
7350 | instance of that variable. An address so obtained may be used by any | |
7351 | thread. When a thread terminates, any pointers to thread-local variables | |
7352 | in that thread become invalid. | |
7353 | ||
7354 | No static initialization may refer to the address of a thread-local variable. | |
7355 | ||
4facf21c | 7356 | In C++, if an initializer is present for a thread-local variable, it must |
7357 | be a @var{constant-expression}, as defined in 5.19.2 of the ANSI/ISO C++ | |
7358 | standard. | |
2a6f0f81 | 7359 | |
7360 | See @uref{http://people.redhat.com/drepper/tls.pdf, | |
7361 | ELF Handling For Thread-Local Storage} for a detailed explanation of | |
7362 | the four thread-local storage addressing models, and how the run-time | |
7363 | is expected to function. | |
7364 | ||
abf68e10 | 7365 | @menu |
7366 | * C99 Thread-Local Edits:: | |
7367 | * C++98 Thread-Local Edits:: | |
7368 | @end menu | |
7369 | ||
7370 | @node C99 Thread-Local Edits | |
7371 | @subsection ISO/IEC 9899:1999 Edits for Thread-Local Storage | |
7372 | ||
7373 | The following are a set of changes to ISO/IEC 9899:1999 (aka C99) | |
7374 | that document the exact semantics of the language extension. | |
7375 | ||
7376 | @itemize @bullet | |
7377 | @item | |
7378 | @cite{5.1.2 Execution environments} | |
7379 | ||
7380 | Add new text after paragraph 1 | |
7381 | ||
7382 | @quotation | |
7383 | Within either execution environment, a @dfn{thread} is a flow of | |
7384 | control within a program. It is implementation defined whether | |
7385 | or not there may be more than one thread associated with a program. | |
7386 | It is implementation defined how threads beyond the first are | |
7387 | created, the name and type of the function called at thread | |
7388 | startup, and how threads may be terminated. However, objects | |
7389 | with thread storage duration shall be initialized before thread | |
7390 | startup. | |
7391 | @end quotation | |
7392 | ||
7393 | @item | |
7394 | @cite{6.2.4 Storage durations of objects} | |
7395 | ||
7396 | Add new text before paragraph 3 | |
7397 | ||
7398 | @quotation | |
7399 | An object whose identifier is declared with the storage-class | |
7400 | specifier @w{@code{__thread}} has @dfn{thread storage duration}. | |
7401 | Its lifetime is the entire execution of the thread, and its | |
7402 | stored value is initialized only once, prior to thread startup. | |
7403 | @end quotation | |
7404 | ||
7405 | @item | |
7406 | @cite{6.4.1 Keywords} | |
7407 | ||
7408 | Add @code{__thread}. | |
7409 | ||
7410 | @item | |
7411 | @cite{6.7.1 Storage-class specifiers} | |
7412 | ||
7413 | Add @code{__thread} to the list of storage class specifiers in | |
7414 | paragraph 1. | |
7415 | ||
7416 | Change paragraph 2 to | |
7417 | ||
7418 | @quotation | |
7419 | With the exception of @code{__thread}, at most one storage-class | |
7420 | specifier may be given [@dots{}]. The @code{__thread} specifier may | |
7421 | be used alone, or immediately following @code{extern} or | |
7422 | @code{static}. | |
7423 | @end quotation | |
7424 | ||
7425 | Add new text after paragraph 6 | |
7426 | ||
7427 | @quotation | |
7428 | The declaration of an identifier for a variable that has | |
7429 | block scope that specifies @code{__thread} shall also | |
7430 | specify either @code{extern} or @code{static}. | |
7431 | ||
7432 | The @code{__thread} specifier shall be used only with | |
7433 | variables. | |
7434 | @end quotation | |
7435 | @end itemize | |
7436 | ||
7437 | @node C++98 Thread-Local Edits | |
7438 | @subsection ISO/IEC 14882:1998 Edits for Thread-Local Storage | |
7439 | ||
7440 | The following are a set of changes to ISO/IEC 14882:1998 (aka C++98) | |
7441 | that document the exact semantics of the language extension. | |
7442 | ||
7443 | @itemize @bullet | |
258b58a9 | 7444 | @item |
abf68e10 | 7445 | @b{[intro.execution]} |
7446 | ||
7447 | New text after paragraph 4 | |
7448 | ||
7449 | @quotation | |
7450 | A @dfn{thread} is a flow of control within the abstract machine. | |
7451 | It is implementation defined whether or not there may be more than | |
7452 | one thread. | |
7453 | @end quotation | |
7454 | ||
7455 | New text after paragraph 7 | |
7456 | ||
7457 | @quotation | |
85456819 | 7458 | It is unspecified whether additional action must be taken to |
abf68e10 | 7459 | ensure when and whether side effects are visible to other threads. |
7460 | @end quotation | |
7461 | ||
7462 | @item | |
7463 | @b{[lex.key]} | |
7464 | ||
7465 | Add @code{__thread}. | |
7466 | ||
7467 | @item | |
7468 | @b{[basic.start.main]} | |
7469 | ||
7470 | Add after paragraph 5 | |
7471 | ||
7472 | @quotation | |
7473 | The thread that begins execution at the @code{main} function is called | |
85456819 | 7474 | the @dfn{main thread}. It is implementation defined how functions |
abf68e10 | 7475 | beginning threads other than the main thread are designated or typed. |
7476 | A function so designated, as well as the @code{main} function, is called | |
7477 | a @dfn{thread startup function}. It is implementation defined what | |
7478 | happens if a thread startup function returns. It is implementation | |
7479 | defined what happens to other threads when any thread calls @code{exit}. | |
7480 | @end quotation | |
7481 | ||
7482 | @item | |
7483 | @b{[basic.start.init]} | |
7484 | ||
7485 | Add after paragraph 4 | |
7486 | ||
7487 | @quotation | |
7488 | The storage for an object of thread storage duration shall be | |
a99e98db | 7489 | statically initialized before the first statement of the thread startup |
abf68e10 | 7490 | function. An object of thread storage duration shall not require |
7491 | dynamic initialization. | |
7492 | @end quotation | |
7493 | ||
7494 | @item | |
7495 | @b{[basic.start.term]} | |
7496 | ||
7497 | Add after paragraph 3 | |
7498 | ||
7499 | @quotation | |
4facf21c | 7500 | The type of an object with thread storage duration shall not have a |
7501 | non-trivial destructor, nor shall it be an array type whose elements | |
7502 | (directly or indirectly) have non-trivial destructors. | |
abf68e10 | 7503 | @end quotation |
7504 | ||
7505 | @item | |
7506 | @b{[basic.stc]} | |
7507 | ||
7508 | Add ``thread storage duration'' to the list in paragraph 1. | |
7509 | ||
7510 | Change paragraph 2 | |
7511 | ||
7512 | @quotation | |
7513 | Thread, static, and automatic storage durations are associated with | |
7514 | objects introduced by declarations [@dots{}]. | |
7515 | @end quotation | |
7516 | ||
7517 | Add @code{__thread} to the list of specifiers in paragraph 3. | |
7518 | ||
7519 | @item | |
7520 | @b{[basic.stc.thread]} | |
7521 | ||
7522 | New section before @b{[basic.stc.static]} | |
7523 | ||
7524 | @quotation | |
299006ee | 7525 | The keyword @code{__thread} applied to a non-local object gives the |
abf68e10 | 7526 | object thread storage duration. |
7527 | ||
7528 | A local variable or class data member declared both @code{static} | |
7529 | and @code{__thread} gives the variable or member thread storage | |
7530 | duration. | |
7531 | @end quotation | |
7532 | ||
7533 | @item | |
7534 | @b{[basic.stc.static]} | |
7535 | ||
7536 | Change paragraph 1 | |
7537 | ||
7538 | @quotation | |
7539 | All objects which have neither thread storage duration, dynamic | |
7540 | storage duration nor are local [@dots{}]. | |
7541 | @end quotation | |
7542 | ||
7543 | @item | |
7544 | @b{[dcl.stc]} | |
7545 | ||
7546 | Add @code{__thread} to the list in paragraph 1. | |
7547 | ||
7548 | Change paragraph 1 | |
7549 | ||
7550 | @quotation | |
7551 | With the exception of @code{__thread}, at most one | |
7552 | @var{storage-class-specifier} shall appear in a given | |
7553 | @var{decl-specifier-seq}. The @code{__thread} specifier may | |
7554 | be used alone, or immediately following the @code{extern} or | |
7555 | @code{static} specifiers. [@dots{}] | |
7556 | @end quotation | |
7557 | ||
7558 | Add after paragraph 5 | |
7559 | ||
7560 | @quotation | |
7561 | The @code{__thread} specifier can be applied only to the names of objects | |
7562 | and to anonymous unions. | |
7563 | @end quotation | |
7564 | ||
7565 | @item | |
7566 | @b{[class.mem]} | |
7567 | ||
7568 | Add after paragraph 6 | |
7569 | ||
7570 | @quotation | |
7571 | Non-@code{static} members shall not be @code{__thread}. | |
7572 | @end quotation | |
7573 | @end itemize | |
7574 | ||
146ef39f | 7575 | @node C++ Extensions |
7576 | @chapter Extensions to the C++ Language | |
7577 | @cindex extensions, C++ language | |
7578 | @cindex C++ language extensions | |
7579 | ||
7580 | The GNU compiler provides these extensions to the C++ language (and you | |
7581 | can also use most of the C language extensions in your C++ programs). If you | |
7582 | want to write code that checks whether these features are available, you can | |
7583 | test for the GNU compiler the same way as for C programs: check for a | |
7584 | predefined macro @code{__GNUC__}. You can also use @code{__GNUG__} to | |
7585 | test specifically for GNU C++ (@pxref{Standard Predefined,,Standard | |
7586 | Predefined Macros,cpp.info,The C Preprocessor}). | |
7587 | ||
7588 | @menu | |
146ef39f | 7589 | * Min and Max:: C++ Minimum and maximum operators. |
b1a8d4ce | 7590 | * Volatiles:: What constitutes an access to a volatile object. |
dbe4c49e | 7591 | * Restricted Pointers:: C99 restricted pointers and references. |
a89b0e97 | 7592 | * Vague Linkage:: Where G++ puts inlines, vtables and such. |
146ef39f | 7593 | * C++ Interface:: You can use a single C++ header file for both |
64b04d50 | 7594 | declarations and definitions. |
146ef39f | 7595 | * Template Instantiation:: Methods for ensuring that exactly one copy of |
64b04d50 | 7596 | each needed template instantiation is emitted. |
8b76b461 | 7597 | * Bound member functions:: You can extract a function pointer to the |
7598 | method denoted by a @samp{->*} or @samp{.*} expression. | |
64b04d50 | 7599 | * C++ Attributes:: Variable, function, and type attributes for C++ only. |
6df8a9dd | 7600 | * Java Exceptions:: Tweaking exception handling to work with Java. |
a77827f5 | 7601 | * Deprecated Features:: Things will disappear from g++. |
64b04d50 | 7602 | * Backwards Compatibility:: Compatibilities with earlier definitions of C++. |
146ef39f | 7603 | @end menu |
7604 | ||
146ef39f | 7605 | @node Min and Max |
7606 | @section Minimum and Maximum Operators in C++ | |
7607 | ||
7608 | It is very convenient to have operators which return the ``minimum'' or the | |
7609 | ``maximum'' of two arguments. In GNU C++ (but not in GNU C), | |
7610 | ||
7611 | @table @code | |
7612 | @item @var{a} <? @var{b} | |
7613 | @findex <? | |
7614 | @cindex minimum operator | |
7615 | is the @dfn{minimum}, returning the smaller of the numeric values | |
7616 | @var{a} and @var{b}; | |
7617 | ||
7618 | @item @var{a} >? @var{b} | |
7619 | @findex >? | |
7620 | @cindex maximum operator | |
7621 | is the @dfn{maximum}, returning the larger of the numeric values @var{a} | |
7622 | and @var{b}. | |
7623 | @end table | |
7624 | ||
7625 | These operations are not primitive in ordinary C++, since you can | |
7626 | use a macro to return the minimum of two things in C++, as in the | |
7627 | following example. | |
7628 | ||
7629 | @example | |
7630 | #define MIN(X,Y) ((X) < (Y) ? : (X) : (Y)) | |
7631 | @end example | |
7632 | ||
7633 | @noindent | |
7634 | You might then use @w{@samp{int min = MIN (i, j);}} to set @var{min} to | |
7635 | the minimum value of variables @var{i} and @var{j}. | |
7636 | ||
7637 | However, side effects in @code{X} or @code{Y} may cause unintended | |
7638 | behavior. For example, @code{MIN (i++, j++)} will fail, incrementing | |
f6f89f14 | 7639 | the smaller counter twice. The GNU C @code{typeof} extension allows you |
7640 | to write safe macros that avoid this kind of problem (@pxref{Typeof}). | |
7641 | However, writing @code{MIN} and @code{MAX} as macros also forces you to | |
7642 | use function-call notation for a fundamental arithmetic operation. | |
7643 | Using GNU C++ extensions, you can write @w{@samp{int min = i <? j;}} | |
7644 | instead. | |
146ef39f | 7645 | |
7646 | Since @code{<?} and @code{>?} are built into the compiler, they properly | |
7647 | handle expressions with side-effects; @w{@samp{int min = i++ <? j++;}} | |
7648 | works correctly. | |
7649 | ||
b1a8d4ce | 7650 | @node Volatiles |
7651 | @section When is a Volatile Object Accessed? | |
7652 | @cindex accessing volatiles | |
7653 | @cindex volatile read | |
7654 | @cindex volatile write | |
7655 | @cindex volatile access | |
7656 | ||
71d6ad5e | 7657 | Both the C and C++ standard have the concept of volatile objects. These |
7658 | are normally accessed by pointers and used for accessing hardware. The | |
09e71a8f | 7659 | standards encourage compilers to refrain from optimizations |
b1a8d4ce | 7660 | concerning accesses to volatile objects that it might perform on |
71d6ad5e | 7661 | non-volatile objects. The C standard leaves it implementation defined |
7662 | as to what constitutes a volatile access. The C++ standard omits to | |
b1a8d4ce | 7663 | specify this, except to say that C++ should behave in a similar manner |
71d6ad5e | 7664 | to C with respect to volatiles, where possible. The minimum either |
09e71a8f | 7665 | standard specifies is that at a sequence point all previous accesses to |
b1a8d4ce | 7666 | volatile objects have stabilized and no subsequent accesses have |
71d6ad5e | 7667 | occurred. Thus an implementation is free to reorder and combine |
b1a8d4ce | 7668 | volatile accesses which occur between sequence points, but cannot do so |
71d6ad5e | 7669 | for accesses across a sequence point. The use of volatiles does not |
b1a8d4ce | 7670 | allow you to violate the restriction on updating objects multiple times |
7671 | within a sequence point. | |
7672 | ||
7673 | In most expressions, it is intuitively obvious what is a read and what is | |
71d6ad5e | 7674 | a write. For instance |
b1a8d4ce | 7675 | |
7676 | @example | |
8e5fcce7 | 7677 | volatile int *dst = @var{somevalue}; |
7678 | volatile int *src = @var{someothervalue}; | |
b1a8d4ce | 7679 | *dst = *src; |
7680 | @end example | |
7681 | ||
7682 | @noindent | |
7683 | will cause a read of the volatile object pointed to by @var{src} and stores the | |
71d6ad5e | 7684 | value into the volatile object pointed to by @var{dst}. There is no |
b1a8d4ce | 7685 | guarantee that these reads and writes are atomic, especially for objects |
7686 | larger than @code{int}. | |
7687 | ||
7688 | Less obvious expressions are where something which looks like an access | |
71d6ad5e | 7689 | is used in a void context. An example would be, |
b1a8d4ce | 7690 | |
7691 | @example | |
8e5fcce7 | 7692 | volatile int *src = @var{somevalue}; |
b1a8d4ce | 7693 | *src; |
7694 | @end example | |
7695 | ||
7696 | With C, such expressions are rvalues, and as rvalues cause a read of | |
37744367 | 7697 | the object, GCC interprets this as a read of the volatile being pointed |
71d6ad5e | 7698 | to. The C++ standard specifies that such expressions do not undergo |
b1a8d4ce | 7699 | lvalue to rvalue conversion, and that the type of the dereferenced |
71d6ad5e | 7700 | object may be incomplete. The C++ standard does not specify explicitly |
b1a8d4ce | 7701 | that it is this lvalue to rvalue conversion which is responsible for |
71d6ad5e | 7702 | causing an access. However, there is reason to believe that it is, |
7703 | because otherwise certain simple expressions become undefined. However, | |
37744367 | 7704 | because it would surprise most programmers, G++ treats dereferencing a |
b1a8d4ce | 7705 | pointer to volatile object of complete type in a void context as a read |
71d6ad5e | 7706 | of the object. When the object has incomplete type, G++ issues a |
b1a8d4ce | 7707 | warning. |
7708 | ||
7709 | @example | |
7710 | struct S; | |
7711 | struct T @{int m;@}; | |
8e5fcce7 | 7712 | volatile S *ptr1 = @var{somevalue}; |
7713 | volatile T *ptr2 = @var{somevalue}; | |
b1a8d4ce | 7714 | *ptr1; |
7715 | *ptr2; | |
7716 | @end example | |
7717 | ||
7718 | In this example, a warning is issued for @code{*ptr1}, and @code{*ptr2} | |
71d6ad5e | 7719 | causes a read of the object pointed to. If you wish to force an error on |
b1a8d4ce | 7720 | the first case, you must force a conversion to rvalue with, for instance |
7721 | a static cast, @code{static_cast<S>(*ptr1)}. | |
7722 | ||
37744367 | 7723 | When using a reference to volatile, G++ does not treat equivalent |
b1a8d4ce | 7724 | expressions as accesses to volatiles, but instead issues a warning that |
71d6ad5e | 7725 | no volatile is accessed. The rationale for this is that otherwise it |
b1a8d4ce | 7726 | becomes difficult to determine where volatile access occur, and not |
7727 | possible to ignore the return value from functions returning volatile | |
71d6ad5e | 7728 | references. Again, if you wish to force a read, cast the reference to |
b1a8d4ce | 7729 | an rvalue. |
7730 | ||
6795ece9 | 7731 | @node Restricted Pointers |
7732 | @section Restricting Pointer Aliasing | |
7733 | @cindex restricted pointers | |
7734 | @cindex restricted references | |
7735 | @cindex restricted this pointer | |
7736 | ||
dbe4c49e | 7737 | As with gcc, g++ understands the C99 feature of restricted pointers, |
6795ece9 | 7738 | specified with the @code{__restrict__}, or @code{__restrict} type |
71d6ad5e | 7739 | qualifier. Because you cannot compile C++ by specifying the @option{-std=c99} |
6795ece9 | 7740 | language flag, @code{restrict} is not a keyword in C++. |
7741 | ||
7742 | In addition to allowing restricted pointers, you can specify restricted | |
7743 | references, which indicate that the reference is not aliased in the local | |
7744 | context. | |
7745 | ||
7746 | @example | |
7747 | void fn (int *__restrict__ rptr, int &__restrict__ rref) | |
7748 | @{ | |
4ae74ddd | 7749 | /* @r{@dots{}} */ |
6795ece9 | 7750 | @} |
7751 | @end example | |
7752 | ||
7753 | @noindent | |
7754 | In the body of @code{fn}, @var{rptr} points to an unaliased integer and | |
7755 | @var{rref} refers to a (different) unaliased integer. | |
7756 | ||
7757 | You may also specify whether a member function's @var{this} pointer is | |
7758 | unaliased by using @code{__restrict__} as a member function qualifier. | |
7759 | ||
7760 | @example | |
7761 | void T::fn () __restrict__ | |
7762 | @{ | |
4ae74ddd | 7763 | /* @r{@dots{}} */ |
6795ece9 | 7764 | @} |
7765 | @end example | |
7766 | ||
7767 | @noindent | |
7768 | Within the body of @code{T::fn}, @var{this} will have the effective | |
71d6ad5e | 7769 | definition @code{T *__restrict__ const this}. Notice that the |
6795ece9 | 7770 | interpretation of a @code{__restrict__} member function qualifier is |
7771 | different to that of @code{const} or @code{volatile} qualifier, in that it | |
71d6ad5e | 7772 | is applied to the pointer rather than the object. This is consistent with |
6795ece9 | 7773 | other compilers which implement restricted pointers. |
7774 | ||
7775 | As with all outermost parameter qualifiers, @code{__restrict__} is | |
71d6ad5e | 7776 | ignored in function definition matching. This means you only need to |
6795ece9 | 7777 | specify @code{__restrict__} in a function definition, rather than |
7778 | in a function prototype as well. | |
7779 | ||
a89b0e97 | 7780 | @node Vague Linkage |
7781 | @section Vague Linkage | |
7782 | @cindex vague linkage | |
7783 | ||
7784 | There are several constructs in C++ which require space in the object | |
7785 | file but are not clearly tied to a single translation unit. We say that | |
7786 | these constructs have ``vague linkage''. Typically such constructs are | |
7787 | emitted wherever they are needed, though sometimes we can be more | |
7788 | clever. | |
7789 | ||
7790 | @table @asis | |
7791 | @item Inline Functions | |
7792 | Inline functions are typically defined in a header file which can be | |
7793 | included in many different compilations. Hopefully they can usually be | |
7794 | inlined, but sometimes an out-of-line copy is necessary, if the address | |
7795 | of the function is taken or if inlining fails. In general, we emit an | |
7796 | out-of-line copy in all translation units where one is needed. As an | |
7797 | exception, we only emit inline virtual functions with the vtable, since | |
7798 | it will always require a copy. | |
7799 | ||
7800 | Local static variables and string constants used in an inline function | |
7801 | are also considered to have vague linkage, since they must be shared | |
7802 | between all inlined and out-of-line instances of the function. | |
7803 | ||
7804 | @item VTables | |
7805 | @cindex vtable | |
7806 | C++ virtual functions are implemented in most compilers using a lookup | |
7807 | table, known as a vtable. The vtable contains pointers to the virtual | |
7808 | functions provided by a class, and each object of the class contains a | |
7809 | pointer to its vtable (or vtables, in some multiple-inheritance | |
7810 | situations). If the class declares any non-inline, non-pure virtual | |
7811 | functions, the first one is chosen as the ``key method'' for the class, | |
7812 | and the vtable is only emitted in the translation unit where the key | |
7813 | method is defined. | |
7814 | ||
7815 | @emph{Note:} If the chosen key method is later defined as inline, the | |
7816 | vtable will still be emitted in every translation unit which defines it. | |
7817 | Make sure that any inline virtuals are declared inline in the class | |
7818 | body, even if they are not defined there. | |
7819 | ||
7820 | @item type_info objects | |
7821 | @cindex type_info | |
7822 | @cindex RTTI | |
7823 | C++ requires information about types to be written out in order to | |
7824 | implement @samp{dynamic_cast}, @samp{typeid} and exception handling. | |
7825 | For polymorphic classes (classes with virtual functions), the type_info | |
7826 | object is written out along with the vtable so that @samp{dynamic_cast} | |
7827 | can determine the dynamic type of a class object at runtime. For all | |
7828 | other types, we write out the type_info object when it is used: when | |
7829 | applying @samp{typeid} to an expression, throwing an object, or | |
7830 | referring to a type in a catch clause or exception specification. | |
7831 | ||
7832 | @item Template Instantiations | |
7833 | Most everything in this section also applies to template instantiations, | |
7834 | but there are other options as well. | |
7835 | @xref{Template Instantiation,,Where's the Template?}. | |
7836 | ||
7837 | @end table | |
7838 | ||
7839 | When used with GNU ld version 2.8 or later on an ELF system such as | |
7840 | Linux/GNU or Solaris 2, or on Microsoft Windows, duplicate copies of | |
7841 | these constructs will be discarded at link time. This is known as | |
7842 | COMDAT support. | |
7843 | ||
7844 | On targets that don't support COMDAT, but do support weak symbols, GCC | |
7845 | will use them. This way one copy will override all the others, but | |
7846 | the unused copies will still take up space in the executable. | |
7847 | ||
7848 | For targets which do not support either COMDAT or weak symbols, | |
7849 | most entities with vague linkage will be emitted as local symbols to | |
7850 | avoid duplicate definition errors from the linker. This will not happen | |
7851 | for local statics in inlines, however, as having multiple copies will | |
7852 | almost certainly break things. | |
7853 | ||
7854 | @xref{C++ Interface,,Declarations and Definitions in One Header}, for | |
7855 | another way to control placement of these constructs. | |
7856 | ||
146ef39f | 7857 | @node C++ Interface |
7858 | @section Declarations and Definitions in One Header | |
7859 | ||
7860 | @cindex interface and implementation headers, C++ | |
7861 | @cindex C++ interface and implementation headers | |
7862 | C++ object definitions can be quite complex. In principle, your source | |
7863 | code will need two kinds of things for each object that you use across | |
7864 | more than one source file. First, you need an @dfn{interface} | |
7865 | specification, describing its structure with type declarations and | |
7866 | function prototypes. Second, you need the @dfn{implementation} itself. | |
7867 | It can be tedious to maintain a separate interface description in a | |
7868 | header file, in parallel to the actual implementation. It is also | |
7869 | dangerous, since separate interface and implementation definitions may | |
7870 | not remain parallel. | |
7871 | ||
7872 | @cindex pragmas, interface and implementation | |
7873 | With GNU C++, you can use a single header file for both purposes. | |
7874 | ||
7875 | @quotation | |
7876 | @emph{Warning:} The mechanism to specify this is in transition. For the | |
7877 | nonce, you must use one of two @code{#pragma} commands; in a future | |
7878 | release of GNU C++, an alternative mechanism will make these | |
7879 | @code{#pragma} commands unnecessary. | |
7880 | @end quotation | |
7881 | ||
7882 | The header file contains the full definitions, but is marked with | |
7883 | @samp{#pragma interface} in the source code. This allows the compiler | |
7884 | to use the header file only as an interface specification when ordinary | |
7885 | source files incorporate it with @code{#include}. In the single source | |
7886 | file where the full implementation belongs, you can use either a naming | |
7887 | convention or @samp{#pragma implementation} to indicate this alternate | |
7888 | use of the header file. | |
7889 | ||
7890 | @table @code | |
7891 | @item #pragma interface | |
7892 | @itemx #pragma interface "@var{subdir}/@var{objects}.h" | |
7893 | @kindex #pragma interface | |
7894 | Use this directive in @emph{header files} that define object classes, to save | |
7895 | space in most of the object files that use those classes. Normally, | |
7896 | local copies of certain information (backup copies of inline member | |
7897 | functions, debugging information, and the internal tables that implement | |
7898 | virtual functions) must be kept in each object file that includes class | |
7899 | definitions. You can use this pragma to avoid such duplication. When a | |
7900 | header file containing @samp{#pragma interface} is included in a | |
7901 | compilation, this auxiliary information will not be generated (unless | |
7902 | the main input source file itself uses @samp{#pragma implementation}). | |
7903 | Instead, the object files will contain references to be resolved at link | |
7904 | time. | |
7905 | ||
7906 | The second form of this directive is useful for the case where you have | |
7907 | multiple headers with the same name in different directories. If you | |
7908 | use this form, you must specify the same string to @samp{#pragma | |
7909 | implementation}. | |
7910 | ||
7911 | @item #pragma implementation | |
7912 | @itemx #pragma implementation "@var{objects}.h" | |
7913 | @kindex #pragma implementation | |
7914 | Use this pragma in a @emph{main input file}, when you want full output from | |
7915 | included header files to be generated (and made globally visible). The | |
7916 | included header file, in turn, should use @samp{#pragma interface}. | |
7917 | Backup copies of inline member functions, debugging information, and the | |
7918 | internal tables used to implement virtual functions are all generated in | |
7919 | implementation files. | |
7920 | ||
7921 | @cindex implied @code{#pragma implementation} | |
7922 | @cindex @code{#pragma implementation}, implied | |
7923 | @cindex naming convention, implementation headers | |
7924 | If you use @samp{#pragma implementation} with no argument, it applies to | |
7925 | an include file with the same basename@footnote{A file's @dfn{basename} | |
7926 | was the name stripped of all leading path information and of trailing | |
7927 | suffixes, such as @samp{.h} or @samp{.C} or @samp{.cc}.} as your source | |
7928 | file. For example, in @file{allclass.cc}, giving just | |
7929 | @samp{#pragma implementation} | |
7930 | by itself is equivalent to @samp{#pragma implementation "allclass.h"}. | |
7931 | ||
7932 | In versions of GNU C++ prior to 2.6.0 @file{allclass.h} was treated as | |
7933 | an implementation file whenever you would include it from | |
7934 | @file{allclass.cc} even if you never specified @samp{#pragma | |
7935 | implementation}. This was deemed to be more trouble than it was worth, | |
7936 | however, and disabled. | |
7937 | ||
7938 | If you use an explicit @samp{#pragma implementation}, it must appear in | |
7939 | your source file @emph{before} you include the affected header files. | |
7940 | ||
7941 | Use the string argument if you want a single implementation file to | |
7942 | include code from multiple header files. (You must also use | |
7943 | @samp{#include} to include the header file; @samp{#pragma | |
7944 | implementation} only specifies how to use the file---it doesn't actually | |
7945 | include it.) | |
7946 | ||
7947 | There is no way to split up the contents of a single header file into | |
7948 | multiple implementation files. | |
7949 | @end table | |
7950 | ||
7951 | @cindex inlining and C++ pragmas | |
7952 | @cindex C++ pragmas, effect on inlining | |
7953 | @cindex pragmas in C++, effect on inlining | |
7954 | @samp{#pragma implementation} and @samp{#pragma interface} also have an | |
7955 | effect on function inlining. | |
7956 | ||
7957 | If you define a class in a header file marked with @samp{#pragma | |
7958 | interface}, the effect on a function defined in that class is similar to | |
7959 | an explicit @code{extern} declaration---the compiler emits no code at | |
7960 | all to define an independent version of the function. Its definition | |
7961 | is used only for inlining with its callers. | |
7962 | ||
67791935 | 7963 | @opindex fno-implement-inlines |
146ef39f | 7964 | Conversely, when you include the same header file in a main source file |
7965 | that declares it as @samp{#pragma implementation}, the compiler emits | |
7966 | code for the function itself; this defines a version of the function | |
7967 | that can be found via pointers (or by callers compiled without | |
7968 | inlining). If all calls to the function can be inlined, you can avoid | |
67791935 | 7969 | emitting the function by compiling with @option{-fno-implement-inlines}. |
146ef39f | 7970 | If any calls were not inlined, you will get linker errors. |
7971 | ||
7972 | @node Template Instantiation | |
7973 | @section Where's the Template? | |
146ef39f | 7974 | @cindex template instantiation |
7975 | ||
7976 | C++ templates are the first language feature to require more | |
7977 | intelligence from the environment than one usually finds on a UNIX | |
7978 | system. Somehow the compiler and linker have to make sure that each | |
7979 | template instance occurs exactly once in the executable if it is needed, | |
7980 | and not at all otherwise. There are two basic approaches to this | |
7981 | problem, which I will refer to as the Borland model and the Cfront model. | |
7982 | ||
7983 | @table @asis | |
7984 | @item Borland model | |
7985 | Borland C++ solved the template instantiation problem by adding the code | |
f96ff825 | 7986 | equivalent of common blocks to their linker; the compiler emits template |
7987 | instances in each translation unit that uses them, and the linker | |
7988 | collapses them together. The advantage of this model is that the linker | |
7989 | only has to consider the object files themselves; there is no external | |
7990 | complexity to worry about. This disadvantage is that compilation time | |
7991 | is increased because the template code is being compiled repeatedly. | |
7992 | Code written for this model tends to include definitions of all | |
7993 | templates in the header file, since they must be seen to be | |
7994 | instantiated. | |
146ef39f | 7995 | |
7996 | @item Cfront model | |
7997 | The AT&T C++ translator, Cfront, solved the template instantiation | |
7998 | problem by creating the notion of a template repository, an | |
f96ff825 | 7999 | automatically maintained place where template instances are stored. A |
8000 | more modern version of the repository works as follows: As individual | |
8001 | object files are built, the compiler places any template definitions and | |
8002 | instantiations encountered in the repository. At link time, the link | |
8003 | wrapper adds in the objects in the repository and compiles any needed | |
8004 | instances that were not previously emitted. The advantages of this | |
8005 | model are more optimal compilation speed and the ability to use the | |
8006 | system linker; to implement the Borland model a compiler vendor also | |
146ef39f | 8007 | needs to replace the linker. The disadvantages are vastly increased |
f96ff825 | 8008 | complexity, and thus potential for error; for some code this can be |
8009 | just as transparent, but in practice it can been very difficult to build | |
146ef39f | 8010 | multiple programs in one directory and one program in multiple |
f96ff825 | 8011 | directories. Code written for this model tends to separate definitions |
8012 | of non-inline member templates into a separate file, which should be | |
8013 | compiled separately. | |
146ef39f | 8014 | @end table |
8015 | ||
f96ff825 | 8016 | When used with GNU ld version 2.8 or later on an ELF system such as |
865ff07f | 8017 | Linux/GNU or Solaris 2, or on Microsoft Windows, g++ supports the |
8018 | Borland model. On other systems, g++ implements neither automatic | |
8019 | model. | |
f96ff825 | 8020 | |
8021 | A future version of g++ will support a hybrid model whereby the compiler | |
8022 | will emit any instantiations for which the template definition is | |
8023 | included in the compile, and store template definitions and | |
8024 | instantiation context information into the object file for the rest. | |
8025 | The link wrapper will extract that information as necessary and invoke | |
8026 | the compiler to produce the remaining instantiations. The linker will | |
8027 | then combine duplicate instantiations. | |
8028 | ||
8029 | In the mean time, you have the following options for dealing with | |
8030 | template instantiations: | |
146ef39f | 8031 | |
8032 | @enumerate | |
7223a120 | 8033 | @item |
67791935 | 8034 | @opindex frepo |
8035 | Compile your template-using code with @option{-frepo}. The compiler will | |
7223a120 | 8036 | generate files with the extension @samp{.rpo} listing all of the |
8037 | template instantiations used in the corresponding object files which | |
8038 | could be instantiated there; the link wrapper, @samp{collect2}, will | |
8039 | then update the @samp{.rpo} files to tell the compiler where to place | |
8040 | those instantiations and rebuild any affected object files. The | |
8041 | link-time overhead is negligible after the first pass, as the compiler | |
8042 | will continue to place the instantiations in the same files. | |
8043 | ||
8044 | This is your best option for application code written for the Borland | |
8045 | model, as it will just work. Code written for the Cfront model will | |
8046 | need to be modified so that the template definitions are available at | |
8047 | one or more points of instantiation; usually this is as simple as adding | |
8048 | @code{#include <tmethods.cc>} to the end of each template header. | |
8049 | ||
8050 | For library code, if you want the library to provide all of the template | |
8051 | instantiations it needs, just try to link all of its object files | |
8052 | together; the link will fail, but cause the instantiations to be | |
8053 | generated as a side effect. Be warned, however, that this may cause | |
8054 | conflicts if multiple libraries try to provide the same instantiations. | |
8055 | For greater control, use explicit instantiation as described in the next | |
8056 | option. | |
8057 | ||
146ef39f | 8058 | @item |
67791935 | 8059 | @opindex fno-implicit-templates |
8060 | Compile your code with @option{-fno-implicit-templates} to disable the | |
146ef39f | 8061 | implicit generation of template instances, and explicitly instantiate |
8062 | all the ones you use. This approach requires more knowledge of exactly | |
8063 | which instances you need than do the others, but it's less | |
8064 | mysterious and allows greater control. You can scatter the explicit | |
8065 | instantiations throughout your program, perhaps putting them in the | |
8066 | translation units where the instances are used or the translation units | |
8067 | that define the templates themselves; you can put all of the explicit | |
8068 | instantiations you need into one big file; or you can create small files | |
8069 | like | |
8070 | ||
8071 | @example | |
8072 | #include "Foo.h" | |
8073 | #include "Foo.cc" | |
8074 | ||
8075 | template class Foo<int>; | |
8076 | template ostream& operator << | |
8077 | (ostream&, const Foo<int>&); | |
8078 | @end example | |
8079 | ||
8080 | for each of the instances you need, and create a template instantiation | |
8081 | library from those. | |
8082 | ||
8083 | If you are using Cfront-model code, you can probably get away with not | |
67791935 | 8084 | using @option{-fno-implicit-templates} when compiling files that don't |
146ef39f | 8085 | @samp{#include} the member template definitions. |
8086 | ||
8087 | If you use one big file to do the instantiations, you may want to | |
67791935 | 8088 | compile it without @option{-fno-implicit-templates} so you get all of the |
146ef39f | 8089 | instances required by your explicit instantiations (but not by any |
8090 | other files) without having to specify them as well. | |
8091 | ||
4dfab374 | 8092 | g++ has extended the template instantiation syntax given in the ISO |
8093 | standard to allow forward declaration of explicit instantiations | |
d39bcd80 | 8094 | (with @code{extern}), instantiation of the compiler support data for a |
0858f8a2 | 8095 | template class (i.e.@: the vtable) without instantiating any of its |
d39bcd80 | 8096 | members (with @code{inline}), and instantiation of only the static data |
8097 | members of a template class, without the support data or member | |
8098 | functions (with (@code{static}): | |
146ef39f | 8099 | |
8100 | @example | |
8101 | extern template int max (int, int); | |
146ef39f | 8102 | inline template class Foo<int>; |
d39bcd80 | 8103 | static template class Foo<int>; |
146ef39f | 8104 | @end example |
8105 | ||
8106 | @item | |
8107 | Do nothing. Pretend g++ does implement automatic instantiation | |
8108 | management. Code written for the Borland model will work fine, but | |
8109 | each translation unit will contain instances of each of the templates it | |
8110 | uses. In a large program, this can lead to an unacceptable amount of code | |
8111 | duplication. | |
8112 | ||
146ef39f | 8113 | @xref{C++ Interface,,Declarations and Definitions in One Header}, for |
8114 | more discussion of these pragmas. | |
8115 | @end enumerate | |
8116 | ||
8b76b461 | 8117 | @node Bound member functions |
8118 | @section Extracting the function pointer from a bound pointer to member function | |
8b76b461 | 8119 | @cindex pmf |
8120 | @cindex pointer to member function | |
8121 | @cindex bound pointer to member function | |
8122 | ||
8123 | In C++, pointer to member functions (PMFs) are implemented using a wide | |
8124 | pointer of sorts to handle all the possible call mechanisms; the PMF | |
8125 | needs to store information about how to adjust the @samp{this} pointer, | |
8126 | and if the function pointed to is virtual, where to find the vtable, and | |
8127 | where in the vtable to look for the member function. If you are using | |
8128 | PMFs in an inner loop, you should really reconsider that decision. If | |
8129 | that is not an option, you can extract the pointer to the function that | |
8130 | would be called for a given object/PMF pair and call it directly inside | |
8131 | the inner loop, to save a bit of time. | |
8132 | ||
8133 | Note that you will still be paying the penalty for the call through a | |
8134 | function pointer; on most modern architectures, such a call defeats the | |
0858e3a2 | 8135 | branch prediction features of the CPU@. This is also true of normal |
8b76b461 | 8136 | virtual function calls. |
8137 | ||
8138 | The syntax for this extension is | |
8139 | ||
8140 | @example | |
8141 | extern A a; | |
8142 | extern int (A::*fp)(); | |
8143 | typedef int (*fptr)(A *); | |
8144 | ||
8145 | fptr p = (fptr)(a.*fp); | |
8146 | @end example | |
8147 | ||
0858f8a2 | 8148 | For PMF constants (i.e.@: expressions of the form @samp{&Klasse::Member}), |
71d6ad5e | 8149 | no object is needed to obtain the address of the function. They can be |
96149f2d | 8150 | converted to function pointers directly: |
8151 | ||
8152 | @example | |
8153 | fptr p1 = (fptr)(&A::foo); | |
8154 | @end example | |
8155 | ||
67791935 | 8156 | @opindex Wno-pmf-conversions |
8157 | You must specify @option{-Wno-pmf-conversions} to use this extension. | |
8b76b461 | 8158 | |
2f1d6059 | 8159 | @node C++ Attributes |
8160 | @section C++-Specific Variable, Function, and Type Attributes | |
8161 | ||
8162 | Some attributes only make sense for C++ programs. | |
8163 | ||
8164 | @table @code | |
8165 | @item init_priority (@var{priority}) | |
8166 | @cindex init_priority attribute | |
8167 | ||
8168 | ||
8169 | In Standard C++, objects defined at namespace scope are guaranteed to be | |
8170 | initialized in an order in strict accordance with that of their definitions | |
8171 | @emph{in a given translation unit}. No guarantee is made for initializations | |
8172 | across translation units. However, GNU C++ allows users to control the | |
f7b79b48 | 8173 | order of initialization of objects defined at namespace scope with the |
2f1d6059 | 8174 | @code{init_priority} attribute by specifying a relative @var{priority}, |
8175 | a constant integral expression currently bounded between 101 and 65535 | |
8176 | inclusive. Lower numbers indicate a higher priority. | |
8177 | ||
8178 | In the following example, @code{A} would normally be created before | |
8179 | @code{B}, but the @code{init_priority} attribute has reversed that order: | |
8180 | ||
b724fad7 | 8181 | @smallexample |
2f1d6059 | 8182 | Some_Class A __attribute__ ((init_priority (2000))); |
8183 | Some_Class B __attribute__ ((init_priority (543))); | |
b724fad7 | 8184 | @end smallexample |
2f1d6059 | 8185 | |
8186 | @noindent | |
8187 | Note that the particular values of @var{priority} do not matter; only their | |
8188 | relative ordering. | |
8189 | ||
15672c96 | 8190 | @item java_interface |
8191 | @cindex java_interface attribute | |
8192 | ||
3b0848a2 | 8193 | This type attribute informs C++ that the class is a Java interface. It may |
15672c96 | 8194 | only be applied to classes declared within an @code{extern "Java"} block. |
3b0848a2 | 8195 | Calls to methods declared in this interface will be dispatched using GCJ's |
8196 | interface table mechanism, instead of regular virtual table dispatch. | |
15672c96 | 8197 | |
2f1d6059 | 8198 | @end table |
8199 | ||
6df8a9dd | 8200 | @node Java Exceptions |
8201 | @section Java Exceptions | |
8202 | ||
8203 | The Java language uses a slightly different exception handling model | |
8204 | from C++. Normally, GNU C++ will automatically detect when you are | |
8205 | writing C++ code that uses Java exceptions, and handle them | |
8206 | appropriately. However, if C++ code only needs to execute destructors | |
8207 | when Java exceptions are thrown through it, GCC will guess incorrectly. | |
0fff59be | 8208 | Sample problematic code is: |
6df8a9dd | 8209 | |
b724fad7 | 8210 | @smallexample |
6df8a9dd | 8211 | struct S @{ ~S(); @}; |
0fff59be | 8212 | extern void bar(); // is written in Java, and may throw exceptions |
6df8a9dd | 8213 | void foo() |
8214 | @{ | |
8215 | S s; | |
8216 | bar(); | |
8217 | @} | |
b724fad7 | 8218 | @end smallexample |
6df8a9dd | 8219 | |
8220 | @noindent | |
8221 | The usual effect of an incorrect guess is a link failure, complaining of | |
8222 | a missing routine called @samp{__gxx_personality_v0}. | |
8223 | ||
8224 | You can inform the compiler that Java exceptions are to be used in a | |
8225 | translation unit, irrespective of what it might think, by writing | |
8226 | @samp{@w{#pragma GCC java_exceptions}} at the head of the file. This | |
8227 | @samp{#pragma} must appear before any functions that throw or catch | |
8228 | exceptions, or run destructors when exceptions are thrown through them. | |
8229 | ||
8230 | You cannot mix Java and C++ exceptions in the same translation unit. It | |
8231 | is believed to be safe to throw a C++ exception from one file through | |
0fff59be | 8232 | another file compiled for the Java exception model, or vice versa, but |
8233 | there may be bugs in this area. | |
6df8a9dd | 8234 | |
64b04d50 | 8235 | @node Deprecated Features |
8236 | @section Deprecated Features | |
8237 | ||
8238 | In the past, the GNU C++ compiler was extended to experiment with new | |
71d6ad5e | 8239 | features, at a time when the C++ language was still evolving. Now that |
64b04d50 | 8240 | the C++ standard is complete, some of those features are superseded by |
71d6ad5e | 8241 | superior alternatives. Using the old features might cause a warning in |
8242 | some cases that the feature will be dropped in the future. In other | |
64b04d50 | 8243 | cases, the feature might be gone already. |
8244 | ||
8245 | While the list below is not exhaustive, it documents some of the options | |
8246 | that are now deprecated: | |
8247 | ||
8248 | @table @code | |
8249 | @item -fexternal-templates | |
8250 | @itemx -falt-external-templates | |
8251 | These are two of the many ways for g++ to implement template | |
71d6ad5e | 8252 | instantiation. @xref{Template Instantiation}. The C++ standard clearly |
64b04d50 | 8253 | defines how template definitions have to be organized across |
71d6ad5e | 8254 | implementation units. g++ has an implicit instantiation mechanism that |
64b04d50 | 8255 | should work just fine for standard-conforming code. |
8256 | ||
8257 | @item -fstrict-prototype | |
8258 | @itemx -fno-strict-prototype | |
8259 | Previously it was possible to use an empty prototype parameter list to | |
8260 | indicate an unspecified number of parameters (like C), rather than no | |
71d6ad5e | 8261 | parameters, as C++ demands. This feature has been removed, except where |
64b04d50 | 8262 | it is required for backwards compatibility @xref{Backwards Compatibility}. |
8263 | @end table | |
8264 | ||
57a9b138 | 8265 | The named return value extension has been deprecated, and is now |
8266 | removed from g++. | |
64b04d50 | 8267 | |
4ea8b5e2 | 8268 | The use of initializer lists with new expressions has been deprecated, |
57a9b138 | 8269 | and is now removed from g++. |
8270 | ||
8271 | Floating and complex non-type template parameters have been deprecated, | |
8272 | and are now removed from g++. | |
8273 | ||
a77827f5 | 8274 | The implicit typename extension has been deprecated and is now |
8275 | removed from g++. | |
8276 | ||
8277 | The use of default arguments in function pointers, function typedefs and | |
8278 | and other places where they are not permitted by the standard is | |
8279 | deprecated and will be removed from a future version of g++. | |
4ea8b5e2 | 8280 | |
64b04d50 | 8281 | @node Backwards Compatibility |
8282 | @section Backwards Compatibility | |
8283 | @cindex Backwards Compatibility | |
8284 | @cindex ARM [Annotated C++ Reference Manual] | |
8285 | ||
70c2c81c | 8286 | Now that there is a definitive ISO standard C++, G++ has a specification |
71d6ad5e | 8287 | to adhere to. The C++ language evolved over time, and features that |
64b04d50 | 8288 | used to be acceptable in previous drafts of the standard, such as the ARM |
71d6ad5e | 8289 | [Annotated C++ Reference Manual], are no longer accepted. In order to allow |
70c2c81c | 8290 | compilation of C++ written to such drafts, G++ contains some backwards |
71d6ad5e | 8291 | compatibilities. @emph{All such backwards compatibility features are |
70c2c81c | 8292 | liable to disappear in future versions of G++.} They should be considered |
64b04d50 | 8293 | deprecated @xref{Deprecated Features}. |
8294 | ||
8295 | @table @code | |
8296 | @item For scope | |
8297 | If a variable is declared at for scope, it used to remain in scope until | |
8298 | the end of the scope which contained the for statement (rather than just | |
70c2c81c | 8299 | within the for scope). G++ retains this, but issues a warning, if such a |
64b04d50 | 8300 | variable is accessed outside the for scope. |
8301 | ||
57a9b138 | 8302 | @item Implicit C language |
8ae77b3c | 8303 | Old C system header files did not contain an @code{extern "C" @{@dots{}@}} |
71d6ad5e | 8304 | scope to set the language. On such systems, all header files are |
8305 | implicitly scoped inside a C language scope. Also, an empty prototype | |
64b04d50 | 8306 | @code{()} will be treated as an unspecified number of arguments, rather |
8307 | than no arguments, as C++ demands. | |
8308 | @end table |