CPP(1)

💅 CPP — the C Preprocessor, bestie edition 💅

okay so this is the cpp page from the GNU manual, and it's long, so we're doing it in parts. part 1 is right here. buckle up. 🎀

---

✨ NAME ✨

cpp — The C Preprocessor</p> 🦋

---

🌸 SYNOPSIS 🌸

cpp [-Dmacro[=defn]...] [-Umacro]
    [-Idir...] [-iquotedir...]
    [-M|-MM] [-MG] [-MF filename]
    [-MP] [-MQ target...]
    [-MT target...]
    infile [[-o] outfile]

okay real talk: that list up there is only the most useful options. the full preprocessor-specific list is down below, keep scrolling bestie. also, cpp accepts most gcc driver options, and those aren't listed here at all — go check the GCC docs for those, iykyk. 😌

---

👑 DESCRIPTION 👑

the C preprocessor — aka cpp, aka the thing doing the most before your code even gets compiled — is a macro processor. the C compiler runs it automatically to transform your program before compilation. it's called a macro processor because it lets you define macros, which are basically little abbreviations for longer constructs. so you write the short thing, it becomes the long thing. iconic behavior honestly. ✨

⚠️ vibe check, and this one matters: the C preprocessor is meant to be used only with C, C++, and Objective-C source code.

in the past it got abused as a general text processor 💀 and it will literally choke on input that doesn't obey C's lexical rules. for example, apostrophes get interpreted as the beginning of character constants, and that causes errors. also you cannot rely on it preserving characteristics of the input that aren't significant to C-family languages. if you preprocess a Makefile, all the hard tabs get removed, and the Makefile will not work. no cap. 🙈

that said — you can often get away with using cpp on things that aren't C. other Algol-ish programming languages are often safe (Ada, etc.). so is assembly, with caution. and -traditional-cpp mode preserves more white space and is otherwise more permissive. many of the problems can be avoided by writing C or C++ style comments instead of native language comments, and keeping macros simple. simple macros, happy life. 🧚

wherever possible you should use a preprocessor geared to the language you're actually writing in, fr fr. modern versions of the GNU assembler have macro facilities. most high level programming languages have their own conditional compilation and inclusion mechanism. and if all else fails? try a true general text processor, such as GNU M4. 💜

C preprocessors vary in some details. this manual discusses the GNU C preprocessor, which provides a small superset of the features of ISO Standard C. in its default mode, the GNU C preprocessor does not do a few things the standard requires. these are features which are rarely, if ever, used, and they may cause surprising changes to the meaning of a program that doesn't expect them. to get strict ISO Standard C, you should use the -std=c90, -std=c99, -std=c11 or -std=c17 options, depending on which version of the standard you want. and to get all the mandatory diagnostics, you must also use -pedantic. both. together. periodt. 💅

this manual describes the behavior of the ISO preprocessor. to minimize gratuitous differences, where the ISO preprocessor's behavior does not conflict with traditional semantics, the traditional preprocessor should behave the same way. the various differences that do exist are detailed in the section Traditional Mode. 📚

for clarity, unless noted otherwise, references to CPP in this manual refer to GNU CPP. 🫶

---

🎀 OPTIONS 🎀

the cpp command 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. if either file is omitted, it means the same as if - had been specified for that file. you can also use the -o outfile option to specify the output file. easy. ✨

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: -Ifoo and -I foo have the same effect. both slay, pick whichever. 🌸

🚨 careful bestie: many options have multi-letter names, therefore multiple single-letter options may not be grouped. -dM is very different from -d -M. do not do the grouping thing. 💀

---

• -D name — predefine name as a macro, with definition 1. 🍓
• -D name=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 is truncated by embedded newline characters. 😭

if you're 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.

• -U name — cancel any previous definition of name, either built in or provided with a -D option. bye bye macro 👋
• -include file — 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.

• -imacros file — 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. bestie that's the whole point.

all files specified by -imacros are processed before all files specified by -include.

• -undef — do not predefine any system-specific or GCC-specific macros. the standard predefined macros remain defined. 🌈
• -pthread — 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. 🧵
• -M — instead of outputting the result of preprocessing, output a rule suitable for make 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 DEPENDENCIES_OUTPUT. 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.

• -MM — like -M but 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 appears in -MM dependency output.

• -MF file — 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.

• -MG — in conjunction with an option such as -M requesting dependency generation, -MG assumes 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.

