diff options
Diffstat (limited to 'gcc/doc/gcc.1')
| -rw-r--r-- | gcc/doc/gcc.1 | 48 |
1 files changed, 25 insertions, 23 deletions
diff --git a/gcc/doc/gcc.1 b/gcc/doc/gcc.1 index 82fd7bc2b36..fd33750eb24 100644 --- a/gcc/doc/gcc.1 +++ b/gcc/doc/gcc.1 @@ -1,5 +1,5 @@ .\" Automatically generated by Pod::Man version 1.16 -.\" Sat Jun 16 09:19:37 2001 +.\" Mon Jun 25 00:14:37 2001 .\" .\" Standard preamble: .\" ====================================================================== @@ -138,7 +138,7 @@ .\" ====================================================================== .\" .IX Title "GCC 1" -.TH GCC 1 "gcc-3.1" "2001-06-16" "GNU" +.TH GCC 1 "gcc-3.1" "2001-06-25" "GNU" .UC .SH "NAME" gcc \- \s-1GNU\s0 project C and \*(C+ compiler @@ -821,7 +821,7 @@ languages; or options that are meaningful only for \*(C+ programs. .Sh "Options Controlling C Dialect" .IX Subsection "Options Controlling C Dialect" The following options control the dialect of C (or languages derived -from C, such as \*(C+ and Objective C) that the compiler accepts: +from C, such as \*(C+ and Objective-C) that the compiler accepts: .Ip "\fB\-ansi\fR" 4 .IX Item "-ansi" In C mode, support all \s-1ISO\s0 C89 programs. In \*(C+ mode, @@ -1502,14 +1502,14 @@ Traditionally, diagnostic messages have been formatted irrespective of the output device's aspect (e.g. its width, ...). The options described below can be used to control the diagnostic messages formatting algorithm, e.g. how many characters per line, how often source location -information should be reported. Right now, only the \*(C+ front-end can +information should be reported. Right now, only the \*(C+ front end can honor these options. However it is expected, in the near future, that -the remaining front-ends would be able to digest them correctly. +the remaining front ends would be able to digest them correctly. .Ip "\fB\-fmessage-length=\fR\fIn\fR" 4 .IX Item "-fmessage-length=n" Try to format error messages so that they fit on lines of about \fIn\fR characters. The default is 72 characters for g++ and 0 for the rest of -the front-ends supported by \s-1GCC\s0. If \fIn\fR is zero, then no +the front ends supported by \s-1GCC\s0. If \fIn\fR is zero, then no line-wrapping will be done; each error message will appear on a single line. .Ip "\fB\-fdiagnostics-show-location=once\fR" 4 @@ -1714,7 +1714,7 @@ In C, every \f(CW\*(C`else\*(C'\fR branch belongs to the innermost possible \f(C statement, which in this example is \f(CW\*(C`if (b)\*(C'\fR. This is often not what the programmer expected, as illustrated in the above example by indentation the programmer chose. When there is the potential for this -confusion, \s-1GNU\s0 C will issue a warning when this flag is specified. +confusion, \s-1GCC\s0 will issue a warning when this flag is specified. To eliminate the warning, add explicit braces around the innermost \&\f(CW\*(C`if\*(C'\fR statement so there is no way the \f(CW\*(C`else\*(C'\fR could belong to the enclosing \f(CW\*(C`if\*(C'\fR. The resulting code would look like this: @@ -3010,7 +3010,9 @@ sets \fB\-fno-math-errno\fR. .IX Item "-funsafe-math-optimizations" Allow optimizations for floating-point arithmetic that (a) assume that arguments and results are valid and (b) may violate \s-1IEEE\s0 or -\&\s-1ANSI\s0 standards. +\&\s-1ANSI\s0 standards. When used at link-time, it may include libraries +or startup files that change the default \s-1FPU\s0 control word or other +similar optimizations. .Sp This option should never be turned on by any \fB\-O\fR option since it can result in incorrect output for programs which depend on @@ -3739,7 +3741,7 @@ and searches several directories. .Ip "\fB\-lobjc\fR" 4 .IX Item "-lobjc" You need this special case of the \fB\-l\fR option in order to -link an Objective C program. +link an Objective-C program. .Ip "\fB\-nostartfiles\fR" 4 .IX Item "-nostartfiles" Do not use the standard system startup files when linking. @@ -5114,12 +5116,12 @@ references. In particular, a load instruction may execute before a preceding store instruction. Such reordering violates sequential consistency of volatile memory references, when there are multiple processors. When consistency must be guaranteed, -\&\s-1GNU\s0 C generates special instructions, as needed, to force +\&\s-1GCC\s0 generates special instructions, as needed, to force execution in the proper order. .Sp The \s-1MC88100\s0 processor does not reorder memory references and so -always provides sequential consistency. However, by default, \s-1GNU\s0 -C generates the special instructions to guarantee consistency +always provides sequential consistency. However, by default, \s-1GCC\s0 +generates the special instructions to guarantee consistency even when you use \fB\-m88100\fR, so that the code may be run on an \&\s-1MC88110\s0 processor. If you intend to run your code only on the \&\s-1MC88100\s0 processor, you may use \fB\-mno-serialize-volatile\fR. @@ -5165,13 +5167,13 @@ zero will be detected. By default, detection is guaranteed. .Sp Some models of the \s-1MC88100\s0 processor fail to trap upon integer division by zero under certain conditions. By default, when -compiling code that might be run on such a processor, \s-1GNU\s0 C +compiling code that might be run on such a processor, \s-1GCC\s0 generates code that explicitly checks for zero-valued divisors and traps with exception number 503 when one is detected. Use of mno-check-zero-division suppresses such checking for code generated to run on an \s-1MC88100\s0 processor. .Sp -\&\s-1GNU\s0 C assumes that the \s-1MC88110\s0 processor correctly detects all +\&\s-1GCC\s0 assumes that the \s-1MC88110\s0 processor correctly detects all instances of integer division by zero. When \fB\-m88110\fR is specified, both \fB\-mcheck-zero-division\fR and \&\fB\-mno-check-zero-division\fR are ignored, and no explicit checks for @@ -5185,7 +5187,7 @@ On the \s-1MC88100\s0 processor the signed integer division instruction div) traps to the operating system on a negative operand. The operating system transparently completes the operation, but at a large cost in execution time. By default, when compiling code -that might be run on an \s-1MC88100\s0 processor, \s-1GNU\s0 C emulates signed +that might be run on an \s-1MC88100\s0 processor, \s-1GCC\s0 emulates signed integer division using the unsigned integer division instruction divu), thereby avoiding the large penalty of a trap to the operating system. Such emulation has its own, smaller, execution @@ -5400,7 +5402,7 @@ these options, specify \fB\-mminimal-toc\fR instead. This option causes \&\s-1GCC\s0 to make only one \s-1TOC\s0 entry for every file. When you specify this option, \s-1GCC\s0 will produce code that is slower and larger but which uses extremely little \s-1TOC\s0 space. You may wish to use this option -only on files that contain less frequently executed code. +only on files that contain less frequently executed code. .Ip "\fB\-maix64\fR" 4 .IX Item "-maix64" .PD 0 @@ -7556,10 +7558,10 @@ it. .Ip "\fB\-fexceptions\fR" 4 .IX Item "-fexceptions" Enable exception handling. Generates extra code needed to propagate -exceptions. For some targets, this implies \s-1GNU\s0 \s-1CC\s0 will generate frame +exceptions. For some targets, this implies \s-1GCC\s0 will generate frame unwind information for all functions, which can produce significant data size overhead, although it does not affect execution. If you do not -specify this option, \s-1GNU\s0 \s-1CC\s0 will enable it by default for languages like +specify this option, \s-1GCC\s0 will enable it by default for languages like \&\*(C+ which normally require exception handling, and disable it for languages like C that do not normally require it. However, you may need to enable this option when compiling C code that needs to interoperate @@ -7765,13 +7767,13 @@ stubs for every function you call, you might have to specify \&\fB\-fcheck-memory-usage\fR without \fB\-fprefix-function-name\fR. .Sp If you specify this option, you can not use the \f(CW\*(C`asm\*(C'\fR or -\&\f(CW\*(C`_\|_asm_\|_\*(C'\fR keywords in functions with memory checking enabled. \s-1GNU\s0 -\&\s-1CC\s0 cannot understand what the \f(CW\*(C`asm\*(C'\fR statement may do, and therefore +\&\f(CW\*(C`_\|_asm_\|_\*(C'\fR keywords in functions with memory checking enabled. \s-1GCC\s0 +cannot understand what the \f(CW\*(C`asm\*(C'\fR statement may do, and therefore cannot generate the appropriate code, so it will reject it. However, if -you specify the function attribute \f(CW\*(C`no_check_memory_usage\*(C'\fR, \s-1GNU\s0 \s-1CC\s0 will disable memory checking within a +you specify the function attribute \f(CW\*(C`no_check_memory_usage\*(C'\fR, \s-1GCC\s0 will disable memory checking within a function; you may use \f(CW\*(C`asm\*(C'\fR statements inside such functions. You may have an inline expansion of a non-checked function within a checked -function; in that case \s-1GNU\s0 \s-1CC\s0 will not generate checks for the inlined +function; in that case \s-1GCC\s0 will not generate checks for the inlined function's memory accesses. .Sp If you move your \f(CW\*(C`asm\*(C'\fR statements to non-checked inline functions @@ -7957,7 +7959,7 @@ names of the subprograms executed by the compiler. No slash is added when this prefix is combined with the name of a subprogram, but you can specify a prefix that ends with a slash if you wish. .Sp -If \fB\s-1GCC_EXEC_PREFIX\s0\fR is not set, \s-1GNU\s0 \s-1CC\s0 will attempt to figure out +If \fB\s-1GCC_EXEC_PREFIX\s0\fR is not set, \s-1GCC\s0 will attempt to figure out an appropriate prefix to use based on the pathname it was invoked with. .Sp If \s-1GCC\s0 cannot find the subprogram using the specified prefix, it |