Lines Matching full:macro
333 * Preprocessor Options:: Controlling header files and macro definitions.
1004 * Preprocessor Options:: Controlling header files and macro definitions.
1325 The macro `__STRICT_ANSI__' is predefined when the `-ansi' option
1326 is used. Some header files may notice this macro and refrain from
1391 Inline Function is As Fast As a Macro: Inline. Using this option
2058 The macro `__NEXT_RUNTIME__' is predefined if (and only if) this
3006 * Macro parameters that appear within string literals in the
3007 macro body. In traditional C macro replacement takes place
3021 * A function-like macro that appears without arguments.
3392 Suppress warnings from applying the `offsetof' macro to a non-POD
3602 Level 3 includes extra information, such as all the macro
3603 definitions present in the program. Some debuggers support macro
3823 Dump all macro definitions, at the end of preprocessing, in
4519 machine-description macro `FRAME_POINTER_REQUIRED' controls
5426 This option causes the preprocessor macro `__FAST_MATH__' to be
5524 This option causes the preprocessor macro `__SUPPORT_SNAN__' to be
6223 Predefine NAME as a macro, with definition `1'.
6235 If you wish to define a function-like macro on the command line,
6302 Warn whenever an identifier which is not a macro is encountered in
6308 macro is "used" if it is expanded or tested for existence at least
6309 once. The preprocessor will also warn if the macro has not been
6315 _Note:_ If a macro is actually used, but only used in skipped
6318 macro's definition by, for example, moving it into the first
6634 If the `-E' option is enabled, it suppresses things like macro
6637 except that macro definitions are output similar to the `-dD'
6655 preprocessed. This suppresses things like macro expansion,
6750 Like `D', but emit only the macro names, not their expansions.
6775 Do not discard comments, including during macro expansion. This is
6777 passed through to the output file where the macro is expanded.
6780 option causes all C++-style comments inside a macro to be
6782 that macro from inadvertently commenting out the remainder of the
7396 Substitutes the standard macro predefinitions for the current
7401 predefined macro, except for macros that start with `__' or with
8523 preprocessor macro `_IEEE_FP' is defined during compilation. The
8533 `_IEEE_FP', `_IEEE_FP_EXACT' is defined as a preprocessor macro.
10404 to `"r2000"' and define the macro `_MIPS_ARCH_R2000'.
10406 Note that the `_MIPS_ARCH' macro uses the processor names given
10408 abbreviate `000' as `k'. In the case of `from-abi', the macro
12893 are machine-specific and are defined in the `REGISTER_NAMES' macro
12894 in the machine description macro file.
13396 The `-D' option is one way to define a macro before a precompiled
13876 environments, and classifications, and their macro names (C99 7.6,
14126 macro expansion) in a `#include' directive are combined into a
14157 * `The null pointer constant to which the macro `NULL' expands (C90
14207 features in conditional compilation, check for a predefined macro
14305 This feature is especially useful in making macro definitions "safe"
14307 "maximum" function is commonly defined as a macro in standard C as
14314 operands (here taken as `int'), you can define the macro safely as
14347 #define macro(a) ({__typeof__(a) b = (a); b + 3; })
14352 macro (X ());
14357 `macro' case, the temporary `X' will be destroyed just after the
14412 The local label feature is useful for complex macros. If a macro
14415 used: if the macro can be expanded several times in one function, the
14721 be used to define a safe "maximum" macro that operates on any
14803 does, or may (if it is a macro argument), contain a side effect. Then
15125 In the ISO C standard of 1999, a macro can be declared to accept a
15127 defining the macro is similar to that of a function. Here is an
15133 macro, it represents the zero or more tokens until the closing
15135 tokens replaces the identifier `__VA_ARGS__' in the macro body wherever
15147 GNU CPP has two further variadic macro extensions, and permits them to
15148 be used with either of the above forms of macro definition.
15159 the expansion of the macro still has the extra comma after the format
15170 provide some variable arguments in your macro invocation, GNU CPP does
15172 arguments after the comma. Just like any other pasted macro argument,
15173 these arguments are not macro expanded.
15519 concerned about a possible macro of the same name. For example, you
15554 has almost the effect of a macro. The way to use this is to put a
15575 As Fast As a Macro: Inline.
16189 type. If your system defines the `NULL' macro with an integer type
16413 1. It is impossible to generate `#pragma' commands from a macro.
16777 concerned about a possible macro of the same name. For example, you
17232 header files without being concerned about a possible macro of the same
17557 5.34 An Inline Function is As Fast As a Macro
17638 macro. The way to use it is to put a function definition in a header
19177 An address that can be used in a non-macro load or store.
20159 the `offsetof' macro.
20173 is a suitable definition of the `offsetof' macro. In C++, TYPE may be
20495 to simply `#define' each standard macro to its built-in equivalent.
20604 You may use this built-in function in either a macro or an inline
20696 implementing the ISO C macro `HUGE_VAL'.
20721 This function is suitable for implementing the ISO C99 macro
22295 Since `vec_add' is a macro, the vector constant in the example is
24310 Attributes::). Macro expansion occurs on the arguments to this
24341 NEWNAME. The preprocessor macro `__PRAGMA_REDEFINE_EXTNAME' will
24348 whose argument is an empty string. The preprocessor macro
24772 programs: check for a predefined macro `__GNUC__'. You can also use
26046 helpful--they only report on the line where the macro call appears. If
26739 * GCC does not substitute macro arguments when they appear inside of
26740 string constants. For example, the following macro in GCC
26774 * Programs that use preprocessing directives in the middle of macro
27364 * Both conversion programs can be confused if there are macro calls
27367 from expanding a macro. This problem is inherent in the design of
27369 macro calls, you can easily convert them manually.
32544 * macro with variable arguments: Variadic Macros. (line 6)
32751 * rest argument (in macro): Variadic Macros. (line 6)
32802 * side effects, macro argument: Statement Exprs. (line 35)
