Lines Matching full:macro
383 * Preprocessor Options:: Controlling header files and macro definitions.
1084 * Preprocessor Options:: Controlling header files and macro definitions.
1517 The macro `__STRICT_ANSI__' is predefined when the `-ansi' option
1518 is used. Some header files may notice this macro and refrain from
1605 Inline Function is As Fast As a Macro: Inline. This option is
2308 The macro `__NEXT_RUNTIME__' is predefined if (and only if) this
3298 * Macro parameters that appear within string literals in the
3299 macro body. In traditional C macro replacement takes place
3313 * A function-like macro that appears without arguments.
3745 Suppress warnings from applying the `offsetof' macro to a non-POD
3941 Level 3 includes extra information, such as all the macro
3942 definitions present in the program. Some debuggers support macro
4193 Dump all macro definitions, at the end of preprocessing, in
4895 machine-description macro `FRAME_POINTER_REQUIRED' controls
5904 This option causes the preprocessor macro `__FAST_MATH__' to be
6043 This option causes the preprocessor macro `__SUPPORT_SNAN__' to be
6864 Predefine NAME as a macro, with definition `1'.
6876 If you wish to define a function-like macro on the command line,
6945 Warn whenever an identifier which is not a macro is encountered in
6951 macro is "used" if it is expanded or tested for existence at least
6952 once. The preprocessor will also warn if the macro has not been
6958 _Note:_ If a macro is actually used, but only used in skipped
6961 macro's definition by, for example, moving it into the first
7287 operations, such as macro expansion and trigraph conversion are
7311 preprocessed. This suppresses things like macro expansion,
7410 Like `D', but emit only the macro names, not their expansions.
7435 Do not discard comments, including during macro expansion. This is
7437 passed through to the output file where the macro is expanded.
7440 option causes all C++-style comments inside a macro to be
7442 that macro from inadvertently commenting out the remainder of the
8056 Substitutes the standard macro predefinitions for the current
8061 predefined macro, except for macros that start with `__' or with
8722 If this option is used, a preprocessor macro `__ANDROID__' is
8824 `__SILICON_REVISION__' macro is defined to two hexadecimal digits
8833 processor macro is defined. Without this option, `bf532' is used
9324 preprocessor macro `_IEEE_FP' is defined during compilation. The
9334 `_IEEE_FP', `_IEEE_FP_EXACT' is defined as a preprocessor macro.
11039 gcc defines a macro `__mcfARCH__' whenever it is generating code
11040 for a ColdFire target. The ARCH in this macro is one of the
11081 gcc defines the macro `__mcf_cpu_CPU' when ColdFire target CPU is
11105 gcc also defines the macro `__mUARCH__' when tuning for ColdFire
11215 defines the macro `__HAVE_68881__' on M680x0 targets and
11233 gcc defines the macro `__mcfhwdiv__' when this option is enabled.
11474 to `"r2000"' and define the macro `_MIPS_ARCH_R2000'.
11476 Note that the `_MIPS_ARCH' macro uses the processor names given
11478 abbreviate `000' as `k'. In the case of `from-abi', the macro
11665 Built-in Functions::. This option defines the preprocessor macro
13772 latter. It also defines the preprocessor macro `__RTP__'.
14124 are machine-specific and are defined in the `REGISTER_NAMES' macro
14125 in the machine description macro file.
14630 The `-D' option is one way to define a macro before a precompiled
15110 environments, and classifications, and their macro names (C99 7.6,
15360 macro expansion) in a `#include' directive are combined into a
15391 * `The null pointer constant to which the macro `NULL' expands (C90
15441 features in conditional compilation, check for a predefined macro
15542 This feature is especially useful in making macro definitions "safe"
15544 "maximum" function is commonly defined as a macro in standard C as
15551 operands (here taken as `int'), you can define the macro safely as
15584 #define macro(a) ({__typeof__(a) b = (a); b + 3; })
15589 macro (X ());
15594 `macro' case, the temporary `X' will be destroyed just after the
15649 The local label feature is useful for complex macros. If a macro
15652 used: if the macro can be expanded several times in one function, the
16019 be used to define a safe "maximum" macro that operates on any
16101 does, or may (if it is a macro argument), contain a side effect. Then
16502 In the ISO C standard of 1999, a macro can be declared to accept a
16504 defining the macro is similar to that of a function. Here is an
16510 macro, it represents the zero or more tokens until the closing
16512 tokens replaces the identifier `__VA_ARGS__' in the macro body wherever
16524 GNU CPP has two further variadic macro extensions, and permits them to
16525 be used with either of the above forms of macro definition.
16536 the expansion of the macro still has the extra comma after the format
16547 provide some variable arguments in your macro invocation, GNU CPP does
16549 arguments after the comma. Just like any other pasted macro argument,
16550 these arguments are not macro expanded.
16897 concerned about a possible macro of the same name. For example, you
16973 has almost the effect of a macro. The way to use this is to put a
16994 As Fast As a Macro: Inline.
17757 type. If your system defines the `NULL' macro with an integer type
17991 1. It is impossible to generate `#pragma' commands from a macro.
18345 concerned about a possible macro of the same name. For example, you
18840 header files without being concerned about a possible macro of the same
19174 5.36 An Inline Function is As Fast As a Macro
19270 macro. The way to use it is to put a function definition in a header
20904 An address that can be used in a non-macro load or store.
21944 the `offsetof' macro.
21958 is a suitable definition of the `offsetof' macro. In C++, TYPE may be
22282 to simply `#define' each standard macro to its built-in equivalent. In
22393 You may use this built-in function in either a macro or an inline
22504 implementing the ISO C macro `HUGE_VAL'.
22529 This function is suitable for implementing the ISO C99 macro
30368 Since `vec_add' is a macro, the vector constant in the example is
32259 * By default, the keyword `__vector' is added. The macro `vector' is
32270 Since `spu_add' is a macro, the vector constant in the example is
32429 Attributes::). Macro expansion occurs on the arguments to this
32460 NEWNAME. The preprocessor macro `__PRAGMA_REDEFINE_EXTNAME' will
32467 whose argument is an empty string. The preprocessor macro
32913 programs: check for a predefined macro `__GNUC__'. You can also use
34306 helpful--they only report on the line where the macro call appears. If
34990 * GCC does not substitute macro arguments when they appear inside of
34991 string constants. For example, the following macro in GCC
35025 * Programs that use preprocessing directives in the middle of macro
35615 * Both conversion programs can be confused if there are macro calls
35618 from expanding a macro. This problem is inherent in the design of
35620 macro calls, you can easily convert them manually.
41443 * macro with variable arguments: Variadic Macros. (line 6)
41661 * rest argument (in macro): Variadic Macros. (line 6)
41712 * side effects, macro argument: Statement Exprs. (line 35)
