1,2c1
< .\" Automatically generated by Pod::Man version 1.15
< .\" Wed Feb 5 03:13:55 2003
---
> .\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.14
5c4
< .\" ======================================================================
---
> .\" ========================================================================
18,23d16
< .de Ip \" List item
< .br
< .ie \\n(.$>=3 .ne \\$3
< .el .ne 3
< .IP "\\$1" \\$2
< ..
31d23
<
37,39c29,31
< .\" real vertical bar. \*(C+ will give a nicer C++. Capital omega is used
< .\" to do unbreakable dashes and therefore won't be available. \*(C` and
< .\" \*(C' expand to `' in nroff, nothing in troff, for use with C<>
---
> .\" real vertical bar. \*(C+ will give a nicer C++. Capital omega is used to
> .\" do unbreakable dashes and therefore won't be available. \*(C` and \*(C'
> .\" expand to `' in nroff, nothing in troff, for use with C<>.
59,62c51,54
< .\" If the F register is turned on, we'll generate index entries on stderr
< .\" for titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and
< .\" index entries marked with X<> in POD. Of course, you'll have to process
< .\" the output yourself in some meaningful fashion.
---
> .\" If the F register is turned on, we'll generate index entries on stderr for
> .\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
> .\" entries marked with X<> in POD. Of course, you'll have to process the
> .\" output yourself in some meaningful fashion.
71,72c63,64
< .\" For nroff, turn off justification. Always turn off hyphenation; it
< .\" makes way too many mistakes in technical documents.
---
> .\" For nroff, turn off justification. Always turn off hyphenation; it makes
> .\" way too many mistakes in technical documents.
78d69
< .bd B 3
138c129
< .\" ======================================================================
---
> .\" ========================================================================
141,142c132
< .TH CPP 1 "gcc-3.2.2" "2003-02-05" "GNU"
< .UC
---
> .TH CPP 1 "2006-03-06" "gcc-3.4.6" "GNU"
150c140,142
< [\fB\-MP\fR] [\fB\-MQ\fR \fItarget\fR...] [\fB\-MT\fR \fItarget\fR...]
---
> [\fB\-MP\fR] [\fB\-MQ\fR \fItarget\fR...]
> [\fB\-MT\fR \fItarget\fR...]
> [\fB\-P\fR] [\fB\-fno\-working\-directory\fR]
169c161
< C-family languages. If a Makefile is preprocessed, all the hard tabs
---
> C\-family languages. If a Makefile is preprocessed, all the hard tabs
174c166
< (Pascal, Ada, etc.) So is assembly, with caution. \fB\-traditional\fR
---
> (Pascal, Ada, etc.) So is assembly, with caution. \fB\-traditional\-cpp\fR
193a186,195
> .PP
> This manual describes the behavior of the \s-1ISO\s0 preprocessor. To
> minimize gratuitous differences, where the \s-1ISO\s0 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 \fBTraditional
> Mode\fR.
> .PP
> For clarity, unless noted otherwise, references to \fB\s-1CPP\s0\fR in this
> manual refer to \s-1GNU\s0 \s-1CPP\s0.
201c203
< Either \fIinfile\fR or \fIoutfile\fR may be \fB-\fR, which as
---
> Either \fIinfile\fR or \fIoutfile\fR may be \fB\-\fR, which as
204c206
< means the same as if \fB-\fR had been specified for that file.
---
> means the same as if \fB\-\fR had been specified for that file.
214c216
< .Ip "\fB\-D\fR \fIname\fR" 4
---
> .IP "\fB\-D\fR \fIname\fR" 4
216,217c218,219
< Predefine \fIname\fR as a macro, with definition \f(CW\*(C`1\*(C'\fR.
< .Ip "\fB\-D\fR \fIname\fR\fB=\fR\fIdefinition\fR" 4
---
> Predefine \fIname\fR as a macro, with definition \f(CW1\fR.
> .IP "\fB\-D\fR \fIname\fR\fB=\fR\fIdefinition\fR" 4
220,223c222,225
< There are no restrictions on the contents of \fIdefinition\fR, but 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.
---
> The contents of \fIdefinition\fR are tokenized and processed as if
> they appeared during translation phase three in a \fB#define\fR
> directive. In particular, the definition will be truncated by
> embedded newline characters.
224a227,230
> 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.
> .Sp
235c241
< .Ip "\fB\-U\fR \fIname\fR" 4
---
> .IP "\fB\-U\fR \fIname\fR" 4
239c245
< .Ip "\fB\-undef\fR" 4
---
> .IP "\fB\-undef\fR" 4
241,243c247,249
< Do not predefine any system-specific macros. The common predefined
< macros remain defined.
< .Ip "\fB\-I\fR \fIdir\fR" 4
---
> Do not predefine any system-specific or GCC-specific macros. The
> standard predefined macros remain defined.
> .IP "\fB\-I\fR \fIdir\fR" 4
249,256c255,260
< system include directories.
< .Sp
< It is dangerous to specify a standard system include directory in an
< \&\fB\-I\fR option. This defeats the special treatment of system
< headers
< \&. It can also defeat the repairs to buggy system headers which \s-1GCC\s0
< makes when it is installed.
< .Ip "\fB\-o\fR \fIfile\fR" 4
---
> system include directories. If the directory \fIdir\fR 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
> \&.
> .IP "\fB\-o\fR \fIfile\fR" 4
262c266
< .Ip "\fB\-Wall\fR" 4
---
> .IP "\fB\-Wall\fR" 4
264,268c268,274
< Turns on all optional warnings which are desirable for normal code. At
< present this is \fB\-Wcomment\fR and \fB\-Wtrigraphs\fR. Note that
< many of the preprocessor's warnings are on by default and have no
< options to control them.
< .Ip "\fB\-Wcomment\fR" 4
---
> Turns on all optional warnings which are desirable for normal code.
> At present this is \fB\-Wcomment\fR, \fB\-Wtrigraphs\fR,
> \&\fB\-Wmultichar\fR and a warning about integer promotion causing a
> change of sign in \f(CW\*(C`#if\*(C'\fR expressions. Note that many of the
> preprocessor's warnings are on by default and have no options to
> control them.
> .IP "\fB\-Wcomment\fR" 4
271c277
< .Ip "\fB\-Wcomments\fR" 4
---
> .IP "\fB\-Wcomments\fR" 4
277c283
< .Ip "\fB\-Wtrigraphs\fR" 4
---
> .IP "\fB\-Wtrigraphs\fR" 4
279,283c285,296
< Warn if any trigraphs are encountered. This option used to take effect
< only if \fB\-trigraphs\fR was also specified, but now works
< independently. Warnings are not given for trigraphs within comments, as
< they do not affect the meaning of the program.
< .Ip "\fB\-Wtraditional\fR" 4
---
> @anchor{Wtrigraphs}
> Most trigraphs in comments cannot affect the meaning of the program.
> However, a trigraph that would form an escaped newline (\fB??/\fR 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.
> .Sp
> This option is implied by \fB\-Wall\fR. If \fB\-Wall\fR is not
> given, this option is still enabled unless trigraphs are enabled. To
> get trigraph conversion without warnings, but get the other
> \&\fB\-Wall\fR warnings, use \fB\-trigraphs \-Wall \-Wno\-trigraphs\fR.
> .IP "\fB\-Wtraditional\fR" 4
288c301
< .Ip "\fB\-Wimport\fR" 4
---
> .IP "\fB\-Wimport\fR" 4
291c304
< .Ip "\fB\-Wundef\fR" 4
---
> .IP "\fB\-Wundef\fR" 4
296c309,344
< .Ip "\fB\-Werror\fR" 4
---
> .IP "\fB\-Wunused\-macros\fR" 4
> .IX Item "-Wunused-macros"
> Warn about macros defined in the main file that are unused. A macro
> is \fIused\fR 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.
> .Sp
> Built-in macros, macros defined on the command line, and macros
> defined in include files are not warned about.
> .Sp
> \&\fBNote:\fR If a macro is actually used, but only used in skipped
> conditional blocks, then \s-1CPP\s0 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:
> .Sp
> .Vb 2
> \& #if defined the_macro_causing_the_warning
> \& #endif
> .Ve
> .IP "\fB\-Wendif\-labels\fR" 4
> .IX Item "-Wendif-labels"
> Warn whenever an \fB#else\fR or an \fB#endif\fR are followed by text.
> This usually happens in code of the form
> .Sp
> .Vb 5
> \& #if FOO
> \& ...
> \& #else FOO
> \& ...
> \& #endif FOO
> .Ve
> .Sp
> The second and third \f(CW\*(C`FOO\*(C'\fR should be in comments, but often are not
> in older programs. This warning is on by default.
> .IP "\fB\-Werror\fR" 4
300c348
< .Ip "\fB\-Wsystem-headers\fR" 4
---
> .IP "\fB\-Wsystem\-headers\fR" 4
305c353
< .Ip "\fB\-w\fR" 4
---
> .IP "\fB\-w\fR" 4
308c356
< .Ip "\fB\-pedantic\fR" 4
---
> .IP "\fB\-pedantic\fR" 4
313c361
< .Ip "\fB\-pedantic-errors\fR" 4
---
> .IP "\fB\-pedantic\-errors\fR" 4
318c366
< .Ip "\fB\-M\fR" 4
---
> .IP "\fB\-M\fR" 4
340,341c388,390
< Passing \fB\-M\fR to the driver implies \fB\-E\fR.
< .Ip "\fB\-MM\fR" 4
---
> Passing \fB\-M\fR to the driver implies \fB\-E\fR, and suppresses
> warnings with an implicit \fB\-w\fR.
> .IP "\fB\-MM\fR" 4
351c400,402
< .Ip "\fB\-MF\fR \fIfile\fR" 4
---
> .Sp
> @anchor{dashMF}
> .IP "\fB\-MF\fR \fIfile\fR" 4
353d403
< @anchor{\-MF}
361c411
< .Ip "\fB\-MG\fR" 4
---
> .IP "\fB\-MG\fR" 4
363,366c413,419
< When used with \fB\-M\fR or \fB\-MM\fR, \fB\-MG\fR says to treat missing
< header files as generated files and assume they live in the same
< directory as the source file. It suppresses preprocessed output, as a
< missing header file is ordinarily an error.
---
> In conjunction with an option such as \fB\-M\fR requesting
> dependency generation, \fB\-MG\fR 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
> \&\f(CW\*(C`#include\*(C'\fR directive without prepending any path. \fB\-MG\fR
> also suppresses preprocessed output, as a missing header file renders
> this useless.
369c422
< .Ip "\fB\-MP\fR" 4
---
> .IP "\fB\-MP\fR" 4
380a434
> .Sp
384c438
< .Ip "\fB\-MT\fR \fItarget\fR" 4
---
> .IP "\fB\-MT\fR \fItarget\fR" 4
400c454
< .Ip "\fB\-MQ\fR \fItarget\fR" 4
---
> .IP "\fB\-MQ\fR \fItarget\fR" 4
407a462
> .Sp
410c465
< .Ip "\fB\-MD\fR" 4
---
> .IP "\fB\-MD\fR" 4
420c475
< (but \f(CW@pxref\fR{\-MF}), but if used without \fB\-E\fR, each \fB\-o\fR
---
> (but \f(CW@pxref\fR{dashMF,,\-MF}), but if used without \fB\-E\fR, each \fB\-o\fR
425c480
< .Ip "\fB\-MMD\fR" 4
---
> .IP "\fB\-MMD\fR" 4
429c484
< .Ip "\fB\-x c\fR" 4
---
> .IP "\fB\-x c\fR" 4
432c487
< .Ip "\fB\-x c++\fR" 4
---
> .IP "\fB\-x c++\fR" 4
434c489
< .Ip "\fB\-x objective-c\fR" 4
---
> .IP "\fB\-x objective-c\fR" 4
436c491
< .Ip "\fB\-x assembler-with-cpp\fR" 4
---
> .IP "\fB\-x assembler-with-cpp\fR" 4
439c494
< Specify the source language: C, \*(C+, Objective-C, or assembly. This has
---
> Specify the source language: C, \*(C+, Objective\-C, or assembly. This has
452c507
< .Ip "\fB\-std=\fR\fIstandard\fR" 4
---
> .IP "\fB\-std=\fR\fIstandard\fR" 4
455c510
< .Ip "\fB\-ansi\fR" 4
---
> .IP "\fB\-ansi\fR" 4
458,460c513,514
< Specify the standard to which the code should conform. Currently cpp
< only knows about the standards for C; other language standards will be
< added in the future.
---
> Specify the standard to which the code should conform. Currently \s-1CPP\s0
> knows about C and \*(C+ standards; others may be added in the future.
465,466c519,520
< .if n .Ip "\f(CW""""iso9899:1990""""\fR" 4
< .el .Ip "\f(CWiso9899:1990\fR" 4
---
> .ie n .IP """iso9899:1990""" 4
> .el .IP "\f(CWiso9899:1990\fR" 4
469,470c523,524
< .if n .Ip "\f(CW""""c89""""\fR" 4
< .el .Ip "\f(CWc89\fR" 4
---
> .ie n .IP """c89""" 4
> .el .IP "\f(CWc89\fR" 4
477,478c531,532
< .if n .Ip "\f(CW""""iso9899:199409""""\fR" 4
< .el .Ip "\f(CWiso9899:199409\fR" 4
---
> .ie n .IP """iso9899:199409""" 4
> .el .IP "\f(CWiso9899:199409\fR" 4
481,482c535,536
< .if n .Ip "\f(CW""""iso9899:1999""""\fR" 4
< .el .Ip "\f(CWiso9899:1999\fR" 4
---
> .ie n .IP """iso9899:1999""" 4
> .el .IP "\f(CWiso9899:1999\fR" 4
485,486c539,540
< .if n .Ip "\f(CW""""c99""""\fR" 4
< .el .Ip "\f(CWc99\fR" 4
---
> .ie n .IP """c99""" 4
> .el .IP "\f(CWc99\fR" 4
488,489c542,543
< .if n .Ip "\f(CW""""iso9899:199x""""\fR" 4
< .el .Ip "\f(CWiso9899:199x\fR" 4
---
> .ie n .IP """iso9899:199x""" 4
> .el .IP "\f(CWiso9899:199x\fR" 4
491,492c545,546
< .if n .Ip "\f(CW""""c9x""""\fR" 4
< .el .Ip "\f(CWc9x\fR" 4
---
> .ie n .IP """c9x""" 4
> .el .IP "\f(CWc9x\fR" 4
497,498c551,552
< .if n .Ip "\f(CW""""gnu89""""\fR" 4
< .el .Ip "\f(CWgnu89\fR" 4
---
> .ie n .IP """gnu89""" 4
> .el .IP "\f(CWgnu89\fR" 4
501,502c555,556
< .if n .Ip "\f(CW""""gnu99""""\fR" 4
< .el .Ip "\f(CWgnu99\fR" 4
---
> .ie n .IP """gnu99""" 4
> .el .IP "\f(CWgnu99\fR" 4
505,506c559,560
< .if n .Ip "\f(CW""""gnu9x""""\fR" 4
< .el .Ip "\f(CWgnu9x\fR" 4
---
> .ie n .IP """gnu9x""" 4
> .el .IP "\f(CWgnu9x\fR" 4
509a564,572
> .ie n .IP """c++98""" 4
> .el .IP "\f(CWc++98\fR" 4
> .IX Item "c++98"
> The 1998 \s-1ISO\s0 \*(C+ standard plus amendments.
> .ie n .IP """gnu++98""" 4
> .el .IP "\f(CWgnu++98\fR" 4
> .IX Item "gnu++98"
> The same as \fB\-std=c++98\fR plus \s-1GNU\s0 extensions. This is the
> default for \*(C+ code.
513c576
< .Ip "\fB\-I-\fR" 4
---
> .IP "\fB\-I\-\fR" 4
516c579
< options before \fB\-I-\fR are searched only for headers requested with
---
> options before \fB\-I\-\fR are searched only for headers requested with
519c582
< specified with \fB\-I\fR options after the \fB\-I-\fR, those
---
> specified with \fB\-I\fR options after the \fB\-I\-\fR, those
522c585
< In addition, \fB\-I-\fR inhibits the use of the directory of the current
---
> In addition, \fB\-I\-\fR inhibits the use of the directory of the current
524c587
< .Ip "\fB\-nostdinc\fR" 4
---
> .IP "\fB\-nostdinc\fR" 4
529c592
< .Ip "\fB\-nostdinc++\fR" 4
---
> .IP "\fB\-nostdinc++\fR" 4
534c597
< .Ip "\fB\-include\fR \fIfile\fR" 4
---
> .IP "\fB\-include\fR \fIfile\fR" 4
545c608
< .Ip "\fB\-imacros\fR \fIfile\fR" 4
---
> .IP "\fB\-imacros\fR \fIfile\fR" 4
554c617
< .Ip "\fB\-idirafter\fR \fIdir\fR" 4
---
> .IP "\fB\-idirafter\fR \fIdir\fR" 4
559c622
< .Ip "\fB\-iprefix\fR \fIprefix\fR" 4
---
> .IP "\fB\-iprefix\fR \fIprefix\fR" 4
564c627
< .Ip "\fB\-iwithprefix\fR \fIdir\fR" 4
---
> .IP "\fB\-iwithprefix\fR \fIdir\fR" 4
567c630
< .Ip "\fB\-iwithprefixbefore\fR \fIdir\fR" 4
---
> .IP "\fB\-iwithprefixbefore\fR \fIdir\fR" 4
574,576c637
< .Sp
< Use of these options is discouraged.
< .Ip "\fB\-isystem\fR \fIdir\fR" 4
---
> .IP "\fB\-isystem\fR \fIdir\fR" 4
582c643,647
< .Ip "\fB\-fpreprocessed\fR" 4
---
> .IP "\fB\-fdollars\-in\-identifiers\fR" 4
> .IX Item "-fdollars-in-identifiers"
> @anchor{fdollars\-in\-identifiers}
> Accept \fB$\fR in identifiers.
> .IP "\fB\-fpreprocessed\fR" 4
595,596c660,661
< \&\fB\-save-temps\fR.
< .Ip "\fB\-ftabstop=\fR\fIwidth\fR" 4
---
> \&\fB\-save\-temps\fR.
> .IP "\fB\-ftabstop=\fR\fIwidth\fR" 4
602c667,703
< .Ip "\fB\-fno-show-column\fR" 4
---
> .IP "\fB\-fexec\-charset=\fR\fIcharset\fR" 4
> .IX Item "-fexec-charset=charset"
> Set the execution character set, used for string and character
> constants. The default is \s-1UTF\-8\s0. \fIcharset\fR can be any encoding
> supported by the system's \f(CW\*(C`iconv\*(C'\fR library routine.
> .IP "\fB\-fwide\-exec\-charset=\fR\fIcharset\fR" 4
> .IX Item "-fwide-exec-charset=charset"
> Set the wide execution character set, used for wide string and
> character constants. The default is \s-1UTF\-32\s0 or \s-1UTF\-16\s0, whichever
> corresponds to the width of \f(CW\*(C`wchar_t\*(C'\fR. As with
> \&\fB\-ftarget\-charset\fR, \fIcharset\fR can be any encoding supported
> by the system's \f(CW\*(C`iconv\*(C'\fR library routine; however, you will have
> problems with encodings that do not fit exactly in \f(CW\*(C`wchar_t\*(C'\fR.
> .IP "\fB\-finput\-charset=\fR\fIcharset\fR" 4
> .IX Item "-finput-charset=charset"
> Set the input character set, used for translation from the character
> set of the input file to the source character set used by \s-1GCC\s0. If the
> locale does not specify, or \s-1GCC\s0 cannot get this information from the
> locale, the default is \s-1UTF\-8\s0. 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. \fIcharset\fR can be any encoding
> supported by the system's \f(CW\*(C`iconv\*(C'\fR library routine.
> .IP "\fB\-fworking\-directory\fR" 4
> .IX Item "-fworking-directory"
> 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. \s-1GCC\s0 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 \fB\-fno\-working\-directory\fR. If the \fB\-P\fR flag is
> present in the command line, this option has no effect, since no
> \&\f(CW\*(C`#line\*(C'\fR directives are emitted whatsoever.
> .IP "\fB\-fno\-show\-column\fR" 4
607c708
< .Ip "\fB\-A\fR \fIpredicate\fR\fB=\fR\fIanswer\fR" 4
---
> .IP "\fB\-A\fR \fIpredicate\fR\fB=\fR\fIanswer\fR" 4
613c714
< .Ip "\fB\-A -\fR\fIpredicate\fR\fB=\fR\fIanswer\fR" 4
---
> .IP "\fB\-A \-\fR\fIpredicate\fR\fB=\fR\fIanswer\fR" 4
617,623c718
< .Ip "\fB\-A-\fR" 4
< .IX Item "-A-"
< Cancel all predefined assertions and all assertions preceding it on
< the command line. Also, undefine all predefined macros and all
< macros preceding it on the command line. (This is a historical wart and
< may change in the future.)
< .Ip "\fB\-dCHARS\fR" 4
---
> .IP "\fB\-dCHARS\fR" 4
631c726
< .Ip "\fBM\fR" 4
---
> .IP "\fBM\fR" 4
641a737
> .Sp
643c739
< .Ip "\fBD\fR" 4
---
> .IP "\fBD\fR" 4
649c745
< .Ip "\fBN\fR" 4
---
> .IP "\fBN\fR" 4
652c748
< .Ip "\fBI\fR" 4
---
> .IP "\fBI\fR" 4
659c755
< .Ip "\fB\-P\fR" 4
---
> .IP "\fB\-P\fR" 4
665c761
< .Ip "\fB\-C\fR" 4
---
> .IP "\fB\-C\fR" 4
676,686c772,789
< .Ip "\fB\-gcc\fR" 4
< .IX Item "-gcc"
< Define the macros _\|_GNUC_\|_, _\|_GNUC_MINOR_\|_ and
< _\|_GNUC_PATCHLEVEL_\|_. These are defined automatically when you use
< \&\fBgcc \-E\fR; you can turn them off in that case with
< \&\fB\-no-gcc\fR.
< .Ip "\fB\-traditional\fR" 4
< .IX Item "-traditional"
< Try to imitate the behavior of old-fashioned C, as opposed to \s-1ISO\s0
< C.
< .Ip "\fB\-trigraphs\fR" 4
---
> .IP "\fB\-CC\fR" 4
> .IX Item "-CC"
> Do not discard comments, including during macro expansion. This is
> like \fB\-C\fR, except that comments contained within macros are
> also passed through to the output file where the macro is expanded.
> .Sp
> In addition to the side-effects of the \fB\-C\fR option, the
> \&\fB\-CC\fR 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.
> .Sp
> The \fB\-CC\fR option is generally used to support lint comments.
> .IP "\fB\-traditional\-cpp\fR" 4
> .IX Item "-traditional-cpp"
> Try to imitate the behavior of old-fashioned C preprocessors, as
> opposed to \s-1ISO\s0 C preprocessors.
> .IP "\fB\-trigraphs\fR" 4
689c792
< .Ip "\fB\-remap\fR" 4
---
> .IP "\fB\-remap\fR" 4
692,699c795,797
< short file names, such as \s-1MS-DOS\s0.
< .Ip "\fB\-$\fR" 4
< .IX Item "-$"
< Forbid the use of \fB$\fR in identifiers. The C standard allows
< implementations to define extra characters that can appear in
< identifiers. By default \s-1GNU\s0 \s-1CPP\s0 permits \fB$\fR, a common extension.
< .Ip "\fB\-h\fR" 4
< .IX Item "-h"
---
> short file names, such as \s-1MS\-DOS\s0.
> .IP "\fB\-\-help\fR" 4
> .IX Item "--help"
701,704c799,800
< .Ip "\fB\*(--help\fR" 4
< .IX Item "help"
< .Ip "\fB\*(--target-help\fR" 4
< .IX Item "target-help"
---
> .IP "\fB\-\-target\-help\fR" 4
> .IX Item "--target-help"
708c804
< .Ip "\fB\-v\fR" 4
---
> .IP "\fB\-v\fR" 4
712c808
< .Ip "\fB\-H\fR" 4
---
> .IP "\fB\-H\fR" 4
716,717c812,815
< \&\fB#include\fR stack it is.
< .Ip "\fB\-version\fR" 4
---
> \&\fB#include\fR 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 \fB...x\fR and a valid one with \fB...!\fR .
> .IP "\fB\-version\fR" 4
720,721c818,819
< .Ip "\fB\*(--version\fR" 4
< .IX Item "version"
---
> .IP "\fB\-\-version\fR" 4
> .IX Item "--version"
736c834
< .Ip "\fB\s-1CPATH\s0\fR" 4
---
> .IP "\fB\s-1CPATH\s0\fR" 4
739c837
< .Ip "\fBC_INCLUDE_PATH\fR" 4
---
> .IP "\fBC_INCLUDE_PATH\fR" 4
741c839
< .Ip "\fB\s-1CPLUS_INCLUDE_PATH\s0\fR" 4
---
> .IP "\fB\s-1CPLUS_INCLUDE_PATH\s0\fR" 4
743c841
< .Ip "\fB\s-1OBJC_INCLUDE_PATH\s0\fR" 4
---
> .IP "\fB\s-1OBJC_INCLUDE_PATH\s0\fR" 4
749c847
< determined at \s-1GCC\s0 build time. For Windows-based targets it is a
---
> determined at \s-1GCC\s0 build time. For Microsoft Windows-based targets it is a
754c852
< options on the command line. The environment variable is used
---
> options on the command line. This environment variable is used
762,763c860,865
< See also \f(CW@ref\fR{Search Path}.
< .Ip "\fB\s-1DEPENDENCIES_OUTPUT\s0\fR" 4
---
> 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
> \&\fB\s-1CPATH\s0\fR is \f(CW\*(C`:/special/include\*(C'\fR, that has the same
> effect as \fB\-I.\ \-I/special/include\fR.
> .IP "\fB\s-1DEPENDENCIES_OUTPUT\s0\fR" 4
765d866
< @anchor{\s-1DEPENDENCIES_OUTPUT\s0}
780c881
< .Ip "\fB\s-1SUNPRO_DEPENDENCIES\s0\fR" 4
---
> .IP "\fB\s-1SUNPRO_DEPENDENCIES\s0\fR" 4
782,786c883,886
< This variable is the same as the environment variable
< \&\fB\s-1DEPENDENCIES_OUTPUT\s0\fR, except that
< system header files are not ignored, so it implies \fB\-M\fR rather
< than \fB\-MM\fR. However, the dependence on the main input file is
< omitted.
---
> This variable is the same as \fB\s-1DEPENDENCIES_OUTPUT\s0\fR (see above),
> except that system header files are not ignored, so it implies
> \&\fB\-M\fR rather than \fB\-MM\fR. However, the dependence on the
> main input file is omitted.
789c889
< \&\fIgpl\fR\|(7), \fIgfdl\fR\|(7), \fIfsf-funding\fR\|(7),
---
> \&\fIgpl\fR\|(7), \fIgfdl\fR\|(7), \fIfsf\-funding\fR\|(7),
795c895
< 1997, 1998, 1999, 2000, 2001
---
> 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004
810a911
> .PP
< .\" Automatically generated by Pod::Man version 1.15
< .\" Wed Feb 5 03:13:55 2003
---
> .\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.14
5c4
< .\" ======================================================================
---
> .\" ========================================================================
18,23d16
< .de Ip \" List item
< .br
< .ie \\n(.$>=3 .ne \\$3
< .el .ne 3
< .IP "\\$1" \\$2
< ..
31d23
<
37,39c29,31
< .\" real vertical bar. \*(C+ will give a nicer C++. Capital omega is used
< .\" to do unbreakable dashes and therefore won't be available. \*(C` and
< .\" \*(C' expand to `' in nroff, nothing in troff, for use with C<>
---
> .\" real vertical bar. \*(C+ will give a nicer C++. Capital omega is used to
> .\" do unbreakable dashes and therefore won't be available. \*(C` and \*(C'
> .\" expand to `' in nroff, nothing in troff, for use with C<>.
59,62c51,54
< .\" If the F register is turned on, we'll generate index entries on stderr
< .\" for titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and
< .\" index entries marked with X<> in POD. Of course, you'll have to process
< .\" the output yourself in some meaningful fashion.
---
> .\" If the F register is turned on, we'll generate index entries on stderr for
> .\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
> .\" entries marked with X<> in POD. Of course, you'll have to process the
> .\" output yourself in some meaningful fashion.
71,72c63,64
< .\" For nroff, turn off justification. Always turn off hyphenation; it
< .\" makes way too many mistakes in technical documents.
---
> .\" For nroff, turn off justification. Always turn off hyphenation; it makes
> .\" way too many mistakes in technical documents.
78d69
< .bd B 3
138c129
< .\" ======================================================================
---
> .\" ========================================================================
141,142c132
< .TH CPP 1 "gcc-3.2.2" "2003-02-05" "GNU"
< .UC
---
> .TH CPP 1 "2006-03-06" "gcc-3.4.6" "GNU"
150c140,142
< [\fB\-MP\fR] [\fB\-MQ\fR \fItarget\fR...] [\fB\-MT\fR \fItarget\fR...]
---
> [\fB\-MP\fR] [\fB\-MQ\fR \fItarget\fR...]
> [\fB\-MT\fR \fItarget\fR...]
> [\fB\-P\fR] [\fB\-fno\-working\-directory\fR]
169c161
< C-family languages. If a Makefile is preprocessed, all the hard tabs
---
> C\-family languages. If a Makefile is preprocessed, all the hard tabs
174c166
< (Pascal, Ada, etc.) So is assembly, with caution. \fB\-traditional\fR
---
> (Pascal, Ada, etc.) So is assembly, with caution. \fB\-traditional\-cpp\fR
193a186,195
> .PP
> This manual describes the behavior of the \s-1ISO\s0 preprocessor. To
> minimize gratuitous differences, where the \s-1ISO\s0 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 \fBTraditional
> Mode\fR.
> .PP
> For clarity, unless noted otherwise, references to \fB\s-1CPP\s0\fR in this
> manual refer to \s-1GNU\s0 \s-1CPP\s0.
201c203
< Either \fIinfile\fR or \fIoutfile\fR may be \fB-\fR, which as
---
> Either \fIinfile\fR or \fIoutfile\fR may be \fB\-\fR, which as
204c206
< means the same as if \fB-\fR had been specified for that file.
---
> means the same as if \fB\-\fR had been specified for that file.
214c216
< .Ip "\fB\-D\fR \fIname\fR" 4
---
> .IP "\fB\-D\fR \fIname\fR" 4
216,217c218,219
< Predefine \fIname\fR as a macro, with definition \f(CW\*(C`1\*(C'\fR.
< .Ip "\fB\-D\fR \fIname\fR\fB=\fR\fIdefinition\fR" 4
---
> Predefine \fIname\fR as a macro, with definition \f(CW1\fR.
> .IP "\fB\-D\fR \fIname\fR\fB=\fR\fIdefinition\fR" 4
220,223c222,225
< There are no restrictions on the contents of \fIdefinition\fR, but 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.
---
> The contents of \fIdefinition\fR are tokenized and processed as if
> they appeared during translation phase three in a \fB#define\fR
> directive. In particular, the definition will be truncated by
> embedded newline characters.
224a227,230
> 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.
> .Sp
235c241
< .Ip "\fB\-U\fR \fIname\fR" 4
---
> .IP "\fB\-U\fR \fIname\fR" 4
239c245
< .Ip "\fB\-undef\fR" 4
---
> .IP "\fB\-undef\fR" 4
241,243c247,249
< Do not predefine any system-specific macros. The common predefined
< macros remain defined.
< .Ip "\fB\-I\fR \fIdir\fR" 4
---
> Do not predefine any system-specific or GCC-specific macros. The
> standard predefined macros remain defined.
> .IP "\fB\-I\fR \fIdir\fR" 4
249,256c255,260
< system include directories.
< .Sp
< It is dangerous to specify a standard system include directory in an
< \&\fB\-I\fR option. This defeats the special treatment of system
< headers
< \&. It can also defeat the repairs to buggy system headers which \s-1GCC\s0
< makes when it is installed.
< .Ip "\fB\-o\fR \fIfile\fR" 4
---
> system include directories. If the directory \fIdir\fR 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
> \&.
> .IP "\fB\-o\fR \fIfile\fR" 4
262c266
< .Ip "\fB\-Wall\fR" 4
---
> .IP "\fB\-Wall\fR" 4
264,268c268,274
< Turns on all optional warnings which are desirable for normal code. At
< present this is \fB\-Wcomment\fR and \fB\-Wtrigraphs\fR. Note that
< many of the preprocessor's warnings are on by default and have no
< options to control them.
< .Ip "\fB\-Wcomment\fR" 4
---
> Turns on all optional warnings which are desirable for normal code.
> At present this is \fB\-Wcomment\fR, \fB\-Wtrigraphs\fR,
> \&\fB\-Wmultichar\fR and a warning about integer promotion causing a
> change of sign in \f(CW\*(C`#if\*(C'\fR expressions. Note that many of the
> preprocessor's warnings are on by default and have no options to
> control them.
> .IP "\fB\-Wcomment\fR" 4
271c277
< .Ip "\fB\-Wcomments\fR" 4
---
> .IP "\fB\-Wcomments\fR" 4
277c283
< .Ip "\fB\-Wtrigraphs\fR" 4
---
> .IP "\fB\-Wtrigraphs\fR" 4
279,283c285,296
< Warn if any trigraphs are encountered. This option used to take effect
< only if \fB\-trigraphs\fR was also specified, but now works
< independently. Warnings are not given for trigraphs within comments, as
< they do not affect the meaning of the program.
< .Ip "\fB\-Wtraditional\fR" 4
---
> @anchor{Wtrigraphs}
> Most trigraphs in comments cannot affect the meaning of the program.
> However, a trigraph that would form an escaped newline (\fB??/\fR 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.
> .Sp
> This option is implied by \fB\-Wall\fR. If \fB\-Wall\fR is not
> given, this option is still enabled unless trigraphs are enabled. To
> get trigraph conversion without warnings, but get the other
> \&\fB\-Wall\fR warnings, use \fB\-trigraphs \-Wall \-Wno\-trigraphs\fR.
> .IP "\fB\-Wtraditional\fR" 4
288c301
< .Ip "\fB\-Wimport\fR" 4
---
> .IP "\fB\-Wimport\fR" 4
291c304
< .Ip "\fB\-Wundef\fR" 4
---
> .IP "\fB\-Wundef\fR" 4
296c309,344
< .Ip "\fB\-Werror\fR" 4
---
> .IP "\fB\-Wunused\-macros\fR" 4
> .IX Item "-Wunused-macros"
> Warn about macros defined in the main file that are unused. A macro
> is \fIused\fR 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.
> .Sp
> Built-in macros, macros defined on the command line, and macros
> defined in include files are not warned about.
> .Sp
> \&\fBNote:\fR If a macro is actually used, but only used in skipped
> conditional blocks, then \s-1CPP\s0 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:
> .Sp
> .Vb 2
> \& #if defined the_macro_causing_the_warning
> \& #endif
> .Ve
> .IP "\fB\-Wendif\-labels\fR" 4
> .IX Item "-Wendif-labels"
> Warn whenever an \fB#else\fR or an \fB#endif\fR are followed by text.
> This usually happens in code of the form
> .Sp
> .Vb 5
> \& #if FOO
> \& ...
> \& #else FOO
> \& ...
> \& #endif FOO
> .Ve
> .Sp
> The second and third \f(CW\*(C`FOO\*(C'\fR should be in comments, but often are not
> in older programs. This warning is on by default.
> .IP "\fB\-Werror\fR" 4
300c348
< .Ip "\fB\-Wsystem-headers\fR" 4
---
> .IP "\fB\-Wsystem\-headers\fR" 4
305c353
< .Ip "\fB\-w\fR" 4
---
> .IP "\fB\-w\fR" 4
308c356
< .Ip "\fB\-pedantic\fR" 4
---
> .IP "\fB\-pedantic\fR" 4
313c361
< .Ip "\fB\-pedantic-errors\fR" 4
---
> .IP "\fB\-pedantic\-errors\fR" 4
318c366
< .Ip "\fB\-M\fR" 4
---
> .IP "\fB\-M\fR" 4
340,341c388,390
< Passing \fB\-M\fR to the driver implies \fB\-E\fR.
< .Ip "\fB\-MM\fR" 4
---
> Passing \fB\-M\fR to the driver implies \fB\-E\fR, and suppresses
> warnings with an implicit \fB\-w\fR.
> .IP "\fB\-MM\fR" 4
351c400,402
< .Ip "\fB\-MF\fR \fIfile\fR" 4
---
> .Sp
> @anchor{dashMF}
> .IP "\fB\-MF\fR \fIfile\fR" 4
353d403
< @anchor{\-MF}
361c411
< .Ip "\fB\-MG\fR" 4
---
> .IP "\fB\-MG\fR" 4
363,366c413,419
< When used with \fB\-M\fR or \fB\-MM\fR, \fB\-MG\fR says to treat missing
< header files as generated files and assume they live in the same
< directory as the source file. It suppresses preprocessed output, as a
< missing header file is ordinarily an error.
---
> In conjunction with an option such as \fB\-M\fR requesting
> dependency generation, \fB\-MG\fR 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
> \&\f(CW\*(C`#include\*(C'\fR directive without prepending any path. \fB\-MG\fR
> also suppresses preprocessed output, as a missing header file renders
> this useless.
369c422
< .Ip "\fB\-MP\fR" 4
---
> .IP "\fB\-MP\fR" 4
380a434
> .Sp
384c438
< .Ip "\fB\-MT\fR \fItarget\fR" 4
---
> .IP "\fB\-MT\fR \fItarget\fR" 4
400c454
< .Ip "\fB\-MQ\fR \fItarget\fR" 4
---
> .IP "\fB\-MQ\fR \fItarget\fR" 4
407a462
> .Sp
410c465
< .Ip "\fB\-MD\fR" 4
---
> .IP "\fB\-MD\fR" 4
420c475
< (but \f(CW@pxref\fR{\-MF}), but if used without \fB\-E\fR, each \fB\-o\fR
---
> (but \f(CW@pxref\fR{dashMF,,\-MF}), but if used without \fB\-E\fR, each \fB\-o\fR
425c480
< .Ip "\fB\-MMD\fR" 4
---
> .IP "\fB\-MMD\fR" 4
429c484
< .Ip "\fB\-x c\fR" 4
---
> .IP "\fB\-x c\fR" 4
432c487
< .Ip "\fB\-x c++\fR" 4
---
> .IP "\fB\-x c++\fR" 4
434c489
< .Ip "\fB\-x objective-c\fR" 4
---
> .IP "\fB\-x objective-c\fR" 4
436c491
< .Ip "\fB\-x assembler-with-cpp\fR" 4
---
> .IP "\fB\-x assembler-with-cpp\fR" 4
439c494
< Specify the source language: C, \*(C+, Objective-C, or assembly. This has
---
> Specify the source language: C, \*(C+, Objective\-C, or assembly. This has
452c507
< .Ip "\fB\-std=\fR\fIstandard\fR" 4
---
> .IP "\fB\-std=\fR\fIstandard\fR" 4
455c510
< .Ip "\fB\-ansi\fR" 4
---
> .IP "\fB\-ansi\fR" 4
458,460c513,514
< Specify the standard to which the code should conform. Currently cpp
< only knows about the standards for C; other language standards will be
< added in the future.
---
> Specify the standard to which the code should conform. Currently \s-1CPP\s0
> knows about C and \*(C+ standards; others may be added in the future.
465,466c519,520
< .if n .Ip "\f(CW""""iso9899:1990""""\fR" 4
< .el .Ip "\f(CWiso9899:1990\fR" 4
---
> .ie n .IP """iso9899:1990""" 4
> .el .IP "\f(CWiso9899:1990\fR" 4
469,470c523,524
< .if n .Ip "\f(CW""""c89""""\fR" 4
< .el .Ip "\f(CWc89\fR" 4
---
> .ie n .IP """c89""" 4
> .el .IP "\f(CWc89\fR" 4
477,478c531,532
< .if n .Ip "\f(CW""""iso9899:199409""""\fR" 4
< .el .Ip "\f(CWiso9899:199409\fR" 4
---
> .ie n .IP """iso9899:199409""" 4
> .el .IP "\f(CWiso9899:199409\fR" 4
481,482c535,536
< .if n .Ip "\f(CW""""iso9899:1999""""\fR" 4
< .el .Ip "\f(CWiso9899:1999\fR" 4
---
> .ie n .IP """iso9899:1999""" 4
> .el .IP "\f(CWiso9899:1999\fR" 4
485,486c539,540
< .if n .Ip "\f(CW""""c99""""\fR" 4
< .el .Ip "\f(CWc99\fR" 4
---
> .ie n .IP """c99""" 4
> .el .IP "\f(CWc99\fR" 4
488,489c542,543
< .if n .Ip "\f(CW""""iso9899:199x""""\fR" 4
< .el .Ip "\f(CWiso9899:199x\fR" 4
---
> .ie n .IP """iso9899:199x""" 4
> .el .IP "\f(CWiso9899:199x\fR" 4
491,492c545,546
< .if n .Ip "\f(CW""""c9x""""\fR" 4
< .el .Ip "\f(CWc9x\fR" 4
---
> .ie n .IP """c9x""" 4
> .el .IP "\f(CWc9x\fR" 4
497,498c551,552
< .if n .Ip "\f(CW""""gnu89""""\fR" 4
< .el .Ip "\f(CWgnu89\fR" 4
---
> .ie n .IP """gnu89""" 4
> .el .IP "\f(CWgnu89\fR" 4
501,502c555,556
< .if n .Ip "\f(CW""""gnu99""""\fR" 4
< .el .Ip "\f(CWgnu99\fR" 4
---
> .ie n .IP """gnu99""" 4
> .el .IP "\f(CWgnu99\fR" 4
505,506c559,560
< .if n .Ip "\f(CW""""gnu9x""""\fR" 4
< .el .Ip "\f(CWgnu9x\fR" 4
---
> .ie n .IP """gnu9x""" 4
> .el .IP "\f(CWgnu9x\fR" 4
509a564,572
> .ie n .IP """c++98""" 4
> .el .IP "\f(CWc++98\fR" 4
> .IX Item "c++98"
> The 1998 \s-1ISO\s0 \*(C+ standard plus amendments.
> .ie n .IP """gnu++98""" 4
> .el .IP "\f(CWgnu++98\fR" 4
> .IX Item "gnu++98"
> The same as \fB\-std=c++98\fR plus \s-1GNU\s0 extensions. This is the
> default for \*(C+ code.
513c576
< .Ip "\fB\-I-\fR" 4
---
> .IP "\fB\-I\-\fR" 4
516c579
< options before \fB\-I-\fR are searched only for headers requested with
---
> options before \fB\-I\-\fR are searched only for headers requested with
519c582
< specified with \fB\-I\fR options after the \fB\-I-\fR, those
---
> specified with \fB\-I\fR options after the \fB\-I\-\fR, those
522c585
< In addition, \fB\-I-\fR inhibits the use of the directory of the current
---
> In addition, \fB\-I\-\fR inhibits the use of the directory of the current
524c587
< .Ip "\fB\-nostdinc\fR" 4
---
> .IP "\fB\-nostdinc\fR" 4
529c592
< .Ip "\fB\-nostdinc++\fR" 4
---
> .IP "\fB\-nostdinc++\fR" 4
534c597
< .Ip "\fB\-include\fR \fIfile\fR" 4
---
> .IP "\fB\-include\fR \fIfile\fR" 4
545c608
< .Ip "\fB\-imacros\fR \fIfile\fR" 4
---
> .IP "\fB\-imacros\fR \fIfile\fR" 4
554c617
< .Ip "\fB\-idirafter\fR \fIdir\fR" 4
---
> .IP "\fB\-idirafter\fR \fIdir\fR" 4
559c622
< .Ip "\fB\-iprefix\fR \fIprefix\fR" 4
---
> .IP "\fB\-iprefix\fR \fIprefix\fR" 4
564c627
< .Ip "\fB\-iwithprefix\fR \fIdir\fR" 4
---
> .IP "\fB\-iwithprefix\fR \fIdir\fR" 4
567c630
< .Ip "\fB\-iwithprefixbefore\fR \fIdir\fR" 4
---
> .IP "\fB\-iwithprefixbefore\fR \fIdir\fR" 4
574,576c637
< .Sp
< Use of these options is discouraged.
< .Ip "\fB\-isystem\fR \fIdir\fR" 4
---
> .IP "\fB\-isystem\fR \fIdir\fR" 4
582c643,647
< .Ip "\fB\-fpreprocessed\fR" 4
---
> .IP "\fB\-fdollars\-in\-identifiers\fR" 4
> .IX Item "-fdollars-in-identifiers"
> @anchor{fdollars\-in\-identifiers}
> Accept \fB$\fR in identifiers.
> .IP "\fB\-fpreprocessed\fR" 4
595,596c660,661
< \&\fB\-save-temps\fR.
< .Ip "\fB\-ftabstop=\fR\fIwidth\fR" 4
---
> \&\fB\-save\-temps\fR.
> .IP "\fB\-ftabstop=\fR\fIwidth\fR" 4
602c667,703
< .Ip "\fB\-fno-show-column\fR" 4
---
> .IP "\fB\-fexec\-charset=\fR\fIcharset\fR" 4
> .IX Item "-fexec-charset=charset"
> Set the execution character set, used for string and character
> constants. The default is \s-1UTF\-8\s0. \fIcharset\fR can be any encoding
> supported by the system's \f(CW\*(C`iconv\*(C'\fR library routine.
> .IP "\fB\-fwide\-exec\-charset=\fR\fIcharset\fR" 4
> .IX Item "-fwide-exec-charset=charset"
> Set the wide execution character set, used for wide string and
> character constants. The default is \s-1UTF\-32\s0 or \s-1UTF\-16\s0, whichever
> corresponds to the width of \f(CW\*(C`wchar_t\*(C'\fR. As with
> \&\fB\-ftarget\-charset\fR, \fIcharset\fR can be any encoding supported
> by the system's \f(CW\*(C`iconv\*(C'\fR library routine; however, you will have
> problems with encodings that do not fit exactly in \f(CW\*(C`wchar_t\*(C'\fR.
> .IP "\fB\-finput\-charset=\fR\fIcharset\fR" 4
> .IX Item "-finput-charset=charset"
> Set the input character set, used for translation from the character
> set of the input file to the source character set used by \s-1GCC\s0. If the
> locale does not specify, or \s-1GCC\s0 cannot get this information from the
> locale, the default is \s-1UTF\-8\s0. 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. \fIcharset\fR can be any encoding
> supported by the system's \f(CW\*(C`iconv\*(C'\fR library routine.
> .IP "\fB\-fworking\-directory\fR" 4
> .IX Item "-fworking-directory"
> 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. \s-1GCC\s0 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 \fB\-fno\-working\-directory\fR. If the \fB\-P\fR flag is
> present in the command line, this option has no effect, since no
> \&\f(CW\*(C`#line\*(C'\fR directives are emitted whatsoever.
> .IP "\fB\-fno\-show\-column\fR" 4
607c708
< .Ip "\fB\-A\fR \fIpredicate\fR\fB=\fR\fIanswer\fR" 4
---
> .IP "\fB\-A\fR \fIpredicate\fR\fB=\fR\fIanswer\fR" 4
613c714
< .Ip "\fB\-A -\fR\fIpredicate\fR\fB=\fR\fIanswer\fR" 4
---
> .IP "\fB\-A \-\fR\fIpredicate\fR\fB=\fR\fIanswer\fR" 4
617,623c718
< .Ip "\fB\-A-\fR" 4
< .IX Item "-A-"
< Cancel all predefined assertions and all assertions preceding it on
< the command line. Also, undefine all predefined macros and all
< macros preceding it on the command line. (This is a historical wart and
< may change in the future.)
< .Ip "\fB\-dCHARS\fR" 4
---
> .IP "\fB\-dCHARS\fR" 4
631c726
< .Ip "\fBM\fR" 4
---
> .IP "\fBM\fR" 4
641a737
> .Sp
643c739
< .Ip "\fBD\fR" 4
---
> .IP "\fBD\fR" 4
649c745
< .Ip "\fBN\fR" 4
---
> .IP "\fBN\fR" 4
652c748
< .Ip "\fBI\fR" 4
---
> .IP "\fBI\fR" 4
659c755
< .Ip "\fB\-P\fR" 4
---
> .IP "\fB\-P\fR" 4
665c761
< .Ip "\fB\-C\fR" 4
---
> .IP "\fB\-C\fR" 4
676,686c772,789
< .Ip "\fB\-gcc\fR" 4
< .IX Item "-gcc"
< Define the macros _\|_GNUC_\|_, _\|_GNUC_MINOR_\|_ and
< _\|_GNUC_PATCHLEVEL_\|_. These are defined automatically when you use
< \&\fBgcc \-E\fR; you can turn them off in that case with
< \&\fB\-no-gcc\fR.
< .Ip "\fB\-traditional\fR" 4
< .IX Item "-traditional"
< Try to imitate the behavior of old-fashioned C, as opposed to \s-1ISO\s0
< C.
< .Ip "\fB\-trigraphs\fR" 4
---
> .IP "\fB\-CC\fR" 4
> .IX Item "-CC"
> Do not discard comments, including during macro expansion. This is
> like \fB\-C\fR, except that comments contained within macros are
> also passed through to the output file where the macro is expanded.
> .Sp
> In addition to the side-effects of the \fB\-C\fR option, the
> \&\fB\-CC\fR 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.
> .Sp
> The \fB\-CC\fR option is generally used to support lint comments.
> .IP "\fB\-traditional\-cpp\fR" 4
> .IX Item "-traditional-cpp"
> Try to imitate the behavior of old-fashioned C preprocessors, as
> opposed to \s-1ISO\s0 C preprocessors.
> .IP "\fB\-trigraphs\fR" 4
689c792
< .Ip "\fB\-remap\fR" 4
---
> .IP "\fB\-remap\fR" 4
692,699c795,797
< short file names, such as \s-1MS-DOS\s0.
< .Ip "\fB\-$\fR" 4
< .IX Item "-$"
< Forbid the use of \fB$\fR in identifiers. The C standard allows
< implementations to define extra characters that can appear in
< identifiers. By default \s-1GNU\s0 \s-1CPP\s0 permits \fB$\fR, a common extension.
< .Ip "\fB\-h\fR" 4
< .IX Item "-h"
---
> short file names, such as \s-1MS\-DOS\s0.
> .IP "\fB\-\-help\fR" 4
> .IX Item "--help"
701,704c799,800
< .Ip "\fB\*(--help\fR" 4
< .IX Item "help"
< .Ip "\fB\*(--target-help\fR" 4
< .IX Item "target-help"
---
> .IP "\fB\-\-target\-help\fR" 4
> .IX Item "--target-help"
708c804
< .Ip "\fB\-v\fR" 4
---
> .IP "\fB\-v\fR" 4
712c808
< .Ip "\fB\-H\fR" 4
---
> .IP "\fB\-H\fR" 4
716,717c812,815
< \&\fB#include\fR stack it is.
< .Ip "\fB\-version\fR" 4
---
> \&\fB#include\fR 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 \fB...x\fR and a valid one with \fB...!\fR .
> .IP "\fB\-version\fR" 4
720,721c818,819
< .Ip "\fB\*(--version\fR" 4
< .IX Item "version"
---
> .IP "\fB\-\-version\fR" 4
> .IX Item "--version"
736c834
< .Ip "\fB\s-1CPATH\s0\fR" 4
---
> .IP "\fB\s-1CPATH\s0\fR" 4
739c837
< .Ip "\fBC_INCLUDE_PATH\fR" 4
---
> .IP "\fBC_INCLUDE_PATH\fR" 4
741c839
< .Ip "\fB\s-1CPLUS_INCLUDE_PATH\s0\fR" 4
---
> .IP "\fB\s-1CPLUS_INCLUDE_PATH\s0\fR" 4
743c841
< .Ip "\fB\s-1OBJC_INCLUDE_PATH\s0\fR" 4
---
> .IP "\fB\s-1OBJC_INCLUDE_PATH\s0\fR" 4
749c847
< determined at \s-1GCC\s0 build time. For Windows-based targets it is a
---
> determined at \s-1GCC\s0 build time. For Microsoft Windows-based targets it is a
754c852
< options on the command line. The environment variable is used
---
> options on the command line. This environment variable is used
762,763c860,865
< See also \f(CW@ref\fR{Search Path}.
< .Ip "\fB\s-1DEPENDENCIES_OUTPUT\s0\fR" 4
---
> 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
> \&\fB\s-1CPATH\s0\fR is \f(CW\*(C`:/special/include\*(C'\fR, that has the same
> effect as \fB\-I.\ \-I/special/include\fR.
> .IP "\fB\s-1DEPENDENCIES_OUTPUT\s0\fR" 4
765d866
< @anchor{\s-1DEPENDENCIES_OUTPUT\s0}
780c881
< .Ip "\fB\s-1SUNPRO_DEPENDENCIES\s0\fR" 4
---
> .IP "\fB\s-1SUNPRO_DEPENDENCIES\s0\fR" 4
782,786c883,886
< This variable is the same as the environment variable
< \&\fB\s-1DEPENDENCIES_OUTPUT\s0\fR, except that
< system header files are not ignored, so it implies \fB\-M\fR rather
< than \fB\-MM\fR. However, the dependence on the main input file is
< omitted.
---
> This variable is the same as \fB\s-1DEPENDENCIES_OUTPUT\s0\fR (see above),
> except that system header files are not ignored, so it implies
> \&\fB\-M\fR rather than \fB\-MM\fR. However, the dependence on the
> main input file is omitted.
789c889
< \&\fIgpl\fR\|(7), \fIgfdl\fR\|(7), \fIfsf-funding\fR\|(7),
---
> \&\fIgpl\fR\|(7), \fIgfdl\fR\|(7), \fIfsf\-funding\fR\|(7),
795c895
< 1997, 1998, 1999, 2000, 2001
---
> 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004
810a911
> .PP