| cpp.1 (162509) | cpp.1 (171825) |
|---|---|
| 1.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.14 2.\" 3.\" Standard preamble: 4.\" ======================================================================== 5.de Sh \" Subsection heading 6.br 7.if t .Sp 8.ne 5 --- 115 unchanged lines hidden (view full) --- 124. ds Th \o'LP' 125. ds ae ae 126. ds Ae AE 127.\} 128.rm #[ #] #H #V #F C 129.\" ======================================================================== 130.\" 131.IX Title "CPP 1" | 1.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.14 2.\" 3.\" Standard preamble: 4.\" ======================================================================== 5.de Sh \" Subsection heading 6.br 7.if t .Sp 8.ne 5 --- 115 unchanged lines hidden (view full) --- 124. ds Th \o'LP' 125. ds ae ae 126. ds Ae AE 127.\} 128.rm #[ #] #H #V #F C 129.\" ======================================================================== 130.\" 131.IX Title "CPP 1" |
| 132.TH CPP 1 "2006-03-06" "gcc-3.4.6" "GNU" | 132.TH CPP 1 "2007-07-19" "gcc-4.2.1" "GNU" |
| 133.SH "NAME" 134cpp \- The C Preprocessor 135.SH "SYNOPSIS" 136.IX Header "SYNOPSIS" 137cpp [\fB\-D\fR\fImacro\fR[=\fIdefn\fR]...] [\fB\-U\fR\fImacro\fR] | 133.SH "NAME" 134cpp \- The C Preprocessor 135.SH "SYNOPSIS" 136.IX Header "SYNOPSIS" 137cpp [\fB\-D\fR\fImacro\fR[=\fIdefn\fR]...] [\fB\-U\fR\fImacro\fR] |
| 138 [\fB\-I\fR\fIdir\fR...] [\fB\-W\fR\fIwarn\fR...] | 138 [\fB\-I\fR\fIdir\fR...] [\fB\-iquote\fR\fIdir\fR...] 139 [\fB\-W\fR\fIwarn\fR...] |
| 139 [\fB\-M\fR|\fB\-MM\fR] [\fB\-MG\fR] [\fB\-MF\fR \fIfilename\fR] 140 [\fB\-MP\fR] [\fB\-MQ\fR \fItarget\fR...] 141 [\fB\-MT\fR \fItarget\fR...] 142 [\fB\-P\fR] [\fB\-fno\-working\-directory\fR] 143 [\fB\-x\fR \fIlanguage\fR] [\fB\-std=\fR\fIstandard\fR] 144 \fIinfile\fR \fIoutfile\fR 145.PP 146Only the most useful options are listed here; see below for the remainder. --- 66 unchanged lines hidden (view full) --- 213Many options have multi-letter names; therefore multiple single-letter 214options may \fInot\fR be grouped: \fB\-dM\fR is very different from 215\&\fB\-d\ \-M\fR. 216.IP "\fB\-D\fR \fIname\fR" 4 217.IX Item "-D name" 218Predefine \fIname\fR as a macro, with definition \f(CW1\fR. 219.IP "\fB\-D\fR \fIname\fR\fB=\fR\fIdefinition\fR" 4 220.IX Item "-D name=definition" | 140 [\fB\-M\fR|\fB\-MM\fR] [\fB\-MG\fR] [\fB\-MF\fR \fIfilename\fR] 141 [\fB\-MP\fR] [\fB\-MQ\fR \fItarget\fR...] 142 [\fB\-MT\fR \fItarget\fR...] 143 [\fB\-P\fR] [\fB\-fno\-working\-directory\fR] 144 [\fB\-x\fR \fIlanguage\fR] [\fB\-std=\fR\fIstandard\fR] 145 \fIinfile\fR \fIoutfile\fR 146.PP 147Only the most useful options are listed here; see below for the remainder. --- 66 unchanged lines hidden (view full) --- 214Many options have multi-letter names; therefore multiple single-letter 215options may \fInot\fR be grouped: \fB\-dM\fR is very different from 216\&\fB\-d\ \-M\fR. 217.IP "\fB\-D\fR \fIname\fR" 4 218.IX Item "-D name" 219Predefine \fIname\fR as a macro, with definition \f(CW1\fR. 220.IP "\fB\-D\fR \fIname\fR\fB=\fR\fIdefinition\fR" 4 221.IX Item "-D name=definition" |
| 221Predefine \fIname\fR as a macro, with definition \fIdefinition\fR. | |
| 222The contents of \fIdefinition\fR are tokenized and processed as if 223they appeared during translation phase three in a \fB#define\fR 224directive. In particular, the definition will be truncated by 225embedded newline characters. 226.Sp 227If you are invoking the preprocessor from a shell or shell-like 228program you may need to use the shell's quoting syntax to protect 229characters such as spaces that have a meaning in the shell syntax. --- 47 unchanged lines hidden (view full) --- 277.IP "\fB\-Wcomments\fR" 4 278.IX Item "-Wcomments" 279.PD 280Warn whenever a comment-start sequence \fB/*\fR appears in a \fB/*\fR 281comment, or whenever a backslash-newline appears in a \fB//\fR comment. 282(Both forms have the same effect.) 283.IP "\fB\-Wtrigraphs\fR" 4 284.IX Item "-Wtrigraphs" | 222The contents of \fIdefinition\fR are tokenized and processed as if 223they appeared during translation phase three in a \fB#define\fR 224directive. In particular, the definition will be truncated by 225embedded newline characters. 226.Sp 227If you are invoking the preprocessor from a shell or shell-like 228program you may need to use the shell's quoting syntax to protect 229characters such as spaces that have a meaning in the shell syntax. --- 47 unchanged lines hidden (view full) --- 277.IP "\fB\-Wcomments\fR" 4 278.IX Item "-Wcomments" 279.PD 280Warn whenever a comment-start sequence \fB/*\fR appears in a \fB/*\fR 281comment, or whenever a backslash-newline appears in a \fB//\fR comment. 282(Both forms have the same effect.) 283.IP "\fB\-Wtrigraphs\fR" 4 284.IX Item "-Wtrigraphs" |
| 285@anchor{Wtrigraphs} | |
| 286Most trigraphs in comments cannot affect the meaning of the program. 287However, a trigraph that would form an escaped newline (\fB??/\fR at 288the end of a line) can, by changing where the comment begins or ends. 289Therefore, only trigraphs that would form escaped newlines produce 290warnings inside a comment. 291.Sp 292This option is implied by \fB\-Wall\fR. If \fB\-Wall\fR is not 293given, this option is still enabled unless trigraphs are enabled. To --- 17 unchanged lines hidden (view full) --- 311Warn about macros defined in the main file that are unused. A macro 312is \fIused\fR if it is expanded or tested for existence at least once. 313The preprocessor will also warn if the macro has not been used at the 314time it is redefined or undefined. 315.Sp 316Built-in macros, macros defined on the command line, and macros 317defined in include files are not warned about. 318.Sp | 285Most trigraphs in comments cannot affect the meaning of the program. 286However, a trigraph that would form an escaped newline (\fB??/\fR at 287the end of a line) can, by changing where the comment begins or ends. 288Therefore, only trigraphs that would form escaped newlines produce 289warnings inside a comment. 290.Sp 291This option is implied by \fB\-Wall\fR. If \fB\-Wall\fR is not 292given, this option is still enabled unless trigraphs are enabled. To --- 17 unchanged lines hidden (view full) --- 310Warn about macros defined in the main file that are unused. A macro 311is \fIused\fR if it is expanded or tested for existence at least once. 312The preprocessor will also warn if the macro has not been used at the 313time it is redefined or undefined. 314.Sp 315Built-in macros, macros defined on the command line, and macros 316defined in include files are not warned about. 317.Sp |
| 319\&\fBNote:\fR If a macro is actually used, but only used in skipped | 318\&\fINote:\fR If a macro is actually used, but only used in skipped |
| 320conditional blocks, then \s-1CPP\s0 will report it as unused. To avoid the 321warning in such a case, you might improve the scope of the macro's 322definition by, for example, moving it into the first skipped block. 323Alternatively, you could provide a dummy use with something like: 324.Sp 325.Vb 2 326\& #if defined the_macro_causing_the_warning 327\& #endif --- 64 unchanged lines hidden (view full) --- 392Like \fB\-M\fR but do not mention header files that are found in 393system header directories, nor header files that are included, 394directly or indirectly, from such a header. 395.Sp 396This implies that the choice of angle brackets or double quotes in an 397\&\fB#include\fR directive does not in itself determine whether that 398header will appear in \fB\-MM\fR dependency output. This is a 399slight change in semantics from \s-1GCC\s0 versions 3.0 and earlier. | 319conditional blocks, then \s-1CPP\s0 will report it as unused. To avoid the 320warning in such a case, you might improve the scope of the macro's 321definition by, for example, moving it into the first skipped block. 322Alternatively, you could provide a dummy use with something like: 323.Sp 324.Vb 2 325\& #if defined the_macro_causing_the_warning 326\& #endif --- 64 unchanged lines hidden (view full) --- 391Like \fB\-M\fR but do not mention header files that are found in 392system header directories, nor header files that are included, 393directly or indirectly, from such a header. 394.Sp 395This implies that the choice of angle brackets or double quotes in an 396\&\fB#include\fR directive does not in itself determine whether that 397header will appear in \fB\-MM\fR dependency output. This is a 398slight change in semantics from \s-1GCC\s0 versions 3.0 and earlier. |
| 400.Sp 401@anchor{dashMF} | |
| 402.IP "\fB\-MF\fR \fIfile\fR" 4 403.IX Item "-MF file" 404When used with \fB\-M\fR or \fB\-MM\fR, specifies a 405file to write the dependencies to. If no \fB\-MF\fR switch is given 406the preprocessor sends the rules to the same place it would have sent 407preprocessed output. 408.Sp 409When used with the driver options \fB\-MD\fR or \fB\-MMD\fR, --- 56 unchanged lines hidden (view full) --- 466.IX Item "-MD" 467\&\fB\-MD\fR is equivalent to \fB\-M \-MF\fR \fIfile\fR, except that 468\&\fB\-E\fR is not implied. The driver determines \fIfile\fR based on 469whether an \fB\-o\fR option is given. If it is, the driver uses its 470argument but with a suffix of \fI.d\fR, otherwise it take the 471basename of the input file and applies a \fI.d\fR suffix. 472.Sp 473If \fB\-MD\fR is used in conjunction with \fB\-E\fR, any | 399.IP "\fB\-MF\fR \fIfile\fR" 4 400.IX Item "-MF file" 401When used with \fB\-M\fR or \fB\-MM\fR, specifies a 402file to write the dependencies to. If no \fB\-MF\fR switch is given 403the preprocessor sends the rules to the same place it would have sent 404preprocessed output. 405.Sp 406When used with the driver options \fB\-MD\fR or \fB\-MMD\fR, --- 56 unchanged lines hidden (view full) --- 463.IX Item "-MD" 464\&\fB\-MD\fR is equivalent to \fB\-M \-MF\fR \fIfile\fR, except that 465\&\fB\-E\fR is not implied. The driver determines \fIfile\fR based on 466whether an \fB\-o\fR option is given. If it is, the driver uses its 467argument but with a suffix of \fI.d\fR, otherwise it take the 468basename of the input file and applies a \fI.d\fR suffix. 469.Sp 470If \fB\-MD\fR is used in conjunction with \fB\-E\fR, any |
| 474\&\fB\-o\fR switch is understood to specify the dependency output file 475(but \f(CW@pxref\fR{dashMF,,\-MF}), but if used without \fB\-E\fR, each \fB\-o\fR | 471\&\fB\-o\fR switch is understood to specify the dependency output file, but if used without \fB\-E\fR, each \fB\-o\fR |
| 476is understood to specify a target object file. 477.Sp 478Since \fB\-E\fR is not implied, \fB\-MD\fR can be used to generate 479a dependency output file as a side-effect of the compilation process. 480.IP "\fB\-MMD\fR" 4 481.IX Item "-MMD" 482Like \fB\-MD\fR except mention only user header files, not system | 472is understood to specify a target object file. 473.Sp 474Since \fB\-E\fR is not implied, \fB\-MD\fR can be used to generate 475a dependency output file as a side-effect of the compilation process. 476.IP "\fB\-MMD\fR" 4 477.IX Item "-MMD" 478Like \fB\-MD\fR except mention only user header files, not system |
| 483\&\-header files. | 479header files. |
| 484.IP "\fB\-x c\fR" 4 485.IX Item "-x c" 486.PD 0 487.IP "\fB\-x c++\fR" 4 488.IX Item "-x c++" 489.IP "\fB\-x objective-c\fR" 4 490.IX Item "-x objective-c" 491.IP "\fB\-x assembler-with-cpp\fR" 4 492.IX Item "-x assembler-with-cpp" 493.PD 494Specify the source language: C, \*(C+, Objective\-C, or assembly. This has 495nothing to do with standards conformance or extensions; it merely 496selects which base syntax to expect. If you give none of these options, 497cpp will deduce the language from the extension of the source file: 498\&\fB.c\fR, \fB.cc\fR, \fB.m\fR, or \fB.S\fR. Some other common 499extensions for \*(C+ and assembly are also recognized. If cpp does not 500recognize the extension, it will treat the file as C; this is the most 501generic mode. 502.Sp | 480.IP "\fB\-x c\fR" 4 481.IX Item "-x c" 482.PD 0 483.IP "\fB\-x c++\fR" 4 484.IX Item "-x c++" 485.IP "\fB\-x objective-c\fR" 4 486.IX Item "-x objective-c" 487.IP "\fB\-x assembler-with-cpp\fR" 4 488.IX Item "-x assembler-with-cpp" 489.PD 490Specify the source language: C, \*(C+, Objective\-C, or assembly. This has 491nothing to do with standards conformance or extensions; it merely 492selects which base syntax to expect. If you give none of these options, 493cpp will deduce the language from the extension of the source file: 494\&\fB.c\fR, \fB.cc\fR, \fB.m\fR, or \fB.S\fR. Some other common 495extensions for \*(C+ and assembly are also recognized. If cpp does not 496recognize the extension, it will treat the file as C; this is the most 497generic mode. 498.Sp |
| 503\&\fBNote:\fR Previous versions of cpp accepted a \fB\-lang\fR option | 499\&\fINote:\fR Previous versions of cpp accepted a \fB\-lang\fR option |
| 504which selected both the language and the standards conformance level. 505This option has been removed, because it conflicts with the \fB\-l\fR 506option. 507.IP "\fB\-std=\fR\fIstandard\fR" 4 508.IX Item "-std=standard" 509.PD 0 510.IP "\fB\-ansi\fR" 4 511.IX Item "-ansi" --- 67 unchanged lines hidden (view full) --- 579options before \fB\-I\-\fR are searched only for headers requested with 580\&\f(CW\*(C`#include\ "\f(CIfile\f(CW"\*(C'\fR; they are not searched for 581\&\f(CW\*(C`#include\ <\f(CIfile\f(CW>\*(C'\fR. If additional directories are 582specified with \fB\-I\fR options after the \fB\-I\-\fR, those 583directories are searched for all \fB#include\fR directives. 584.Sp 585In addition, \fB\-I\-\fR inhibits the use of the directory of the current 586file directory as the first search directory for \f(CW\*(C`#include\ "\f(CIfile\f(CW"\*(C'\fR. | 500which selected both the language and the standards conformance level. 501This option has been removed, because it conflicts with the \fB\-l\fR 502option. 503.IP "\fB\-std=\fR\fIstandard\fR" 4 504.IX Item "-std=standard" 505.PD 0 506.IP "\fB\-ansi\fR" 4 507.IX Item "-ansi" --- 67 unchanged lines hidden (view full) --- 575options before \fB\-I\-\fR are searched only for headers requested with 576\&\f(CW\*(C`#include\ "\f(CIfile\f(CW"\*(C'\fR; they are not searched for 577\&\f(CW\*(C`#include\ <\f(CIfile\f(CW>\*(C'\fR. If additional directories are 578specified with \fB\-I\fR options after the \fB\-I\-\fR, those 579directories are searched for all \fB#include\fR directives. 580.Sp 581In addition, \fB\-I\-\fR inhibits the use of the directory of the current 582file directory as the first search directory for \f(CW\*(C`#include\ "\f(CIfile\f(CW"\*(C'\fR. |
| 583.Sp 584This option has been deprecated. |
|
| 587.IP "\fB\-nostdinc\fR" 4 588.IX Item "-nostdinc" 589Do not search the standard system directories for header files. 590Only the directories you have specified with \fB\-I\fR options 591(and the directory of the current file, if appropriate) are searched. 592.IP "\fB\-nostdinc++\fR" 4 593.IX Item "-nostdinc++" 594Do not search for header files in the \*(C+\-specific standard directories, --- 34 unchanged lines hidden (view full) --- 629.PD 0 630.IP "\fB\-iwithprefixbefore\fR \fIdir\fR" 4 631.IX Item "-iwithprefixbefore dir" 632.PD 633Append \fIdir\fR to the prefix specified previously with 634\&\fB\-iprefix\fR, and add the resulting directory to the include search 635path. \fB\-iwithprefixbefore\fR puts it in the same place \fB\-I\fR 636would; \fB\-iwithprefix\fR puts it where \fB\-idirafter\fR would. | 585.IP "\fB\-nostdinc\fR" 4 586.IX Item "-nostdinc" 587Do not search the standard system directories for header files. 588Only the directories you have specified with \fB\-I\fR options 589(and the directory of the current file, if appropriate) are searched. 590.IP "\fB\-nostdinc++\fR" 4 591.IX Item "-nostdinc++" 592Do not search for header files in the \*(C+\-specific standard directories, --- 34 unchanged lines hidden (view full) --- 627.PD 0 628.IP "\fB\-iwithprefixbefore\fR \fIdir\fR" 4 629.IX Item "-iwithprefixbefore dir" 630.PD 631Append \fIdir\fR to the prefix specified previously with 632\&\fB\-iprefix\fR, and add the resulting directory to the include search 633path. \fB\-iwithprefixbefore\fR puts it in the same place \fB\-I\fR 634would; \fB\-iwithprefix\fR puts it where \fB\-idirafter\fR would. |
| 635.IP "\fB\-isysroot\fR \fIdir\fR" 4 636.IX Item "-isysroot dir" 637This option is like the \fB\-\-sysroot\fR option, but applies only to 638header files. See the \fB\-\-sysroot\fR option for more information. 639.IP "\fB\-imultilib\fR \fIdir\fR" 4 640.IX Item "-imultilib dir" 641Use \fIdir\fR as a subdirectory of the directory containing 642target-specific \*(C+ headers. |
|
| 637.IP "\fB\-isystem\fR \fIdir\fR" 4 638.IX Item "-isystem dir" 639Search \fIdir\fR for header files, after all directories specified by 640\&\fB\-I\fR but before the standard system directories. Mark it 641as a system directory, so that it gets the same special treatment as 642is applied to the standard system directories. | 643.IP "\fB\-isystem\fR \fIdir\fR" 4 644.IX Item "-isystem dir" 645Search \fIdir\fR for header files, after all directories specified by 646\&\fB\-I\fR but before the standard system directories. Mark it 647as a system directory, so that it gets the same special treatment as 648is applied to the standard system directories. |
| 649.IP "\fB\-iquote\fR \fIdir\fR" 4 650.IX Item "-iquote dir" 651Search \fIdir\fR only for header files requested with 652\&\f(CW\*(C`#include\ "\f(CIfile\f(CW"\*(C'\fR; they are not searched for 653\&\f(CW\*(C`#include\ <\f(CIfile\f(CW>\*(C'\fR, before all directories specified by 654\&\fB\-I\fR and before the standard system directories. |
|
| 643.IP "\fB\-fdollars\-in\-identifiers\fR" 4 644.IX Item "-fdollars-in-identifiers" | 655.IP "\fB\-fdollars\-in\-identifiers\fR" 4 656.IX Item "-fdollars-in-identifiers" |
| 645@anchor{fdollars\-in\-identifiers} | |
| 646Accept \fB$\fR in identifiers. | 657Accept \fB$\fR in identifiers. |
| 658.IP "\fB\-fextended\-identifiers\fR" 4 659.IX Item "-fextended-identifiers" 660Accept universal character names in identifiers. This option is 661experimental; in a future version of \s-1GCC\s0, it will be enabled by 662default for C99 and \*(C+. |
|
| 647.IP "\fB\-fpreprocessed\fR" 4 648.IX Item "-fpreprocessed" 649Indicate to the preprocessor that the input file has already been 650preprocessed. This suppresses things like macro expansion, trigraph 651conversion, escaped newline splicing, and processing of most directives. 652The preprocessor still recognizes and removes comments, so that you can 653pass a file preprocessed with \fB\-C\fR to the compiler without 654problems. In this mode the integrated preprocessor is little more than --- 14 unchanged lines hidden (view full) --- 669Set the execution character set, used for string and character 670constants. The default is \s-1UTF\-8\s0. \fIcharset\fR can be any encoding 671supported by the system's \f(CW\*(C`iconv\*(C'\fR library routine. 672.IP "\fB\-fwide\-exec\-charset=\fR\fIcharset\fR" 4 673.IX Item "-fwide-exec-charset=charset" 674Set the wide execution character set, used for wide string and 675character constants. The default is \s-1UTF\-32\s0 or \s-1UTF\-16\s0, whichever 676corresponds to the width of \f(CW\*(C`wchar_t\*(C'\fR. As with | 663.IP "\fB\-fpreprocessed\fR" 4 664.IX Item "-fpreprocessed" 665Indicate to the preprocessor that the input file has already been 666preprocessed. This suppresses things like macro expansion, trigraph 667conversion, escaped newline splicing, and processing of most directives. 668The preprocessor still recognizes and removes comments, so that you can 669pass a file preprocessed with \fB\-C\fR to the compiler without 670problems. In this mode the integrated preprocessor is little more than --- 14 unchanged lines hidden (view full) --- 685Set the execution character set, used for string and character 686constants. The default is \s-1UTF\-8\s0. \fIcharset\fR can be any encoding 687supported by the system's \f(CW\*(C`iconv\*(C'\fR library routine. 688.IP "\fB\-fwide\-exec\-charset=\fR\fIcharset\fR" 4 689.IX Item "-fwide-exec-charset=charset" 690Set the wide execution character set, used for wide string and 691character constants. The default is \s-1UTF\-32\s0 or \s-1UTF\-16\s0, whichever 692corresponds to the width of \f(CW\*(C`wchar_t\*(C'\fR. As with |
| 677\&\fB\-ftarget\-charset\fR, \fIcharset\fR can be any encoding supported | 693\&\fB\-fexec\-charset\fR, \fIcharset\fR can be any encoding supported |
| 678by the system's \f(CW\*(C`iconv\*(C'\fR library routine; however, you will have 679problems with encodings that do not fit exactly in \f(CW\*(C`wchar_t\*(C'\fR. 680.IP "\fB\-finput\-charset=\fR\fIcharset\fR" 4 681.IX Item "-finput-charset=charset" 682Set the input character set, used for translation from the character | 694by the system's \f(CW\*(C`iconv\*(C'\fR library routine; however, you will have 695problems with encodings that do not fit exactly in \f(CW\*(C`wchar_t\*(C'\fR. 696.IP "\fB\-finput\-charset=\fR\fIcharset\fR" 4 697.IX Item "-finput-charset=charset" 698Set the input character set, used for translation from the character |
| 683set of the input file to the source character set used by \s-1GCC\s0. If the | 699set of the input file to the source character set used by \s-1GCC\s0. If the |
| 684locale does not specify, or \s-1GCC\s0 cannot get this information from the | 700locale does not specify, or \s-1GCC\s0 cannot get this information from the |
| 685locale, the default is \s-1UTF\-8\s0. This can be overridden by either the locale 686or this command line option. Currently the command line option takes 687precedence if there's a conflict. \fIcharset\fR can be any encoding | 701locale, the default is \s-1UTF\-8\s0. This can be overridden by either the locale 702or this command line option. Currently the command line option takes 703precedence if there's a conflict. \fIcharset\fR can be any encoding |
| 688supported by the system's \f(CW\*(C`iconv\*(C'\fR library routine. 689.IP "\fB\-fworking\-directory\fR" 4 690.IX Item "-fworking-directory" 691Enable generation of linemarkers in the preprocessor output that will 692let the compiler know the current working directory at the time of 693preprocessing. When this option is enabled, the preprocessor will 694emit, after the initial linemarker, a second linemarker with the 695current working directory followed by two slashes. \s-1GCC\s0 will use this --- 191 unchanged lines hidden (view full) --- 887.SH "SEE ALSO" 888.IX Header "SEE ALSO" 889\&\fIgpl\fR\|(7), \fIgfdl\fR\|(7), \fIfsf\-funding\fR\|(7), 890\&\fIgcc\fR\|(1), \fIas\fR\|(1), \fIld\fR\|(1), and the Info entries for \fIcpp\fR, \fIgcc\fR, and 891\&\fIbinutils\fR. 892.SH "COPYRIGHT" 893.IX Header "COPYRIGHT" 894Copyright (c) 1987, 1989, 1991, 1992, 1993, 1994, 1995, 1996, | 704supported by the system's \f(CW\*(C`iconv\*(C'\fR library routine. 705.IP "\fB\-fworking\-directory\fR" 4 706.IX Item "-fworking-directory" 707Enable generation of linemarkers in the preprocessor output that will 708let the compiler know the current working directory at the time of 709preprocessing. When this option is enabled, the preprocessor will 710emit, after the initial linemarker, a second linemarker with the 711current working directory followed by two slashes. \s-1GCC\s0 will use this --- 191 unchanged lines hidden (view full) --- 903.SH "SEE ALSO" 904.IX Header "SEE ALSO" 905\&\fIgpl\fR\|(7), \fIgfdl\fR\|(7), \fIfsf\-funding\fR\|(7), 906\&\fIgcc\fR\|(1), \fIas\fR\|(1), \fIld\fR\|(1), and the Info entries for \fIcpp\fR, \fIgcc\fR, and 907\&\fIbinutils\fR. 908.SH "COPYRIGHT" 909.IX Header "COPYRIGHT" 910Copyright (c) 1987, 1989, 1991, 1992, 1993, 1994, 1995, 1996, |
| 8951997, 1998, 1999, 2000, 2001, 2002, 2003, 2004 | 9111997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005 |
| 896Free Software Foundation, Inc. 897.PP 898Permission is granted to copy, distribute and/or modify this document 899under the terms of the \s-1GNU\s0 Free Documentation License, Version 1.1 or 900any later version published by the Free Software Foundation. A copy of 901the license is included in the 902man page \fIgfdl\fR\|(7). 903This manual contains no Invariant Sections. The Front-Cover Texts are --- 15 unchanged lines hidden --- | 912Free Software Foundation, Inc. 913.PP 914Permission is granted to copy, distribute and/or modify this document 915under the terms of the \s-1GNU\s0 Free Documentation License, Version 1.1 or 916any later version published by the Free Software Foundation. A copy of 917the license is included in the 918man page \fIgfdl\fR\|(7). 919This manual contains no Invariant Sections. The Front-Cover Texts are --- 15 unchanged lines hidden --- |