• -Mno-modules — disable dependency generation for compiled module interfaces. 🚫
• -MP — 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 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:

• -MT target — 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

• -MQ target — 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. ✨

• -MD — -MD is equivalent to -M -MF file, except that -E is not implied. the driver determines 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. sneaky and efficient. 😌

---

part 1 done, bestie — more coming, don't go anywhere 💖

• -MMD — literally -MD but make it ✨selective✨: it only name-drops user header files, not the system ones. bestie said "not my business" to system headers 💅
• -fpreprocessed — tells the preprocessor "girl, this file is already preprocessed, we're done here." it suppresses macro expansion, trigraph conversion, escaped newline splicing, and processing of most directives. but it still recognizes and removes comments, so you can hand a file preprocessed with -C to the compiler and nothing breaks 🫶. in this mode the integrated preprocessor is basically just a tokenizer for the front ends, no cap.

-fpreprocessed is implicit if your input file has one of these extensions: .i, .ii, or .mi. those are the exact extensions GCC uses for preprocessed files created by -save-temps. iconic behavior honestly.

• -fdirectives-only — when preprocessing, handle directives but do not expand macros. main character energy: it does the minimum.

the way this option behaves depends on -E and -fpreprocessed:

• with -E, preprocessing is limited to handling directives like "#define", "#ifdef", and "#error". other preprocessor operations, like macro expansion and trigraph conversion, are not performed. plus, -dD gets implicitly enabled. surprise ✨
• with -fpreprocessed, predefinition of command line and most builtin macros is disabled. macros like "__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". slay.

• -fdollars-in-identifiers — accept $ in identifiers. yes, the dollar sign. in an identifier. we're doing this 💅
• -fextended-identifiers — accept universal character names and extended characters in identifiers. this one is enabled by default for C99 (and later C standard versions) and C++. it's giving default-on for the girlies 🌈
• -fno-canonical-system-headers — when preprocessing, do not shorten system header paths with canonicalization. that's it. that's the whole thing.
• -fmax-include-depth=depth — sets the max depth of the nested #include. the default is 200. don't go deeper than that, bestie, we're not exploring the ocean 🦋
• -ftabstop=width — sets 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.
• -ftrack-macro-expansion[=level] — tracks locations of tokens across macro expansions. this lets the compiler emit diagnostics about the current macro expansion stack when a compilation error happens inside a macro expansion. using this option makes the preprocessor and the compiler consume more memory 😭. the level parameter chooses the precision of token location tracking, so you can dial down the memory consumption if you need to:
  • value 0 of level de-activates this option.
  • value 1 tracks token 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 token 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. so yeah, you're already paying that memory tax unless you say otherwise.

• -fmacro-prefix-map=old=new — when preprocessing files residing in directory old, expand the "__FILE__" and "__BASE_FILE__" macros as if the files resided in directory new instead. you can use this to change an absolute path into a relative path by using . for new, which can result in more reproducible builds that are location independent 🫶. this option also affects "__builtin_FILE()" during compilation. see also -ffile-prefix-map and -fcanon-prefix-map.
• -fexec-charset=charset — sets 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. flexible queen ✨
• -fwide-exec-charset=charset — sets 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 "wchar_t" and the big-endian or little-endian byte order being used for code generation. same as -fexec-charset, charset can be any encoding supported by the system's "iconv" library routine; however, you'll have problems with encodings that don't fit exactly in "wchar_t". so like. don't do that.
• -finput-charset=charset — sets 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 doesn't specify it, or GCC can't get this info 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.
• -fworking-directory — enables 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 that can be inhibited with the negated form -fno-working-directory. if the -P flag is present on the command line, this option has no effect, since no "#line" directives are emitted whatsoever. okay so it's a whole thing.
• -A predicate=answer — make an assertion with the predicate predicate and answer answer. this form is preferred over the older form -A predicate(answer), which is still supported, because it doesn't use shell special characters 🐚✨
• -A -predicate=answer — cancel an assertion with the predicate predicate and answer answer.
• -C — 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 #. so like, careful bestie 😭

• -CC — 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 -C, -CC 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. thank you for your service honestly 🫡

the -CC option is generally used to support lint comments.

