{ "mode": "man", "parameter": "x86_64-linux-gnu-cpp", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/x86_64-linux-gnu-cpp/1/json", "generated": "2026-09-01T16:56:28Z", "synopsis": "cpp [-Dmacro[=defn]...] [-Umacro]\n[-Idir...] [-iquotedir...]\n[-M|-MM] [-MG] [-MF filename]\n[-MP] [-MQ target...]\n[-MT target...]\ninfile [[-o] outfile]\nOnly the most useful options are given above; see below for a more complete list of\npreprocessor-specific options. In addition, cpp accepts most gcc driver options, which are\nnot listed here. Refer to the GCC documentation for details.", "sections": { "NAME": { "content": "cpp - The C Preprocessor\n", "subsections": [] }, "SYNOPSIS": { "content": "cpp [-Dmacro[=defn]...] [-Umacro]\n[-Idir...] [-iquotedir...]\n[-M|-MM] [-MG] [-MF filename]\n[-MP] [-MQ target...]\n[-MT target...]\ninfile [[-o] outfile]\n\nOnly the most useful options are given above; see below for a more complete list of\npreprocessor-specific options. In addition, cpp accepts most gcc driver options, which are\nnot listed here. Refer to the GCC documentation for details.\n", "subsections": [] }, "DESCRIPTION": { "content": "The C preprocessor, often known as cpp, is a macro processor that is used automatically by\nthe C compiler to transform your program before compilation. It is called a macro processor\nbecause it allows you to define macros, which are brief abbreviations for longer constructs.\n\nThe C preprocessor is intended to be used only with C, C++, and Objective-C source code. In\nthe past, it has been abused as a general text processor. It will choke on input which does\nnot obey C's lexical rules. For example, apostrophes will be interpreted as the beginning of\ncharacter constants, and cause errors. Also, you cannot rely on it preserving\ncharacteristics of the input which are not significant to C-family languages. If a Makefile\nis preprocessed, all the hard tabs will be removed, and the Makefile will not work.\n\nHaving said that, you can often get away with using cpp on things which are not C. Other\nAlgol-ish programming languages are often safe (Ada, etc.) So is assembly, with caution.", "subsections": [ { "name": "-traditional-cpp", "content": "the problems can be avoided by writing C or C++ style comments instead of native language\ncomments, and keeping macros simple.\n\nWherever possible, you should use a preprocessor geared to the language you are writing in.\nModern versions of the GNU assembler have macro facilities. Most high level programming\nlanguages have their own conditional compilation and inclusion mechanism. If all else fails,\ntry a true general text processor, such as GNU M4.\n\nC preprocessors vary in some details. This manual discusses the GNU C preprocessor, which\nprovides a small superset of the features of ISO Standard C. In its default mode, the GNU C\npreprocessor does not do a few things required by the standard. These are features which are\nrarely, if ever, used, and may cause surprising changes to the meaning of a program which\ndoes not expect them. To get strict ISO Standard C, you should use the -std=c90, -std=c99," }, { "name": "-std=c11 -std=c17", "content": "all the mandatory diagnostics, you must also use -pedantic.\n\nThis manual describes the behavior of the ISO preprocessor. To minimize gratuitous\ndifferences, where the ISO preprocessor's behavior does not conflict with traditional\nsemantics, the traditional preprocessor should behave the same way. The various differences\nthat do exist are detailed in the section Traditional Mode.\n\nFor clarity, unless noted otherwise, references to CPP in this manual refer to GNU CPP.\n" } ] }, "OPTIONS": { "content": "The cpp command expects two file names as arguments, infile and outfile. The preprocessor\nreads infile together with any other files it specifies with #include. All the output\ngenerated by the combined input files is written in outfile.\n\nEither infile or outfile may be -, which as infile means to read from standard input and as\noutfile means to write to standard output. If either file is omitted, it means the same as\nif - had been specified for that file. You can also use the -o outfile option to specify the\noutput file.\n\nUnless otherwise noted, or the option ends in =, all options which take an argument may have\nthat argument appear either immediately after the option, or with a space between option and\nargument: -Ifoo and -I foo have the same effect.\n\nMany options have multi-letter names; therefore multiple single-letter options may not be\ngrouped: -dM is very different from -d -M.\n", "subsections": [ { "name": "-D _", "content": "Predefine name as a macro, with definition 1.\n", "flag": "-D" }, { "name": "-D _", "content": "The contents of definition are tokenized and processed as if they appeared during\ntranslation phase three in a #define directive. In particular, the definition is\ntruncated by embedded newline characters.\n\nIf you are invoking the preprocessor from a shell or shell-like program you may need to\nuse the shell's quoting syntax to protect characters such as spaces that have a meaning\nin the shell syntax.\n\nIf you wish to define a function-like macro on the command line, write its argument list\nwith surrounding parentheses before the equals sign (if any). Parentheses are meaningful\nto most shells, so you should quote the option. With sh and csh,\n-D'name(args...)=definition' works.\n\n-D and -U options are processed in the order they are given on the command line. All\n-imacros file and -include file options are processed after all -D and -U options.\n", "flag": "-D" }, { "name": "-U _", "content": "Cancel any previous definition of name, either built in or provided with a -D option.\n", "flag": "-U" }, { "name": "-include _", "content": "Process file as if \"#include \"file\"\" appeared as the first line of the primary source\nfile. However, the first directory searched for file is the preprocessor's working\ndirectory instead of the directory containing the main source file. If not found there,\nit is searched for in the remainder of the \"#include \"...\"\" search chain as normal.\n\nIf multiple -include options are given, the files are included in the order they appear\non the command line.\n" }, { "name": "-imacros _", "content": "Exactly like -include, except that any output produced by scanning file is thrown away.\nMacros it defines remain defined. This allows you to acquire all the macros from a\nheader without also processing its declarations.\n\nAll files specified by -imacros are processed before all files specified by -include.\n" }, { "name": "-undef", "content": "Do not predefine any system-specific or GCC-specific macros. The standard predefined\nmacros remain defined.\n" }, { "name": "-pthread", "content": "Define additional macros required for using the POSIX threads library. You should use\nthis option consistently for both compilation and linking. This option is supported on\nGNU/Linux targets, most other Unix derivatives, and also on x86 Cygwin and MinGW targets.\n" }, { "name": "-M", "content": "describing the dependencies of the main source file. The preprocessor outputs one make\nrule containing the object file name for that source file, a colon, and the names of all\nthe included files, including those coming from -include or -imacros command-line\noptions.\n\nUnless specified explicitly (with -MT or -MQ), the object file name consists of the name\nof the source file with any suffix replaced with object file suffix and with any leading\ndirectory parts removed. If there are many included files then the rule is split into\nseveral lines using \\-newline. The rule has no commands.\n\nThis option does not suppress the preprocessor's debug output, such as -dM. To avoid\nmixing such debug output with the dependency rules you should explicitly specify the\ndependency output file with -MF, or use an environment variable like DEPENDENCIESOUTPUT.\nDebug output is still sent to the regular output stream as normal.\n\nPassing -M to the driver implies -E, and suppresses warnings with an implicit -w.\n", "flag": "-M" }, { "name": "-MM -M", "content": "header files that are included, directly or indirectly, from such a header.\n\nThis implies that the choice of angle brackets or double quotes in an #include directive\ndoes not in itself determine whether that header appears in -MM dependency output.\n", "flag": "-M" }, { "name": "-MF _", "content": "When used with -M or -MM, specifies a file to write the dependencies to. If no -MF\nswitch is given the preprocessor sends the rules to the same place it would send\npreprocessed output.\n\nWhen used with the driver options -MD or -MMD, -MF overrides the default dependency\noutput file.\n\nIf file is -, then the dependencies are written to stdout.\n" }, { "name": "-MG -M -MG", "content": "missing header files are generated files and adds them to the dependency list without\nraising an error. The dependency filename is taken directly from the \"#include\"\ndirective without prepending any path. -MG also suppresses preprocessed output, as a\nmissing header file renders this useless.\n\nThis feature is used in automatic updating of makefiles.\n", "flag": "-M" }, { "name": "-Mno-modules", "content": "Disable dependency generation for compiled module interfaces.\n" }, { "name": "-MP", "content": "file, causing each to depend on nothing. These dummy rules work around errors make gives\nif you remove header files without updating the Makefile to match.\n\nThis is typical output:\n\ntest.o: test.c test.h\n\ntest.h:\n" }, { "name": "-MT _", "content": "Change the target of the rule emitted by dependency generation. By default CPP takes the\nname of the main input file, deletes any directory components and any file suffix such as\n.c, and appends the platform's usual object suffix. The result is the target.\n\nAn -MT option sets the target to be exactly the string you specify. If you want multiple\ntargets, you can specify them as a single argument to -MT, or use multiple -MT options.\n\nFor example, -MT '$(objpfx)foo.o' might give\n\n$(objpfx)foo.o: foo.c\n" }, { "name": "-MQ _", "content": "Same as -MT, but it quotes any characters which are special to Make.\n-MQ '$(objpfx)foo.o' gives\n\n$$(objpfx)foo.o: foo.c\n\nThe default target is automatically quoted, as if it were given with -MQ.\n" }, { "name": "-MD -MD -M -MF _ -E", "content": "file based on whether an -o option is given. If it is, the driver uses its argument but\nwith a suffix of .d, otherwise it takes the name of the input file, removes any directory\ncomponents and suffix, and applies a .d suffix.\n\nIf -MD is used in conjunction with -E, any -o switch is understood to specify the\ndependency output file, but if used without -E, each -o is understood to specify a target\nobject file.\n\nSince -E is not implied, -MD can be used to generate a dependency output file as a side\neffect of the compilation process.\n", "flag": "-E" }, { "name": "-MMD", "content": "Like -MD except mention only user header files, not system header files.\n" }, { "name": "-fpreprocessed", "content": "Indicate to the preprocessor that the input file has already been preprocessed. This\nsuppresses things like macro expansion, trigraph conversion, escaped newline splicing,\nand processing of most directives. The preprocessor still recognizes and removes\ncomments, so that you can pass a file preprocessed with -C to the compiler without\nproblems. In this mode the integrated preprocessor is little more than a tokenizer for\nthe front ends.\n\n-fpreprocessed is implicit if the input file has one of the extensions .i, .ii or .mi.\nThese are the extensions that GCC uses for preprocessed files created by -save-temps.\n" }, { "name": "-fdirectives-only", "content": "When preprocessing, handle directives, but do not expand macros.\n\nThe option's behavior depends on the -E and -fpreprocessed options.\n\nWith -E, preprocessing is limited to the handling of directives such as \"#define\",\n\"#ifdef\", and \"#error\". Other preprocessor operations, such as macro expansion and\ntrigraph conversion are not performed. In addition, the -dD option is implicitly\nenabled.\n\nWith -fpreprocessed, predefinition of command line and most builtin macros is disabled.\nMacros such as \"LINE\", which are contextually dependent, are handled normally. This\nenables compilation of files previously preprocessed with \"-E -fdirectives-only\".\n\nWith both -E and -fpreprocessed, the rules for -fpreprocessed take precedence. This\nenables full preprocessing of files previously preprocessed with \"-E -fdirectives-only\".\n" }, { "name": "-fdollars-in-identifiers", "content": "Accept $ in identifiers.\n" }, { "name": "-fextended-identifiers", "content": "Accept universal character names and extended characters in identifiers. This option is\nenabled by default for C99 (and later C standard versions) and C++.\n" }, { "name": "-fno-canonical-system-headers", "content": "When preprocessing, do not shorten system header paths with canonicalization.\n" }, { "name": "-fmax-include-depth=_", "content": "Set the maximum depth of the nested #include. The default is 200.\n" }, { "name": "-ftabstop=_", "content": "Set the distance between tab stops. This helps the preprocessor report correct column\nnumbers in warnings or errors, even if tabs appear on the line. If the value is less\nthan 1 or greater than 100, the option is ignored. The default is 8.\n" }, { "name": "-ftrack-macro-expansion", "content": "Track locations of tokens across macro expansions. This allows the compiler to emit\ndiagnostic about the current macro expansion stack when a compilation error occurs in a\nmacro expansion. Using this option makes the preprocessor and the compiler consume more\nmemory. The level parameter can be used to choose the level of precision of token\nlocation tracking thus decreasing the memory consumption if necessary. Value 0 of level\nde-activates this option. Value 1 tracks tokens locations in a degraded mode for the sake\nof minimal memory overhead. In this mode all tokens resulting from the expansion of an\nargument of a function-like macro have the same location. Value 2 tracks tokens locations\ncompletely. This value is the most memory hungry. When this option is given no argument,\nthe default parameter value is 2.\n\nNote that \"-ftrack-macro-expansion=2\" is activated by default.\n" }, { "name": "-fmacro-prefix-map=_", "content": "When preprocessing files residing in directory old, expand the \"FILE\" and\n\"BASEFILE\" macros as if the files resided in directory new instead. This can be\nused to change an absolute path to a relative path by using . for new which can result in\nmore reproducible builds that are location independent. This option also affects\n\"builtinFILE()\" during compilation. See also -ffile-prefix-map and\n-fcanon-prefix-map.\n" }, { "name": "-fexec-charset=_", "content": "Set the execution character set, used for string and character constants. The default is\nUTF-8. charset can be any encoding supported by the system's \"iconv\" library routine.\n" }, { "name": "-fwide-exec-charset=_", "content": "Set the wide execution character set, used for wide string and character constants. The\ndefault is one of UTF-32BE, UTF-32LE, UTF-16BE, or UTF-16LE, whichever corresponds to the\nwidth of \"wchart\" and the big-endian or little-endian byte order being used for code\ngeneration. As with -fexec-charset, charset can be any encoding supported by the\nsystem's \"iconv\" library routine; however, you will have problems with encodings that do\nnot fit exactly in \"wchart\".\n" }, { "name": "-finput-charset=_", "content": "Set the input character set, used for translation from the character set of the input\nfile to the source character set used by GCC. If the locale does not specify, or GCC\ncannot get this information from the locale, the default is UTF-8. This can be\noverridden by either the locale or this command-line option. Currently the command-line\noption takes precedence if there's a conflict. charset can be any encoding supported by\nthe system's \"iconv\" library routine.\n" }, { "name": "-fworking-directory", "content": "Enable generation of linemarkers in the preprocessor output that let the compiler know\nthe current working directory at the time of preprocessing. When this option is enabled,\nthe preprocessor emits, after the initial linemarker, a second linemarker with the\ncurrent working directory followed by two slashes. GCC uses this directory, when it's\npresent in the preprocessed input, as the directory emitted as the current working\ndirectory in some debugging information formats. This option is implicitly enabled if\ndebugging information is enabled, but this can be inhibited with the negated form\n-fno-working-directory. If the -P flag is present in the command line, this option has\nno effect, since no \"#line\" directives are emitted whatsoever.\n" }, { "name": "-A _", "content": "Make an assertion with the predicate predicate and answer answer. This form is preferred\nto the older form -A predicate(answer), which is still supported, because it does not use\nshell special characters.\n", "flag": "-A" }, { "name": "-A -_", "content": "Cancel an assertion with the predicate predicate and answer answer.\n", "flag": "-A" }, { "name": "-C", "content": "comments in processed directives, which are deleted along with the directive.\n\nYou should be prepared for side effects when using -C; it causes the preprocessor to\ntreat comments as tokens in their own right. For example, comments appearing at the\nstart of what would be a directive line have the effect of turning that line into an\nordinary source line, since the first token on the line is no longer a #.\n", "flag": "-C" }, { "name": "-CC -C", "content": "comments contained within macros are also passed through to the output file where the\nmacro is expanded.\n\nIn addition to the side effects of the -C option, the -CC option causes all C++-style\ncomments inside a macro to be converted to C-style comments. This is to prevent later\nuse of that macro from inadvertently commenting out the remainder of the source line.\n\nThe -CC option is generally used to support lint comments.\n", "flag": "-C" }, { "name": "-P", "content": "useful when running the preprocessor on something that is not C code, and will be sent to\na program which might be confused by the linemarkers.\n", "flag": "-P" }, { "name": "-traditional", "content": "" }, { "name": "-traditional-cpp", "content": "Try to imitate the behavior of pre-standard C preprocessors, as opposed to ISO C\npreprocessors.\n\nNote that GCC does not otherwise attempt to emulate a pre-standard C compiler, and these\noptions are only supported with the -E switch, or when invoking CPP explicitly.\n" }, { "name": "-trigraphs", "content": "Support ISO C trigraphs. These are three-character sequences, all starting with ??, that\nare defined by ISO C to stand for single characters. For example, ??/ stands for \\, so\n'??/n' is a character constant for a newline.\n\nBy default, GCC ignores trigraphs, but in standard-conforming modes it converts them.\nSee the -std and -ansi options.\n" }, { "name": "-remap", "content": "Enable special code to work around file systems which only permit very short file names,\nsuch as MS-DOS.\n" }, { "name": "-H", "content": "name is indented to show how deep in the #include stack it is. Precompiled header files\nare also printed, even if they are found to be invalid; an invalid precompiled header\nfile is printed with ...x and a valid one with ...! .\n", "flag": "-H" }, { "name": "-d_", "content": "Says to make debugging dumps during compilation as specified by letters. The flags\ndocumented here are those relevant to the preprocessor. Other letters are interpreted by\nthe compiler proper, or reserved for future versions of GCC, and so are silently ignored.\nIf you specify letters whose behavior conflicts, the result is undefined.\n\n-dM Instead of the normal output, generate a list of #define directives for all the\nmacros defined during the execution of the preprocessor, including predefined macros.\nThis gives you a way of finding out what is predefined in your version of the\npreprocessor. Assuming you have no file foo.h, the command\n\ntouch foo.h; cpp -dM foo.h\n\nshows all the predefined macros.\n\n-dD Like -dM except in two respects: it does not include the predefined macros, and it\noutputs both the #define directives and the result of preprocessing. Both kinds of\noutput go to the standard output file.\n\n-dN Like -dD, but emit only the macro names, not their expansions.\n\n-dI Output #include directives in addition to the result of preprocessing.\n\n-dU Like -dD except that only macros that are expanded, or whose definedness is tested in\npreprocessor directives, are output; the output is delayed until the use or test of\nthe macro; and #undef directives are also output for macros tested but undefined at\nthe time.\n" }, { "name": "-fdebug-cpp", "content": "This option is only useful for debugging GCC. When used from CPP or with -E, it dumps\ndebugging information about location maps. Every token in the output is preceded by the\ndump of the map its location belongs to.\n\nWhen used from GCC without -E, this option has no effect.\n" }, { "name": "-I _", "content": "", "flag": "-I" }, { "name": "-iquote _", "content": "" }, { "name": "-isystem _", "content": "" }, { "name": "-idirafter _", "content": "Add the directory dir to the list of directories to be searched for header files during\npreprocessing.\n\nIf dir begins with = or $SYSROOT, then the = or $SYSROOT is replaced by the sysroot\nprefix; see --sysroot and -isysroot.\n\nDirectories specified with -iquote apply only to the quote form of the directive,\n\"#include \"file\"\". Directories specified with -I, -isystem, or -idirafter apply to\nlookup for both the \"#include \"file\"\" and \"#include \" directives.\n\nYou can specify any number or combination of these options on the command line to search\nfor header files in several directories. The lookup order is as follows:\n\n1. For the quote form of the include directive, the directory of the current file is\nsearched first.\n\n2. For the quote form of the include directive, the directories specified by -iquote\noptions are searched in left-to-right order, as they appear on the command line.\n\n3. Directories specified with -I options are scanned in left-to-right order.\n\n4. Directories specified with -isystem options are scanned in left-to-right order.\n\n5. Standard system directories are scanned.\n\n6. Directories specified with -idirafter options are scanned in left-to-right order.\n\nYou can use -I to override a system header file, substituting your own version, since\nthese directories are searched before the standard system header file directories.\nHowever, you should not use this option to add directories that contain vendor-supplied\nsystem header files; use -isystem for that.\n\nThe -isystem and -idirafter options also mark the directory as a system directory, so\nthat it gets the same special treatment that is applied to the standard system\ndirectories.\n\nIf a standard system include directory, or a directory specified with -isystem, is also\nspecified with -I, the -I option is ignored. The directory is still searched but as a\nsystem directory at its normal position in the system include chain. This is to ensure\nthat GCC's procedure to fix buggy system headers and the ordering for the \"#includenext\"\ndirective are not inadvertently changed. If you really need to change the search order\nfor system directories, use the -nostdinc and/or -isystem options.\n" }, { "name": "-I- -iquote", "content": "-I directories before the -I- and remove the -I- option.\n\nAny directories specified with -I options before -I- are searched only for headers\nrequested with \"#include \"file\"\"; they are not searched for \"#include \". If\nadditional directories are specified with -I options after the -I-, those directories are\nsearched for all #include directives.\n\nIn addition, -I- inhibits the use of the directory of the current file directory as the\nfirst search directory for \"#include \"file\"\". There is no way to override this effect of\n-I-.\n" }, { "name": "-iprefix _", "content": "Specify prefix as the prefix for subsequent -iwithprefix options. If the prefix\nrepresents a directory, you should include the final /.\n" }, { "name": "-iwithprefix _", "content": "" }, { "name": "-iwithprefixbefore _", "content": "Append dir to the prefix specified previously with -iprefix, and add the resulting\ndirectory to the include search path. -iwithprefixbefore puts it in the same place -I\nwould; -iwithprefix puts it where -idirafter would.\n" }, { "name": "-isysroot _", "content": "This option is like the --sysroot option, but applies only to header files (except for\nDarwin targets, where it applies to both header files and libraries). See the --sysroot\noption for more information.\n" }, { "name": "-imultilib _", "content": "Use dir as a subdirectory of the directory containing target-specific C++ headers.\n" }, { "name": "-nostdinc", "content": "Do not search the standard system directories for header files. Only the directories\nexplicitly specified with -I, -iquote, -isystem, and/or -idirafter options (and the\ndirectory of the current file, if appropriate) are searched.\n" }, { "name": "-nostdinc++", "content": "Do not search for header files in the C++-specific standard directories, but do still\nsearch the other standard directories. (This option is used when building the C++\nlibrary.)\n" }, { "name": "-Wcomment", "content": "" }, { "name": "-Wcomments", "content": "Warn whenever a comment-start sequence /* appears in a /* comment, or whenever a\nbackslash-newline appears in a // comment. This warning is enabled by -Wall.\n" }, { "name": "-Wtrigraphs", "content": "Warn if any trigraphs are encountered that might change the meaning of the program.\nTrigraphs within comments are not warned about, except those that would form escaped\nnewlines.\n\nThis option is implied by -Wall. If -Wall is not given, this option is still enabled\nunless trigraphs are enabled. To get trigraph conversion without warnings, but get the\nother -Wall warnings, use -trigraphs -Wall -Wno-trigraphs.\n" }, { "name": "-Wundef", "content": "Warn if an undefined identifier is evaluated in an \"#if\" directive. Such identifiers are\nreplaced with zero.\n" }, { "name": "-Wexpansion-to-defined", "content": "Warn whenever defined is encountered in the expansion of a macro (including the case\nwhere the macro is expanded by an #if directive). Such usage is not portable. This\nwarning is also enabled by -Wpedantic and -Wextra.\n" }, { "name": "-Wunused-macros", "content": "Warn about macros defined in the main file that are unused. A macro is used if it is\nexpanded or tested for existence at least once. The preprocessor also warns if the macro\nhas not been used at the time it is redefined or undefined.\n\nBuilt-in macros, macros defined on the command line, and macros defined in include files\nare not warned about.\n\nNote: If a macro is actually used, but only used in skipped conditional blocks, then the\npreprocessor reports it as unused. To avoid the warning in such a case, you might\nimprove the scope of the macro's definition by, for example, moving it into the first\nskipped block. Alternatively, you could provide a dummy use with something like:\n\n#if defined themacrocausingthewarning\n#endif\n" }, { "name": "-Wno-endif-labels", "content": "Do not warn whenever an \"#else\" or an \"#endif\" are followed by text. This sometimes\nhappens in older programs with code of the form\n\n#if FOO\n...\n#else FOO\n...\n#endif FOO\n\nThe second and third \"FOO\" should be in comments. This warning is on by default.\n" } ] }, "ENVIRONMENT": { "content": "This section describes the environment variables that affect how CPP operates. You can use\nthem to specify directories or prefixes to use when searching for include files, or to\ncontrol dependency output.\n\nNote that you can also specify places to search using options such as -I, and control\ndependency output with options like -M. These take precedence over environment variables,\nwhich in turn take precedence over the configuration of GCC.\n\nCPATH\nCINCLUDEPATH\nCPLUSINCLUDEPATH\nOBJCINCLUDEPATH\nEach variable's value is a list of directories separated by a special character, much\nlike PATH, in which to look for header files. The special character, \"PATHSEPARATOR\",\nis target-dependent and determined at GCC build time. For Microsoft Windows-based\ntargets it is a semicolon, and for almost all other targets it is a colon.\n\nCPATH specifies a list of directories to be searched as if specified with -I, but after\nany paths given with -I options on the command line. This environment variable is used\nregardless of which language is being preprocessed.\n\nThe remaining environment variables apply only when preprocessing the particular language\nindicated. Each specifies a list of directories to be searched as if specified with\n-isystem, but after any paths given with -isystem options on the command line.\n\nIn all these variables, an empty element instructs the compiler to search its current\nworking directory. Empty elements can appear at the beginning or end of a path. For\ninstance, if the value of CPATH is \":/special/include\", that has the same effect as\n-I. -I/special/include.\n\nDEPENDENCIESOUTPUT\nIf this variable is set, its value specifies how to output dependencies for Make based on\nthe non-system header files processed by the compiler. System header files are ignored\nin the dependency output.\n\nThe value of DEPENDENCIESOUTPUT can be just a file name, in which case the Make rules\nare written to that file, guessing the target name from the source file name. Or the\nvalue can have the form file target, in which case the rules are written to file file\nusing target as the target name.\n\nIn other words, this environment variable is equivalent to combining the options -MM and\n-MF, with an optional -MT switch too.\n\nSUNPRODEPENDENCIES\nThis variable is the same as DEPENDENCIESOUTPUT (see above), except that system header\nfiles are not ignored, so it implies -M rather than -MM. However, the dependence on the\nmain input file is omitted.\n\nSOURCEDATEEPOCH\nIf this variable is set, its value specifies a UNIX timestamp to be used in replacement\nof the current date and time in the \"DATE\" and \"TIME\" macros, so that the\nembedded timestamps become reproducible.\n\nThe value of SOURCEDATEEPOCH must be a UNIX timestamp, defined as the number of seconds\n(excluding leap seconds) since 01 Jan 1970 00:00:00 represented in ASCII; identical to\nthe output of \"date +%s\" on GNU/Linux and other systems that support the %s extension in\nthe \"date\" command.\n\nThe value should be a known timestamp such as the last modification time of the source or\npackage and it should be set by the build process.\n", "subsections": [] }, "SEE ALSO": { "content": "gpl(7), gfdl(7), fsf-funding(7), gcc(1), and the Info entries for cpp and gcc.\n", "subsections": [] }, "COPYRIGHT": { "content": "Copyright (c) 1987-2023 Free Software Foundation, Inc.\n\nPermission is granted to copy, distribute and/or modify this document under the terms of the\nGNU Free Documentation License, Version 1.3 or any later version published by the Free\nSoftware Foundation. A copy of the license is included in the man page gfdl(7). This manual\ncontains no Invariant Sections. The Front-Cover Texts are (a) (see below), and the Back-\nCover Texts are (b) (see below).\n\n(a) The FSF's Front-Cover Text is:\n\nA GNU Manual\n\n(b) The FSF's Back-Cover Text is:\n\nYou have freedom to copy and modify this GNU Manual, like GNU\nsoftware. Copies published by the Free Software Foundation raise\nfunds for GNU development.\n\ngcc-13 2024-09-04 CPP(1)", "subsections": [] } }, "summary": "cpp - The C Preprocessor", "flags": [ { "flag": "-D", "long": null, "arg": null, "description": "Predefine name as a macro, with definition 1." }, { "flag": "-D", "long": null, "arg": null, "description": "The contents of definition are tokenized and processed as if they appeared during translation phase three in a #define directive. In particular, the definition is 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 should quote the option. With sh and csh, -D'name(args...)=definition' works. -D and -U options are processed in the order they are given on the command line. All -imacros file and -include file options are processed after all -D and -U options." }, { "flag": "-U", "long": null, "arg": null, "description": "Cancel any previous definition of name, either built in or provided with a -D option." }, { "flag": "", "long": null, "arg": null, "description": "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. If multiple -include options are given, the files are included in the order they appear on the command line." }, { "flag": "", "long": null, "arg": null, "description": "Exactly like -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 -imacros are processed before all files specified by -include." }, { "flag": "", "long": null, "arg": null, "description": "Do not predefine any system-specific or GCC-specific macros. The standard predefined macros remain defined." }, { "flag": "", "long": null, "arg": null, "description": "Define additional macros required for using the POSIX threads library. You should use this option consistently for both compilation and linking. This option is supported on GNU/Linux targets, most other Unix derivatives, and also on x86 Cygwin and MinGW targets." }, { "flag": "-M", "long": null, "arg": null, "description": "describing the dependencies of the main source file. The preprocessor outputs one make rule containing the object file name for that source file, a colon, and the names of all the included files, including those coming from -include or -imacros command-line options. Unless specified explicitly (with -MT or -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 DEPENDENCIESOUTPUT. Debug output is still sent to the regular output stream as normal. Passing -M to the driver implies -E, and suppresses warnings with an implicit -w." }, { "flag": "-M", "long": null, "arg": null, "description": "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 appears in -MM dependency output." }, { "flag": "", "long": null, "arg": null, "description": "When used with -M or -MM, specifies a file to write the dependencies to. If no -MF switch is given the preprocessor sends the rules to the same place it would send preprocessed output. When used with the driver options -MD or -MMD, -MF overrides the default dependency output file. If file is -, then the dependencies are written to stdout." }, { "flag": "-M", "long": null, "arg": null, "description": "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 \"#include\" directive without prepending any path. -MG also suppresses preprocessed output, as a missing header file renders this useless. This feature is used in automatic updating of makefiles." }, { "flag": "", "long": null, "arg": null, "description": "Disable dependency generation for compiled module interfaces." }, { "flag": "", "long": null, "arg": null, "description": "file, causing each to depend on nothing. These dummy rules work around errors make gives if you remove header files without updating the Makefile to match. This is typical output: test.o: test.c test.h test.h:" }, { "flag": "", "long": null, "arg": null, "description": "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. An -MT option sets 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 options. For example, -MT '$(objpfx)foo.o' might give $(objpfx)foo.o: foo.c" }, { "flag": "", "long": null, "arg": null, "description": "Same as -MT, but it quotes any characters which are special to Make. -MQ '$(objpfx)foo.o' gives $$(objpfx)foo.o: foo.c The default target is automatically quoted, as if it were given with -MQ." }, { "flag": "-E", "long": null, "arg": null, "description": "file based on whether an -o option 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 .d suffix. If -MD is used in conjunction with -E, any -o switch is understood to specify the dependency output file, but if used without -E, each -o is understood to specify a target object file. Since -E is not implied, -MD can be used to generate a dependency output file as a side effect of the compilation process." }, { "flag": "", "long": null, "arg": null, "description": "Like -MD except mention only user header files, not system header files." }, { "flag": "", "long": null, "arg": null, "description": "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 -C to the compiler without problems. In this mode the integrated preprocessor is little more than a tokenizer for the front ends. -fpreprocessed is implicit if the input file has one of the extensions .i, .ii or .mi. These are the extensions that GCC uses for preprocessed files created by -save-temps." }, { "flag": "", "long": null, "arg": null, "description": "When preprocessing, handle directives, but do not expand macros. The option's behavior depends on the -E and -fpreprocessed options. With -E, preprocessing is limited to the handling of directives such as \"#define\", \"#ifdef\", and \"#error\". Other preprocessor operations, such as macro expansion and trigraph conversion are not performed. In addition, the -dD option is implicitly enabled. With -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 \"-E -fdirectives-only\". With both -E and -fpreprocessed, the rules for -fpreprocessed take precedence. This enables full preprocessing of files previously preprocessed with \"-E -fdirectives-only\"." }, { "flag": "", "long": null, "arg": null, "description": "Accept $ in identifiers." }, { "flag": "", "long": null, "arg": null, "description": "Accept universal character names and extended characters in identifiers. This option is enabled by default for C99 (and later C standard versions) and C++." }, { "flag": "", "long": null, "arg": null, "description": "When preprocessing, do not shorten system header paths with canonicalization." }, { "flag": "", "long": null, "arg": null, "description": "Set the maximum depth of the nested #include. The default is 200." }, { "flag": "", "long": null, "arg": null, "description": "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." }, { "flag": "", "long": null, "arg": null, "description": "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. 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 2. Note that \"-ftrack-macro-expansion=2\" is activated by default." }, { "flag": "", "long": null, "arg": null, "description": "When preprocessing files residing in directory old, expand the \"FILE\" and \"BASEFILE\" macros as if the files resided in directory new instead. This can be used to change an absolute path to a relative path by using . for new which can result in more reproducible builds that are location independent. This option also affects \"builtinFILE()\" during compilation. See also -ffile-prefix-map and -fcanon-prefix-map." }, { "flag": "", "long": null, "arg": null, "description": "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 \"iconv\" library routine." }, { "flag": "", "long": null, "arg": null, "description": "Set the wide execution character set, used for wide string and character constants. The default is one of UTF-32BE, UTF-32LE, UTF-16BE, or UTF-16LE, whichever corresponds to the width of \"wchart\" and the big-endian or little-endian byte order being used for code generation. As with -fexec-charset, charset can be any encoding supported by the system's \"iconv\" library routine; however, you will have problems with encodings that do not fit exactly in \"wchart\"." }, { "flag": "", "long": null, "arg": null, "description": "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 \"iconv\" library routine." }, { "flag": "", "long": null, "arg": null, "description": "Enable generation of linemarkers in the preprocessor output that let the compiler know the current working directory at the time of preprocessing. When this option is enabled, the preprocessor emits, after the initial linemarker, a second linemarker with the current working directory followed by two slashes. GCC uses 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 -P flag is present in the command line, this option has no effect, since no \"#line\" directives are emitted whatsoever." }, { "flag": "-A", "long": null, "arg": null, "description": "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." }, { "flag": "-A", "long": null, "arg": null, "description": "Cancel an assertion with the predicate predicate and answer answer." }, { "flag": "-C", "long": null, "arg": null, "description": "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 #." }, { "flag": "-C", "long": null, "arg": null, "description": "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 -C option, the -CC option 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. The -CC option is generally used to support lint comments." }, { "flag": "-P", "long": null, "arg": null, "description": "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." }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": null, "arg": null, "description": "Try to imitate the behavior of pre-standard C preprocessors, as opposed to ISO C preprocessors. Note that GCC does not otherwise attempt to emulate a pre-standard C compiler, and these options are only supported with the -E switch, or when invoking CPP explicitly." }, { "flag": "", "long": null, "arg": null, "description": "Support ISO C trigraphs. These are three-character sequences, all starting with ??, that are defined by ISO C to stand for single characters. For example, ??/ stands for \\, so '??/n' is a character constant for a newline. By default, GCC ignores trigraphs, but in standard-conforming modes it converts them. See the -std and -ansi options." }, { "flag": "", "long": null, "arg": null, "description": "Enable special code to work around file systems which only permit very short file names, such as MS-DOS." }, { "flag": "-H", "long": null, "arg": null, "description": "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 ...! ." }, { "flag": "", "long": null, "arg": null, "description": "Says to make debugging dumps during compilation as specified by letters. The flags documented here are those relevant to the preprocessor. Other letters are interpreted by the compiler proper, or reserved for future versions of GCC, and so are silently ignored. If you specify letters whose behavior conflicts, the result is undefined. -dM 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 shows all the predefined macros. -dD Like -dM 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. -dN Like -dD, but emit only the macro names, not their expansions. -dI Output #include directives in addition to the result of preprocessing. -dU Like -dD 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." }, { "flag": "", "long": null, "arg": null, "description": "This option is only useful for debugging GCC. When used from CPP or with -E, it dumps debugging information about location maps. Every token in the output is preceded by the dump of the map its location belongs to. When used from GCC without -E, this option has no effect." }, { "flag": "-I", "long": null, "arg": null, "description": "" }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": null, "arg": null, "description": "Add the directory dir to the list of directories to be searched for header files during preprocessing. If dir begins with = or $SYSROOT, then the = or $SYSROOT is replaced by the sysroot prefix; see --sysroot and -isysroot. Directories specified with -iquote apply only to the quote form of the directive, \"#include \"file\"\". Directories specified with -I, -isystem, or -idirafter apply to lookup for both the \"#include \"file\"\" and \"#include \" directives. You can specify any number or combination of these options on the command line to search for header files in several directories. The lookup order is as follows: 1. For the quote form of the include directive, the directory of the current file is searched first. 2. For the quote form of the include directive, the directories specified by -iquote options are searched in left-to-right order, as they appear on the command line. 3. Directories specified with -I options are scanned in left-to-right order. 4. Directories specified with -isystem options are scanned in left-to-right order. 5. Standard system directories are scanned. 6. Directories specified with -idirafter options are scanned in left-to-right order. You can use -I to override a system header file, substituting your own version, since these directories are searched before the standard system header file directories. However, you should not use this option to add directories that contain vendor-supplied system header files; use -isystem for that. The -isystem and -idirafter options also mark the directory as a system directory, so that it gets the same special treatment that is applied to the standard system directories. If a standard system include directory, or a directory specified with -isystem, is also specified with -I, the -I option is ignored. The directory is still searched but as a system directory at its normal position in the system include chain. This is to ensure that GCC's procedure to fix buggy system headers and the ordering for the \"#includenext\" directive are not inadvertently changed. If you really need to change the search order for system directories, use the -nostdinc and/or -isystem options." }, { "flag": "", "long": null, "arg": null, "description": "-I directories before the -I- and remove the -I- option. Any directories specified with -I options before -I- are searched only for headers requested with \"#include \"file\"\"; they are not searched for \"#include \". If additional directories are specified with -I options after the -I-, those directories are searched for all #include directives. In addition, -I- inhibits the use of the directory of the current file directory as the first search directory for \"#include \"file\"\". There is no way to override this effect of -I-." }, { "flag": "", "long": null, "arg": null, "description": "Specify prefix as the prefix for subsequent -iwithprefix options. If the prefix represents a directory, you should include the final /." }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": null, "arg": null, "description": "Append dir to the prefix specified previously with -iprefix, and add the resulting directory to the include search path. -iwithprefixbefore puts it in the same place -I would; -iwithprefix puts it where -idirafter would." }, { "flag": "", "long": null, "arg": null, "description": "This option is like the --sysroot option, but applies only to header files (except for Darwin targets, where it applies to both header files and libraries). See the --sysroot option for more information." }, { "flag": "", "long": null, "arg": null, "description": "Use dir as a subdirectory of the directory containing target-specific C++ headers." }, { "flag": "", "long": null, "arg": null, "description": "Do not search the standard system directories for header files. Only the directories explicitly specified with -I, -iquote, -isystem, and/or -idirafter options (and the directory of the current file, if appropriate) are searched." }, { "flag": "", "long": null, "arg": null, "description": "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.)" }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": null, "arg": null, "description": "Warn whenever a comment-start sequence /* appears in a /* comment, or whenever a backslash-newline appears in a // comment. This warning is enabled by -Wall." }, { "flag": "", "long": null, "arg": null, "description": "Warn if any trigraphs are encountered that might change the meaning of the program. Trigraphs within comments are not warned about, except those that would form escaped newlines. This option is implied by -Wall. If -Wall is not given, this option is still enabled unless trigraphs are enabled. To get trigraph conversion without warnings, but get the other -Wall warnings, use -trigraphs -Wall -Wno-trigraphs." }, { "flag": "", "long": null, "arg": null, "description": "Warn if an undefined identifier is evaluated in an \"#if\" directive. Such identifiers are replaced with zero." }, { "flag": "", "long": null, "arg": null, "description": "Warn whenever defined is encountered in the expansion of a macro (including the case where the macro is expanded by an #if directive). Such usage is not portable. This warning is also enabled by -Wpedantic and -Wextra." }, { "flag": "", "long": null, "arg": null, "description": "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 also warns 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 the preprocessor reports 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 themacrocausingthewarning #endif" }, { "flag": "", "long": null, "arg": null, "description": "Do not warn whenever an \"#else\" or an \"#endif\" are followed by text. This sometimes happens in older programs with code of the form #if FOO ... #else FOO ... #endif FOO The second and third \"FOO\" should be in comments. This warning is on by default." } ], "examples": [], "see_also": [ { "name": "gpl", "section": "7", "url": "https://www.chedong.com/phpMan.php/man/gpl/7/json" }, { "name": "gfdl", "section": "7", "url": "https://www.chedong.com/phpMan.php/man/gfdl/7/json" }, { "name": "fsf-funding", "section": "7", "url": "https://www.chedong.com/phpMan.php/man/fsf-funding/7/json" }, { "name": "gcc", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/gcc/1/json" } ] }