Most often when you use the C preprocessor you will not have to invoke it explicitly: the C compiler will do so automatically. However, the preprocessor is sometimes useful on its own. All the options listed here are also acceptable to the C compiler and have the same meaning, except that the C compiler has different rules for specifying the output file.
Note: Whether you use the preprocessor by way of
cpp, the compiler driver is run first. This program's purpose is to translate your command into invocations of the programs that do the actual work. Their command line interfaces are similar but not identical to the documented interface, and may change without notice.
The C preprocessor expects two file names as arguments, infile and outfile. The preprocessor reads infile together with any other files it specifies with ‘
#include’. All the output generated by the combined input files is written in outfile.
Either infile or outfile may be
-, which as infile means to read from standard input and as outfile means to write to standard output. Also, if either file is omitted, it means the same as if
- had been specified for that file.
Unless otherwise noted, or the option ends in ‘
=’, all options which take an argument may have that argument appear either immediately after the option, or with a space between option and argument:
-I foo have the same effect.
Many options have multi-letter names; therefore multiple single-letter options may not be grouped:
-dM is very different from ‘
Predefine name as a macro, with definition
- The contents of definition are tokenized and processed as if they appeared during translation phase three in a ‘
#define’ directive. In particular, the definition will be truncated by embedded newline characters.
If you are invoking the preprocessor from a shell or shell-like program you may need to use the shell's quoting syntax to protect characters such as spaces that have a meaning in the shell syntax.
If you wish to define a function-like macro on the command line, write its argument list with surrounding parentheses before the equals sign (if any). Parentheses are meaningful to most shells, so you will need to quote the option. With
csh, -D'name(args...)=definition' works.
-Uoptions are processed in the order they are given on the command line. All -imacros file and -include file options are processed after all
Cancel any previous definition of name, either built in or provided with a
- Do not predefine any system-specific or GCC-specific macros. The standard predefined macros remain defined. See Standard Predefined Macros.
Add the directory dir to the list of directories to be searched for header files. See Search Path. Directories named by
-Iare searched before the standard system include directories. If the directory dir is a standard system include directory, the option is ignored to ensure that the default search order for system directories and the special treatment of system headers are not defeated (see System Headers) . If dir begins with
=, then the
=will be replaced by the sysroot prefix; see
Write output to file. This is the same as specifying file as the second non-option argument to
gcchas a different interpretation of a second non-option argument, so you must use
-oto specify the output file.
Turns on all optional warnings which are desirable for normal code. At present this is
-Wmulticharand a warning about integer promotion causing a change of sign in
#ifexpressions. Note that many of the preprocessor's warnings are on by default and have no options to control them.
Warn whenever a comment-start sequence ‘
/*’ appears in a ‘
/*’ comment, or whenever a backslash-newline appears in a ‘
//’ comment. (Both forms have the same effect.)
Most trigraphs in comments cannot affect the meaning of the program. However, a trigraph that would form an escaped newline (‘
??/’ at the end of a line) can, by changing where the comment begins or ends. Therefore, only trigraphs that would form escaped newlines produce warnings inside a comment.
This option is implied by
-Wallis not given, this option is still enabled unless trigraphs are enabled. To get trigraph conversion without warnings, but get the other
-Wallwarnings, use ‘
-trigraphs -Wall -Wno-trigraphs’.
- Warn about certain constructs that behave differently in traditional and ISO C. Also warn about ISO C constructs that have no traditional C equivalent, and problematic constructs which should be avoided. See Traditional Mode.
Warn whenever an identifier which is not a macro is encountered in an ‘
#if’ directive, outside of ‘
defined’. Such identifiers are replaced with zero.
Warn about macros defined in the main file that are unused. A macro is used if it is expanded or tested for existence at least once. The preprocessor will also warn if the macro has not been used at the time it is redefined or undefined.
Built-in macros, macros defined on the command line, and macros defined in include files are not warned about.
Note: If a macro is actually used, but only used in skipped conditional blocks, then CPP will report it as unused. To avoid the warning in such a case, you might improve the scope of the macro's definition by, for example, moving it into the first skipped block. Alternatively, you could provide a dummy use with something like:
#if defined the_macro_causing_the_warning #endif
Warn whenever an ‘
#else’ or an ‘
#endif’ are followed by text. This usually happens in code of the form
#if FOO ... #else FOO ... #endif FOO
The second and third
FOOshould be in comments, but often are not in older programs. This warning is on by default.
- Make all warnings into hard errors. Source code which triggers warnings will be rejected.
- Issue warnings for code in system headers. These are normally unhelpful in finding bugs in your own code, therefore suppressed. If you are responsible for the system library, you may want to see them.
- Suppress all warnings, including those which GNU CPP issues by default.
- Issue all the mandatory diagnostics listed in the C standard. Some of them are left out by default, since they trigger frequently on harmless code.
Issue all the mandatory diagnostics, and make all mandatory diagnostics into errors. This includes mandatory diagnostics that GCC issues without ‘
-pedantic’ but treats as warnings.
Instead of outputting the result of preprocessing, output a rule suitable for
makedescribing the dependencies of the main source file. The preprocessor outputs one
makerule containing the object file name for that source file, a colon, and the names of all the included files, including those coming from
-imacroscommand line options.
Unless specified explicitly (with
-MQ), the object file name consists of the name of the source file with any suffix replaced with object file suffix and with any leading directory parts removed. If there are many included files then the rule is split into several lines using ‘
\’-newline. The rule has no commands.
This option does not suppress the preprocessor's debug output, such as
-dM. To avoid mixing such debug output with the dependency rules you should explicitly specify the dependency output file with
-MF, or use an environment variable like
DEPENDENCIES_OUTPUT(see Environment Variables). Debug output will still be sent to the regular output stream as normal.
-Mto the driver implies
-E, and suppresses warnings with an implicit
-Mbut do not mention header files that are found in system header directories, nor header files that are included, directly or indirectly, from such a header.
This implies that the choice of angle brackets or double quotes in an ‘
#include’ directive does not in itself determine whether that header will appear in
-MMdependency output. This is a slight change in semantics from GCC versions 3.0 and earlier.
When used with
-MM, specifies a file to write the dependencies to. If no
-MFswitch is given the preprocessor sends the rules to the same place it would have sent preprocessed output.
When used with the driver options
-MFoverrides the default dependency output file.
In conjunction with an option such as
-Mrequesting dependency generation,
-MGassumes missing header files are generated files and adds them to the dependency list without raising an error. The dependency filename is taken directly from the
#includedirective without prepending any path.
-MGalso suppresses preprocessed output, as a missing header file renders this useless.
This feature is used in automatic updating of makefiles.
This option instructs CPP to add a phony target for each dependency other than the main file, causing each to depend on nothing. These dummy rules work around errors
makegives if you remove header files without updating the
This is typical output:
test.o: test.c test.h test.h:
Change the target of the rule emitted by dependency generation. By default CPP takes the name of the main input file, deletes any directory components and any file suffix such as ‘
.c’, and appends the platform's usual object suffix. The result is the target.
-MToption will set the target to be exactly the string you specify. If you want multiple targets, you can specify them as a single argument to
-MT, or use multiple
-MT '$(objpfx)foo.o'might give
-MT, but it quotes any characters which are special to Make.
The default target is automatically quoted, as if it were given with
-MDis equivalent to -M -MF file, except that
-Eis not implied. The driver determines file based on whether an
-ooption is given. If it is, the driver uses its argument but with a suffix of
.d, otherwise it takes the name of the input file, removes any directory components and suffix, and applies a
-MDis used in conjunction with
-oswitch is understood to specify the dependency output file (see -MF), but if used without
-ois understood to specify a target object file.
-Eis not implied,
-MDcan be used to generate a dependency output file as a side-effect of the compilation process.
-MDexcept mention only user header files, not system header files.
Specify the source language: C, C++, Objective-C, or assembly. This has nothing to do with standards conformance or extensions; it merely selects which base syntax to expect. If you give none of these options, cpp will deduce the language from the extension of the source file: ‘
.m’, or ‘
.S’. Some other common extensions for C++ and assembly are also recognized. If cpp does not recognize the extension, it will treat the file as C; this is the most generic mode.
Note: Previous versions of cpp accepted a
-langoption which selected both the language and the standards conformance level. This option has been removed, because it conflicts with the
Specify the standard to which the code should conform. Currently CPP knows about C and C++ standards; others may be added in the future.
standard may be one of:
- The ISO C standard from 1990. ‘
c90’ is the customary shorthand for this version of the standard.
-ansioption is equivalent to
- The 1990 C standard, as amended in 1994.
- The revised ISO C standard, published in December 1999. Before publication, this was known as C9X.
- The revised ISO C standard, published in December 2011. Before publication, this was known as C1X.
- The 1990 C standard plus GNU extensions. This is the default.
- The 1999 C standard plus GNU extensions.
- The 2011 C standard plus GNU extensions.
- The 1998 ISO C++ standard plus amendments.
- The same as
-std=c++98plus GNU extensions. This is the default for C++ code.
Split the include path. Any directories specified with
-I-are searched only for headers requested with
"; they are not searched for
>. If additional directories are specified with
-Ioptions after the
-I-, those directories are searched for all ‘
-I-inhibits the use of the directory of the current file directory as the first search directory for
". See Search Path. This option has been deprecated.
Do not search the standard system directories for header files. Only the directories you have specified with
-Ioptions (and the directory of the current file, if appropriate) are searched.
- Do not search for header files in the C++-specific standard directories, but do still search the other standard directories. (This option is used when building the C++ library.)
Process file as if
#include "file"appeared as the first line of the primary source file. However, the first directory searched for file is the preprocessor's working directory instead of the directory containing the main source file. If not found there, it is searched for in the remainder of the
#include "..."search chain as normal.
-includeoptions are given, the files are included in the order they appear on the command line.
-include, except that any output produced by scanning file is thrown away. Macros it defines remain defined. This allows you to acquire all the macros from a header without also processing its declarations.
All files specified by
-imacrosare processed before all files specified by
Search dir for header files, but do it after all directories specified with
-Iand the standard system directories have been exhausted. dir is treated as a system include directory. If dir begins with
=, then the
=will be replaced by the sysroot prefix; see
Specify prefix as the prefix for subsequent
-iwithprefixoptions. If the prefix represents a directory, you should include the final ‘
Append dir to the prefix specified previously with
-iprefix, and add the resulting directory to the include search path.
-iwithprefixbeforeputs it in the same place
-iwithprefixputs it where
This option is like the
--sysrootoption, but applies only to header files (except for Darwin targets, where it applies to both header files and libraries). See the
--sysrootoption for more information.
- Use dir as a subdirectory of the directory containing target-specific C++ headers.
Search dir for header files, after all directories specified by
-Ibut before the standard system directories. Mark it as a system directory, so that it gets the same special treatment as is applied to the standard system directories. See System Headers. If dir begins with
=, then the
=will be replaced by the sysroot prefix; see
Search dir only for header files requested with
"; they are not searched for
>, before all directories specified by
-Iand before the standard system directories. See Search Path. If dir begins with
=, then the
=will be replaced by the sysroot prefix; see
When preprocessing, handle directives, but do not expand macros.
The option's behavior depends on the
-E, preprocessing is limited to the handling of directives such as
#error. Other preprocessor operations, such as macro expansion and trigraph conversion are not performed. In addition, the
-dDoption is implicitly enabled.
-fpreprocessed, predefinition of command line and most builtin macros is disabled. Macros such as
__LINE__, which are contextually dependent, are handled normally. This enables compilation of files previously preprocessed with
-fpreprocessed, the rules for
-fpreprocessedtake precedence. This enables full preprocessing of files previously preprocessed with
$’ in identifiers. See Identifier characters.
- Accept universal character names in identifiers. This option is experimental; in a future version of GCC, it will be enabled by default for C99 and C++.
- When preprocessing, do not shorten system header paths with canonicalization.
Indicate to the preprocessor that the input file has already been preprocessed. This suppresses things like macro expansion, trigraph conversion, escaped newline splicing, and processing of most directives. The preprocessor still recognizes and removes comments, so that you can pass a file preprocessed with
-Cto the compiler without problems. In this mode the integrated preprocessor is little more than a tokenizer for the front ends.
-fpreprocessedis implicit if the input file has one of the extensions ‘
.ii’ or ‘
.mi’. These are the extensions that GCC uses for preprocessed files created by
- Set the distance between tab stops. This helps the preprocessor report correct column numbers in warnings or errors, even if tabs appear on the line. If the value is less than 1 or greater than 100, the option is ignored. The default is 8.
This option is only useful for debugging GCC. When used with
-E, dumps debugging information about location maps. Every token in the output is preceded by the dump of the map its location belongs to. The dump of the map holding the location of a token would be:
When used without
-E, this option has no effect.
Track locations of tokens across macro expansions. This allows the compiler to emit diagnostic about the current macro expansion stack when a compilation error occurs in a macro expansion. Using this option makes the preprocessor and the compiler consume more memory. The level parameter can be used to choose the level of precision of token location tracking thus decreasing the memory consumption if necessary. Value ‘
0’ of level de-activates this option just as if no
-ftrack-macro-expansionwas present on the command line. Value ‘
1’ tracks tokens locations in a degraded mode for the sake of minimal memory overhead. In this mode all tokens resulting from the expansion of an argument of a function-like macro have the same location. Value ‘
2’ tracks tokens locations completely. This value is the most memory hungry. When this option is given no argument, the default parameter value is ‘
Note that -ftrack-macro-expansion=2 is activated by default.
Set the execution character set, used for string and character constants. The default is UTF-8. charset can be any encoding supported by the system's
Set the wide execution character set, used for wide string and character constants. The default is UTF-32 or UTF-16, whichever corresponds to the width of
wchar_t. As with
-fexec-charset, charset can be any encoding supported by the system's
iconvlibrary routine; however, you will have problems with encodings that do not fit exactly in
Set the input character set, used for translation from the character set of the input file to the source character set used by GCC. If the locale does not specify, or GCC cannot get this information from the locale, the default is UTF-8. This can be overridden by either the locale or this command line option. Currently the command line option takes precedence if there's a conflict. charset can be any encoding supported by the system's
Enable generation of linemarkers in the preprocessor output that will let the compiler know the current working directory at the time of preprocessing. When this option is enabled, the preprocessor will emit, after the initial linemarker, a second linemarker with the current working directory followed by two slashes. GCC will use this directory, when it's present in the preprocessed input, as the directory emitted as the current working directory in some debugging information formats. This option is implicitly enabled if debugging information is enabled, but this can be inhibited with the negated form
-fno-working-directory. If the
-Pflag is present in the command line, this option has no effect, since no
#linedirectives are emitted whatsoever.
Do not print column numbers in diagnostics. This may be necessary if diagnostics are being scanned by a program that does not understand the column numbers, such as
- Make an assertion with the predicate predicate and answer answer. This form is preferred to the older form -A predicate(answer), which is still supported, because it does not use shell special characters. See Obsolete Features.
- Cancel an assertion with the predicate predicate and answer answer.
CHARS is a sequence of one or more of the following characters, and must not be preceded by a space. Other characters are interpreted by the compiler proper, or reserved for future versions of GCC, and so are silently ignored. If you specify characters whose behavior conflicts, the result is undefined.
Instead of the normal output, generate a list of ‘
#define’ directives for all the macros defined during the execution of the preprocessor, including predefined macros. This gives you a way of finding out what is predefined in your version of the preprocessor. Assuming you have no file
foo.h, the command
touch foo.h; cpp -dM foo.h
will show all the predefined macros.
If you use
-dMis interpreted as a synonym for
-fdump-rtl-mach. See Debugging Options.
M’ except in two respects: it does not include the predefined macros, and it outputs both the ‘
#define’ directives and the result of preprocessing. Both kinds of output go to the standard output file.
D’, but emit only the macro names, not their expansions.
#include’ directives in addition to the result of preprocessing.
D’ except that only macros that are expanded, or whose definedness is tested in preprocessor directives, are output; the output is delayed until the use or test of the macro; and ‘
#undef’ directives are also output for macros tested but undefined at the time.
- Inhibit generation of linemarkers in the output from the preprocessor. This might be useful when running the preprocessor on something that is not C code, and will be sent to a program which might be confused by the linemarkers. See Preprocessor Output.
Do not discard comments. All comments are passed through to the output file, except for comments in processed directives, which are deleted along with the directive.
You should be prepared for side effects when using
-C; it causes the preprocessor to treat comments as tokens in their own right. For example, comments appearing at the start of what would be a directive line have the effect of turning that line into an ordinary source line, since the first token on the line is no longer a ‘
- Do not discard comments, including during macro expansion. This is like
-C, except that comments contained within macros are also passed through to the output file where the macro is expanded.
In addition to the side-effects of the
-CCoption causes all C++-style comments inside a macro to be converted to C-style comments. This is to prevent later use of that macro from inadvertently commenting out the remainder of the source line.
-CCoption is generally used to support lint comments.
- Try to imitate the behavior of old-fashioned C preprocessors, as opposed to ISO C preprocessors. See Traditional Mode.
- Process trigraph sequences. See Initial processing.
- Enable special code to work around file systems which only permit very short file names, such as MS-DOS.
- Print text describing all the command line options instead of preprocessing anything.
- Verbose mode. Print out GNU CPP's version number at the beginning of execution, and report the final form of the include path.
Print the name of each header file used, in addition to other normal activities. Each name is indented to show how deep in the ‘
#include’ stack it is. Precompiled header files are also printed, even if they are found to be invalid; an invalid precompiled header file is printed with ‘
...x’ and a valid one with ‘
- Print out GNU CPP's version number. With one dash, proceed to preprocess as normal. With two dashes, exit immediately.
© Free Software Foundation
Licensed under the GNU Free Documentation License, Version 1.3.