• -P — inhibit generation of linemarkers in the output from the preprocessor. this might be useful when you're running the preprocessor on something that is not C code, and it'll be sent to a program which might get confused by the linemarkers. protect the baby programs 🌸
• -traditional
• -traditional-cpp — try to imitate the behavior of pre-standard C preprocessors, as opposed to ISO C preprocessors. it's giving vintage. it's giving thrifted.

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.

• -trigraphs — 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. quirky little things.

by default, GCC ignores trigraphs, but in standard-conforming modes it converts them. see the -std and -ansi options.

• -remap — enable special code to work around file systems which only permit very short file names, such as MS-DOS. a relic. a legend. 💀
• -H — 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're found to be invalid; an invalid precompiled header file is printed with ...x and a valid one with ...! . visual storytelling ✨
• -dletters — 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. so like, don't.
  • -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. chef's kiss 👑

• -dD — like -dM except that 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. no spoilers 💅
• -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. it's giving "we'll deal with it when we get there."

• -fdebug-cpp — 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. a little x-ray for your tokens 🦋

when used from GCC without -E, this option has no effect.

• -I dir
• -iquote dir
• -isystem dir
• -idirafter dir — add the directory dir to the list of directories to be searched for header files during preprocessing.

If dir starts with = or $SYSROOT, then that = or $SYSROOT gets swapped out for the sysroot prefix, k? Go read --sysroot and -isysroot for the lore.

Directories you hand over with -iquote only count for the quote flavor of the directive, like #include "file". Directories from -I, -isystem, or -idirafter count for both #include "file" and #include <file>. Equal opportunity header hunting. 💅

You can stack any number or combo of these options on the command line to search a bunch of directories for headers. And the lookup order is exactly this, no skipping:

1. For the quote form of the include directive, the directory of the current file gets searched first.
2. For the quote form of the include directive, the directories from -iquote options get searched left-to-right, in the order they appear on the command line.
3. Directories from -I options get scanned left-to-right.
4. Directories from -isystem options get scanned left-to-right.
5. Standard system directories get scanned.
6. Directories from -idirafter options get scanned left-to-right.

You can use -I to override a system header file, swapping in your own version, because these directories are searched before the standard system header directories. But — and this is the important part, bestie — do not use this option to add directories full of vendor-supplied system header files. Use -isystem for that, okay? 🫶

The -isystem and -idirafter options also mark the directory as a system directory, so it gets the exact same special treatment the standard system directories get. Iconic behaviour.

If a standard system include directory, or a directory you gave with -isystem, is also specified with -I, then the -I option is ignored. The directory is still searched — but as a system directory, at its normal position in the system include chain. Why? To make sure GCC's procedure for fixing buggy system headers, and the ordering for the #include_next directive, don't get inadvertently changed. If you really need to change the search order for system directories, use the -nostdinc and/or -isystem options instead.

• -I- — Split the include path.

🚨 This option has been deprecated. Please use -iquote instead for -I directories before the -I-, and remove the -I- option. It's giving legacy.

Any directories you specified with -I options before -I- are searched only for headers requested with #include "file"; they are not searched for #include <file>. If you specify extra directories with -I options after the -I-, those directories get searched for all #include directives.

On top of that, -I- inhibits the use of the directory of the current file as the first search directory for #include "file". And there is no way to override this effect of -I-. None. Periodt.

