Lines Matching full:macro
374 * Preprocessor Options:: Controlling header files and macro definitions.
469 -Wno-attributes -Wno-builtin-macro-redefined
1118 * Preprocessor Options:: Controlling header files and macro definitions.
1582 The macro `__STRICT_ANSI__' is predefined when the `-ansi' option
1583 is used. Some header files may notice this macro and refrain from
1670 Inline Function is As Fast As a Macro: Inline. This option is
2383 The macro `__NEXT_RUNTIME__' is predefined if (and only if) this
3381 * Macro parameters that appear within string literals in the
3382 macro body. In traditional C macro replacement takes place
3396 * A function-like macro that appears without arguments.
3630 `-Wno-builtin-macro-redefined'
3873 Suppress warnings from applying the `offsetof' macro to a non-POD
4082 Level 3 includes extra information, such as all the macro
4083 definitions present in the program. Some debuggers support macro
4511 Dump all macro definitions, at the end of preprocessing, in
5109 machine-description macro `FRAME_POINTER_REQUIRED' controls
6342 This option causes the preprocessor macro `__FAST_MATH__' to be
6474 This option causes the preprocessor macro `__SUPPORT_SNAN__' to be
7439 Predefine NAME as a macro, with definition `1'.
7451 If you wish to define a function-like macro on the command line,
7517 Warn whenever an identifier which is not a macro is encountered in
7523 macro is "used" if it is expanded or tested for existence at least
7524 once. The preprocessor will also warn if the macro has not been
7530 _Note:_ If a macro is actually used, but only used in skipped
7533 macro's definition by, for example, moving it into the first
7859 operations, such as macro expansion and trigraph conversion are
7883 preprocessed. This suppresses things like macro expansion,
7982 Like `D', but emit only the macro names, not their expansions.
7991 the output is delayed until the use or test of the macro; and
8014 Do not discard comments, including during macro expansion. This is
8016 passed through to the output file where the macro is expanded.
8019 option causes all C++-style comments inside a macro to be
8021 that macro from inadvertently commenting out the remainder of the
8652 Substitutes the standard macro predefinitions for the current
8657 predefined macro, except for macros that start with `__' or with
9332 If this option is used, a preprocessor macro `__ANDROID__' is
9437 macro is defined to two hexadecimal digits representing the major
9445 processor macro is defined. Without this option, `bf532' is used
9960 preprocessor macro `_IEEE_FP' is defined during compilation. The
9970 `_IEEE_FP', `_IEEE_FP_EXACT' is defined as a preprocessor macro.
11722 gcc defines a macro `__mcfARCH__' whenever it is generating code
11723 for a ColdFire target. The ARCH in this macro is one of the
11764 gcc defines the macro `__mcf_cpu_CPU' when ColdFire target CPU is
11788 gcc also defines the macro `__mUARCH__' when tuning for ColdFire
11898 defines the macro `__HAVE_68881__' on M680x0 targets and
11916 gcc defines the macro `__mcfhwdiv__' when this option is enabled.
12203 to `"r2000"' and define the macro `_MIPS_ARCH_R2000'.
12205 Note that the `_MIPS_ARCH' macro uses the processor names given
12207 abbreviate `000' as `k'. In the case of `from-abi', the macro
12407 Built-in Functions::. This option defines the preprocessor macro
14678 latter. It also defines the preprocessor macro `__RTP__'.
15104 are machine-specific and are defined in the `REGISTER_NAMES' macro
15105 in the machine description macro file.
15634 The `-D' option is one way to define a macro before a precompiled
16114 environments, and classifications, and their macro names (C99 7.6,
16364 macro expansion) in a `#include' directive are combined into a
16395 * `The null pointer constant to which the macro `NULL' expands (C90
16445 features in conditional compilation, check for a predefined macro
16546 This feature is especially useful in making macro definitions "safe"
16548 "maximum" function is commonly defined as a macro in standard C as
16555 operands (here taken as `int'), you can define the macro safely as
16588 #define macro(a) ({__typeof__(a) b = (a); b + 3; })
16593 macro (X ());
16598 `macro' case, the temporary `X' will be destroyed just after the
16653 The local label feature is useful for complex macros. If a macro
16656 used: if the macro can be expanded several times in one function, the
17023 be used to define a safe "maximum" macro that operates on any
17105 does, or may (if it is a macro argument), contain a side effect. Then
17251 this the GNU C compiler does not define macro `__STDC_DEC_FP__' to
17546 In the ISO C standard of 1999, a macro can be declared to accept a
17548 defining the macro is similar to that of a function. Here is an
17554 macro, it represents the zero or more tokens until the closing
17556 tokens replaces the identifier `__VA_ARGS__' in the macro body wherever
17568 GNU CPP has two further variadic macro extensions, and permits them to
17569 be used with either of the above forms of macro definition.
17580 the expansion of the macro still has the extra comma after the format
17591 provide some variable arguments in your macro invocation, GNU CPP does
17593 arguments after the comma. Just like any other pasted macro argument,
17594 these arguments are not macro expanded.
17941 concerned about a possible macro of the same name. For example, you
18017 has almost the effect of a macro. The way to use this is to put a
18038 As Fast As a Macro: Inline.
18877 type. If your system defines the `NULL' macro with an integer type
19262 1. It is impossible to generate `#pragma' commands from a macro.
19616 concerned about a possible macro of the same name. For example, you
19652 Gcc also provides a target specific macro `__BIGGEST_ALIGNMENT__',
20123 header files without being concerned about a possible macro of the same
20463 5.36 An Inline Function is As Fast As a Macro
20559 macro. The way to use it is to put a function definition in a header
21030 the `TARGET_MEM_CONSTRAINT' macro.
22218 An address that can be used in a non-macro load or store.
23262 the `offsetof' macro.
23276 is a suitable definition of the `offsetof' macro. In C++, TYPE may be
23608 to simply `#define' each standard macro to its built-in equivalent. In
23721 You may use this built-in function in either a macro or an inline
23832 implementing the ISO C macro `HUGE_VAL'.
23868 This function is suitable for implementing the ISO C99 macro
32012 defines the preprocessor macro `___GCC_HAVE_BUILTIN_MIPS_CACHE'
32070 Since `vec_add' is a macro, the vector constant in the example is
33961 * By default, the keyword `__vector' is added. The macro `vector' is
33972 Since `spu_add' is a macro, the vector constant in the example is
34032 * Push/Pop Macro Pragmas::
34133 Attributes::). Macro expansion occurs on the arguments to this
34164 NEWNAME. The preprocessor macro `__PRAGMA_REDEFINE_EXTNAME' will
34171 whose argument is an empty string. The preprocessor macro
34326 File: gcc.info, Node: Visibility Pragmas, Next: Push/Pop Macro Pragmas, Prev: Diagnostic Pragmas, Up: Pragmas
34345 File: gcc.info, Node: Push/Pop Macro Pragmas, Next: Function Specific Option Pragmas, Prev: Visibility Pragmas, Up: Pragmas
34347 5.52.11 Push/Pop Macro Pragmas
34355 This pragma saves the value of the macro named as MACRO_NAME to
34356 the top of the stack for this macro.
34359 This pragma sets the value of the macro named as MACRO_NAME to the
34360 value on top of the stack for this macro. If the stack for
34361 MACRO_NAME is empty, the value of the macro remains unchanged.
34376 File: gcc.info, Node: Function Specific Option Pragmas, Prev: Push/Pop Macro Pragmas, Up: Pragmas
34720 programs: check for a predefined macro `__GNUC__'. You can also use
36113 helpful--they only report on the line where the macro call appears. If
36803 * GCC does not substitute macro arguments when they appear inside of
36804 string constants. For example, the following macro in GCC
36838 * Programs that use preprocessing directives in the middle of macro
37428 * Both conversion programs can be confused if there are macro calls
37431 from expanding a macro. This problem is inherent in the design of
37433 macro calls, you can easily convert them manually.
42177 * Wbuiltin-macro-redefined: Warning Options. (line 991)
42263 * Wno-builtin-macro-redefined: Warning Options. (line 991)
43376 * macro with variable arguments: Variadic Macros. (line 6)
43551 * pragma, pop_macro: Push/Pop Macro Pragmas.
43553 * pragma, push_macro: Push/Pop Macro Pragmas.
43615 * rest argument (in macro): Variadic Macros. (line 6)
43666 * side effects, macro argument: Statement Exprs. (line 35)
44159 Node: Push/Pop Macro Pragmas1420549