• -iprefix prefix — Set prefix as the prefix for any subsequent -iwithprefix options. If the prefix represents a directory, you should include the final /. Don't forget it, bestie. 🌸
• -iwithprefix dir, -iwithprefixbefore dir — Append dir to the prefix you specified earlier 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. Same energy, different real estate.
• -isysroot dir — This one is like the --sysroot option, but it applies only to header files (except for Darwin targets, where it applies to both header files and libraries). See the --sysroot option for more info. 🦋
• -imultilib dir — Use dir as a subdirectory of the directory that contains target-specific C++ headers.
• -nostdinc — Do not search the standard system directories for header files. Only the directories explicitly specified with -I, -iquote, -isystem, and/or -idirafter options get searched (plus the directory of the current file, if that's appropriate). You're on your own now, main character. 👑
• -nostdinc++ — 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.) Very niche, very valid.
• -Wcomment, -Wcomments — Warn whenever a comment-start sequence /* appears inside a /* comment, or whenever a backslash-newline shows up inside a // comment. This warning is enabled by -Wall.
• -Wtrigraphs — Warn if any trigraphs are encountered that might change the meaning of the program. Trigraphs inside comments are not warned about, except the ones 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 still get the other -Wall warnings, use:

-trigraphs -Wall -Wno-trigraphs

• -Wundef — Warn if an undefined identifier is evaluated in an #if directive. Such identifiers get replaced with zero. 😭
• -Wexpansion-to-defined — Warn whenever defined is encountered in the expansion of a macro (including the case where the macro gets expanded by an #if directive). Such usage is not portable. This warning is also enabled by -Wpedantic and -Wextra.
• -Wunused-macros — Warn about macros defined in the main file that are unused. A macro counts as used if it's expanded or tested for existence at least once. The preprocessor also warns if the macro hasn't been used at the time it's 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 dodge the warning in that 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

• -Wno-endif-labels — Do not warn whenever an #else or an #endif is 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. 🙈

---

✨ ENVIRONMENT ✨

This section spills the tea on the environment variables that affect how CPP operates. You can use them to specify directories or prefixes to use when searching for include files, or to control dependency output.

Note that you can also specify places to search using options like -I, and control dependency output with options like -M. These take precedence over environment variables, which in turn take precedence over the configuration of GCC. Hierarchy, bestie. 💅

• CPATH
• C_INCLUDE_PATH
• CPLUS_INCLUDE_PATH
• OBJC_INCLUDE_PATH

Each variable's value is a list of directories separated by a special character, much like PATH, in which to look for header files. That special character, "PATH_SEPARATOR", is target-dependent and determined at GCC build time. For Microsoft Windows-based targets it's a semicolon, and for almost all other targets it's a colon.

CPATH specifies a list of directories to be searched as if specified with -I, but after any paths given with -I options on the command line. This environment variable is used regardless of which language is being preprocessed.

The remaining environment variables apply only when preprocessing the particular language indicated. Each specifies a list of directories to be searched as if specified with -isystem, but after any paths given with -isystem options on the command line.

In all these variables, an empty element instructs the compiler to search its current working directory. Empty elements can appear at the beginning or end of a path. For instance, if the value of CPATH is :/special/include, that has the same effect as:

-I. -I/special/include

• DEPENDENCIES_OUTPUT — If this variable is set, its value specifies how to output dependencies for Make based on the non-system header files processed by the compiler. System header files are ignored in the dependency output.

The value of DEPENDENCIES_OUTPUT can be just a file name, in which case the Make rules are written to that file, guessing the target name from the source file name. Or the value can have the form file target, in which case the rules are written to file file using target as the target name.

In other words, this environment variable is equivalent to combining the options -MM and -MF, with an optional -MT switch too. So efficient. ✨

• SUNPRO_DEPENDENCIES — This variable is the same as DEPENDENCIES_OUTPUT (see above), except that system header files are not ignored, so it implies -M rather than -MM. However, the dependence on the main input file is omitted.
• SOURCE_DATE_EPOCH — If this variable is set, its value specifies a UNIX timestamp to be used in replacement of the current date and time in the "__DATE__" and "__TIME__" macros, so that the embedded timestamps become reproducible. Reproducible builds stay winning. 🎀

The value of SOURCE_DATE_EPOCH must be a UNIX timestamp, defined as the number of seconds (excluding leap seconds) since 01 Jan 1970 00:00:00 represented in ASCII; identical to the output of "date +%s" on GNU/Linux and other systems that support the %s extension in the "date" command.

The value should be a known timestamp such as the last modification time of the source or package, and it should be set by the build process. Not vibes-based. Set it properly. 🧚

---

🌈 SEE ALSO 🌈

gpl(7), gfdl(7), fsf-funding(7), gcc(1), and the Info entries for cpp and gcc. Go read them, iykyk. 📚

---

💖 COPYRIGHT 💖

Copyright (c) 1987-2024 Free Software Foundation, Inc.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation. A copy of the license is included in the man page gfdl(7). This manual contains no Invariant Sections. The Front-Cover Texts are (a) (see below), and the Back-Cover Texts are (b) (see below).

(a) The FSF's Front-Cover Text is:

A GNU Manual

(b) The FSF's Back-Cover Text is:

You have freedom to copy and modify this GNU Manual, like GNU
software.  Copies published by the Free Software Foundation raise
funds for GNU development.

---

And that's the whole page, bestie — you made it to the end, actual main character energy. 🌟 This lil masterpiece is from gcc-14, dated 2026-07-24, and it's the CPP(1) man page. Slay, go preprocess something. 💜🦋✨