diff options
Diffstat (limited to 'contrib/gcc/doc')
| -rw-r--r-- | contrib/gcc/doc/cpp.1 | 817 | ||||
| -rw-r--r-- | contrib/gcc/doc/gcc.1 | 9464 | ||||
| -rw-r--r-- | contrib/gcc/doc/gcov.1 | 453 | ||||
| -rw-r--r-- | contrib/gcc/doc/install-old.texi | 725 | ||||
| -rw-r--r-- | contrib/gcc/doc/install.texi | 3928 | ||||
| -rwxr-xr-x | contrib/gcc/doc/install.texi2html | 31 | ||||
| -rw-r--r-- | contrib/gcc/doc/vms.texi | 331 |
7 files changed, 0 insertions, 15749 deletions
diff --git a/contrib/gcc/doc/cpp.1 b/contrib/gcc/doc/cpp.1 deleted file mode 100644 index 8b7412325911..000000000000 --- a/contrib/gcc/doc/cpp.1 +++ /dev/null @@ -1,817 +0,0 @@ -.\" Automatically generated by Pod::Man version 1.15 -.\" Wed Feb 5 03:13:55 2003 -.\" -.\" Standard preamble: -.\" ====================================================================== -.de Sh \" Subsection heading -.br -.if t .Sp -.ne 5 -.PP -\fB\\$1\fR -.PP -.. -.de Sp \" Vertical space (when we can't use .PP) -.if t .sp .5v -.if n .sp -.. -.de Ip \" List item -.br -.ie \\n(.$>=3 .ne \\$3 -.el .ne 3 -.IP "\\$1" \\$2 -.. -.de Vb \" Begin verbatim text -.ft CW -.nf -.ne \\$1 -.. -.de Ve \" End verbatim text -.ft R - -.fi -.. -.\" Set up some character translations and predefined strings. \*(-- will -.\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left -.\" double quote, and \*(R" will give a right double quote. | will give a -.\" 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<> -.tr \(*W-|\(bv\*(Tr -.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p' -.ie n \{\ -. ds -- \(*W- -. ds PI pi -. if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch -. if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch -. ds L" "" -. ds R" "" -. ds C` "" -. ds C' "" -'br\} -.el\{\ -. ds -- \|\(em\| -. ds PI \(*p -. ds L" `` -. ds R" '' -'br\} -.\" -.\" 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 \nF \{\ -. de IX -. tm Index:\\$1\t\\n%\t"\\$2" -.. -. nr % 0 -. rr F -.\} -.\" -.\" For nroff, turn off justification. Always turn off hyphenation; it -.\" makes way too many mistakes in technical documents. -.hy 0 -.if n .na -.\" -.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). -.\" Fear. Run. Save yourself. No user-serviceable parts. -.bd B 3 -. \" fudge factors for nroff and troff -.if n \{\ -. ds #H 0 -. ds #V .8m -. ds #F .3m -. ds #[ \f1 -. ds #] \fP -.\} -.if t \{\ -. ds #H ((1u-(\\\\n(.fu%2u))*.13m) -. ds #V .6m -. ds #F 0 -. ds #[ \& -. ds #] \& -.\} -. \" simple accents for nroff and troff -.if n \{\ -. ds ' \& -. ds ` \& -. ds ^ \& -. ds , \& -. ds ~ ~ -. ds / -.\} -.if t \{\ -. ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u" -. ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u' -. ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u' -. ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u' -. ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u' -. ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u' -.\} -. \" troff and (daisy-wheel) nroff accents -.ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V' -.ds 8 \h'\*(#H'\(*b\h'-\*(#H' -.ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#] -.ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H' -.ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u' -.ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#] -.ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#] -.ds ae a\h'-(\w'a'u*4/10)'e -.ds Ae A\h'-(\w'A'u*4/10)'E -. \" corrections for vroff -.if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u' -.if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u' -. \" for low resolution devices (crt and lpr) -.if \n(.H>23 .if \n(.V>19 \ -\{\ -. ds : e -. ds 8 ss -. ds o a -. ds d- d\h'-1'\(ga -. ds D- D\h'-1'\(hy -. ds th \o'bp' -. ds Th \o'LP' -. ds ae ae -. ds Ae AE -.\} -.rm #[ #] #H #V #F C -.\" ====================================================================== -.\" -.IX Title "CPP 1" -.TH CPP 1 "gcc-3.2.2" "2003-02-05" "GNU" -.UC -.SH "NAME" -cpp \- The C Preprocessor -.SH "SYNOPSIS" -.IX Header "SYNOPSIS" -cpp [\fB\-D\fR\fImacro\fR[=\fIdefn\fR]...] [\fB\-U\fR\fImacro\fR] - [\fB\-I\fR\fIdir\fR...] [\fB\-W\fR\fIwarn\fR...] - [\fB\-M\fR|\fB\-MM\fR] [\fB\-MG\fR] [\fB\-MF\fR \fIfilename\fR] - [\fB\-MP\fR] [\fB\-MQ\fR \fItarget\fR...] [\fB\-MT\fR \fItarget\fR...] - [\fB\-x\fR \fIlanguage\fR] [\fB\-std=\fR\fIstandard\fR] - \fIinfile\fR \fIoutfile\fR -.PP -Only the most useful options are listed here; see below for the remainder. -.SH "DESCRIPTION" -.IX Header "DESCRIPTION" -The C preprocessor, often known as \fIcpp\fR, is a \fImacro processor\fR -that is used automatically by the C compiler to transform your program -before compilation. It is called a macro processor because it allows -you to define \fImacros\fR, which are brief abbreviations for longer -constructs. -.PP -The C preprocessor is intended to be used only with C, \*(C+, and -Objective-C source code. In the past, it has been abused as a general -text processor. It will choke on input which does not obey C's lexical -rules. For example, apostrophes will be interpreted as the beginning of -character constants, and cause errors. Also, you cannot rely on it -preserving characteristics of the input which are not significant to -C-family languages. If a Makefile is preprocessed, all the hard tabs -will be removed, and the Makefile will not work. -.PP -Having said that, you can often get away with using cpp on things which -are not C. Other Algol-ish programming languages are often safe -(Pascal, Ada, etc.) So is assembly, with caution. \fB\-traditional\fR -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. -.PP -Wherever possible, you should use a preprocessor geared to the language -you are writing in. Modern versions of the \s-1GNU\s0 assembler have macro -facilities. Most high level programming languages have their own -conditional compilation and inclusion mechanism. If all else fails, -try a true general text processor, such as \s-1GNU\s0 M4. -.PP -C preprocessors vary in some details. This manual discusses the \s-1GNU\s0 C -preprocessor, which provides a small superset of the features of \s-1ISO\s0 -Standard C. In its default mode, the \s-1GNU\s0 C preprocessor does not do a -few things required by the standard. These are features which are -rarely, if ever, used, and may cause surprising changes to the meaning -of a program which does not expect them. To get strict \s-1ISO\s0 Standard C, -you should use the \fB\-std=c89\fR or \fB\-std=c99\fR options, depending -on which version of the standard you want. To get all the mandatory -diagnostics, you must also use \fB\-pedantic\fR. -.SH "OPTIONS" -.IX Header "OPTIONS" -The C preprocessor expects two file names as arguments, \fIinfile\fR and -\&\fIoutfile\fR. The preprocessor reads \fIinfile\fR together with any -other files it specifies with \fB#include\fR. All the output generated -by the combined input files is written in \fIoutfile\fR. -.PP -Either \fIinfile\fR or \fIoutfile\fR may be \fB-\fR, which as -\&\fIinfile\fR means to read from standard input and as \fIoutfile\fR -means to write to standard output. Also, if either file is omitted, it -means the same as if \fB-\fR had been specified for that file. -.PP -Unless otherwise noted, or the option ends in \fB=\fR, all options -which take an argument may have that argument appear either immediately -after the option, or with a space between option and argument: -\&\fB\-Ifoo\fR and \fB\-I foo\fR have the same effect. -.PP -Many options have multi-letter names; therefore multiple single-letter -options may \fInot\fR be grouped: \fB\-dM\fR is very different from -\&\fB\-d\ \-M\fR. -.Ip "\fB\-D\fR \fIname\fR" 4 -.IX Item "-D name" -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 -.IX Item "-D name=definition" -Predefine \fIname\fR as a macro, with definition \fIdefinition\fR. -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. -.Sp -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 will need -to quote the option. With \fBsh\fR and \fBcsh\fR, -\&\fB\-D'\fR\fIname\fR\fB(\fR\fIargs...\fR\fB)=\fR\fIdefinition\fR\fB'\fR works. -.Sp -\&\fB\-D\fR and \fB\-U\fR options are processed in the order they -are given on the command line. All \fB\-imacros\fR \fIfile\fR and -\&\fB\-include\fR \fIfile\fR options are processed after all -\&\fB\-D\fR and \fB\-U\fR options. -.Ip "\fB\-U\fR \fIname\fR" 4 -.IX Item "-U name" -Cancel any previous definition of \fIname\fR, either built in or -provided with a \fB\-D\fR option. -.Ip "\fB\-undef\fR" 4 -.IX Item "-undef" -Do not predefine any system-specific macros. The common predefined -macros remain defined. -.Ip "\fB\-I\fR \fIdir\fR" 4 -.IX Item "-I dir" -Add the directory \fIdir\fR to the list of directories to be searched -for header files. -.Sp -Directories named by \fB\-I\fR are searched before the standard -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 -.IX Item "-o file" -Write output to \fIfile\fR. This is the same as specifying \fIfile\fR -as the second non-option argument to \fBcpp\fR. \fBgcc\fR has a -different interpretation of a second non-option argument, so you must -use \fB\-o\fR to specify the output file. -.Ip "\fB\-Wall\fR" 4 -.IX Item "-Wall" -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 -.IX Item "-Wcomment" -.PD 0 -.Ip "\fB\-Wcomments\fR" 4 -.IX Item "-Wcomments" -.PD -Warn whenever a comment-start sequence \fB/*\fR appears in a \fB/*\fR -comment, or whenever a backslash-newline appears in a \fB//\fR comment. -(Both forms have the same effect.) -.Ip "\fB\-Wtrigraphs\fR" 4 -.IX Item "-Wtrigraphs" -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 -.IX Item "-Wtraditional" -Warn about certain constructs that behave differently in traditional and -\&\s-1ISO\s0 C. Also warn about \s-1ISO\s0 C constructs that have no traditional C -equivalent, and problematic constructs which should be avoided. -.Ip "\fB\-Wimport\fR" 4 -.IX Item "-Wimport" -Warn the first time \fB#import\fR is used. -.Ip "\fB\-Wundef\fR" 4 -.IX Item "-Wundef" -Warn whenever an identifier which is not a macro is encountered in an -\&\fB#if\fR directive, outside of \fBdefined\fR. Such identifiers are -replaced with zero. -.Ip "\fB\-Werror\fR" 4 -.IX Item "-Werror" -Make all warnings into hard errors. Source code which triggers warnings -will be rejected. -.Ip "\fB\-Wsystem-headers\fR" 4 -.IX Item "-Wsystem-headers" -Issue warnings for code in system headers. These are normally unhelpful -in finding bugs in your own code, therefore suppressed. If you are -responsible for the system library, you may want to see them. -.Ip "\fB\-w\fR" 4 -.IX Item "-w" -Suppress all warnings, including those which \s-1GNU\s0 \s-1CPP\s0 issues by default. -.Ip "\fB\-pedantic\fR" 4 -.IX Item "-pedantic" -Issue all the mandatory diagnostics listed in the C standard. Some of -them are left out by default, since they trigger frequently on harmless -code. -.Ip "\fB\-pedantic-errors\fR" 4 -.IX Item "-pedantic-errors" -Issue all the mandatory diagnostics, and make all mandatory diagnostics -into errors. This includes mandatory diagnostics that \s-1GCC\s0 issues -without \fB\-pedantic\fR but treats as warnings. -.Ip "\fB\-M\fR" 4 -.IX Item "-M" -Instead of outputting the result of preprocessing, output a rule -suitable for \fBmake\fR describing the dependencies of the main -source file. The preprocessor outputs one \fBmake\fR rule containing -the object file name for that source file, a colon, and the names of all -the included files, including those coming from \fB\-include\fR or -\&\fB\-imacros\fR command line options. -.Sp -Unless specified explicitly (with \fB\-MT\fR or \fB\-MQ\fR), the -object file name consists of the basename of the source file with any -suffix replaced with object file suffix. If there are many included -files then the rule is split into several lines using \fB\e\fR\-newline. -The rule has no commands. -.Sp -This option does not suppress the preprocessor's debug output, such as -\&\fB\-dM\fR. To avoid mixing such debug output with the dependency -rules you should explicitly specify the dependency output file with -\&\fB\-MF\fR, or use an environment variable like -\&\fB\s-1DEPENDENCIES_OUTPUT\s0\fR. Debug output -will still be sent to the regular output stream as normal. -.Sp -Passing \fB\-M\fR to the driver implies \fB\-E\fR. -.Ip "\fB\-MM\fR" 4 -.IX Item "-MM" -Like \fB\-M\fR 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. -.Sp -This implies that the choice of angle brackets or double quotes in an -\&\fB#include\fR directive does not in itself determine whether that -header will appear in \fB\-MM\fR dependency output. This is a -slight change in semantics from \s-1GCC\s0 versions 3.0 and earlier. -.Ip "\fB\-MF\fR \fIfile\fR" 4 -.IX Item "-MF file" -@anchor{\-MF} -When used with \fB\-M\fR or \fB\-MM\fR, specifies a -file to write the dependencies to. If no \fB\-MF\fR switch is given -the preprocessor sends the rules to the same place it would have sent -preprocessed output. -.Sp -When used with the driver options \fB\-MD\fR or \fB\-MMD\fR, -\&\fB\-MF\fR overrides the default dependency output file. -.Ip "\fB\-MG\fR" 4 -.IX Item "-MG" -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. -.Sp -This feature is used in automatic updating of makefiles. -.Ip "\fB\-MP\fR" 4 -.IX Item "-MP" -This option instructs \s-1CPP\s0 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 \fBmake\fR gives if you remove header -files without updating the \fIMakefile\fR to match. -.Sp -This is typical output: -.Sp -.Vb 1 -\& test.o: test.c test.h -.Ve -.Vb 1 -\& test.h: -.Ve -.Ip "\fB\-MT\fR \fItarget\fR" 4 -.IX Item "-MT target" -Change the target of the rule emitted by dependency generation. By -default \s-1CPP\s0 takes the name of the main input file, including any path, -deletes any file suffix such as \fB.c\fR, and appends the platform's -usual object suffix. The result is the target. -.Sp -An \fB\-MT\fR option will set the target to be exactly the string you -specify. If you want multiple targets, you can specify them as a single -argument to \fB\-MT\fR, or use multiple \fB\-MT\fR options. -.Sp -For example, \fB\-MT\ '$(objpfx)foo.o'\fR might give -.Sp -.Vb 1 -\& $(objpfx)foo.o: foo.c -.Ve -.Ip "\fB\-MQ\fR \fItarget\fR" 4 -.IX Item "-MQ target" -Same as \fB\-MT\fR, but it quotes any characters which are special to -Make. \fB\-MQ\ '$(objpfx)foo.o'\fR gives -.Sp -.Vb 1 -\& $$(objpfx)foo.o: foo.c -.Ve -The default target is automatically quoted, as if it were given with -\&\fB\-MQ\fR. -.Ip "\fB\-MD\fR" 4 -.IX Item "-MD" -\&\fB\-MD\fR is equivalent to \fB\-M \-MF\fR \fIfile\fR, except that -\&\fB\-E\fR is not implied. The driver determines \fIfile\fR based on -whether an \fB\-o\fR option is given. If it is, the driver uses its -argument but with a suffix of \fI.d\fR, otherwise it take the -basename of the input file and applies a \fI.d\fR suffix. -.Sp -If \fB\-MD\fR is used in conjunction with \fB\-E\fR, any -\&\fB\-o\fR switch is understood to specify the dependency output file -(but \f(CW@pxref\fR{\-MF}), but if used without \fB\-E\fR, each \fB\-o\fR -is understood to specify a target object file. -.Sp -Since \fB\-E\fR is not implied, \fB\-MD\fR can be used to generate -a dependency output file as a side-effect of the compilation process. -.Ip "\fB\-MMD\fR" 4 -.IX Item "-MMD" -Like \fB\-MD\fR except mention only user header files, not system -\&\-header files. -.Ip "\fB\-x c\fR" 4 -.IX Item "-x c" -.PD 0 -.Ip "\fB\-x c++\fR" 4 -.IX Item "-x c++" -.Ip "\fB\-x objective-c\fR" 4 -.IX Item "-x objective-c" -.Ip "\fB\-x assembler-with-cpp\fR" 4 -.IX Item "-x assembler-with-cpp" -.PD -Specify the source language: C, \*(C+, Objective-C, or assembly. This has -nothing to do with standards conformance or extensions; it merely -selects which base syntax to expect. If you give none of these options, -cpp will deduce the language from the extension of the source file: -\&\fB.c\fR, \fB.cc\fR, \fB.m\fR, or \fB.S\fR. Some other common -extensions for \*(C+ and assembly are also recognized. If cpp does not -recognize the extension, it will treat the file as C; this is the most -generic mode. -.Sp -\&\fBNote:\fR Previous versions of cpp accepted a \fB\-lang\fR option -which selected both the language and the standards conformance level. -This option has been removed, because it conflicts with the \fB\-l\fR -option. -.Ip "\fB\-std=\fR\fIstandard\fR" 4 -.IX Item "-std=standard" -.PD 0 -.Ip "\fB\-ansi\fR" 4 -.IX Item "-ansi" -.PD -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. -.Sp -\&\fIstandard\fR -may be one of: -.RS 4 -.if n .Ip "\f(CW""""iso9899:1990""""\fR" 4 -.el .Ip "\f(CWiso9899:1990\fR" 4 -.IX Item "iso9899:1990" -.PD 0 -.if n .Ip "\f(CW""""c89""""\fR" 4 -.el .Ip "\f(CWc89\fR" 4 -.IX Item "c89" -.PD -The \s-1ISO\s0 C standard from 1990. \fBc89\fR is the customary shorthand for -this version of the standard. -.Sp -The \fB\-ansi\fR option is equivalent to \fB\-std=c89\fR. -.if n .Ip "\f(CW""""iso9899:199409""""\fR" 4 -.el .Ip "\f(CWiso9899:199409\fR" 4 -.IX Item "iso9899:199409" -The 1990 C standard, as amended in 1994. -.if n .Ip "\f(CW""""iso9899:1999""""\fR" 4 -.el .Ip "\f(CWiso9899:1999\fR" 4 -.IX Item "iso9899:1999" -.PD 0 -.if n .Ip "\f(CW""""c99""""\fR" 4 -.el .Ip "\f(CWc99\fR" 4 -.IX Item "c99" -.if n .Ip "\f(CW""""iso9899:199x""""\fR" 4 -.el .Ip "\f(CWiso9899:199x\fR" 4 -.IX Item "iso9899:199x" -.if n .Ip "\f(CW""""c9x""""\fR" 4 -.el .Ip "\f(CWc9x\fR" 4 -.IX Item "c9x" -.PD -The revised \s-1ISO\s0 C standard, published in December 1999. Before -publication, this was known as C9X. -.if n .Ip "\f(CW""""gnu89""""\fR" 4 -.el .Ip "\f(CWgnu89\fR" 4 -.IX Item "gnu89" -The 1990 C standard plus \s-1GNU\s0 extensions. This is the default. -.if n .Ip "\f(CW""""gnu99""""\fR" 4 -.el .Ip "\f(CWgnu99\fR" 4 -.IX Item "gnu99" -.PD 0 -.if n .Ip "\f(CW""""gnu9x""""\fR" 4 -.el .Ip "\f(CWgnu9x\fR" 4 -.IX Item "gnu9x" -.PD -The 1999 C standard plus \s-1GNU\s0 extensions. -.RE -.RS 4 -.RE -.Ip "\fB\-I-\fR" 4 -.IX Item "-I-" -Split the include path. Any directories specified with \fB\-I\fR -options before \fB\-I-\fR are searched only for headers requested with -\&\f(CW\*(C`#include\ "\f(CIfile\f(CW"\*(C'\fR; they are not searched for -\&\f(CW\*(C`#include\ <\f(CIfile\f(CW>\*(C'\fR. If additional directories are -specified with \fB\-I\fR options after the \fB\-I-\fR, those -directories are searched for all \fB#include\fR directives. -.Sp -In addition, \fB\-I-\fR inhibits the use of the directory of the current -file directory as the first search directory for \f(CW\*(C`#include\ "\f(CIfile\f(CW"\*(C'\fR. -.Ip "\fB\-nostdinc\fR" 4 -.IX Item "-nostdinc" -Do not search the standard system directories for header files. -Only the directories you have specified with \fB\-I\fR options -(and the directory of the current file, if appropriate) are searched. -.Ip "\fB\-nostdinc++\fR" 4 -.IX Item "-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.) -.Ip "\fB\-include\fR \fIfile\fR" 4 -.IX Item "-include file" -Process \fIfile\fR as if \f(CW\*(C`#include "file"\*(C'\fR appeared as the first -line of the primary source file. However, the first directory searched -for \fIfile\fR is the preprocessor's working directory \fIinstead of\fR -the directory containing the main source file. If not found there, it -is searched for in the remainder of the \f(CW\*(C`#include "..."\*(C'\fR search -chain as normal. -.Sp -If multiple \fB\-include\fR options are given, the files are included -in the order they appear on the command line. -.Ip "\fB\-imacros\fR \fIfile\fR" 4 -.IX Item "-imacros file" -Exactly like \fB\-include\fR, except that any output produced by -scanning \fIfile\fR is thrown away. Macros it defines remain defined. -This allows you to acquire all the macros from a header without also -processing its declarations. -.Sp -All files specified by \fB\-imacros\fR are processed before all files -specified by \fB\-include\fR. -.Ip "\fB\-idirafter\fR \fIdir\fR" 4 -.IX Item "-idirafter dir" -Search \fIdir\fR for header files, but do it \fIafter\fR all -directories specified with \fB\-I\fR and the standard system directories -have been exhausted. \fIdir\fR is treated as a system include directory. -.Ip "\fB\-iprefix\fR \fIprefix\fR" 4 -.IX Item "-iprefix prefix" -Specify \fIprefix\fR as the prefix for subsequent \fB\-iwithprefix\fR -options. If the prefix represents a directory, you should include the -final \fB/\fR. -.Ip "\fB\-iwithprefix\fR \fIdir\fR" 4 -.IX Item "-iwithprefix dir" -.PD 0 -.Ip "\fB\-iwithprefixbefore\fR \fIdir\fR" 4 -.IX Item "-iwithprefixbefore dir" -.PD -Append \fIdir\fR to the prefix specified previously with -\&\fB\-iprefix\fR, and add the resulting directory to the include search -path. \fB\-iwithprefixbefore\fR puts it in the same place \fB\-I\fR -would; \fB\-iwithprefix\fR puts it where \fB\-idirafter\fR would. -.Sp -Use of these options is discouraged. -.Ip "\fB\-isystem\fR \fIdir\fR" 4 -.IX Item "-isystem dir" -Search \fIdir\fR for header files, after all directories specified by -\&\fB\-I\fR but before the standard system directories. Mark it -as a system directory, so that it gets the same special treatment as -is applied to the standard system directories. -.Ip "\fB\-fpreprocessed\fR" 4 -.IX Item "-fpreprocessed" -Indicate to the preprocessor that the input file has already been -preprocessed. This suppresses things like macro expansion, trigraph -conversion, escaped newline splicing, and processing of most directives. -The preprocessor still recognizes and removes comments, so that you can -pass a file preprocessed with \fB\-C\fR to the compiler without -problems. In this mode the integrated preprocessor is little more than -a tokenizer for the front ends. -.Sp -\&\fB\-fpreprocessed\fR is implicit if the input file has one of the -extensions \fB.i\fR, \fB.ii\fR or \fB.mi\fR. These are the -extensions that \s-1GCC\s0 uses for preprocessed files created by -\&\fB\-save-temps\fR. -.Ip "\fB\-ftabstop=\fR\fIwidth\fR" 4 -.IX Item "-ftabstop=width" -Set the distance between tab stops. This helps the preprocessor report -correct column numbers in warnings or errors, even if tabs appear on the -line. If the value is less than 1 or greater than 100, the option is -ignored. The default is 8. -.Ip "\fB\-fno-show-column\fR" 4 -.IX Item "-fno-show-column" -Do not print column numbers in diagnostics. This may be necessary if -diagnostics are being scanned by a program that does not understand the -column numbers, such as \fBdejagnu\fR. -.Ip "\fB\-A\fR \fIpredicate\fR\fB=\fR\fIanswer\fR" 4 -.IX Item "-A predicate=answer" -Make an assertion with the predicate \fIpredicate\fR and answer -\&\fIanswer\fR. This form is preferred to the older form \fB\-A\fR -\&\fIpredicate\fR\fB(\fR\fIanswer\fR\fB)\fR, which is still supported, because -it does not use shell special characters. -.Ip "\fB\-A -\fR\fIpredicate\fR\fB=\fR\fIanswer\fR" 4 -.IX Item "-A -predicate=answer" -Cancel an assertion with the predicate \fIpredicate\fR and answer -\&\fIanswer\fR. -.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 -.IX Item "-dCHARS" -\&\fI\s-1CHARS\s0\fR is a sequence of one or more of the following characters, -and must not be preceded by a space. Other characters are interpreted -by the compiler proper, or reserved for future versions of \s-1GCC\s0, and so -are silently ignored. If you specify characters whose behavior -conflicts, the result is undefined. -.RS 4 -.Ip "\fBM\fR" 4 -.IX Item "M" -Instead of the normal output, generate a list of \fB#define\fR -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 \fIfoo.h\fR, the command -.Sp -.Vb 1 -\& touch foo.h; cpp -dM foo.h -.Ve -will show all the predefined macros. -.Ip "\fBD\fR" 4 -.IX Item "D" -Like \fBM\fR except in two respects: it does \fInot\fR include the -predefined macros, and it outputs \fIboth\fR the \fB#define\fR -directives and the result of preprocessing. Both kinds of output go to -the standard output file. -.Ip "\fBN\fR" 4 -.IX Item "N" -Like \fBD\fR, but emit only the macro names, not their expansions. -.Ip "\fBI\fR" 4 -.IX Item "I" -Output \fB#include\fR directives in addition to the result of -preprocessing. -.RE -.RS 4 -.RE -.Ip "\fB\-P\fR" 4 -.IX Item "-P" -Inhibit generation of linemarkers in the output from the preprocessor. -This might be useful when running the preprocessor on something that is -not C code, and will be sent to a program which might be confused by the -linemarkers. -.Ip "\fB\-C\fR" 4 -.IX Item "-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. -.Sp -You should be prepared for side effects when using \fB\-C\fR; 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 \fB#\fR. -.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 -.IX Item "-trigraphs" -Process trigraph sequences. -.Ip "\fB\-remap\fR" 4 -.IX Item "-remap" -Enable special code to work around file systems which only permit very -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" -.PD 0 -.Ip "\fB\*(--help\fR" 4 -.IX Item "help" -.Ip "\fB\*(--target-help\fR" 4 -.IX Item "target-help" -.PD -Print text describing all the command line options instead of -preprocessing anything. -.Ip "\fB\-v\fR" 4 -.IX Item "-v" -Verbose mode. Print out \s-1GNU\s0 \s-1CPP\s0's version number at the beginning of -execution, and report the final form of the include path. -.Ip "\fB\-H\fR" 4 -.IX Item "-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 -\&\fB#include\fR stack it is. -.Ip "\fB\-version\fR" 4 -.IX Item "-version" -.PD 0 -.Ip "\fB\*(--version\fR" 4 -.IX Item "version" -.PD -Print out \s-1GNU\s0 \s-1CPP\s0's version number. With one dash, proceed to -preprocess as normal. With two dashes, exit immediately. -.SH "ENVIRONMENT" -.IX Header "ENVIRONMENT" -This section describes the environment variables that affect how \s-1CPP\s0 -operates. You can use them to specify directories or prefixes to use -when searching for include files, or to control dependency output. -.PP -Note that you can also specify places to search using options such as -\&\fB\-I\fR, and control dependency output with options like -\&\fB\-M\fR. These take precedence over -environment variables, which in turn take precedence over the -configuration of \s-1GCC\s0. -.Ip "\fB\s-1CPATH\s0\fR" 4 -.IX Item "CPATH" -.PD 0 -.Ip "\fBC_INCLUDE_PATH\fR" 4 -.IX Item "C_INCLUDE_PATH" -.Ip "\fB\s-1CPLUS_INCLUDE_PATH\s0\fR" 4 -.IX Item "CPLUS_INCLUDE_PATH" -.Ip "\fB\s-1OBJC_INCLUDE_PATH\s0\fR" 4 -.IX Item "OBJC_INCLUDE_PATH" -.PD -Each variable's value is a list of directories separated by a special -character, much like \fB\s-1PATH\s0\fR, in which to look for header files. -The special character, \f(CW\*(C`PATH_SEPARATOR\*(C'\fR, is target-dependent and -determined at \s-1GCC\s0 build time. For Windows-based targets it is a -semicolon, and for almost all other targets it is a colon. -.Sp -\&\fB\s-1CPATH\s0\fR specifies a list of directories to be searched as if -specified with \fB\-I\fR, but after any paths given with \fB\-I\fR -options on the command line. The environment variable is used -regardless of which language is being preprocessed. -.Sp -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 \fB\-isystem\fR, but after any -paths given with \fB\-isystem\fR options on the command line. -.Sp -See also \f(CW@ref\fR{Search Path}. -.Ip "\fB\s-1DEPENDENCIES_OUTPUT\s0\fR" 4 -.IX Item "DEPENDENCIES_OUTPUT" -@anchor{\s-1DEPENDENCIES_OUTPUT\s0} -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. -.Sp -The value of \fB\s-1DEPENDENCIES_OUTPUT\s0\fR 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 -\&\fIfile\fR\fB \fR\fItarget\fR, in which case the rules are written to -file \fIfile\fR using \fItarget\fR as the target name. -.Sp -In other words, this environment variable is equivalent to combining -the options \fB\-MM\fR and \fB\-MF\fR, -with an optional \fB\-MT\fR switch too. -.Ip "\fB\s-1SUNPRO_DEPENDENCIES\s0\fR" 4 -.IX Item "SUNPRO_DEPENDENCIES" -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. -.SH "SEE ALSO" -.IX Header "SEE ALSO" -\&\fIgpl\fR\|(7), \fIgfdl\fR\|(7), \fIfsf-funding\fR\|(7), -\&\fIgcc\fR\|(1), \fIas\fR\|(1), \fIld\fR\|(1), and the Info entries for \fIcpp\fR, \fIgcc\fR, and -\&\fIbinutils\fR. -.SH "COPYRIGHT" -.IX Header "COPYRIGHT" -Copyright (c) 1987, 1989, 1991, 1992, 1993, 1994, 1995, 1996, -1997, 1998, 1999, 2000, 2001 -Free Software Foundation, Inc. -.PP -Permission is granted to copy, distribute and/or modify this document -under the terms of the \s-1GNU\s0 Free Documentation License, Version 1.1 or -any later version published by the Free Software Foundation. A copy of -the license is included in the -man page \fIgfdl\fR\|(7). -This manual contains no Invariant Sections. The Front-Cover Texts are -(a) (see below), and the Back-Cover Texts are (b) (see below). -.PP -(a) The \s-1FSF\s0's Front-Cover Text is: -.PP -.Vb 1 -\& A GNU Manual -.Ve -(b) The \s-1FSF\s0's Back-Cover Text is: -.PP -.Vb 3 -\& 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. -.Ve diff --git a/contrib/gcc/doc/gcc.1 b/contrib/gcc/doc/gcc.1 deleted file mode 100644 index 16a2b28300fd..000000000000 --- a/contrib/gcc/doc/gcc.1 +++ /dev/null @@ -1,9464 +0,0 @@ -.\" Automatically generated by Pod::Man version 1.15 -.\" Wed Feb 5 03:13:56 2003 -.\" -.\" Standard preamble: -.\" ====================================================================== -.de Sh \" Subsection heading -.br -.if t .Sp -.ne 5 -.PP -\fB\\$1\fR -.PP -.. -.de Sp \" Vertical space (when we can't use .PP) -.if t .sp .5v -.if n .sp -.. -.de Ip \" List item -.br -.ie \\n(.$>=3 .ne \\$3 -.el .ne 3 -.IP "\\$1" \\$2 -.. -.de Vb \" Begin verbatim text -.ft CW -.nf -.ne \\$1 -.. -.de Ve \" End verbatim text -.ft R - -.fi -.. -.\" Set up some character translations and predefined strings. \*(-- will -.\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left -.\" double quote, and \*(R" will give a right double quote. | will give a -.\" 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<> -.tr \(*W-|\(bv\*(Tr -.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p' -.ie n \{\ -. ds -- \(*W- -. ds PI pi -. if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch -. if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch -. ds L" "" -. ds R" "" -. ds C` "" -. ds C' "" -'br\} -.el\{\ -. ds -- \|\(em\| -. ds PI \(*p -. ds L" `` -. ds R" '' -'br\} -.\" -.\" 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 \nF \{\ -. de IX -. tm Index:\\$1\t\\n%\t"\\$2" -.. -. nr % 0 -. rr F -.\} -.\" -.\" For nroff, turn off justification. Always turn off hyphenation; it -.\" makes way too many mistakes in technical documents. -.hy 0 -.if n .na -.\" -.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). -.\" Fear. Run. Save yourself. No user-serviceable parts. -.bd B 3 -. \" fudge factors for nroff and troff -.if n \{\ -. ds #H 0 -. ds #V .8m -. ds #F .3m -. ds #[ \f1 -. ds #] \fP -.\} -.if t \{\ -. ds #H ((1u-(\\\\n(.fu%2u))*.13m) -. ds #V .6m -. ds #F 0 -. ds #[ \& -. ds #] \& -.\} -. \" simple accents for nroff and troff -.if n \{\ -. ds ' \& -. ds ` \& -. ds ^ \& -. ds , \& -. ds ~ ~ -. ds / -.\} -.if t \{\ -. ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u" -. ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u' -. ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u' -. ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u' -. ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u' -. ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u' -.\} -. \" troff and (daisy-wheel) nroff accents -.ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V' -.ds 8 \h'\*(#H'\(*b\h'-\*(#H' -.ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#] -.ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H' -.ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u' -.ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#] -.ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#] -.ds ae a\h'-(\w'a'u*4/10)'e -.ds Ae A\h'-(\w'A'u*4/10)'E -. \" corrections for vroff -.if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u' -.if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u' -. \" for low resolution devices (crt and lpr) -.if \n(.H>23 .if \n(.V>19 \ -\{\ -. ds : e -. ds 8 ss -. ds o a -. ds d- d\h'-1'\(ga -. ds D- D\h'-1'\(hy -. ds th \o'bp' -. ds Th \o'LP' -. ds ae ae -. ds Ae AE -.\} -.rm #[ #] #H #V #F C -.\" ====================================================================== -.\" -.IX Title "GCC 1" -.TH GCC 1 "gcc-3.2.2" "2003-02-05" "GNU" -.UC -.SH "NAME" -gcc \- \s-1GNU\s0 project C and \*(C+ compiler -.SH "SYNOPSIS" -.IX Header "SYNOPSIS" -gcc [\fB\-c\fR|\fB\-S\fR|\fB\-E\fR] [\fB\-std=\fR\fIstandard\fR] - [\fB\-g\fR] [\fB\-pg\fR] [\fB\-O\fR\fIlevel\fR] - [\fB\-W\fR\fIwarn\fR...] [\fB\-pedantic\fR] - [\fB\-I\fR\fIdir\fR...] [\fB\-L\fR\fIdir\fR...] - [\fB\-D\fR\fImacro\fR[=\fIdefn\fR]...] [\fB\-U\fR\fImacro\fR] - [\fB\-f\fR\fIoption\fR...] [\fB\-m\fR\fImachine-option\fR...] - [\fB\-o\fR \fIoutfile\fR] \fIinfile\fR... -.PP -Only the most useful options are listed here; see below for the -remainder. \fBg++\fR accepts mostly the same options as \fBgcc\fR. -.SH "DESCRIPTION" -.IX Header "DESCRIPTION" -When you invoke \s-1GCC\s0, it normally does preprocessing, compilation, -assembly and linking. The ``overall options'' allow you to stop this -process at an intermediate stage. For example, the \fB\-c\fR option -says not to run the linker. Then the output consists of object files -output by the assembler. -.PP -Other options are passed on to one stage of processing. Some options -control the preprocessor and others the compiler itself. Yet other -options control the assembler and linker; most of these are not -documented here, since you rarely need to use any of them. -.PP -Most of the command line options that you can use with \s-1GCC\s0 are useful -for C programs; when an option is only useful with another language -(usually \*(C+), the explanation says so explicitly. If the description -for a particular option does not mention a source language, you can use -that option with all supported languages. -.PP -The \fBgcc\fR program accepts options and file names as operands. Many -options have multi-letter names; therefore multiple single-letter options -may \fInot\fR be grouped: \fB\-dr\fR is very different from \fB\-d\ \-r\fR. -.PP -You can mix options and other arguments. For the most part, the order -you use doesn't matter. Order does matter when you use several options -of the same kind; for example, if you specify \fB\-L\fR more than once, -the directories are searched in the order specified. -.PP -Many options have long names starting with \fB\-f\fR or with -\&\fB\-W\fR\-\-\-for example, \fB\-fforce-mem\fR, -\&\fB\-fstrength-reduce\fR, \fB\-Wformat\fR and so on. Most of -these have both positive and negative forms; the negative form of -\&\fB\-ffoo\fR would be \fB\-fno-foo\fR. This manual documents -only one of these two forms, whichever one is not the default. -.SH "OPTIONS" -.IX Header "OPTIONS" -.Sh "Option Summary" -.IX Subsection "Option Summary" -Here is a summary of all the options, grouped by type. Explanations are -in the following sections. -.Ip "\fIOverall Options\fR" 4 -.IX Item "Overall Options" -\&\fB\-c \-S \-E \-o\fR \fIfile\fR \fB\-pipe \-pass-exit-codes \-x\fR \fIlanguage\fR -\&\fB\-v \-### \-\-help \-\-target-help \-\-version\fR -.Ip "\fIC Language Options\fR" 4 -.IX Item "C Language Options" -\&\fB\-ansi \-std=\fR\fIstandard\fR \fB\-aux-info\fR \fIfilename\fR -\&\fB\-fno-asm \-fno-builtin \-fno-builtin-\fR\fIfunction\fR -\&\fB\-fhosted \-ffreestanding -\&\-trigraphs \-no-integrated-cpp \-traditional \-traditional-cpp -\&\-fallow-single-precision \-fcond-mismatch -\&\-fsigned-bitfields \-fsigned-char -\&\-funsigned-bitfields \-funsigned-char -\&\-fwritable-strings\fR -.Ip "\fI\*(C+ Language Options\fR" 4 -.IX Item " Language Options" -\&\fB\-fno-access-control \-fcheck-new \-fconserve-space -\&\-fno-const-strings \-fdollars-in-identifiers -\&\-fno-elide-constructors -\&\-fno-enforce-eh-specs \-fexternal-templates -\&\-falt-external-templates -\&\-ffor-scope \-fno-for-scope \-fno-gnu-keywords -\&\-fno-implicit-templates -\&\-fno-implicit-inline-templates -\&\-fno-implement-inlines \-fms-extensions -\&\-fno-nonansi-builtins \-fno-operator-names -\&\-fno-optional-diags \-fpermissive -\&\-frepo \-fno-rtti \-fstats \-ftemplate-depth-\fR\fIn\fR -\&\fB\-fuse-cxa-atexit \-fvtable-gc \-fno-weak \-nostdinc++ -\&\-fno-default-inline \-Wabi \-Wctor-dtor-privacy -\&\-Wnon-virtual-dtor \-Wreorder -\&\-Weffc++ \-Wno-deprecated -\&\-Wno-non-template-friend \-Wold-style-cast -\&\-Woverloaded-virtual \-Wno-pmf-conversions -\&\-Wsign-promo \-Wsynth\fR -.Ip "\fIObjective-C Language Options\fR" 4 -.IX Item "Objective-C Language Options" -\&\fB\-fconstant-string-class=\fR\fIclass-name\fR -\&\fB\-fgnu-runtime \-fnext-runtime \-gen-decls -\&\-Wno-protocol \-Wselector\fR -.Ip "\fILanguage Independent Options\fR" 4 -.IX Item "Language Independent Options" -\&\fB\-fmessage-length=\fR\fIn\fR -\&\fB\-fdiagnostics-show-location=\fR[\fBonce\fR|\fBevery-line\fR] -.Ip "\fIWarning Options\fR" 4 -.IX Item "Warning Options" -\&\fB\-fsyntax-only \-pedantic \-pedantic-errors -\&\-w \-W \-Wall \-Waggregate-return -\&\-Wcast-align \-Wcast-qual \-Wchar-subscripts \-Wcomment -\&\-Wconversion \-Wno-deprecated-declarations -\&\-Wdisabled-optimization \-Wdiv-by-zero \-Werror -\&\-Wfloat-equal \-Wformat \-Wformat=2 -\&\-Wformat-nonliteral \-Wformat-security -\&\-Wimplicit \-Wimplicit-int -\&\-Wimplicit-function-declaration -\&\-Werror-implicit-function-declaration -\&\-Wimport \-Winline -\&\-Wlarger-than-\fR\fIlen\fR \fB\-Wlong-long -\&\-Wmain \-Wmissing-braces -\&\-Wmissing-format-attribute \-Wmissing-noreturn -\&\-Wmultichar \-Wno-format-extra-args \-Wno-format-y2k -\&\-Wno-import \-Wpacked \-Wpadded -\&\-Wparentheses \-Wpointer-arith \-Wredundant-decls -\&\-Wreturn-type \-Wsequence-point \-Wshadow -\&\-Wsign-compare \-Wswitch \-Wsystem-headers -\&\-Wtrigraphs \-Wundef \-Wuninitialized -\&\-Wunknown-pragmas \-Wunreachable-code -\&\-Wunused \-Wunused-function \-Wunused-label \-Wunused-parameter -\&\-Wunused-value \-Wunused-variable \-Wwrite-strings\fR -.Ip "\fIC-only Warning Options\fR" 4 -.IX Item "C-only Warning Options" -\&\fB\-Wbad-function-cast \-Wmissing-declarations -\&\-Wmissing-prototypes \-Wnested-externs -\&\-Wstrict-prototypes \-Wtraditional\fR -.Ip "\fIDebugging Options\fR" 4 -.IX Item "Debugging Options" -\&\fB\-d\fR\fIletters\fR \fB\-dumpspecs \-dumpmachine \-dumpversion -\&\-fdump-unnumbered \-fdump-translation-unit\fR[\fB-\fR\fIn\fR] -\&\fB\-fdump-class-hierarchy\fR[\fB-\fR\fIn\fR] -\&\fB\-fdump-tree-original\fR[\fB-\fR\fIn\fR] \fB\-fdump-tree-optimized\fR[\fB-\fR\fIn\fR] -\&\fB\-fdump-tree-inlined\fR[\fB-\fR\fIn\fR] -\&\fB\-fmem-report \-fpretend-float -\&\-fprofile-arcs \-fsched-verbose=\fR\fIn\fR -\&\fB\-ftest-coverage \-ftime-report -\&\-g \-g\fR\fIlevel\fR \fB\-gcoff \-gdwarf \-gdwarf-1 \-gdwarf-1+ \-gdwarf-2 -\&\-ggdb \-gstabs \-gstabs+ \-gvms \-gxcoff \-gxcoff+ -\&\-p \-pg \-print-file-name=\fR\fIlibrary\fR \fB\-print-libgcc-file-name -\&\-print-multi-directory \-print-multi-lib -\&\-print-prog-name=\fR\fIprogram\fR \fB\-print-search-dirs \-Q -\&\-save-temps \-time\fR -.Ip "\fIOptimization Options\fR" 4 -.IX Item "Optimization Options" -\&\fB\-falign-functions=\fR\fIn\fR \fB\-falign-jumps=\fR\fIn\fR -\&\fB\-falign-labels=\fR\fIn\fR \fB\-falign-loops=\fR\fIn\fR -\&\fB\-fbounds-check -\&\-fbranch-probabilities \-fcaller-saves \-fcprop-registers -\&\-fcse-follow-jumps \-fcse-skip-blocks \-fdata-sections -\&\-fdelayed-branch \-fdelete-null-pointer-checks -\&\-fexpensive-optimizations \-ffast-math \-ffloat-store -\&\-fforce-addr \-fforce-mem \-ffunction-sections -\&\-fgcse \-fgcse-lm \-fgcse-sm -\&\-finline-functions \-finline-limit=\fR\fIn\fR \fB\-fkeep-inline-functions -\&\-fkeep-static-consts \-fmerge-constants \-fmerge-all-constants -\&\-fmove-all-movables \-fno-branch-count-reg -\&\-fno-default-inline \-fno-defer-pop -\&\-fno-function-cse \-fno-guess-branch-probability -\&\-fno-inline \-fno-math-errno \-fno-peephole \-fno-peephole2 -\&\-funsafe-math-optimizations \-fno-trapping-math -\&\-fomit-frame-pointer \-foptimize-register-move -\&\-foptimize-sibling-calls \-fprefetch-loop-arrays -\&\-freduce-all-givs \-fregmove \-frename-registers -\&\-frerun-cse-after-loop \-frerun-loop-opt -\&\-fschedule-insns \-fschedule-insns2 -\&\-fno-sched-interblock \-fno-sched-spec -\&\-fsched-spec-load \-fsched-spec-load-dangerous -\&\-fsingle-precision-constant \-fssa \-fssa-ccp \-fssa-dce -\&\-fstrength-reduce \-fstrict-aliasing \-fthread-jumps -\&\-ftrapv \-funroll-all-loops \-funroll-loops -\&\-\-param\fR \fIname\fR\fB=\fR\fIvalue\fR -\&\fB\-O \-O0 \-O1 \-O2 \-O3 \-Os\fR -.Ip "\fIPreprocessor Options\fR" 4 -.IX Item "Preprocessor Options" -\&\fB\-$ \-A\fR\fIquestion\fR\fB=\fR\fIanswer\fR \fB\-A-\fR\fIquestion\fR[\fB=\fR\fIanswer\fR] -\&\fB\-C \-dD \-dI \-dM \-dN -\&\-D\fR\fImacro\fR[\fB=\fR\fIdefn\fR] \fB\-E \-H -\&\-idirafter\fR \fIdir\fR -\&\fB\-include\fR \fIfile\fR \fB\-imacros\fR \fIfile\fR -\&\fB\-iprefix\fR \fIfile\fR \fB\-iwithprefix\fR \fIdir\fR -\&\fB\-iwithprefixbefore\fR \fIdir\fR \fB\-isystem\fR \fIdir\fR -\&\fB\-M \-MM \-MF \-MG \-MP \-MQ \-MT \-nostdinc \-P \-remap -\&\-trigraphs \-undef \-U\fR\fImacro\fR \fB\-Wp,\fR\fIoption\fR -.Ip "\fIAssembler Option\fR" 4 -.IX Item "Assembler Option" -\&\fB\-Wa,\fR\fIoption\fR -.Ip "\fILinker Options\fR" 4 -.IX Item "Linker Options" -\&\fB -\&\fR\fIobject-file-name\fR \fB\-l\fR\fIlibrary\fR -\&\fB\-nostartfiles \-nodefaultlibs \-nostdlib -\&\-s \-static \-static-libgcc \-shared \-shared-libgcc \-symbolic -\&\-Wl,\fR\fIoption\fR \fB\-Xlinker\fR \fIoption\fR -\&\fB\-u\fR \fIsymbol\fR -.Ip "\fIDirectory Options\fR" 4 -.IX Item "Directory Options" -\&\fB\-B\fR\fIprefix\fR \fB\-I\fR\fIdir\fR \fB\-I- \-L\fR\fIdir\fR \fB\-specs=\fR\fIfile\fR -.Ip "\fITarget Options\fR" 4 -.IX Item "Target Options" -\&\fB\-b\fR \fImachine\fR \fB\-V\fR \fIversion\fR -.Ip "\fIMachine Dependent Options\fR" 4 -.IX Item "Machine Dependent Options" -\&\fIM680x0 Options\fR -.Sp -\&\fB\-m68000 \-m68020 \-m68020\-40 \-m68020\-60 \-m68030 \-m68040 -\&\-m68060 \-mcpu32 \-m5200 \-m68881 \-mbitfield \-mc68000 \-mc68020 -\&\-mfpa \-mnobitfield \-mrtd \-mshort \-msoft-float \-mpcrel -\&\-malign-int \-mstrict-align\fR -.Sp -\&\fIM68hc1x Options\fR -.Sp -\&\fB\-m6811 \-m6812 \-m68hc11 \-m68hc12 -\&\-mauto-incdec \-mshort \-msoft-reg-count=\fR\fIcount\fR -.Sp -\&\fI\s-1VAX\s0 Options\fR -.Sp -\&\fB\-mg \-mgnu \-munix\fR -.Sp -\&\fI\s-1SPARC\s0 Options\fR -.Sp -\&\fB\-mcpu=\fR\fIcpu-type\fR -\&\fB\-mtune=\fR\fIcpu-type\fR -\&\fB\-mcmodel=\fR\fIcode-model\fR -\&\fB\-m32 \-m64 -\&\-mapp-regs \-mbroken-saverestore \-mcypress -\&\-mfaster-structs \-mflat -\&\-mfpu \-mhard-float \-mhard-quad-float -\&\-mimpure-text \-mlive-g0 \-mno-app-regs -\&\-mno-faster-structs \-mno-flat \-mno-fpu -\&\-mno-impure-text \-mno-stack-bias \-mno-unaligned-doubles -\&\-msoft-float \-msoft-quad-float \-msparclite \-mstack-bias -\&\-msupersparc \-munaligned-doubles \-mv8\fR -.Sp -\&\fIConvex Options\fR -.Sp -\&\fB\-mc1 \-mc2 \-mc32 \-mc34 \-mc38 -\&\-margcount \-mnoargcount -\&\-mlong32 \-mlong64 -\&\-mvolatile-cache \-mvolatile-nocache\fR -.Sp -\&\fI\s-1AMD29K\s0 Options\fR -.Sp -\&\fB\-m29000 \-m29050 \-mbw \-mnbw \-mdw \-mndw -\&\-mlarge \-mnormal \-msmall -\&\-mkernel-registers \-mno-reuse-arg-regs -\&\-mno-stack-check \-mno-storem-bug -\&\-mreuse-arg-regs \-msoft-float \-mstack-check -\&\-mstorem-bug \-muser-registers\fR -.Sp -\&\fI\s-1ARM\s0 Options\fR -.Sp -\&\fB\-mapcs-frame \-mno-apcs-frame -\&\-mapcs-26 \-mapcs-32 -\&\-mapcs-stack-check \-mno-apcs-stack-check -\&\-mapcs-float \-mno-apcs-float -\&\-mapcs-reentrant \-mno-apcs-reentrant -\&\-msched-prolog \-mno-sched-prolog -\&\-mlittle-endian \-mbig-endian \-mwords-little-endian -\&\-malignment-traps \-mno-alignment-traps -\&\-msoft-float \-mhard-float \-mfpe -\&\-mthumb-interwork \-mno-thumb-interwork -\&\-mcpu=\fR\fIname\fR \fB\-march=\fR\fIname\fR \fB\-mfpe=\fR\fIname\fR -\&\fB\-mstructure-size-boundary=\fR\fIn\fR -\&\fB\-mbsd \-mxopen \-mno-symrename -\&\-mabort-on-noreturn -\&\-mlong-calls \-mno-long-calls -\&\-msingle-pic-base \-mno-single-pic-base -\&\-mpic-register=\fR\fIreg\fR -\&\fB\-mnop-fun-dllimport -\&\-mpoke-function-name -\&\-mthumb \-marm -\&\-mtpcs-frame \-mtpcs-leaf-frame -\&\-mcaller-super-interworking \-mcallee-super-interworking\fR -.Sp -\&\fI\s-1MN10200\s0 Options\fR -.Sp -\&\fB\-mrelax\fR -.Sp -\&\fI\s-1MN10300\s0 Options\fR -.Sp -\&\fB\-mmult-bug \-mno-mult-bug -\&\-mam33 \-mno-am33 -\&\-mno-crt0 \-mrelax\fR -.Sp -\&\fIM32R/D Options\fR -.Sp -\&\fB\-m32rx \-m32r \-mcode-model=\fR\fImodel-type\fR \fB\-msdata=\fR\fIsdata-type\fR -\&\fB\-G\fR \fInum\fR -.Sp -\&\fIM88K Options\fR -.Sp -\&\fB\-m88000 \-m88100 \-m88110 \-mbig-pic -\&\-mcheck-zero-division \-mhandle-large-shift -\&\-midentify-revision \-mno-check-zero-division -\&\-mno-ocs-debug-info \-mno-ocs-frame-position -\&\-mno-optimize-arg-area \-mno-serialize-volatile -\&\-mno-underscores \-mocs-debug-info -\&\-mocs-frame-position \-moptimize-arg-area -\&\-mserialize-volatile \-mshort-data-\fR\fInum\fR \fB\-msvr3 -\&\-msvr4 \-mtrap-large-shift \-muse-div-instruction -\&\-mversion-03.00 \-mwarn-passed-structs\fR -.Sp -\&\fI\s-1RS/6000\s0 and PowerPC Options\fR -.Sp -\&\fB\-mcpu=\fR\fIcpu-type\fR -\&\fB\-mtune=\fR\fIcpu-type\fR -\&\fB\-mpower \-mno-power \-mpower2 \-mno-power2 -\&\-mpowerpc \-mpowerpc64 \-mno-powerpc -\&\-maltivec \-mno-altivec -\&\-mpowerpc-gpopt \-mno-powerpc-gpopt -\&\-mpowerpc-gfxopt \-mno-powerpc-gfxopt -\&\-mnew-mnemonics \-mold-mnemonics -\&\-mfull-toc \-mminimal-toc \-mno-fp-in-toc \-mno-sum-in-toc -\&\-m64 \-m32 \-mxl-call \-mno-xl-call \-mpe -\&\-msoft-float \-mhard-float \-mmultiple \-mno-multiple -\&\-mstring \-mno-string \-mupdate \-mno-update -\&\-mfused-madd \-mno-fused-madd \-mbit-align \-mno-bit-align -\&\-mstrict-align \-mno-strict-align \-mrelocatable -\&\-mno-relocatable \-mrelocatable-lib \-mno-relocatable-lib -\&\-mtoc \-mno-toc \-mlittle \-mlittle-endian \-mbig \-mbig-endian -\&\-mcall-aix \-mcall-sysv \-mcall-netbsd -\&\-maix-struct-return \-msvr4\-struct-return -\&\-mabi=altivec \-mabi=no-altivec -\&\-mprototype \-mno-prototype -\&\-msim \-mmvme \-mads \-myellowknife \-memb \-msdata -\&\-msdata=\fR\fIopt\fR \fB\-mvxworks \-G\fR \fInum\fR \fB\-pthread\fR -.Sp -\&\fI\s-1RT\s0 Options\fR -.Sp -\&\fB\-mcall-lib-mul \-mfp-arg-in-fpregs \-mfp-arg-in-gregs -\&\-mfull-fp-blocks \-mhc-struct-return \-min-line-mul -\&\-mminimum-fp-blocks \-mnohc-struct-return\fR -.Sp -\&\fI\s-1MIPS\s0 Options\fR -.Sp -\&\fB\-mabicalls \-march=\fR\fIcpu-type\fR \fB\-mtune=\fR\fIcpu=type\fR -\&\fB\-mcpu=\fR\fIcpu-type\fR \fB\-membedded-data \-muninit-const-in-rodata -\&\-membedded-pic \-mfp32 \-mfp64 \-mfused-madd \-mno-fused-madd -\&\-mgas \-mgp32 \-mgp64 -\&\-mgpopt \-mhalf-pic \-mhard-float \-mint64 \-mips1 -\&\-mips2 \-mips3 \-mips4 \-mlong64 \-mlong32 \-mlong-calls \-mmemcpy -\&\-mmips-as \-mmips-tfile \-mno-abicalls -\&\-mno-embedded-data \-mno-uninit-const-in-rodata -\&\-mno-embedded-pic \-mno-gpopt \-mno-long-calls -\&\-mno-memcpy \-mno-mips-tfile \-mno-rnames \-mno-stats -\&\-mrnames \-msoft-float -\&\-m4650 \-msingle-float \-mmad -\&\-mstats \-EL \-EB \-G\fR \fInum\fR \fB\-nocpp -\&\-mabi=32 \-mabi=n32 \-mabi=64 \-mabi=eabi -\&\-mfix7000 \-mno-crt0 \-mflush-func=\fR\fIfunc\fR \fB\-mno-flush-func\fR -.Sp -\&\fIi386 and x86\-64 Options\fR -.Sp -\&\fB\-mcpu=\fR\fIcpu-type\fR \fB\-march=\fR\fIcpu-type\fR \fB\-mfpmath=\fR\fIunit\fR -\&\fB\-masm=\fR\fIdialect\fR \fB\-mno-fancy-math-387 -\&\-mno-fp-ret-in-387 \-msoft-float \-msvr3\-shlib -\&\-mno-wide-multiply \-mrtd \-malign-double -\&\-mpreferred-stack-boundary=\fR\fInum\fR -\&\fB\-mmmx \-msse \-msse2 \-m3dnow -\&\-mthreads \-mno-align-stringops \-minline-all-stringops -\&\-mpush-args \-maccumulate-outgoing-args \-m128bit-long-double -\&\-m96bit-long-double \-mregparm=\fR\fInum\fR \fB\-momit-leaf-frame-pointer -\&\-mno-red-zone -\&\-mcmodel=\fR\fIcode-model\fR -\&\fB\-m32 \-m64\fR -.Sp -\&\fI\s-1HPPA\s0 Options\fR -.Sp -\&\fB\-march=\fR\fIarchitecture-type\fR -\&\fB\-mbig-switch \-mdisable-fpregs \-mdisable-indexing -\&\-mfast-indirect-calls \-mgas \-mjump-in-delay -\&\-mlong-load-store \-mno-big-switch \-mno-disable-fpregs -\&\-mno-disable-indexing \-mno-fast-indirect-calls \-mno-gas -\&\-mno-jump-in-delay \-mno-long-load-store -\&\-mno-portable-runtime \-mno-soft-float -\&\-mno-space-regs \-msoft-float \-mpa-risc-1\-0 -\&\-mpa-risc-1\-1 \-mpa-risc-2\-0 \-mportable-runtime -\&\-mschedule=\fR\fIcpu-type\fR \fB\-mspace-regs\fR -.Sp -\&\fIIntel 960 Options\fR -.Sp -\&\fB\-m\fR\fIcpu-type\fR \fB\-masm-compat \-mclean-linkage -\&\-mcode-align \-mcomplex-addr \-mleaf-procedures -\&\-mic-compat \-mic2.0\-compat \-mic3.0\-compat -\&\-mintel-asm \-mno-clean-linkage \-mno-code-align -\&\-mno-complex-addr \-mno-leaf-procedures -\&\-mno-old-align \-mno-strict-align \-mno-tail-call -\&\-mnumerics \-mold-align \-msoft-float \-mstrict-align -\&\-mtail-call\fR -.Sp -\&\fI\s-1DEC\s0 Alpha Options\fR -.Sp -\&\fB\-mno-fp-regs \-msoft-float \-malpha-as \-mgas -\&\-mieee \-mieee-with-inexact \-mieee-conformant -\&\-mfp-trap-mode=\fR\fImode\fR \fB\-mfp-rounding-mode=\fR\fImode\fR -\&\fB\-mtrap-precision=\fR\fImode\fR \fB\-mbuild-constants -\&\-mcpu=\fR\fIcpu-type\fR \fB\-mtune=\fR\fIcpu-type\fR -\&\fB\-mbwx \-mmax \-mfix \-mcix -\&\-mfloat-vax \-mfloat-ieee -\&\-mexplicit-relocs \-msmall-data \-mlarge-data -\&\-mmemory-latency=\fR\fItime\fR -.Sp -\&\fI\s-1DEC\s0 Alpha/VMS Options\fR -.Sp -\&\fB\-mvms-return-codes\fR -.Sp -\&\fIClipper Options\fR -.Sp -\&\fB\-mc300 \-mc400\fR -.Sp -\&\fIH8/300 Options\fR -.Sp -\&\fB\-mrelax \-mh \-ms \-mint32 \-malign-300\fR -.Sp -\&\fI\s-1SH\s0 Options\fR -.Sp -\&\fB\-m1 \-m2 \-m3 \-m3e -\&\-m4\-nofpu \-m4\-single-only \-m4\-single \-m4 -\&\-m5\-64media \-m5\-64media-nofpu -\&\-m5\-32media \-m5\-32media-nofpu -\&\-m5\-compact \-m5\-compact-nofpu -\&\-mb \-ml \-mdalign \-mrelax -\&\-mbigtable \-mfmovd \-mhitachi \-mnomacsave -\&\-mieee \-misize \-mpadstruct \-mspace -\&\-mprefergot \-musermode\fR -.Sp -\&\fISystem V Options\fR -.Sp -\&\fB\-Qy \-Qn \-YP,\fR\fIpaths\fR \fB\-Ym,\fR\fIdir\fR -.Sp -\&\fI\s-1ARC\s0 Options\fR -.Sp -\&\fB\-EB \-EL -\&\-mmangle-cpu \-mcpu=\fR\fIcpu\fR \fB\-mtext=\fR\fItext-section\fR -\&\fB\-mdata=\fR\fIdata-section\fR \fB\-mrodata=\fR\fIreadonly-data-section\fR -.Sp -\&\fITMS320C3x/C4x Options\fR -.Sp -\&\fB\-mcpu=\fR\fIcpu\fR \fB\-mbig \-msmall \-mregparm \-mmemparm -\&\-mfast-fix \-mmpyi \-mbk \-mti \-mdp-isr-reload -\&\-mrpts=\fR\fIcount\fR \fB\-mrptb \-mdb \-mloop-unsigned -\&\-mparallel-insns \-mparallel-mpy \-mpreserve-float\fR -.Sp -\&\fIV850 Options\fR -.Sp -\&\fB\-mlong-calls \-mno-long-calls \-mep \-mno-ep -\&\-mprolog-function \-mno-prolog-function \-mspace -\&\-mtda=\fR\fIn\fR \fB\-msda=\fR\fIn\fR \fB\-mzda=\fR\fIn\fR -\&\fB\-mv850 \-mbig-switch\fR -.Sp -\&\fI\s-1NS32K\s0 Options\fR -.Sp -\&\fB\-m32032 \-m32332 \-m32532 \-m32081 \-m32381 -\&\-mmult-add \-mnomult-add \-msoft-float \-mrtd \-mnortd -\&\-mregparam \-mnoregparam \-msb \-mnosb -\&\-mbitfield \-mnobitfield \-mhimem \-mnohimem\fR -.Sp -\&\fI\s-1AVR\s0 Options\fR -.Sp -\&\fB\-mmcu=\fR\fImcu\fR \fB\-msize \-minit-stack=\fR\fIn\fR \fB\-mno-interrupts -\&\-mcall-prologues \-mno-tablejump \-mtiny-stack\fR -.Sp -\&\fIMCore Options\fR -.Sp -\&\fB\-mhardlit \-mno-hardlit \-mdiv \-mno-div \-mrelax-immediates -\&\-mno-relax-immediates \-mwide-bitfields \-mno-wide-bitfields -\&\-m4byte-functions \-mno-4byte-functions \-mcallgraph-data -\&\-mno-callgraph-data \-mslow-bytes \-mno-slow-bytes \-mno-lsim -\&\-mlittle-endian \-mbig-endian \-m210 \-m340 \-mstack-increment\fR -.Sp -\&\fI\s-1MMIX\s0 Options\fR -.Sp -\&\fB\-mlibfuncs \-mno-libfuncs \-mepsilon \-mno-epsilon \-mabi=gnu -\&\-mabi=mmixware \-mzero-extend \-mknuthdiv \-mtoplevel-symbols -\&\-melf \-mbranch-predict \-mno-branch-predict \-mbase-addresses -\&\-mno-base-addresses\fR -.Sp -\&\fI\s-1IA-64\s0 Options\fR -.Sp -\&\fB\-mbig-endian \-mlittle-endian \-mgnu-as \-mgnu-ld \-mno-pic -\&\-mvolatile-asm-stop \-mb-step \-mregister-names \-mno-sdata -\&\-mconstant-gp \-mauto-pic \-minline-divide-min-latency -\&\-minline-divide-max-throughput \-mno-dwarf2\-asm -\&\-mfixed-range=\fR\fIregister-range\fR -.Sp -\&\fID30V Options\fR -.Sp -\&\fB\-mextmem \-mextmemory \-monchip \-mno-asm-optimize -\&\-masm-optimize \-mbranch-cost=\fR\fIn\fR \fB\-mcond-exec=\fR\fIn\fR -.Sp -\&\fIS/390 and zSeries Options\fR -.Sp -\&\fB\-mhard-float \-msoft-float \-mbackchain \-mno-backchain -\&\-msmall-exec \-mno-small-exec \-mmvcle \-mno-mvcle -\&\-m64 \-m31 \-mdebug \-mno-debug\fR -.Sp -\&\fI\s-1CRIS\s0 Options\fR -.Sp -\&\fB\-mcpu=\fR\fIcpu\fR \fB\-march=\fR\fIcpu\fR \fB\-mtune=\fR\fIcpu\fR -\&\fB\-mmax-stack-frame=\fR\fIn\fR \fB\-melinux-stacksize=\fR\fIn\fR -\&\fB\-metrax4 \-metrax100 \-mpdebug \-mcc-init \-mno-side-effects -\&\-mstack-align \-mdata-align \-mconst-align -\&\-m32\-bit \-m16\-bit \-m8\-bit \-mno-prologue-epilogue \-mno-gotplt -\&\-melf \-maout \-melinux \-mlinux \-sim \-sim2\fR -.Sp -\&\fI\s-1PDP-11\s0 Options\fR -.Sp -\&\fB\-mfpu \-msoft-float \-mac0 \-mno-ac0 \-m40 \-m45 \-m10 -\&\-mbcopy \-mbcopy-builtin \-mint32 \-mno-int16 -\&\-mint16 \-mno-int32 \-mfloat32 \-mno-float64 -\&\-mfloat64 \-mno-float32 \-mabshi \-mno-abshi -\&\-mbranch-expensive \-mbranch-cheap -\&\-msplit \-mno-split \-munix-asm \-mdec-asm\fR -.Sp -\&\fIXstormy16 Options\fR -.Sp -\&\fB\-msim\fR -.Sp -\&\fIXtensa Options\fR -.Sp -\&\fB\-mbig-endian \-mlittle-endian -\&\-mdensity \-mno-density -\&\-mmac16 \-mno-mac16 -\&\-mmul16 \-mno-mul16 -\&\-mmul32 \-mno-mul32 -\&\-mnsa \-mno-nsa -\&\-mminmax \-mno-minmax -\&\-msext \-mno-sext -\&\-mbooleans \-mno-booleans -\&\-mhard-float \-msoft-float -\&\-mfused-madd \-mno-fused-madd -\&\-mserialize-volatile \-mno-serialize-volatile -\&\-mtext-section-literals \-mno-text-section-literals -\&\-mtarget-align \-mno-target-align -\&\-mlongcalls \-mno-longcalls\fR -.Ip "\fICode Generation Options\fR" 4 -.IX Item "Code Generation Options" -\&\fB\-fcall-saved-\fR\fIreg\fR \fB\-fcall-used-\fR\fIreg\fR -\&\fB\-ffixed-\fR\fIreg\fR \fB\-fexceptions -\&\-fnon-call-exceptions \-funwind-tables -\&\-fasynchronous-unwind-tables -\&\-finhibit-size-directive \-finstrument-functions -\&\-fno-common \-fno-ident \-fno-gnu-linker -\&\-fpcc-struct-return \-fpic \-fPIC -\&\-freg-struct-return \-fshared-data \-fshort-enums -\&\-fshort-double \-fshort-wchar \-fvolatile -\&\-fvolatile-global \-fvolatile-static -\&\-fverbose-asm \-fpack-struct \-fstack-check -\&\-fstack-limit-register=\fR\fIreg\fR \fB\-fstack-limit-symbol=\fR\fIsym\fR -\&\fB\-fargument-alias \-fargument-noalias -\&\-fargument-noalias-global \-fleading-underscore\fR -.Sh "Options Controlling the Kind of Output" -.IX Subsection "Options Controlling the Kind of Output" -Compilation can involve up to four stages: preprocessing, compilation -proper, assembly and linking, always in that order. The first three -stages apply to an individual source file, and end by producing an -object file; linking combines all the object files (those newly -compiled, and those specified as input) into an executable file. -.PP -For any given input file, the file name suffix determines what kind of -compilation is done: -.Ip "\fIfile\fR\fB.c\fR" 4 -.IX Item "file.c" -C source code which must be preprocessed. -.Ip "\fIfile\fR\fB.i\fR" 4 -.IX Item "file.i" -C source code which should not be preprocessed. -.Ip "\fIfile\fR\fB.ii\fR" 4 -.IX Item "file.ii" -\&\*(C+ source code which should not be preprocessed. -.Ip "\fIfile\fR\fB.m\fR" 4 -.IX Item "file.m" -Objective-C source code. Note that you must link with the library -\&\fIlibobjc.a\fR to make an Objective-C program work. -.Ip "\fIfile\fR\fB.mi\fR" 4 -.IX Item "file.mi" -Objective-C source code which should not be preprocessed. -.Ip "\fIfile\fR\fB.h\fR" 4 -.IX Item "file.h" -C header file (not to be compiled or linked). -.Ip "\fIfile\fR\fB.cc\fR" 4 -.IX Item "file.cc" -.PD 0 -.Ip "\fIfile\fR\fB.cp\fR" 4 -.IX Item "file.cp" -.Ip "\fIfile\fR\fB.cxx\fR" 4 -.IX Item "file.cxx" -.Ip "\fIfile\fR\fB.cpp\fR" 4 -.IX Item "file.cpp" -.Ip "\fIfile\fR\fB.c++\fR" 4 -.IX Item "file.c++" -.Ip "\fIfile\fR\fB.C\fR" 4 -.IX Item "file.C" -.PD -\&\*(C+ source code which must be preprocessed. Note that in \fB.cxx\fR, -the last two letters must both be literally \fBx\fR. Likewise, -\&\fB.C\fR refers to a literal capital C. -.Ip "\fIfile\fR\fB.f\fR" 4 -.IX Item "file.f" -.PD 0 -.Ip "\fIfile\fR\fB.for\fR" 4 -.IX Item "file.for" -.Ip "\fIfile\fR\fB.FOR\fR" 4 -.IX Item "file.FOR" -.PD -Fortran source code which should not be preprocessed. -.Ip "\fIfile\fR\fB.F\fR" 4 -.IX Item "file.F" -.PD 0 -.Ip "\fIfile\fR\fB.fpp\fR" 4 -.IX Item "file.fpp" -.Ip "\fIfile\fR\fB.FPP\fR" 4 -.IX Item "file.FPP" -.PD -Fortran source code which must be preprocessed (with the traditional -preprocessor). -.Ip "\fIfile\fR\fB.r\fR" 4 -.IX Item "file.r" -Fortran source code which must be preprocessed with a \s-1RATFOR\s0 -preprocessor (not included with \s-1GCC\s0). -.Ip "\fIfile\fR\fB.ads\fR" 4 -.IX Item "file.ads" -Ada source code file which contains a library unit declaration (a -declaration of a package, subprogram, or generic, or a generic -instantiation), or a library unit renaming declaration (a package, -generic, or subprogram renaming declaration). Such files are also -called \fIspecs\fR. -.Ip "\fIfile\fR\fB.adb\fR" 4 -.IX Item "file.adb" -Ada source code file containing a library unit body (a subprogram or -package body). Such files are also called \fIbodies\fR. -.Ip "\fIfile\fR\fB.s\fR" 4 -.IX Item "file.s" -Assembler code. -.Ip "\fIfile\fR\fB.S\fR" 4 -.IX Item "file.S" -Assembler code which must be preprocessed. -.Ip "\fIother\fR" 4 -.IX Item "other" -An object file to be fed straight into linking. -Any file name with no recognized suffix is treated this way. -.PP -You can specify the input language explicitly with the \fB\-x\fR option: -.Ip "\fB\-x\fR \fIlanguage\fR" 4 -.IX Item "-x language" -Specify explicitly the \fIlanguage\fR for the following input files -(rather than letting the compiler choose a default based on the file -name suffix). This option applies to all following input files until -the next \fB\-x\fR option. Possible values for \fIlanguage\fR are: -.Sp -.Vb 7 -\& c c-header cpp-output -\& c++ c++-cpp-output -\& objective-c objc-cpp-output -\& assembler assembler-with-cpp -\& ada -\& f77 f77-cpp-input ratfor -\& java -.Ve -.Ip "\fB\-x none\fR" 4 -.IX Item "-x none" -Turn off any specification of a language, so that subsequent files are -handled according to their file name suffixes (as they are if \fB\-x\fR -has not been used at all). -.Ip "\fB\-pass-exit-codes\fR" 4 -.IX Item "-pass-exit-codes" -Normally the \fBgcc\fR program will exit with the code of 1 if any -phase of the compiler returns a non-success return code. If you specify -\&\fB\-pass-exit-codes\fR, the \fBgcc\fR program will instead return with -numerically highest error produced by any phase that returned an error -indication. -.PP -If you only want some of the stages of compilation, you can use -\&\fB\-x\fR (or filename suffixes) to tell \fBgcc\fR where to start, and -one of the options \fB\-c\fR, \fB\-S\fR, or \fB\-E\fR to say where -\&\fBgcc\fR is to stop. Note that some combinations (for example, -\&\fB\-x cpp-output \-E\fR) instruct \fBgcc\fR to do nothing at all. -.Ip "\fB\-c\fR" 4 -.IX Item "-c" -Compile or assemble the source files, but do not link. The linking -stage simply is not done. The ultimate output is in the form of an -object file for each source file. -.Sp -By default, the object file name for a source file is made by replacing -the suffix \fB.c\fR, \fB.i\fR, \fB.s\fR, etc., with \fB.o\fR. -.Sp -Unrecognized input files, not requiring compilation or assembly, are -ignored. -.Ip "\fB\-S\fR" 4 -.IX Item "-S" -Stop after the stage of compilation proper; do not assemble. The output -is in the form of an assembler code file for each non-assembler input -file specified. -.Sp -By default, the assembler file name for a source file is made by -replacing the suffix \fB.c\fR, \fB.i\fR, etc., with \fB.s\fR. -.Sp -Input files that don't require compilation are ignored. -.Ip "\fB\-E\fR" 4 -.IX Item "-E" -Stop after the preprocessing stage; do not run the compiler proper. The -output is in the form of preprocessed source code, which is sent to the -standard output. -.Sp -Input files which don't require preprocessing are ignored. -.Ip "\fB\-o\fR \fIfile\fR" 4 -.IX Item "-o file" -Place output in file \fIfile\fR. This applies regardless to whatever -sort of output is being produced, whether it be an executable file, -an object file, an assembler file or preprocessed C code. -.Sp -Since only one output file can be specified, it does not make sense to -use \fB\-o\fR when compiling more than one input file, unless you are -producing an executable file as output. -.Sp -If \fB\-o\fR is not specified, the default is to put an executable file -in \fIa.out\fR, the object file for \fI\fIsource\fI.\fIsuffix\fI\fR in -\&\fI\fIsource\fI.o\fR, its assembler file in \fI\fIsource\fI.s\fR, and -all preprocessed C source on standard output. -.Ip "\fB\-v\fR" 4 -.IX Item "-v" -Print (on standard error output) the commands executed to run the stages -of compilation. Also print the version number of the compiler driver -program and of the preprocessor and the compiler proper. -.Ip "\fB\-###\fR" 4 -.IX Item "-###" -Like \fB\-v\fR except the commands are not executed and all command -arguments are quoted. This is useful for shell scripts to capture the -driver-generated command lines. -.Ip "\fB\-pipe\fR" 4 -.IX Item "-pipe" -Use pipes rather than temporary files for communication between the -various stages of compilation. This fails to work on some systems where -the assembler is unable to read from a pipe; but the \s-1GNU\s0 assembler has -no trouble. -.Ip "\fB\*(--help\fR" 4 -.IX Item "help" -Print (on the standard output) a description of the command line options -understood by \fBgcc\fR. If the \fB\-v\fR option is also specified -then \fB\*(--help\fR will also be passed on to the various processes -invoked by \fBgcc\fR, so that they can display the command line options -they accept. If the \fB\-W\fR option is also specified then command -line options which have no documentation associated with them will also -be displayed. -.Ip "\fB\*(--target-help\fR" 4 -.IX Item "target-help" -Print (on the standard output) a description of target specific command -line options for each tool. -.Ip "\fB\*(--version\fR" 4 -.IX Item "version" -Display the version number and copyrights of the invoked \s-1GCC\s0. -.Sh "Compiling \*(C+ Programs" -.IX Subsection "Compiling Programs" -\&\*(C+ source files conventionally use one of the suffixes \fB.C\fR, -\&\fB.cc\fR, \fB.cpp\fR, \fB.c++\fR, \fB.cp\fR, or \fB.cxx\fR; -preprocessed \*(C+ files use the suffix \fB.ii\fR. \s-1GCC\s0 recognizes -files with these names and compiles them as \*(C+ programs even if you -call the compiler the same way as for compiling C programs (usually with -the name \fBgcc\fR). -.PP -However, \*(C+ programs often require class libraries as well as a -compiler that understands the \*(C+ language\-\-\-and under some -circumstances, you might want to compile programs from standard input, -or otherwise without a suffix that flags them as \*(C+ programs. -\&\fBg++\fR is a program that calls \s-1GCC\s0 with the default language -set to \*(C+, and automatically specifies linking against the \*(C+ -library. On many systems, \fBg++\fR is also -installed with the name \fBc++\fR. -.PP -When you compile \*(C+ programs, you may specify many of the same -command-line options that you use for compiling programs in any -language; or command-line options meaningful for C and related -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: -.Ip "\fB\-ansi\fR" 4 -.IX Item "-ansi" -In C mode, support all \s-1ISO\s0 C89 programs. In \*(C+ mode, -remove \s-1GNU\s0 extensions that conflict with \s-1ISO\s0 \*(C+. -.Sp -This turns off certain features of \s-1GCC\s0 that are incompatible with \s-1ISO\s0 -C89 (when compiling C code), or of standard \*(C+ (when compiling \*(C+ code), -such as the \f(CW\*(C`asm\*(C'\fR and \f(CW\*(C`typeof\*(C'\fR keywords, and -predefined macros such as \f(CW\*(C`unix\*(C'\fR and \f(CW\*(C`vax\*(C'\fR that identify the -type of system you are using. It also enables the undesirable and -rarely used \s-1ISO\s0 trigraph feature. For the C compiler, -it disables recognition of \*(C+ style \fB//\fR comments as well as -the \f(CW\*(C`inline\*(C'\fR keyword. -.Sp -The alternate keywords \f(CW\*(C`_\|_asm_\|_\*(C'\fR, \f(CW\*(C`_\|_extension_\|_\*(C'\fR, -\&\f(CW\*(C`_\|_inline_\|_\*(C'\fR and \f(CW\*(C`_\|_typeof_\|_\*(C'\fR continue to work despite -\&\fB\-ansi\fR. You would not want to use them in an \s-1ISO\s0 C program, of -course, but it is useful to put them in header files that might be included -in compilations done with \fB\-ansi\fR. Alternate predefined macros -such as \f(CW\*(C`_\|_unix_\|_\*(C'\fR and \f(CW\*(C`_\|_vax_\|_\*(C'\fR are also available, with or -without \fB\-ansi\fR. -.Sp -The \fB\-ansi\fR option does not cause non-ISO programs to be -rejected gratuitously. For that, \fB\-pedantic\fR is required in -addition to \fB\-ansi\fR. -.Sp -The macro \f(CW\*(C`_\|_STRICT_ANSI_\|_\*(C'\fR is predefined when the \fB\-ansi\fR -option is used. Some header files may notice this macro and refrain -from declaring certain functions or defining certain macros that the -\&\s-1ISO\s0 standard doesn't call for; this is to avoid interfering with any -programs that might use these names for other things. -.Sp -Functions which would normally be built in but do not have semantics -defined by \s-1ISO\s0 C (such as \f(CW\*(C`alloca\*(C'\fR and \f(CW\*(C`ffs\*(C'\fR) are not built-in -functions with \fB\-ansi\fR is used. -.Ip "\fB\-std=\fR" 4 -.IX Item "-std=" -Determine the language standard. This option is currently only -supported when compiling C. A value for this option must be provided; -possible values are -.RS 4 -.Ip "\fBc89\fR" 4 -.IX Item "c89" -.PD 0 -.Ip "\fBiso9899:1990\fR" 4 -.IX Item "iso9899:1990" -.PD -\&\s-1ISO\s0 C89 (same as \fB\-ansi\fR). -.Ip "\fBiso9899:199409\fR" 4 -.IX Item "iso9899:199409" -\&\s-1ISO\s0 C89 as modified in amendment 1. -.Ip "\fBc99\fR" 4 -.IX Item "c99" -.PD 0 -.Ip "\fBc9x\fR" 4 -.IX Item "c9x" -.Ip "\fBiso9899:1999\fR" 4 -.IX Item "iso9899:1999" -.Ip "\fBiso9899:199x\fR" 4 -.IX Item "iso9899:199x" -.PD -\&\s-1ISO\s0 C99. Note that this standard is not yet fully supported; see -<\fBhttp://gcc.gnu.org/gcc-3.1/c99status.html\fR> for more information. The -names \fBc9x\fR and \fBiso9899:199x\fR are deprecated. -.Ip "\fBgnu89\fR" 4 -.IX Item "gnu89" -Default, \s-1ISO\s0 C89 plus \s-1GNU\s0 extensions (including some C99 features). -.Ip "\fBgnu99\fR" 4 -.IX Item "gnu99" -.PD 0 -.Ip "\fBgnu9x\fR" 4 -.IX Item "gnu9x" -.PD -\&\s-1ISO\s0 C99 plus \s-1GNU\s0 extensions. When \s-1ISO\s0 C99 is fully implemented in \s-1GCC\s0, -this will become the default. The name \fBgnu9x\fR is deprecated. -.RE -.RS 4 -.Sp -Even when this option is not specified, you can still use some of the -features of newer standards in so far as they do not conflict with -previous C standards. For example, you may use \f(CW\*(C`_\|_restrict_\|_\*(C'\fR even -when \fB\-std=c99\fR is not specified. -.Sp -The \fB\-std\fR options specifying some version of \s-1ISO\s0 C have the same -effects as \fB\-ansi\fR, except that features that were not in \s-1ISO\s0 C89 -but are in the specified version (for example, \fB//\fR comments and -the \f(CW\*(C`inline\*(C'\fR keyword in \s-1ISO\s0 C99) are not disabled. -.RE -.Ip "\fB\-aux-info\fR \fIfilename\fR" 4 -.IX Item "-aux-info filename" -Output to the given filename prototyped declarations for all functions -declared and/or defined in a translation unit, including those in header -files. This option is silently ignored in any language other than C. -.Sp -Besides declarations, the file indicates, in comments, the origin of -each declaration (source file and line), whether the declaration was -implicit, prototyped or unprototyped (\fBI\fR, \fBN\fR for new or -\&\fBO\fR for old, respectively, in the first character after the line -number and the colon), and whether it came from a declaration or a -definition (\fBC\fR or \fBF\fR, respectively, in the following -character). In the case of function definitions, a K&R-style list of -arguments followed by their declarations is also provided, inside -comments, after the declaration. -.Ip "\fB\-fno-asm\fR" 4 -.IX Item "-fno-asm" -Do not recognize \f(CW\*(C`asm\*(C'\fR, \f(CW\*(C`inline\*(C'\fR or \f(CW\*(C`typeof\*(C'\fR as a -keyword, so that code can use these words as identifiers. You can use -the keywords \f(CW\*(C`_\|_asm_\|_\*(C'\fR, \f(CW\*(C`_\|_inline_\|_\*(C'\fR and \f(CW\*(C`_\|_typeof_\|_\*(C'\fR -instead. \fB\-ansi\fR implies \fB\-fno-asm\fR. -.Sp -In \*(C+, this switch only affects the \f(CW\*(C`typeof\*(C'\fR keyword, since -\&\f(CW\*(C`asm\*(C'\fR and \f(CW\*(C`inline\*(C'\fR are standard keywords. You may want to -use the \fB\-fno-gnu-keywords\fR flag instead, which has the same -effect. In C99 mode (\fB\-std=c99\fR or \fB\-std=gnu99\fR), this -switch only affects the \f(CW\*(C`asm\*(C'\fR and \f(CW\*(C`typeof\*(C'\fR keywords, since -\&\f(CW\*(C`inline\*(C'\fR is a standard keyword in \s-1ISO\s0 C99. -.Ip "\fB\-fno-builtin\fR" 4 -.IX Item "-fno-builtin" -.PD 0 -.Ip "\fB\-fno-builtin-\fR\fIfunction\fR\fB \fR(C and Objective-C only)" 4 -.IX Item "-fno-builtin-function (C and Objective-C only)" -.PD -Don't recognize built-in functions that do not begin with -\&\fB_\|_builtin_\fR as prefix. -.Sp -\&\s-1GCC\s0 normally generates special code to handle certain built-in functions -more efficiently; for instance, calls to \f(CW\*(C`alloca\*(C'\fR may become single -instructions that adjust the stack directly, and calls to \f(CW\*(C`memcpy\*(C'\fR -may become inline copy loops. The resulting code is often both smaller -and faster, but since the function calls no longer appear as such, you -cannot set a breakpoint on those calls, nor can you change the behavior -of the functions by linking with a different library. -.Sp -In \*(C+, \fB\-fno-builtin\fR is always in effect. The \fB\-fbuiltin\fR -option has no effect. Therefore, in \*(C+, the only way to get the -optimization benefits of built-in functions is to call the function -using the \fB_\|_builtin_\fR prefix. The \s-1GNU\s0 \*(C+ Standard Library uses -built-in functions to implement many functions (like -\&\f(CW\*(C`std::strchr\*(C'\fR), so that you automatically get efficient code. -.Sp -With the \fB\-fno-builtin-\fR\fIfunction\fR option, not available -when compiling \*(C+, only the built-in function \fIfunction\fR is -disabled. \fIfunction\fR must not begin with \fB_\|_builtin_\fR. If a -function is named this is not built-in in this version of \s-1GCC\s0, this -option is ignored. There is no corresponding -\&\fB\-fbuiltin-\fR\fIfunction\fR option; if you wish to enable -built-in functions selectively when using \fB\-fno-builtin\fR or -\&\fB\-ffreestanding\fR, you may define macros such as: -.Sp -.Vb 2 -\& #define abs(n) __builtin_abs ((n)) -\& #define strcpy(d, s) __builtin_strcpy ((d), (s)) -.Ve -.Ip "\fB\-fhosted\fR" 4 -.IX Item "-fhosted" -Assert that compilation takes place in a hosted environment. This implies -\&\fB\-fbuiltin\fR. A hosted environment is one in which the -entire standard library is available, and in which \f(CW\*(C`main\*(C'\fR has a return -type of \f(CW\*(C`int\*(C'\fR. Examples are nearly everything except a kernel. -This is equivalent to \fB\-fno-freestanding\fR. -.Ip "\fB\-ffreestanding\fR" 4 -.IX Item "-ffreestanding" -Assert that compilation takes place in a freestanding environment. This -implies \fB\-fno-builtin\fR. A freestanding environment -is one in which the standard library may not exist, and program startup may -not necessarily be at \f(CW\*(C`main\*(C'\fR. The most obvious example is an \s-1OS\s0 kernel. -This is equivalent to \fB\-fno-hosted\fR. -.Ip "\fB\-trigraphs\fR" 4 -.IX Item "-trigraphs" -Support \s-1ISO\s0 C trigraphs. The \fB\-ansi\fR option (and \fB\-std\fR -options for strict \s-1ISO\s0 C conformance) implies \fB\-trigraphs\fR. -.Ip "\fB\-no-integrated-cpp\fR" 4 -.IX Item "-no-integrated-cpp" -Invoke the external cpp during compilation. The default is to use the -integrated cpp (internal cpp). This option also allows a -user-supplied cpp via the \fB\-B\fR option. This flag is applicable -in both C and \*(C+ modes. -.Sp -We do not guarantee to retain this option in future, and we may change -its semantics. -.Ip "\fB\-traditional\fR" 4 -.IX Item "-traditional" -Attempt to support some aspects of traditional C compilers. -Specifically: -.RS 4 -.Ip "\(bu" 4 -All \f(CW\*(C`extern\*(C'\fR declarations take effect globally even if they -are written inside of a function definition. This includes implicit -declarations of functions. -.Ip "\(bu" 4 -The newer keywords \f(CW\*(C`typeof\*(C'\fR, \f(CW\*(C`inline\*(C'\fR, \f(CW\*(C`signed\*(C'\fR, \f(CW\*(C`const\*(C'\fR -and \f(CW\*(C`volatile\*(C'\fR are not recognized. (You can still use the -alternative keywords such as \f(CW\*(C`_\|_typeof_\|_\*(C'\fR, \f(CW\*(C`_\|_inline_\|_\*(C'\fR, and -so on.) -.Ip "\(bu" 4 -Comparisons between pointers and integers are always allowed. -.Ip "\(bu" 4 -Integer types \f(CW\*(C`unsigned short\*(C'\fR and \f(CW\*(C`unsigned char\*(C'\fR promote -to \f(CW\*(C`unsigned int\*(C'\fR. -.Ip "\(bu" 4 -Out-of-range floating point literals are not an error. -.Ip "\(bu" 4 -Certain constructs which \s-1ISO\s0 regards as a single invalid preprocessing -number, such as \fB0xe-0xd\fR, are treated as expressions instead. -.Ip "\(bu" 4 -String ``constants'' are not necessarily constant; they are stored in -writable space, and identical looking constants are allocated -separately. (This is the same as the effect of -\&\fB\-fwritable-strings\fR.) -.Ip "\(bu" 4 -All automatic variables not declared \f(CW\*(C`register\*(C'\fR are preserved by -\&\f(CW\*(C`longjmp\*(C'\fR. Ordinarily, \s-1GNU\s0 C follows \s-1ISO\s0 C: automatic variables -not declared \f(CW\*(C`volatile\*(C'\fR may be clobbered. -.Ip "\(bu" 4 -The character escape sequences \fB\ex\fR and \fB\ea\fR evaluate as the -literal characters \fBx\fR and \fBa\fR respectively. Without -\&\fB\-traditional\fR, \fB\ex\fR is a prefix for the hexadecimal -representation of a character, and \fB\ea\fR produces a bell. -.RE -.RS 4 -.Sp -This option is deprecated and may be removed. -.Sp -You may wish to use \fB\-fno-builtin\fR as well as \fB\-traditional\fR -if your program uses names that are normally \s-1GNU\s0 C built-in functions for -other purposes of its own. -.Sp -You cannot use \fB\-traditional\fR if you include any header files that -rely on \s-1ISO\s0 C features. Some vendors are starting to ship systems with -\&\s-1ISO\s0 C header files and you cannot use \fB\-traditional\fR on such -systems to compile files that include any system headers. -.Sp -The \fB\-traditional\fR option also enables \fB\-traditional-cpp\fR. -.RE -.Ip "\fB\-traditional-cpp\fR" 4 -.IX Item "-traditional-cpp" -Attempt to support some aspects of traditional C preprocessors. -See the \s-1GNU\s0 \s-1CPP\s0 manual for details. -.Ip "\fB\-fcond-mismatch\fR" 4 -.IX Item "-fcond-mismatch" -Allow conditional expressions with mismatched types in the second and -third arguments. The value of such an expression is void. This option -is not supported for \*(C+. -.Ip "\fB\-funsigned-char\fR" 4 -.IX Item "-funsigned-char" -Let the type \f(CW\*(C`char\*(C'\fR be unsigned, like \f(CW\*(C`unsigned char\*(C'\fR. -.Sp -Each kind of machine has a default for what \f(CW\*(C`char\*(C'\fR should -be. It is either like \f(CW\*(C`unsigned char\*(C'\fR by default or like -\&\f(CW\*(C`signed char\*(C'\fR by default. -.Sp -Ideally, a portable program should always use \f(CW\*(C`signed char\*(C'\fR or -\&\f(CW\*(C`unsigned char\*(C'\fR when it depends on the signedness of an object. -But many programs have been written to use plain \f(CW\*(C`char\*(C'\fR and -expect it to be signed, or expect it to be unsigned, depending on the -machines they were written for. This option, and its inverse, let you -make such a program work with the opposite default. -.Sp -The type \f(CW\*(C`char\*(C'\fR is always a distinct type from each of -\&\f(CW\*(C`signed char\*(C'\fR or \f(CW\*(C`unsigned char\*(C'\fR, even though its behavior -is always just like one of those two. -.Ip "\fB\-fsigned-char\fR" 4 -.IX Item "-fsigned-char" -Let the type \f(CW\*(C`char\*(C'\fR be signed, like \f(CW\*(C`signed char\*(C'\fR. -.Sp -Note that this is equivalent to \fB\-fno-unsigned-char\fR, which is -the negative form of \fB\-funsigned-char\fR. Likewise, the option -\&\fB\-fno-signed-char\fR is equivalent to \fB\-funsigned-char\fR. -.Ip "\fB\-fsigned-bitfields\fR" 4 -.IX Item "-fsigned-bitfields" -.PD 0 -.Ip "\fB\-funsigned-bitfields\fR" 4 -.IX Item "-funsigned-bitfields" -.Ip "\fB\-fno-signed-bitfields\fR" 4 -.IX Item "-fno-signed-bitfields" -.Ip "\fB\-fno-unsigned-bitfields\fR" 4 -.IX Item "-fno-unsigned-bitfields" -.PD -These options control whether a bit-field is signed or unsigned, when the -declaration does not use either \f(CW\*(C`signed\*(C'\fR or \f(CW\*(C`unsigned\*(C'\fR. By -default, such a bit-field is signed, because this is consistent: the -basic integer types such as \f(CW\*(C`int\*(C'\fR are signed types. -.Sp -However, when \fB\-traditional\fR is used, bit-fields are all unsigned -no matter what. -.Ip "\fB\-fwritable-strings\fR" 4 -.IX Item "-fwritable-strings" -Store string constants in the writable data segment and don't uniquize -them. This is for compatibility with old programs which assume they can -write into string constants. The option \fB\-traditional\fR also has -this effect. -.Sp -Writing into string constants is a very bad idea; ``constants'' should -be constant. -.Ip "\fB\-fallow-single-precision\fR" 4 -.IX Item "-fallow-single-precision" -Do not promote single precision math operations to double precision, -even when compiling with \fB\-traditional\fR. -.Sp -Traditional K&R C promotes all floating point operations to double -precision, regardless of the sizes of the operands. On the -architecture for which you are compiling, single precision may be faster -than double precision. If you must use \fB\-traditional\fR, but want -to use single precision operations when the operands are single -precision, use this option. This option has no effect when compiling -with \s-1ISO\s0 or \s-1GNU\s0 C conventions (the default). -.Sh "Options Controlling \*(C+ Dialect" -.IX Subsection "Options Controlling Dialect" -This section describes the command-line options that are only meaningful -for \*(C+ programs; but you can also use most of the \s-1GNU\s0 compiler options -regardless of what language your program is in. For example, you -might compile a file \f(CW\*(C`firstClass.C\*(C'\fR like this: -.PP -.Vb 1 -\& g++ -g -frepo -O -c firstClass.C -.Ve -In this example, only \fB\-frepo\fR is an option meant -only for \*(C+ programs; you can use the other options with any -language supported by \s-1GCC\s0. -.PP -Here is a list of options that are \fIonly\fR for compiling \*(C+ programs: -.Ip "\fB\-fno-access-control\fR" 4 -.IX Item "-fno-access-control" -Turn off all access checking. This switch is mainly useful for working -around bugs in the access control code. -.Ip "\fB\-fcheck-new\fR" 4 -.IX Item "-fcheck-new" -Check that the pointer returned by \f(CW\*(C`operator new\*(C'\fR is non-null -before attempting to modify the storage allocated. The current Working -Paper requires that \f(CW\*(C`operator new\*(C'\fR never return a null pointer, so -this check is normally unnecessary. -.Sp -An alternative to using this option is to specify that your -\&\f(CW\*(C`operator new\*(C'\fR does not throw any exceptions; if you declare it -\&\fB\f(BIthrow()\fB\fR, G++ will check the return value. See also \fBnew -(nothrow)\fR. -.Ip "\fB\-fconserve-space\fR" 4 -.IX Item "-fconserve-space" -Put uninitialized or runtime-initialized global variables into the -common segment, as C does. This saves space in the executable at the -cost of not diagnosing duplicate definitions. If you compile with this -flag and your program mysteriously crashes after \f(CW\*(C`main()\*(C'\fR has -completed, you may have an object that is being destroyed twice because -two definitions were merged. -.Sp -This option is no longer useful on most targets, now that support has -been added for putting variables into \s-1BSS\s0 without making them common. -.Ip "\fB\-fno-const-strings\fR" 4 -.IX Item "-fno-const-strings" -Give string constants type \f(CW\*(C`char *\*(C'\fR instead of type \f(CW\*(C`const -char *\*(C'\fR. By default, G++ uses type \f(CW\*(C`const char *\*(C'\fR as required by -the standard. Even if you use \fB\-fno-const-strings\fR, you cannot -actually modify the value of a string constant, unless you also use -\&\fB\-fwritable-strings\fR. -.Sp -This option might be removed in a future release of G++. For maximum -portability, you should structure your code so that it works with -string constants that have type \f(CW\*(C`const char *\*(C'\fR. -.Ip "\fB\-fdollars-in-identifiers\fR" 4 -.IX Item "-fdollars-in-identifiers" -Accept \fB$\fR in identifiers. You can also explicitly prohibit use of -\&\fB$\fR with the option \fB\-fno-dollars-in-identifiers\fR. (\s-1GNU\s0 C allows -\&\fB$\fR by default on most target systems, but there are a few exceptions.) -Traditional C allowed the character \fB$\fR to form part of -identifiers. However, \s-1ISO\s0 C and \*(C+ forbid \fB$\fR in identifiers. -.Ip "\fB\-fno-elide-constructors\fR" 4 -.IX Item "-fno-elide-constructors" -The \*(C+ standard allows an implementation to omit creating a temporary -which is only used to initialize another object of the same type. -Specifying this option disables that optimization, and forces G++ to -call the copy constructor in all cases. -.Ip "\fB\-fno-enforce-eh-specs\fR" 4 -.IX Item "-fno-enforce-eh-specs" -Don't check for violation of exception specifications at runtime. This -option violates the \*(C+ standard, but may be useful for reducing code -size in production builds, much like defining \fB\s-1NDEBUG\s0\fR. The compiler -will still optimize based on the exception specifications. -.Ip "\fB\-fexternal-templates\fR" 4 -.IX Item "-fexternal-templates" -Cause \fB#pragma interface\fR and \fBimplementation\fR to apply to -template instantiation; template instances are emitted or not according -to the location of the template definition. -.Sp -This option is deprecated. -.Ip "\fB\-falt-external-templates\fR" 4 -.IX Item "-falt-external-templates" -Similar to \fB\-fexternal-templates\fR, but template instances are -emitted or not according to the place where they are first instantiated. -.Sp -This option is deprecated. -.Ip "\fB\-ffor-scope\fR" 4 -.IX Item "-ffor-scope" -.PD 0 -.Ip "\fB\-fno-for-scope\fR" 4 -.IX Item "-fno-for-scope" -.PD -If \fB\-ffor-scope\fR is specified, the scope of variables declared in -a \fIfor-init-statement\fR is limited to the \fBfor\fR loop itself, -as specified by the \*(C+ standard. -If \fB\-fno-for-scope\fR is specified, the scope of variables declared in -a \fIfor-init-statement\fR extends to the end of the enclosing scope, -as was the case in old versions of G++, and other (traditional) -implementations of \*(C+. -.Sp -The default if neither flag is given to follow the standard, -but to allow and give a warning for old-style code that would -otherwise be invalid, or have different behavior. -.Ip "\fB\-fno-gnu-keywords\fR" 4 -.IX Item "-fno-gnu-keywords" -Do not recognize \f(CW\*(C`typeof\*(C'\fR as a keyword, so that code can use this -word as an identifier. You can use the keyword \f(CW\*(C`_\|_typeof_\|_\*(C'\fR instead. -\&\fB\-ansi\fR implies \fB\-fno-gnu-keywords\fR. -.Ip "\fB\-fno-implicit-templates\fR" 4 -.IX Item "-fno-implicit-templates" -Never emit code for non-inline templates which are instantiated -implicitly (i.e. by use); only emit code for explicit instantiations. -.Ip "\fB\-fno-implicit-inline-templates\fR" 4 -.IX Item "-fno-implicit-inline-templates" -Don't emit code for implicit instantiations of inline templates, either. -The default is to handle inlines differently so that compiles with and -without optimization will need the same set of explicit instantiations. -.Ip "\fB\-fno-implement-inlines\fR" 4 -.IX Item "-fno-implement-inlines" -To save space, do not emit out-of-line copies of inline functions -controlled by \fB#pragma implementation\fR. This will cause linker -errors if these functions are not inlined everywhere they are called. -.Ip "\fB\-fms-extensions\fR" 4 -.IX Item "-fms-extensions" -Disable pedantic warnings about constructs used in \s-1MFC\s0, such as implicit -int and getting a pointer to member function via non-standard syntax. -.Ip "\fB\-fno-nonansi-builtins\fR" 4 -.IX Item "-fno-nonansi-builtins" -Disable built-in declarations of functions that are not mandated by -\&\s-1ANSI/ISO\s0 C. These include \f(CW\*(C`ffs\*(C'\fR, \f(CW\*(C`alloca\*(C'\fR, \f(CW\*(C`_exit\*(C'\fR, -\&\f(CW\*(C`index\*(C'\fR, \f(CW\*(C`bzero\*(C'\fR, \f(CW\*(C`conjf\*(C'\fR, and other related functions. -.Ip "\fB\-fno-operator-names\fR" 4 -.IX Item "-fno-operator-names" -Do not treat the operator name keywords \f(CW\*(C`and\*(C'\fR, \f(CW\*(C`bitand\*(C'\fR, -\&\f(CW\*(C`bitor\*(C'\fR, \f(CW\*(C`compl\*(C'\fR, \f(CW\*(C`not\*(C'\fR, \f(CW\*(C`or\*(C'\fR and \f(CW\*(C`xor\*(C'\fR as -synonyms as keywords. -.Ip "\fB\-fno-optional-diags\fR" 4 -.IX Item "-fno-optional-diags" -Disable diagnostics that the standard says a compiler does not need to -issue. Currently, the only such diagnostic issued by G++ is the one for -a name having multiple meanings within a class. -.Ip "\fB\-fpermissive\fR" 4 -.IX Item "-fpermissive" -Downgrade messages about nonconformant code from errors to warnings. By -default, G++ effectively sets \fB\-pedantic-errors\fR without -\&\fB\-pedantic\fR; this option reverses that. This behavior and this -option are superseded by \fB\-pedantic\fR, which works as it does for \s-1GNU\s0 C. -.Ip "\fB\-frepo\fR" 4 -.IX Item "-frepo" -Enable automatic template instantiation at link time. This option also -implies \fB\-fno-implicit-templates\fR. -.Ip "\fB\-fno-rtti\fR" 4 -.IX Item "-fno-rtti" -Disable generation of information about every class with virtual -functions for use by the \*(C+ runtime type identification features -(\fBdynamic_cast\fR and \fBtypeid\fR). If you don't use those parts -of the language, you can save some space by using this flag. Note that -exception handling uses the same information, but it will generate it as -needed. -.Ip "\fB\-fstats\fR" 4 -.IX Item "-fstats" -Emit statistics about front-end processing at the end of the compilation. -This information is generally only useful to the G++ development team. -.Ip "\fB\-ftemplate-depth-\fR\fIn\fR" 4 -.IX Item "-ftemplate-depth-n" -Set the maximum instantiation depth for template classes to \fIn\fR. -A limit on the template instantiation depth is needed to detect -endless recursions during template class instantiation. \s-1ANSI/ISO\s0 \*(C+ -conforming programs must not rely on a maximum depth greater than 17. -.Ip "\fB\-fuse-cxa-atexit\fR" 4 -.IX Item "-fuse-cxa-atexit" -Register destructors for objects with static storage duration with the -\&\f(CW\*(C`_\|_cxa_atexit\*(C'\fR function rather than the \f(CW\*(C`atexit\*(C'\fR function. -This option is required for fully standards-compliant handling of static -destructors, but will only work if your C library supports -\&\f(CW\*(C`_\|_cxa_atexit\*(C'\fR. -.Ip "\fB\-fvtable-gc\fR" 4 -.IX Item "-fvtable-gc" -Emit special relocations for vtables and virtual function references -so that the linker can identify unused virtual functions and zero out -vtable slots that refer to them. This is most useful with -\&\fB\-ffunction-sections\fR and \fB\-Wl,\-\-gc-sections\fR, in order to -also discard the functions themselves. -.Sp -This optimization requires \s-1GNU\s0 as and \s-1GNU\s0 ld. Not all systems support -this option. \fB\-Wl,\-\-gc-sections\fR is ignored without \fB\-static\fR. -.Ip "\fB\-fno-weak\fR" 4 -.IX Item "-fno-weak" -Do not use weak symbol support, even if it is provided by the linker. -By default, G++ will use weak symbols if they are available. This -option exists only for testing, and should not be used by end-users; -it will result in inferior code and has no benefits. This option may -be removed in a future release of G++. -.Ip "\fB\-nostdinc++\fR" 4 -.IX Item "-nostdinc++" -Do not search for header files in the standard directories specific to -\&\*(C+, but do still search the other standard directories. (This option -is used when building the \*(C+ library.) -.PP -In addition, these optimization, warning, and code generation options -have meanings only for \*(C+ programs: -.Ip "\fB\-fno-default-inline\fR" 4 -.IX Item "-fno-default-inline" -Do not assume \fBinline\fR for functions defined inside a class scope. - Note that these -functions will have linkage like inline functions; they just won't be -inlined by default. -.Ip "\fB\-Wabi\fR (\*(C+ only)" 4 -.IX Item "-Wabi ( only)" -Warn when G++ generates code that is probably not compatible with the -vendor-neutral \*(C+ \s-1ABI\s0. Although an effort has been made to warn about -all such cases, there are probably some cases that are not warned about, -even though G++ is generating incompatible code. There may also be -cases where warnings are emitted even though the code that is generated -will be compatible. -.Sp -You should rewrite your code to avoid these warnings if you are -concerned about the fact that code generated by G++ may not be binary -compatible with code generated by other compilers. -.Sp -The known incompatibilites at this point include: -.RS 4 -.Ip "\(bu" 4 -Incorrect handling of tail-padding for bit-fields. G++ may attempt to -pack data into the same byte as a base class. For example: -.Sp -.Vb 2 -\& struct A { virtual void f(); int f1 : 1; }; -\& struct B : public A { int f2 : 1; }; -.Ve -In this case, G++ will place \f(CW\*(C`B::f2\*(C'\fR into the same byte -as\f(CW\*(C`A::f1\*(C'\fR; other compilers will not. You can avoid this problem -by explicitly padding \f(CW\*(C`A\*(C'\fR so that its size is a multiple of the -byte size on your platform; that will cause G++ and other compilers to -layout \f(CW\*(C`B\*(C'\fR identically. -.Ip "\(bu" 4 -Incorrect handling of tail-padding for virtual bases. G++ does not use -tail padding when laying out virtual bases. For example: -.Sp -.Vb 3 -\& struct A { virtual void f(); char c1; }; -\& struct B { B(); char c2; }; -\& struct C : public A, public virtual B {}; -.Ve -In this case, G++ will not place \f(CW\*(C`B\*(C'\fR into the tail-padding for -\&\f(CW\*(C`A\*(C'\fR; other compilers will. You can avoid this problem by -explicitly padding \f(CW\*(C`A\*(C'\fR so that its size is a multiple of its -alignment (ignoring virtual base classes); that will cause G++ and other -compilers to layout \f(CW\*(C`C\*(C'\fR identically. -.RE -.RS 4 -.RE -.Ip "\fB\-Wctor-dtor-privacy\fR (\*(C+ only)" 4 -.IX Item "-Wctor-dtor-privacy ( only)" -Warn when a class seems unusable, because all the constructors or -destructors in a class are private and the class has no friends or -public static member functions. -.Ip "\fB\-Wnon-virtual-dtor\fR (\*(C+ only)" 4 -.IX Item "-Wnon-virtual-dtor ( only)" -Warn when a class declares a non-virtual destructor that should probably -be virtual, because it looks like the class will be used polymorphically. -.Ip "\fB\-Wreorder\fR (\*(C+ only)" 4 -.IX Item "-Wreorder ( only)" -Warn when the order of member initializers given in the code does not -match the order in which they must be executed. For instance: -.Sp -.Vb 5 -\& struct A { -\& int i; -\& int j; -\& A(): j (0), i (1) { } -\& }; -.Ve -Here the compiler will warn that the member initializers for \fBi\fR -and \fBj\fR will be rearranged to match the declaration order of the -members. -.PP -The following \fB\-W...\fR options are not affected by \fB\-Wall\fR. -.Ip "\fB\-Weffc++\fR (\*(C+ only)" 4 -.IX Item "-Weffc++ ( only)" -Warn about violations of the following style guidelines from Scott Meyers' -\&\fIEffective \*(C+\fR book: -.RS 4 -.Ip "\(bu" 4 -Item 11: Define a copy constructor and an assignment operator for classes -with dynamically allocated memory. -.Ip "\(bu" 4 -Item 12: Prefer initialization to assignment in constructors. -.Ip "\(bu" 4 -Item 14: Make destructors virtual in base classes. -.Ip "\(bu" 4 -Item 15: Have \f(CW\*(C`operator=\*(C'\fR return a reference to \f(CW\*(C`*this\*(C'\fR. -.Ip "\(bu" 4 -Item 23: Don't try to return a reference when you must return an object. -.RE -.RS 4 -.Sp -and about violations of the following style guidelines from Scott Meyers' -\&\fIMore Effective \*(C+\fR book: -.RS 4 -.RE -.Ip "\(bu" 4 -Item 6: Distinguish between prefix and postfix forms of increment and -decrement operators. -.Ip "\(bu" 4 -Item 7: Never overload \f(CW\*(C`&&\*(C'\fR, \f(CW\*(C`||\*(C'\fR, or \f(CW\*(C`,\*(C'\fR. -.RE -.RS 4 -.Sp -If you use this option, you should be aware that the standard library -headers do not obey all of these guidelines; you can use \fBgrep \-v\fR -to filter out those warnings. -.RE -.Ip "\fB\-Wno-deprecated\fR (\*(C+ only)" 4 -.IX Item "-Wno-deprecated ( only)" -Do not warn about usage of deprecated features. -.Ip "\fB\-Wno-non-template-friend\fR (\*(C+ only)" 4 -.IX Item "-Wno-non-template-friend ( only)" -Disable warnings when non-templatized friend functions are declared -within a template. With the advent of explicit template specification -support in G++, if the name of the friend is an unqualified-id (i.e., -\&\fBfriend foo(int)\fR), the \*(C+ language specification demands that the -friend declare or define an ordinary, nontemplate function. (Section -14.5.3). Before G++ implemented explicit specification, unqualified-ids -could be interpreted as a particular specialization of a templatized -function. Because this non-conforming behavior is no longer the default -behavior for G++, \fB\-Wnon-template-friend\fR allows the compiler to -check existing code for potential trouble spots, and is on by default. -This new compiler behavior can be turned off with -\&\fB\-Wno-non-template-friend\fR which keeps the conformant compiler code -but disables the helpful warning. -.Ip "\fB\-Wold-style-cast\fR (\*(C+ only)" 4 -.IX Item "-Wold-style-cast ( only)" -Warn if an old-style (C-style) cast to a non-void type is used within -a \*(C+ program. The new-style casts (\fBstatic_cast\fR, -\&\fBreinterpret_cast\fR, and \fBconst_cast\fR) are less vulnerable to -unintended effects, and much easier to grep for. -.Ip "\fB\-Woverloaded-virtual\fR (\*(C+ only)" 4 -.IX Item "-Woverloaded-virtual ( only)" -Warn when a function declaration hides virtual functions from a -base class. For example, in: -.Sp -.Vb 3 -\& struct A { -\& virtual void f(); -\& }; -.Ve -.Vb 3 -\& struct B: public A { -\& void f(int); -\& }; -.Ve -the \f(CW\*(C`A\*(C'\fR class version of \f(CW\*(C`f\*(C'\fR is hidden in \f(CW\*(C`B\*(C'\fR, and code -like this: -.Sp -.Vb 2 -\& B* b; -\& b->f(); -.Ve -will fail to compile. -.Ip "\fB\-Wno-pmf-conversions\fR (\*(C+ only)" 4 -.IX Item "-Wno-pmf-conversions ( only)" -Disable the diagnostic for converting a bound pointer to member function -to a plain pointer. -.Ip "\fB\-Wsign-promo\fR (\*(C+ only)" 4 -.IX Item "-Wsign-promo ( only)" -Warn when overload resolution chooses a promotion from unsigned or -enumeral type to a signed type over a conversion to an unsigned type of -the same size. Previous versions of G++ would try to preserve -unsignedness, but the standard mandates the current behavior. -.Ip "\fB\-Wsynth\fR (\*(C+ only)" 4 -.IX Item "-Wsynth ( only)" -Warn when G++'s synthesis behavior does not match that of cfront. For -instance: -.Sp -.Vb 4 -\& struct A { -\& operator int (); -\& A& operator = (int); -\& }; -.Ve -.Vb 5 -\& main () -\& { -\& A a,b; -\& a = b; -\& } -.Ve -In this example, G++ will synthesize a default \fBA& operator = -(const A&);\fR, while cfront will use the user-defined \fBoperator =\fR. -.Sh "Options Controlling Objective-C Dialect" -.IX Subsection "Options Controlling Objective-C Dialect" -This section describes the command-line options that are only meaningful -for Objective-C programs; but you can also use most of the \s-1GNU\s0 compiler -options regardless of what language your program is in. For example, -you might compile a file \f(CW\*(C`some_class.m\*(C'\fR like this: -.PP -.Vb 1 -\& gcc -g -fgnu-runtime -O -c some_class.m -.Ve -In this example, only \fB\-fgnu-runtime\fR is an option meant only for -Objective-C programs; you can use the other options with any language -supported by \s-1GCC\s0. -.PP -Here is a list of options that are \fIonly\fR for compiling Objective-C -programs: -.Ip "\fB\-fconstant-string-class=\fR\fIclass-name\fR" 4 -.IX Item "-fconstant-string-class=class-name" -Use \fIclass-name\fR as the name of the class to instantiate for each -literal string specified with the syntax \f(CW\*(C`@"..."\*(C'\fR. The default -class name is \f(CW\*(C`NXConstantString\*(C'\fR. -.Ip "\fB\-fgnu-runtime\fR" 4 -.IX Item "-fgnu-runtime" -Generate object code compatible with the standard \s-1GNU\s0 Objective-C -runtime. This is the default for most types of systems. -.Ip "\fB\-fnext-runtime\fR" 4 -.IX Item "-fnext-runtime" -Generate output compatible with the NeXT runtime. This is the default -for NeXT-based systems, including Darwin and Mac \s-1OS\s0 X. -.Ip "\fB\-gen-decls\fR" 4 -.IX Item "-gen-decls" -Dump interface declarations for all classes seen in the source file to a -file named \fI\fIsourcename\fI.decl\fR. -.Ip "\fB\-Wno-protocol\fR" 4 -.IX Item "-Wno-protocol" -Do not warn if methods required by a protocol are not implemented -in the class adopting it. -.Ip "\fB\-Wselector\fR" 4 -.IX Item "-Wselector" -Warn if a selector has multiple methods of different types defined. -.Sh "Options to Control Diagnostic Messages Formatting" -.IX Subsection "Options to Control Diagnostic Messages Formatting" -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 -honor these options. However it is expected, in the near future, that -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 \fBg++\fR and 0 for the rest of -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 -.IX Item "-fdiagnostics-show-location=once" -Only meaningful in line-wrapping mode. Instructs the diagnostic messages -reporter to emit \fIonce\fR source location information; that is, in -case the message is too long to fit on a single physical line and has to -be wrapped, the source location won't be emitted (as prefix) again, -over and over, in subsequent continuation lines. This is the default -behavior. -.Ip "\fB\-fdiagnostics-show-location=every-line\fR" 4 -.IX Item "-fdiagnostics-show-location=every-line" -Only meaningful in line-wrapping mode. Instructs the diagnostic -messages reporter to emit the same source location information (as -prefix) for physical lines that result from the process of breaking -a message which is too long to fit on a single line. -.Sh "Options to Request or Suppress Warnings" -.IX Subsection "Options to Request or Suppress Warnings" -Warnings are diagnostic messages that report constructions which -are not inherently erroneous but which are risky or suggest there -may have been an error. -.PP -You can request many specific warnings with options beginning \fB\-W\fR, -for example \fB\-Wimplicit\fR to request warnings on implicit -declarations. Each of these specific warning options also has a -negative form beginning \fB\-Wno-\fR to turn off warnings; -for example, \fB\-Wno-implicit\fR. This manual lists only one of the -two forms, whichever is not the default. -.PP -The following options control the amount and kinds of warnings produced -by \s-1GCC\s0; for further, language-specific options also refer to -\&\f(CW@ref\fR{\*(C+ Dialect Options} and \f(CW@ref\fR{Objective-C Dialect Options}. -.Ip "\fB\-fsyntax-only\fR" 4 -.IX Item "-fsyntax-only" -Check the code for syntax errors, but don't do anything beyond that. -.Ip "\fB\-pedantic\fR" 4 -.IX Item "-pedantic" -Issue all the warnings demanded by strict \s-1ISO\s0 C and \s-1ISO\s0 \*(C+; -reject all programs that use forbidden extensions, and some other -programs that do not follow \s-1ISO\s0 C and \s-1ISO\s0 \*(C+. For \s-1ISO\s0 C, follows the -version of the \s-1ISO\s0 C standard specified by any \fB\-std\fR option used. -.Sp -Valid \s-1ISO\s0 C and \s-1ISO\s0 \*(C+ programs should compile properly with or without -this option (though a rare few will require \fB\-ansi\fR or a -\&\fB\-std\fR option specifying the required version of \s-1ISO\s0 C). However, -without this option, certain \s-1GNU\s0 extensions and traditional C and \*(C+ -features are supported as well. With this option, they are rejected. -.Sp -\&\fB\-pedantic\fR does not cause warning messages for use of the -alternate keywords whose names begin and end with \fB_\|_\fR. Pedantic -warnings are also disabled in the expression that follows -\&\f(CW\*(C`_\|_extension_\|_\*(C'\fR. However, only system header files should use -these escape routes; application programs should avoid them. -.Sp -Some users try to use \fB\-pedantic\fR to check programs for strict \s-1ISO\s0 -C conformance. They soon find that it does not do quite what they want: -it finds some non-ISO practices, but not all\-\-\-only those for which -\&\s-1ISO\s0 C \fIrequires\fR a diagnostic, and some others for which -diagnostics have been added. -.Sp -A feature to report any failure to conform to \s-1ISO\s0 C might be useful in -some instances, but would require considerable additional work and would -be quite different from \fB\-pedantic\fR. We don't have plans to -support such a feature in the near future. -.Sp -Where the standard specified with \fB\-std\fR represents a \s-1GNU\s0 -extended dialect of C, such as \fBgnu89\fR or \fBgnu99\fR, there is a -corresponding \fIbase standard\fR, the version of \s-1ISO\s0 C on which the \s-1GNU\s0 -extended dialect is based. Warnings from \fB\-pedantic\fR are given -where they are required by the base standard. (It would not make sense -for such warnings to be given only for features not in the specified \s-1GNU\s0 -C dialect, since by definition the \s-1GNU\s0 dialects of C include all -features the compiler supports with the given option, and there would be -nothing to warn about.) -.Ip "\fB\-pedantic-errors\fR" 4 -.IX Item "-pedantic-errors" -Like \fB\-pedantic\fR, except that errors are produced rather than -warnings. -.Ip "\fB\-w\fR" 4 -.IX Item "-w" -Inhibit all warning messages. -.Ip "\fB\-Wno-import\fR" 4 -.IX Item "-Wno-import" -Inhibit warning messages about the use of \fB#import\fR. -.Ip "\fB\-Wchar-subscripts\fR" 4 -.IX Item "-Wchar-subscripts" -Warn if an array subscript has type \f(CW\*(C`char\*(C'\fR. This is a common cause -of error, as programmers often forget that this type is signed on some -machines. -.Ip "\fB\-Wcomment\fR" 4 -.IX Item "-Wcomment" -Warn whenever a comment-start sequence \fB/*\fR appears in a \fB/*\fR -comment, or whenever a Backslash-Newline appears in a \fB//\fR comment. -.Ip "\fB\-Wformat\fR" 4 -.IX Item "-Wformat" -Check calls to \f(CW\*(C`printf\*(C'\fR and \f(CW\*(C`scanf\*(C'\fR, etc., to make sure that -the arguments supplied have types appropriate to the format string -specified, and that the conversions specified in the format string make -sense. This includes standard functions, and others specified by format -attributes, in the \f(CW\*(C`printf\*(C'\fR, -\&\f(CW\*(C`scanf\*(C'\fR, \f(CW\*(C`strftime\*(C'\fR and \f(CW\*(C`strfmon\*(C'\fR (an X/Open extension, -not in the C standard) families. -.Sp -The formats are checked against the format features supported by \s-1GNU\s0 -libc version 2.2. These include all \s-1ISO\s0 C89 and C99 features, as well -as features from the Single Unix Specification and some \s-1BSD\s0 and \s-1GNU\s0 -extensions. Other library implementations may not support all these -features; \s-1GCC\s0 does not support warning about features that go beyond a -particular library's limitations. However, if \fB\-pedantic\fR is used -with \fB\-Wformat\fR, warnings will be given about format features not -in the selected standard version (but not for \f(CW\*(C`strfmon\*(C'\fR formats, -since those are not in any version of the C standard). -.Sp -\&\fB\-Wformat\fR is included in \fB\-Wall\fR. For more control over some -aspects of format checking, the options \fB\-Wno-format-y2k\fR, -\&\fB\-Wno-format-extra-args\fR, \fB\-Wformat-nonliteral\fR, -\&\fB\-Wformat-security\fR and \fB\-Wformat=2\fR are available, but are -not included in \fB\-Wall\fR. -.Ip "\fB\-Wno-format-y2k\fR" 4 -.IX Item "-Wno-format-y2k" -If \fB\-Wformat\fR is specified, do not warn about \f(CW\*(C`strftime\*(C'\fR -formats which may yield only a two-digit year. -.Ip "\fB\-Wno-format-extra-args\fR" 4 -.IX Item "-Wno-format-extra-args" -If \fB\-Wformat\fR is specified, do not warn about excess arguments to a -\&\f(CW\*(C`printf\*(C'\fR or \f(CW\*(C`scanf\*(C'\fR format function. The C standard specifies -that such arguments are ignored. -.Sp -Where the unused arguments lie between used arguments that are -specified with \fB$\fR operand number specifications, normally -warnings are still given, since the implementation could not know what -type to pass to \f(CW\*(C`va_arg\*(C'\fR to skip the unused arguments. However, -in the case of \f(CW\*(C`scanf\*(C'\fR formats, this option will suppress the -warning if the unused arguments are all pointers, since the Single -Unix Specification says that such unused arguments are allowed. -.Ip "\fB\-Wformat-nonliteral\fR" 4 -.IX Item "-Wformat-nonliteral" -If \fB\-Wformat\fR is specified, also warn if the format string is not a -string literal and so cannot be checked, unless the format function -takes its format arguments as a \f(CW\*(C`va_list\*(C'\fR. -.Ip "\fB\-Wformat-security\fR" 4 -.IX Item "-Wformat-security" -If \fB\-Wformat\fR is specified, also warn about uses of format -functions that represent possible security problems. At present, this -warns about calls to \f(CW\*(C`printf\*(C'\fR and \f(CW\*(C`scanf\*(C'\fR functions where the -format string is not a string literal and there are no format arguments, -as in \f(CW\*(C`printf (foo);\*(C'\fR. This may be a security hole if the format -string came from untrusted input and contains \fB%n\fR. (This is -currently a subset of what \fB\-Wformat-nonliteral\fR warns about, but -in future warnings may be added to \fB\-Wformat-security\fR that are not -included in \fB\-Wformat-nonliteral\fR.) -.Ip "\fB\-Wformat=2\fR" 4 -.IX Item "-Wformat=2" -Enable \fB\-Wformat\fR plus format checks not included in -\&\fB\-Wformat\fR. Currently equivalent to \fB\-Wformat -\&\-Wformat-nonliteral \-Wformat-security\fR. -.Ip "\fB\-Wimplicit-int\fR" 4 -.IX Item "-Wimplicit-int" -Warn when a declaration does not specify a type. -.Ip "\fB\-Wimplicit-function-declaration\fR" 4 -.IX Item "-Wimplicit-function-declaration" -.PD 0 -.Ip "\fB\-Werror-implicit-function-declaration\fR" 4 -.IX Item "-Werror-implicit-function-declaration" -.PD -Give a warning (or error) whenever a function is used before being -declared. -.Ip "\fB\-Wimplicit\fR" 4 -.IX Item "-Wimplicit" -Same as \fB\-Wimplicit-int\fR and \fB\-Wimplicit-function-declaration\fR. -.Ip "\fB\-Wmain\fR" 4 -.IX Item "-Wmain" -Warn if the type of \fBmain\fR is suspicious. \fBmain\fR should be a -function with external linkage, returning int, taking either zero -arguments, two, or three arguments of appropriate types. -.Ip "\fB\-Wmissing-braces\fR" 4 -.IX Item "-Wmissing-braces" -Warn if an aggregate or union initializer is not fully bracketed. In -the following example, the initializer for \fBa\fR is not fully -bracketed, but that for \fBb\fR is fully bracketed. -.Sp -.Vb 2 -\& int a[2][2] = { 0, 1, 2, 3 }; -\& int b[2][2] = { { 0, 1 }, { 2, 3 } }; -.Ve -.Ip "\fB\-Wparentheses\fR" 4 -.IX Item "-Wparentheses" -Warn if parentheses are omitted in certain contexts, such -as when there is an assignment in a context where a truth value -is expected, or when operators are nested whose precedence people -often get confused about. -.Sp -Also warn about constructions where there may be confusion to which -\&\f(CW\*(C`if\*(C'\fR statement an \f(CW\*(C`else\*(C'\fR branch belongs. Here is an example of -such a case: -.Sp -.Vb 7 -\& { -\& if (a) -\& if (b) -\& foo (); -\& else -\& bar (); -\& } -.Ve -In C, every \f(CW\*(C`else\*(C'\fR branch belongs to the innermost possible \f(CW\*(C`if\*(C'\fR -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-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: -.Sp -.Vb 9 -\& { -\& if (a) -\& { -\& if (b) -\& foo (); -\& else -\& bar (); -\& } -\& } -.Ve -.Ip "\fB\-Wsequence-point\fR" 4 -.IX Item "-Wsequence-point" -Warn about code that may have undefined semantics because of violations -of sequence point rules in the C standard. -.Sp -The C standard defines the order in which expressions in a C program are -evaluated in terms of \fIsequence points\fR, which represent a partial -ordering between the execution of parts of the program: those executed -before the sequence point, and those executed after it. These occur -after the evaluation of a full expression (one which is not part of a -larger expression), after the evaluation of the first operand of a -\&\f(CW\*(C`&&\*(C'\fR, \f(CW\*(C`||\*(C'\fR, \f(CW\*(C`? :\*(C'\fR or \f(CW\*(C`,\*(C'\fR (comma) operator, before a -function is called (but after the evaluation of its arguments and the -expression denoting the called function), and in certain other places. -Other than as expressed by the sequence point rules, the order of -evaluation of subexpressions of an expression is not specified. All -these rules describe only a partial order rather than a total order, -since, for example, if two functions are called within one expression -with no sequence point between them, the order in which the functions -are called is not specified. However, the standards committee have -ruled that function calls do not overlap. -.Sp -It is not specified when between sequence points modifications to the -values of objects take effect. Programs whose behavior depends on this -have undefined behavior; the C standard specifies that ``Between the -previous and next sequence point an object shall have its stored value -modified at most once by the evaluation of an expression. Furthermore, -the prior value shall be read only to determine the value to be -stored.''. If a program breaks these rules, the results on any -particular implementation are entirely unpredictable. -.Sp -Examples of code with undefined behavior are \f(CW\*(C`a = a++;\*(C'\fR, \f(CW\*(C`a[n] -= b[n++]\*(C'\fR and \f(CW\*(C`a[i++] = i;\*(C'\fR. Some more complicated cases are not -diagnosed by this option, and it may give an occasional false positive -result, but in general it has been found fairly effective at detecting -this sort of problem in programs. -.Sp -The present implementation of this option only works for C programs. A -future implementation may also work for \*(C+ programs. -.Sp -The C standard is worded confusingly, therefore there is some debate -over the precise meaning of the sequence point rules in subtle cases. -Links to discussions of the problem, including proposed formal -definitions, may be found on our readings page, at -<\fBhttp://gcc.gnu.org/readings.html\fR>. -.Ip "\fB\-Wreturn-type\fR" 4 -.IX Item "-Wreturn-type" -Warn whenever a function is defined with a return-type that defaults to -\&\f(CW\*(C`int\*(C'\fR. Also warn about any \f(CW\*(C`return\*(C'\fR statement with no -return-value in a function whose return-type is not \f(CW\*(C`void\*(C'\fR. -.Sp -For \*(C+, a function without return type always produces a diagnostic -message, even when \fB\-Wno-return-type\fR is specified. The only -exceptions are \fBmain\fR and functions defined in system headers. -.Ip "\fB\-Wswitch\fR" 4 -.IX Item "-Wswitch" -Warn whenever a \f(CW\*(C`switch\*(C'\fR statement has an index of enumeral type -and lacks a \f(CW\*(C`case\*(C'\fR for one or more of the named codes of that -enumeration. (The presence of a \f(CW\*(C`default\*(C'\fR label prevents this -warning.) \f(CW\*(C`case\*(C'\fR labels outside the enumeration range also -provoke warnings when this option is used. -.Ip "\fB\-Wtrigraphs\fR" 4 -.IX Item "-Wtrigraphs" -Warn if any trigraphs are encountered that might change the meaning of -the program (trigraphs within comments are not warned about). -.Ip "\fB\-Wunused-function\fR" 4 -.IX Item "-Wunused-function" -Warn whenever a static function is declared but not defined or a -non\e-inline static function is unused. -.Ip "\fB\-Wunused-label\fR" 4 -.IX Item "-Wunused-label" -Warn whenever a label is declared but not used. -.Sp -To suppress this warning use the \fBunused\fR attribute. -.Ip "\fB\-Wunused-parameter\fR" 4 -.IX Item "-Wunused-parameter" -Warn whenever a function parameter is unused aside from its declaration. -.Sp -To suppress this warning use the \fBunused\fR attribute. -.Ip "\fB\-Wunused-variable\fR" 4 -.IX Item "-Wunused-variable" -Warn whenever a local variable or non-constant static variable is unused -aside from its declaration -.Sp -To suppress this warning use the \fBunused\fR attribute. -.Ip "\fB\-Wunused-value\fR" 4 -.IX Item "-Wunused-value" -Warn whenever a statement computes a result that is explicitly not used. -.Sp -To suppress this warning cast the expression to \fBvoid\fR. -.Ip "\fB\-Wunused\fR" 4 -.IX Item "-Wunused" -All all the above \fB\-Wunused\fR options combined. -.Sp -In order to get a warning about an unused function parameter, you must -either specify \fB\-W \-Wunused\fR or separately specify -\&\fB\-Wunused-parameter\fR. -.Ip "\fB\-Wuninitialized\fR" 4 -.IX Item "-Wuninitialized" -Warn if an automatic variable is used without first being initialized or -if a variable may be clobbered by a \f(CW\*(C`setjmp\*(C'\fR call. -.Sp -These warnings are possible only in optimizing compilation, -because they require data flow information that is computed only -when optimizing. If you don't specify \fB\-O\fR, you simply won't -get these warnings. -.Sp -These warnings occur only for variables that are candidates for -register allocation. Therefore, they do not occur for a variable that -is declared \f(CW\*(C`volatile\*(C'\fR, or whose address is taken, or whose size -is other than 1, 2, 4 or 8 bytes. Also, they do not occur for -structures, unions or arrays, even when they are in registers. -.Sp -Note that there may be no warning about a variable that is used only -to compute a value that itself is never used, because such -computations may be deleted by data flow analysis before the warnings -are printed. -.Sp -These warnings are made optional because \s-1GCC\s0 is not smart -enough to see all the reasons why the code might be correct -despite appearing to have an error. Here is one example of how -this can happen: -.Sp -.Vb 12 -\& { -\& int x; -\& switch (y) -\& { -\& case 1: x = 1; -\& break; -\& case 2: x = 4; -\& break; -\& case 3: x = 5; -\& } -\& foo (x); -\& } -.Ve -If the value of \f(CW\*(C`y\*(C'\fR is always 1, 2 or 3, then \f(CW\*(C`x\*(C'\fR is -always initialized, but \s-1GCC\s0 doesn't know this. Here is -another common case: -.Sp -.Vb 6 -\& { -\& int save_y; -\& if (change_y) save_y = y, y = new_y; -\& ... -\& if (change_y) y = save_y; -\& } -.Ve -This has no bug because \f(CW\*(C`save_y\*(C'\fR is used only if it is set. -.Sp -This option also warns when a non-volatile automatic variable might be -changed by a call to \f(CW\*(C`longjmp\*(C'\fR. These warnings as well are possible -only in optimizing compilation. -.Sp -The compiler sees only the calls to \f(CW\*(C`setjmp\*(C'\fR. It cannot know -where \f(CW\*(C`longjmp\*(C'\fR will be called; in fact, a signal handler could -call it at any point in the code. As a result, you may get a warning -even when there is in fact no problem because \f(CW\*(C`longjmp\*(C'\fR cannot -in fact be called at the place which would cause a problem. -.Sp -Some spurious warnings can be avoided if you declare all the functions -you use that never return as \f(CW\*(C`noreturn\*(C'\fR. -.Ip "\fB\-Wreorder\fR (\*(C+ only)" 4 -.IX Item "-Wreorder ( only)" -Warn when the order of member initializers given in the code does not -match the order in which they must be executed. For instance: -.Ip "\fB\-Wunknown-pragmas\fR" 4 -.IX Item "-Wunknown-pragmas" -Warn when a #pragma directive is encountered which is not understood by -\&\s-1GCC\s0. If this command line option is used, warnings will even be issued -for unknown pragmas in system header files. This is not the case if -the warnings were only enabled by the \fB\-Wall\fR command line option. -.Ip "\fB\-Wall\fR" 4 -.IX Item "-Wall" -All of the above \fB\-W\fR options combined. This enables all the -warnings about constructions that some users consider questionable, and -that are easy to avoid (or modify to prevent the warning), even in -conjunction with macros. -.Ip "\fB\-Wdiv-by-zero\fR" 4 -.IX Item "-Wdiv-by-zero" -Warn about compile-time integer division by zero. This is default. To -inhibit the warning messages, use \fB\-Wno-div-by-zero\fR. Floating -point division by zero is not warned about, as it can be a legitimate -way of obtaining infinities and NaNs. -.Ip "\fB\-Wmultichar\fR" 4 -.IX Item "-Wmultichar" -Warn if a multicharacter constant (\fB'\s-1FOOF\s0'\fR) is used. This is -default. To inhibit the warning messages, use \fB\-Wno-multichar\fR. -Usually they indicate a typo in the user's code, as they have -implementation-defined values, and should not be used in portable code. -.Ip "\fB\-Wsystem-headers\fR" 4 -.IX Item "-Wsystem-headers" -Print warning messages for constructs found in system header files. -Warnings from system headers are normally suppressed, on the assumption -that they usually do not indicate real problems and would only make the -compiler output harder to read. Using this command line option tells -\&\s-1GCC\s0 to emit warnings from system headers as if they occurred in user -code. However, note that using \fB\-Wall\fR in conjunction with this -option will \fInot\fR warn about unknown pragmas in system -headers\-\-\-for that, \fB\-Wunknown-pragmas\fR must also be used. -.PP -The following \fB\-W...\fR options are not implied by \fB\-Wall\fR. -Some of them warn about constructions that users generally do not -consider questionable, but which occasionally you might wish to check -for; others warn about constructions that are necessary or hard to avoid -in some cases, and there is no simple way to modify the code to suppress -the warning. -.Ip "\fB\-W\fR" 4 -.IX Item "-W" -Print extra warning messages for these events: -.RS 4 -.Ip "\(bu" 4 -A function can return either with or without a value. (Falling -off the end of the function body is considered returning without -a value.) For example, this function would evoke such a -warning: -.Sp -.Vb 5 -\& foo (a) -\& { -\& if (a > 0) -\& return a; -\& } -.Ve -.Ip "\(bu" 4 -An expression-statement or the left-hand side of a comma expression -contains no side effects. -To suppress the warning, cast the unused expression to void. -For example, an expression such as \fBx[i,j]\fR will cause a warning, -but \fBx[(void)i,j]\fR will not. -.Ip "\(bu" 4 -An unsigned value is compared against zero with \fB<\fR or \fB<=\fR. -.Ip "\(bu" 4 -A comparison like \fBx<=y<=z\fR appears; this is equivalent to -\&\fB(x<=y ? 1 : 0) <= z\fR, which is a different interpretation from -that of ordinary mathematical notation. -.Ip "\(bu" 4 -Storage-class specifiers like \f(CW\*(C`static\*(C'\fR are not the first things in -a declaration. According to the C Standard, this usage is obsolescent. -.Ip "\(bu" 4 -The return type of a function has a type qualifier such as \f(CW\*(C`const\*(C'\fR. -Such a type qualifier has no effect, since the value returned by a -function is not an lvalue. (But don't warn about the \s-1GNU\s0 extension of -\&\f(CW\*(C`volatile void\*(C'\fR return types. That extension will be warned about -if \fB\-pedantic\fR is specified.) -.Ip "\(bu" 4 -If \fB\-Wall\fR or \fB\-Wunused\fR is also specified, warn about unused -arguments. -.Ip "\(bu" 4 -A comparison between signed and unsigned values could produce an -incorrect result when the signed value is converted to unsigned. -(But don't warn if \fB\-Wno-sign-compare\fR is also specified.) -.Ip "\(bu" 4 -An aggregate has a partly bracketed initializer. -For example, the following code would evoke such a warning, -because braces are missing around the initializer for \f(CW\*(C`x.h\*(C'\fR: -.Sp -.Vb 3 -\& struct s { int f, g; }; -\& struct t { struct s h; int i; }; -\& struct t x = { 1, 2, 3 }; -.Ve -.Ip "\(bu" 4 -An aggregate has an initializer which does not initialize all members. -For example, the following code would cause such a warning, because -\&\f(CW\*(C`x.h\*(C'\fR would be implicitly initialized to zero: -.Sp -.Vb 2 -\& struct s { int f, g, h; }; -\& struct s x = { 3, 4 }; -.Ve -.RE -.RS 4 -.RE -.Ip "\fB\-Wfloat-equal\fR" 4 -.IX Item "-Wfloat-equal" -Warn if floating point values are used in equality comparisons. -.Sp -The idea behind this is that sometimes it is convenient (for the -programmer) to consider floating-point values as approximations to -infinitely precise real numbers. If you are doing this, then you need -to compute (by analysing the code, or in some other way) the maximum or -likely maximum error that the computation introduces, and allow for it -when performing comparisons (and when producing output, but that's a -different problem). In particular, instead of testing for equality, you -would check to see whether the two values have ranges that overlap; and -this is done with the relational operators, so equality comparisons are -probably mistaken. -.Ip "\fB\-Wtraditional\fR (C only)" 4 -.IX Item "-Wtraditional (C only)" -Warn about certain constructs that behave differently in traditional and -\&\s-1ISO\s0 C. Also warn about \s-1ISO\s0 C constructs that have no traditional C -equivalent, and/or problematic constructs which should be avoided. -.RS 4 -.Ip "\(bu" 4 -Macro parameters that appear within string literals in the macro body. -In traditional C macro replacement takes place within string literals, -but does not in \s-1ISO\s0 C. -.Ip "\(bu" 4 -In traditional C, some preprocessor directives did not exist. -Traditional preprocessors would only consider a line to be a directive -if the \fB#\fR appeared in column 1 on the line. Therefore -\&\fB\-Wtraditional\fR warns about directives that traditional C -understands but would ignore because the \fB#\fR does not appear as the -first character on the line. It also suggests you hide directives like -\&\fB#pragma\fR not understood by traditional C by indenting them. Some -traditional implementations would not recognize \fB#elif\fR, so it -suggests avoiding it altogether. -.Ip "\(bu" 4 -A function-like macro that appears without arguments. -.Ip "\(bu" 4 -The unary plus operator. -.Ip "\(bu" 4 -The \fBU\fR integer constant suffix, or the \fBF\fR or \fBL\fR floating point -constant suffixes. (Traditional C does support the \fBL\fR suffix on integer -constants.) Note, these suffixes appear in macros defined in the system -headers of most modern systems, e.g. the \fB_MIN\fR/\fB_MAX\fR macros in \f(CW\*(C`<limits.h>\*(C'\fR. -Use of these macros in user code might normally lead to spurious -warnings, however gcc's integrated preprocessor has enough context to -avoid warning in these cases. -.Ip "\(bu" 4 -A function declared external in one block and then used after the end of -the block. -.Ip "\(bu" 4 -A \f(CW\*(C`switch\*(C'\fR statement has an operand of type \f(CW\*(C`long\*(C'\fR. -.Ip "\(bu" 4 -A non-\f(CW\*(C`static\*(C'\fR function declaration follows a \f(CW\*(C`static\*(C'\fR one. -This construct is not accepted by some traditional C compilers. -.Ip "\(bu" 4 -The \s-1ISO\s0 type of an integer constant has a different width or -signedness from its traditional type. This warning is only issued if -the base of the constant is ten. I.e. hexadecimal or octal values, which -typically represent bit patterns, are not warned about. -.Ip "\(bu" 4 -Usage of \s-1ISO\s0 string concatenation is detected. -.Ip "\(bu" 4 -Initialization of automatic aggregates. -.Ip "\(bu" 4 -Identifier conflicts with labels. Traditional C lacks a separate -namespace for labels. -.Ip "\(bu" 4 -Initialization of unions. If the initializer is zero, the warning is -omitted. This is done under the assumption that the zero initializer in -user code appears conditioned on e.g. \f(CW\*(C`_\|_STDC_\|_\*(C'\fR to avoid missing -initializer warnings and relies on default initialization to zero in the -traditional C case. -.Ip "\(bu" 4 -Conversions by prototypes between fixed/floating point values and vice -versa. The absence of these prototypes when compiling with traditional -C would cause serious problems. This is a subset of the possible -conversion warnings, for the full set use \fB\-Wconversion\fR. -.RE -.RS 4 -.RE -.Ip "\fB\-Wundef\fR" 4 -.IX Item "-Wundef" -Warn if an undefined identifier is evaluated in an \fB#if\fR directive. -.Ip "\fB\-Wshadow\fR" 4 -.IX Item "-Wshadow" -Warn whenever a local variable shadows another local variable, parameter or -global variable or whenever a built-in function is shadowed. -.Ip "\fB\-Wlarger-than-\fR\fIlen\fR" 4 -.IX Item "-Wlarger-than-len" -Warn whenever an object of larger than \fIlen\fR bytes is defined. -.Ip "\fB\-Wpointer-arith\fR" 4 -.IX Item "-Wpointer-arith" -Warn about anything that depends on the ``size of'' a function type or -of \f(CW\*(C`void\*(C'\fR. \s-1GNU\s0 C assigns these types a size of 1, for -convenience in calculations with \f(CW\*(C`void *\*(C'\fR pointers and pointers -to functions. -.Ip "\fB\-Wbad-function-cast\fR (C only)" 4 -.IX Item "-Wbad-function-cast (C only)" -Warn whenever a function call is cast to a non-matching type. -For example, warn if \f(CW\*(C`int malloc()\*(C'\fR is cast to \f(CW\*(C`anything *\*(C'\fR. -.Ip "\fB\-Wcast-qual\fR" 4 -.IX Item "-Wcast-qual" -Warn whenever a pointer is cast so as to remove a type qualifier from -the target type. For example, warn if a \f(CW\*(C`const char *\*(C'\fR is cast -to an ordinary \f(CW\*(C`char *\*(C'\fR. -.Ip "\fB\-Wcast-align\fR" 4 -.IX Item "-Wcast-align" -Warn whenever a pointer is cast such that the required alignment of the -target is increased. For example, warn if a \f(CW\*(C`char *\*(C'\fR is cast to -an \f(CW\*(C`int *\*(C'\fR on machines where integers can only be accessed at -two- or four-byte boundaries. -.Ip "\fB\-Wwrite-strings\fR" 4 -.IX Item "-Wwrite-strings" -When compiling C, give string constants the type \f(CW\*(C`const -char[\f(CIlength\f(CW]\*(C'\fR so that -copying the address of one into a non-\f(CW\*(C`const\*(C'\fR \f(CW\*(C`char *\*(C'\fR -pointer will get a warning; when compiling \*(C+, warn about the -deprecated conversion from string constants to \f(CW\*(C`char *\*(C'\fR. -These warnings will help you find at -compile time code that can try to write into a string constant, but -only if you have been very careful about using \f(CW\*(C`const\*(C'\fR in -declarations and prototypes. Otherwise, it will just be a nuisance; -this is why we did not make \fB\-Wall\fR request these warnings. -.Ip "\fB\-Wconversion\fR" 4 -.IX Item "-Wconversion" -Warn if a prototype causes a type conversion that is different from what -would happen to the same argument in the absence of a prototype. This -includes conversions of fixed point to floating and vice versa, and -conversions changing the width or signedness of a fixed point argument -except when the same as the default promotion. -.Sp -Also, warn if a negative integer constant expression is implicitly -converted to an unsigned type. For example, warn about the assignment -\&\f(CW\*(C`x = \-1\*(C'\fR if \f(CW\*(C`x\*(C'\fR is unsigned. But do not warn about explicit -casts like \f(CW\*(C`(unsigned) \-1\*(C'\fR. -.Ip "\fB\-Wsign-compare\fR" 4 -.IX Item "-Wsign-compare" -Warn when a comparison between signed and unsigned values could produce -an incorrect result when the signed value is converted to unsigned. -This warning is also enabled by \fB\-W\fR; to get the other warnings -of \fB\-W\fR without this warning, use \fB\-W \-Wno-sign-compare\fR. -.Ip "\fB\-Waggregate-return\fR" 4 -.IX Item "-Waggregate-return" -Warn if any functions that return structures or unions are defined or -called. (In languages where you can return an array, this also elicits -a warning.) -.Ip "\fB\-Wstrict-prototypes\fR (C only)" 4 -.IX Item "-Wstrict-prototypes (C only)" -Warn if a function is declared or defined without specifying the -argument types. (An old-style function definition is permitted without -a warning if preceded by a declaration which specifies the argument -types.) -.Ip "\fB\-Wmissing-prototypes\fR (C only)" 4 -.IX Item "-Wmissing-prototypes (C only)" -Warn if a global function is defined without a previous prototype -declaration. This warning is issued even if the definition itself -provides a prototype. The aim is to detect global functions that fail -to be declared in header files. -.Ip "\fB\-Wmissing-declarations\fR" 4 -.IX Item "-Wmissing-declarations" -Warn if a global function is defined without a previous declaration. -Do so even if the definition itself provides a prototype. -Use this option to detect global functions that are not declared in -header files. -.Ip "\fB\-Wmissing-noreturn\fR" 4 -.IX Item "-Wmissing-noreturn" -Warn about functions which might be candidates for attribute \f(CW\*(C`noreturn\*(C'\fR. -Note these are only possible candidates, not absolute ones. Care should -be taken to manually verify functions actually do not ever return before -adding the \f(CW\*(C`noreturn\*(C'\fR attribute, otherwise subtle code generation -bugs could be introduced. You will not get a warning for \f(CW\*(C`main\*(C'\fR in -hosted C environments. -.Ip "\fB\-Wmissing-format-attribute\fR" 4 -.IX Item "-Wmissing-format-attribute" -If \fB\-Wformat\fR is enabled, also warn about functions which might be -candidates for \f(CW\*(C`format\*(C'\fR attributes. Note these are only possible -candidates, not absolute ones. \s-1GCC\s0 will guess that \f(CW\*(C`format\*(C'\fR -attributes might be appropriate for any function that calls a function -like \f(CW\*(C`vprintf\*(C'\fR or \f(CW\*(C`vscanf\*(C'\fR, but this might not always be the -case, and some functions for which \f(CW\*(C`format\*(C'\fR attributes are -appropriate may not be detected. This option has no effect unless -\&\fB\-Wformat\fR is enabled (possibly by \fB\-Wall\fR). -.Ip "\fB\-Wno-deprecated-declarations\fR" 4 -.IX Item "-Wno-deprecated-declarations" -Do not warn about uses of functions, variables, and types marked as -deprecated by using the \f(CW\*(C`deprecated\*(C'\fR attribute. -(@pxref{Function Attributes}, \f(CW@pxref\fR{Variable Attributes}, -\&\f(CW@pxref\fR{Type Attributes}.) -.Ip "\fB\-Wpacked\fR" 4 -.IX Item "-Wpacked" -Warn if a structure is given the packed attribute, but the packed -attribute has no effect on the layout or size of the structure. -Such structures may be mis-aligned for little benefit. For -instance, in this code, the variable \f(CW\*(C`f.x\*(C'\fR in \f(CW\*(C`struct bar\*(C'\fR -will be misaligned even though \f(CW\*(C`struct bar\*(C'\fR does not itself -have the packed attribute: -.Sp -.Vb 8 -\& struct foo { -\& int x; -\& char a, b, c, d; -\& } __attribute__((packed)); -\& struct bar { -\& char z; -\& struct foo f; -\& }; -.Ve -.Ip "\fB\-Wpadded\fR" 4 -.IX Item "-Wpadded" -Warn if padding is included in a structure, either to align an element -of the structure or to align the whole structure. Sometimes when this -happens it is possible to rearrange the fields of the structure to -reduce the padding and so make the structure smaller. -.Ip "\fB\-Wredundant-decls\fR" 4 -.IX Item "-Wredundant-decls" -Warn if anything is declared more than once in the same scope, even in -cases where multiple declaration is valid and changes nothing. -.Ip "\fB\-Wnested-externs\fR (C only)" 4 -.IX Item "-Wnested-externs (C only)" -Warn if an \f(CW\*(C`extern\*(C'\fR declaration is encountered within a function. -.Ip "\fB\-Wunreachable-code\fR" 4 -.IX Item "-Wunreachable-code" -Warn if the compiler detects that code will never be executed. -.Sp -This option is intended to warn when the compiler detects that at -least a whole line of source code will never be executed, because -some condition is never satisfied or because it is after a -procedure that never returns. -.Sp -It is possible for this option to produce a warning even though there -are circumstances under which part of the affected line can be executed, -so care should be taken when removing apparently-unreachable code. -.Sp -For instance, when a function is inlined, a warning may mean that the -line is unreachable in only one inlined copy of the function. -.Sp -This option is not made part of \fB\-Wall\fR because in a debugging -version of a program there is often substantial code which checks -correct functioning of the program and is, hopefully, unreachable -because the program does work. Another common use of unreachable -code is to provide behavior which is selectable at compile-time. -.Ip "\fB\-Winline\fR" 4 -.IX Item "-Winline" -Warn if a function can not be inlined and it was declared as inline. -.Ip "\fB\-Wlong-long\fR" 4 -.IX Item "-Wlong-long" -Warn if \fBlong long\fR type is used. This is default. To inhibit -the warning messages, use \fB\-Wno-long-long\fR. Flags -\&\fB\-Wlong-long\fR and \fB\-Wno-long-long\fR are taken into account -only when \fB\-pedantic\fR flag is used. -.Ip "\fB\-Wdisabled-optimization\fR" 4 -.IX Item "-Wdisabled-optimization" -Warn if a requested optimization pass is disabled. This warning does -not generally indicate that there is anything wrong with your code; it -merely indicates that \s-1GCC\s0's optimizers were unable to handle the code -effectively. Often, the problem is that your code is too big or too -complex; \s-1GCC\s0 will refuse to optimize programs when the optimization -itself is likely to take inordinate amounts of time. -.Ip "\fB\-Werror\fR" 4 -.IX Item "-Werror" -Make all warnings into errors. -.Sh "Options for Debugging Your Program or \s-1GCC\s0" -.IX Subsection "Options for Debugging Your Program or GCC" -\&\s-1GCC\s0 has various special options that are used for debugging -either your program or \s-1GCC:\s0 -.Ip "\fB\-g\fR" 4 -.IX Item "-g" -Produce debugging information in the operating system's native format -(stabs, \s-1COFF\s0, \s-1XCOFF\s0, or \s-1DWARF\s0). \s-1GDB\s0 can work with this debugging -information. -.Sp -On most systems that use stabs format, \fB\-g\fR enables use of extra -debugging information that only \s-1GDB\s0 can use; this extra information -makes debugging work better in \s-1GDB\s0 but will probably make other debuggers -crash or -refuse to read the program. If you want to control for certain whether -to generate the extra information, use \fB\-gstabs+\fR, \fB\-gstabs\fR, -\&\fB\-gxcoff+\fR, \fB\-gxcoff\fR, \fB\-gdwarf-1+\fR, \fB\-gdwarf-1\fR, -or \fB\-gvms\fR (see below). -.Sp -Unlike most other C compilers, \s-1GCC\s0 allows you to use \fB\-g\fR with -\&\fB\-O\fR. The shortcuts taken by optimized code may occasionally -produce surprising results: some variables you declared may not exist -at all; flow of control may briefly move where you did not expect it; -some statements may not be executed because they compute constant -results or their values were already at hand; some statements may -execute in different places because they were moved out of loops. -.Sp -Nevertheless it proves possible to debug optimized output. This makes -it reasonable to use the optimizer for programs that might have bugs. -.Sp -The following options are useful when \s-1GCC\s0 is generated with the -capability for more than one debugging format. -.Ip "\fB\-ggdb\fR" 4 -.IX Item "-ggdb" -Produce debugging information for use by \s-1GDB\s0. This means to use the -most expressive format available (\s-1DWARF\s0 2, stabs, or the native format -if neither of those are supported), including \s-1GDB\s0 extensions if at all -possible. -.Ip "\fB\-gstabs\fR" 4 -.IX Item "-gstabs" -Produce debugging information in stabs format (if that is supported), -without \s-1GDB\s0 extensions. This is the format used by \s-1DBX\s0 on most \s-1BSD\s0 -systems. On \s-1MIPS\s0, Alpha and System V Release 4 systems this option -produces stabs debugging output which is not understood by \s-1DBX\s0 or \s-1SDB\s0. -On System V Release 4 systems this option requires the \s-1GNU\s0 assembler. -.Ip "\fB\-gstabs+\fR" 4 -.IX Item "-gstabs+" -Produce debugging information in stabs format (if that is supported), -using \s-1GNU\s0 extensions understood only by the \s-1GNU\s0 debugger (\s-1GDB\s0). The -use of these extensions is likely to make other debuggers crash or -refuse to read the program. -.Ip "\fB\-gcoff\fR" 4 -.IX Item "-gcoff" -Produce debugging information in \s-1COFF\s0 format (if that is supported). -This is the format used by \s-1SDB\s0 on most System V systems prior to -System V Release 4. -.Ip "\fB\-gxcoff\fR" 4 -.IX Item "-gxcoff" -Produce debugging information in \s-1XCOFF\s0 format (if that is supported). -This is the format used by the \s-1DBX\s0 debugger on \s-1IBM\s0 \s-1RS/6000\s0 systems. -.Ip "\fB\-gxcoff+\fR" 4 -.IX Item "-gxcoff+" -Produce debugging information in \s-1XCOFF\s0 format (if that is supported), -using \s-1GNU\s0 extensions understood only by the \s-1GNU\s0 debugger (\s-1GDB\s0). The -use of these extensions is likely to make other debuggers crash or -refuse to read the program, and may cause assemblers other than the \s-1GNU\s0 -assembler (\s-1GAS\s0) to fail with an error. -.Ip "\fB\-gdwarf\fR" 4 -.IX Item "-gdwarf" -Produce debugging information in \s-1DWARF\s0 version 1 format (if that is -supported). This is the format used by \s-1SDB\s0 on most System V Release 4 -systems. -.Ip "\fB\-gdwarf+\fR" 4 -.IX Item "-gdwarf+" -Produce debugging information in \s-1DWARF\s0 version 1 format (if that is -supported), using \s-1GNU\s0 extensions understood only by the \s-1GNU\s0 debugger -(\s-1GDB\s0). The use of these extensions is likely to make other debuggers -crash or refuse to read the program. -.Ip "\fB\-gdwarf-2\fR" 4 -.IX Item "-gdwarf-2" -Produce debugging information in \s-1DWARF\s0 version 2 format (if that is -supported). This is the format used by \s-1DBX\s0 on \s-1IRIX\s0 6. -.Ip "\fB\-gvms\fR" 4 -.IX Item "-gvms" -Produce debugging information in \s-1VMS\s0 debug format (if that is -supported). This is the format used by \s-1DEBUG\s0 on \s-1VMS\s0 systems. -.Ip "\fB\-g\fR\fIlevel\fR" 4 -.IX Item "-glevel" -.PD 0 -.Ip "\fB\-ggdb\fR\fIlevel\fR" 4 -.IX Item "-ggdblevel" -.Ip "\fB\-gstabs\fR\fIlevel\fR" 4 -.IX Item "-gstabslevel" -.Ip "\fB\-gcoff\fR\fIlevel\fR" 4 -.IX Item "-gcofflevel" -.Ip "\fB\-gxcoff\fR\fIlevel\fR" 4 -.IX Item "-gxcofflevel" -.Ip "\fB\-gvms\fR\fIlevel\fR" 4 -.IX Item "-gvmslevel" -.PD -Request debugging information and also use \fIlevel\fR to specify how -much information. The default level is 2. -.Sp -Level 1 produces minimal information, enough for making backtraces in -parts of the program that you don't plan to debug. This includes -descriptions of functions and external variables, but no information -about local variables and no line numbers. -.Sp -Level 3 includes extra information, such as all the macro definitions -present in the program. Some debuggers support macro expansion when -you use \fB\-g3\fR. -.Sp -Note that in order to avoid confusion between \s-1DWARF1\s0 debug level 2, -and \s-1DWARF2\s0, neither \fB\-gdwarf\fR nor \fB\-gdwarf-2\fR accept -a concatenated debug level. Instead use an additional \fB\-g\fR\fIlevel\fR -option to change the debug level for \s-1DWARF1\s0 or \s-1DWARF2\s0. -.Ip "\fB\-p\fR" 4 -.IX Item "-p" -Generate extra code to write profile information suitable for the -analysis program \f(CW\*(C`prof\*(C'\fR. You must use this option when compiling -the source files you want data about, and you must also use it when -linking. -.Ip "\fB\-pg\fR" 4 -.IX Item "-pg" -Generate extra code to write profile information suitable for the -analysis program \f(CW\*(C`gprof\*(C'\fR. You must use this option when compiling -the source files you want data about, and you must also use it when -linking. -.Ip "\fB\-Q\fR" 4 -.IX Item "-Q" -Makes the compiler print out each function name as it is compiled, and -print some statistics about each pass when it finishes. -.Ip "\fB\-ftime-report\fR" 4 -.IX Item "-ftime-report" -Makes the compiler print some statistics about the time consumed by each -pass when it finishes. -.Ip "\fB\-fmem-report\fR" 4 -.IX Item "-fmem-report" -Makes the compiler print some statistics about permanent memory -allocation when it finishes. -.Ip "\fB\-fprofile-arcs\fR" 4 -.IX Item "-fprofile-arcs" -Instrument \fIarcs\fR during compilation to generate coverage data -or for profile-directed block ordering. During execution the program -records how many times each branch is executed and how many times it is -taken. When the compiled program exits it saves this data to a file -called \fI\fIsourcename\fI.da\fR for each source file. -.Sp -For profile-directed block ordering, compile the program with -\&\fB\-fprofile-arcs\fR plus optimization and code generation options, -generate the arc profile information by running the program on a -selected workload, and then compile the program again with the same -optimization and code generation options plus -\&\fB\-fbranch-probabilities\fR. -.Sp -The other use of \fB\-fprofile-arcs\fR is for use with \f(CW\*(C`gcov\*(C'\fR, -when it is used with the \fB\-ftest-coverage\fR option. -.Sp -With \fB\-fprofile-arcs\fR, for each function of your program \s-1GCC\s0 -creates a program flow graph, then finds a spanning tree for the graph. -Only arcs that are not on the spanning tree have to be instrumented: the -compiler adds code to count the number of times that these arcs are -executed. When an arc is the only exit or only entrance to a block, the -instrumentation code can be added to the block; otherwise, a new basic -block must be created to hold the instrumentation code. -.Ip "\fB\-ftest-coverage\fR" 4 -.IX Item "-ftest-coverage" -Create data files for the \fBgcov\fR code-coverage utility. -The data file names begin with the name of your source file: -.RS 4 -.Ip "\fIsourcename\fR\fB.bb\fR" 4 -.IX Item "sourcename.bb" -A mapping from basic blocks to line numbers, which \f(CW\*(C`gcov\*(C'\fR uses to -associate basic block execution counts with line numbers. -.Ip "\fIsourcename\fR\fB.bbg\fR" 4 -.IX Item "sourcename.bbg" -A list of all arcs in the program flow graph. This allows \f(CW\*(C`gcov\*(C'\fR -to reconstruct the program flow graph, so that it can compute all basic -block and arc execution counts from the information in the -\&\f(CW\*(C`\f(CIsourcename\f(CW.da\*(C'\fR file. -.RE -.RS 4 -.Sp -Use \fB\-ftest-coverage\fR with \fB\-fprofile-arcs\fR; the latter -option adds instrumentation to the program, which then writes -execution counts to another data file: -.RS 4 -.RE -.Ip "\fIsourcename\fR\fB.da\fR" 4 -.IX Item "sourcename.da" -Runtime arc execution counts, used in conjunction with the arc -information in the file \f(CW\*(C`\f(CIsourcename\f(CW.bbg\*(C'\fR. -.RE -.RS 4 -.Sp -Coverage data will map better to the source files if -\&\fB\-ftest-coverage\fR is used without optimization. -.RE -.Ip "\fB\-d\fR\fIletters\fR" 4 -.IX Item "-dletters" -Says to make debugging dumps during compilation at times specified by -\&\fIletters\fR. This is used for debugging the compiler. The file names -for most of the dumps are made by appending a pass number and a word to -the source file name (e.g. \fIfoo.c.00.rtl\fR or \fIfoo.c.01.sibling\fR). -Here are the possible letters for use in \fIletters\fR, and their meanings: -.RS 4 -.Ip "\fBA\fR" 4 -.IX Item "A" -Annotate the assembler output with miscellaneous debugging information. -.Ip "\fBb\fR" 4 -.IX Item "b" -Dump after computing branch probabilities, to \fI\fIfile\fI.14.bp\fR. -.Ip "\fBB\fR" 4 -.IX Item "B" -Dump after block reordering, to \fI\fIfile\fI.29.bbro\fR. -.Ip "\fBc\fR" 4 -.IX Item "c" -Dump after instruction combination, to the file \fI\fIfile\fI.16.combine\fR. -.Ip "\fBC\fR" 4 -.IX Item "C" -Dump after the first if conversion, to the file \fI\fIfile\fI.17.ce\fR. -.Ip "\fBd\fR" 4 -.IX Item "d" -Dump after delayed branch scheduling, to \fI\fIfile\fI.31.dbr\fR. -.Ip "\fBD\fR" 4 -.IX Item "D" -Dump all macro definitions, at the end of preprocessing, in addition to -normal output. -.Ip "\fBe\fR" 4 -.IX Item "e" -Dump after \s-1SSA\s0 optimizations, to \fI\fIfile\fI.04.ssa\fR and -\&\fI\fIfile\fI.07.ussa\fR. -.Ip "\fBE\fR" 4 -.IX Item "E" -Dump after the second if conversion, to \fI\fIfile\fI.26.ce2\fR. -.Ip "\fBf\fR" 4 -.IX Item "f" -Dump after life analysis, to \fI\fIfile\fI.15.life\fR. -.Ip "\fBF\fR" 4 -.IX Item "F" -Dump after purging \f(CW\*(C`ADDRESSOF\*(C'\fR codes, to \fI\fIfile\fI.09.addressof\fR. -.Ip "\fBg\fR" 4 -.IX Item "g" -Dump after global register allocation, to \fI\fIfile\fI.21.greg\fR. -.Ip "\fBh\fR" 4 -.IX Item "h" -Dump after finalization of \s-1EH\s0 handling code, to \fI\fIfile\fI.02.eh\fR. -.Ip "\fBk\fR" 4 -.IX Item "k" -Dump after reg-to-stack conversion, to \fI\fIfile\fI.28.stack\fR. -.Ip "\fBo\fR" 4 -.IX Item "o" -Dump after post-reload optimizations, to \fI\fIfile\fI.22.postreload\fR. -.Ip "\fBG\fR" 4 -.IX Item "G" -Dump after \s-1GCSE\s0, to \fI\fIfile\fI.10.gcse\fR. -.Ip "\fBi\fR" 4 -.IX Item "i" -Dump after sibling call optimizations, to \fI\fIfile\fI.01.sibling\fR. -.Ip "\fBj\fR" 4 -.IX Item "j" -Dump after the first jump optimization, to \fI\fIfile\fI.03.jump\fR. -.Ip "\fBk\fR" 4 -.IX Item "k" -Dump after conversion from registers to stack, to \fI\fIfile\fI.32.stack\fR. -.Ip "\fBl\fR" 4 -.IX Item "l" -Dump after local register allocation, to \fI\fIfile\fI.20.lreg\fR. -.Ip "\fBL\fR" 4 -.IX Item "L" -Dump after loop optimization, to \fI\fIfile\fI.11.loop\fR. -.Ip "\fBM\fR" 4 -.IX Item "M" -Dump after performing the machine dependent reorganisation pass, to -\&\fI\fIfile\fI.30.mach\fR. -.Ip "\fBn\fR" 4 -.IX Item "n" -Dump after register renumbering, to \fI\fIfile\fI.25.rnreg\fR. -.Ip "\fBN\fR" 4 -.IX Item "N" -Dump after the register move pass, to \fI\fIfile\fI.18.regmove\fR. -.Ip "\fBr\fR" 4 -.IX Item "r" -Dump after \s-1RTL\s0 generation, to \fI\fIfile\fI.00.rtl\fR. -.Ip "\fBR\fR" 4 -.IX Item "R" -Dump after the second scheduling pass, to \fI\fIfile\fI.27.sched2\fR. -.Ip "\fBs\fR" 4 -.IX Item "s" -Dump after \s-1CSE\s0 (including the jump optimization that sometimes follows -\&\s-1CSE\s0), to \fI\fIfile\fI.08.cse\fR. -.Ip "\fBS\fR" 4 -.IX Item "S" -Dump after the first scheduling pass, to \fI\fIfile\fI.19.sched\fR. -.Ip "\fBt\fR" 4 -.IX Item "t" -Dump after the second \s-1CSE\s0 pass (including the jump optimization that -sometimes follows \s-1CSE\s0), to \fI\fIfile\fI.12.cse2\fR. -.Ip "\fBw\fR" 4 -.IX Item "w" -Dump after the second flow pass, to \fI\fIfile\fI.23.flow2\fR. -.Ip "\fBX\fR" 4 -.IX Item "X" -Dump after \s-1SSA\s0 dead code elimination, to \fI\fIfile\fI.06.ssadce\fR. -.Ip "\fBz\fR" 4 -.IX Item "z" -Dump after the peephole pass, to \fI\fIfile\fI.24.peephole2\fR. -.Ip "\fBa\fR" 4 -.IX Item "a" -Produce all the dumps listed above. -.Ip "\fBm\fR" 4 -.IX Item "m" -Print statistics on memory usage, at the end of the run, to -standard error. -.Ip "\fBp\fR" 4 -.IX Item "p" -Annotate the assembler output with a comment indicating which -pattern and alternative was used. The length of each instruction is -also printed. -.Ip "\fBP\fR" 4 -.IX Item "P" -Dump the \s-1RTL\s0 in the assembler output as a comment before each instruction. -Also turns on \fB\-dp\fR annotation. -.Ip "\fBv\fR" 4 -.IX Item "v" -For each of the other indicated dump files (except for -\&\fI\fIfile\fI.00.rtl\fR), dump a representation of the control flow graph -suitable for viewing with \s-1VCG\s0 to \fI\fIfile\fI.\fIpass\fI.vcg\fR. -.Ip "\fBx\fR" 4 -.IX Item "x" -Just generate \s-1RTL\s0 for a function instead of compiling it. Usually used -with \fBr\fR. -.Ip "\fBy\fR" 4 -.IX Item "y" -Dump debugging information during parsing, to standard error. -.RE -.RS 4 -.RE -.Ip "\fB\-fdump-unnumbered\fR" 4 -.IX Item "-fdump-unnumbered" -When doing debugging dumps (see \fB\-d\fR option above), suppress instruction -numbers and line number note output. This makes it more feasible to -use diff on debugging dumps for compiler invocations with different -options, in particular with and without \fB\-g\fR. -.Ip "\fB\-fdump-translation-unit\fR (C and \*(C+ only)" 4 -.IX Item "-fdump-translation-unit (C and only)" -.PD 0 -.Ip "\fB\-fdump-translation-unit-\fR\fIoptions\fR\fB \fR(C and \*(C+ only)" 4 -.IX Item "-fdump-translation-unit-options (C and only)" -.PD -Dump a representation of the tree structure for the entire translation -unit to a file. The file name is made by appending \fI.tu\fR to the -source file name. If the \fB-\fR\fIoptions\fR form is used, \fIoptions\fR -controls the details of the dump as described for the -\&\fB\-fdump-tree\fR options. -.Ip "\fB\-fdump-class-hierarchy\fR (\*(C+ only)" 4 -.IX Item "-fdump-class-hierarchy ( only)" -.PD 0 -.Ip "\fB\-fdump-class-hierarchy-\fR\fIoptions\fR\fB \fR(\*(C+ only)" 4 -.IX Item "-fdump-class-hierarchy-options ( only)" -.PD -Dump a representation of each class's hierarchy and virtual function -table layout to a file. The file name is made by appending \fI.class\fR -to the source file name. If the \fB-\fR\fIoptions\fR form is used, -\&\fIoptions\fR controls the details of the dump as described for the -\&\fB\-fdump-tree\fR options. -.Ip "\fB\-fdump-tree-\fR\fIswitch\fR\fB \fR(\*(C+ only)" 4 -.IX Item "-fdump-tree-switch ( only)" -.PD 0 -.Ip "\fB\-fdump-tree-\fR\fIswitch\fR\fB-\fR\fIoptions\fR\fB \fR(\*(C+ only)" 4 -.IX Item "-fdump-tree-switch-options ( only)" -.PD -Control the dumping at various stages of processing the intermediate -language tree to a file. The file name is generated by appending a switch -specific suffix to the source file name. If the \fB-\fR\fIoptions\fR -form is used, \fIoptions\fR is a list of \fB-\fR separated options that -control the details of the dump. Not all options are applicable to all -dumps, those which are not meaningful will be ignored. The following -options are available -.RS 4 -.Ip "\fBaddress\fR" 4 -.IX Item "address" -Print the address of each node. Usually this is not meaningful as it -changes according to the environment and source file. Its primary use -is for tying up a dump file with a debug environment. -.Ip "\fBslim\fR" 4 -.IX Item "slim" -Inhibit dumping of members of a scope or body of a function merely -because that scope has been reached. Only dump such items when they -are directly reachable by some other path. -.Ip "\fBall\fR" 4 -.IX Item "all" -Turn on all options. -.RE -.RS 4 -.Sp -The following tree dumps are possible: -.RS 4 -.RE -.Ip "\fBoriginal\fR" 4 -.IX Item "original" -Dump before any tree based optimization, to \fI\fIfile\fI.original\fR. -.Ip "\fBoptimized\fR" 4 -.IX Item "optimized" -Dump after all tree based optimization, to \fI\fIfile\fI.optimized\fR. -.Ip "\fBinlined\fR" 4 -.IX Item "inlined" -Dump after function inlining, to \fI\fIfile\fI.inlined\fR. -.RE -.RS 4 -.RE -.Ip "\fB\-fsched-verbose=\fR\fIn\fR" 4 -.IX Item "-fsched-verbose=n" -On targets that use instruction scheduling, this option controls the -amount of debugging output the scheduler prints. This information is -written to standard error, unless \fB\-dS\fR or \fB\-dR\fR is -specified, in which case it is output to the usual dump -listing file, \fI.sched\fR or \fI.sched2\fR respectively. However -for \fIn\fR greater than nine, the output is always printed to standard -error. -.Sp -For \fIn\fR greater than zero, \fB\-fsched-verbose\fR outputs the -same information as \fB\-dRS\fR. For \fIn\fR greater than one, it -also output basic block probabilities, detailed ready list information -and unit/insn info. For \fIn\fR greater than two, it includes \s-1RTL\s0 -at abort point, control-flow and regions info. And for \fIn\fR over -four, \fB\-fsched-verbose\fR also includes dependence info. -.Ip "\fB\-fpretend-float\fR" 4 -.IX Item "-fpretend-float" -When running a cross-compiler, pretend that the target machine uses the -same floating point format as the host machine. This causes incorrect -output of the actual floating constants, but the actual instruction -sequence will probably be the same as \s-1GCC\s0 would make when running on -the target machine. -.Ip "\fB\-save-temps\fR" 4 -.IX Item "-save-temps" -Store the usual ``temporary'' intermediate files permanently; place them -in the current directory and name them based on the source file. Thus, -compiling \fIfoo.c\fR with \fB\-c \-save-temps\fR would produce files -\&\fIfoo.i\fR and \fIfoo.s\fR, as well as \fIfoo.o\fR. This creates a -preprocessed \fIfoo.i\fR output file even though the compiler now -normally uses an integrated preprocessor. -.Ip "\fB\-time\fR" 4 -.IX Item "-time" -Report the \s-1CPU\s0 time taken by each subprocess in the compilation -sequence. For C source files, this is the compiler proper and assembler -(plus the linker if linking is done). The output looks like this: -.Sp -.Vb 2 -\& # cc1 0.12 0.01 -\& # as 0.00 0.01 -.Ve -The first number on each line is the ``user time,'' that is time spent -executing the program itself. The second number is ``system time,'' -time spent executing operating system routines on behalf of the program. -Both numbers are in seconds. -.Ip "\fB\-print-file-name=\fR\fIlibrary\fR" 4 -.IX Item "-print-file-name=library" -Print the full absolute name of the library file \fIlibrary\fR that -would be used when linking\-\-\-and don't do anything else. With this -option, \s-1GCC\s0 does not compile or link anything; it just prints the -file name. -.Ip "\fB\-print-multi-directory\fR" 4 -.IX Item "-print-multi-directory" -Print the directory name corresponding to the multilib selected by any -other switches present in the command line. This directory is supposed -to exist in \fB\s-1GCC_EXEC_PREFIX\s0\fR. -.Ip "\fB\-print-multi-lib\fR" 4 -.IX Item "-print-multi-lib" -Print the mapping from multilib directory names to compiler switches -that enable them. The directory name is separated from the switches by -\&\fB;\fR, and each switch starts with an \fB@} instead of the -\&\f(CB@samp\fB{-\fR, without spaces between multiple switches. This is supposed to -ease shell-processing. -.Ip "\fB\-print-prog-name=\fR\fIprogram\fR" 4 -.IX Item "-print-prog-name=program" -Like \fB\-print-file-name\fR, but searches for a program such as \fBcpp\fR. -.Ip "\fB\-print-libgcc-file-name\fR" 4 -.IX Item "-print-libgcc-file-name" -Same as \fB\-print-file-name=libgcc.a\fR. -.Sp -This is useful when you use \fB\-nostdlib\fR or \fB\-nodefaultlibs\fR -but you do want to link with \fIlibgcc.a\fR. You can do -.Sp -.Vb 1 -\& gcc -nostdlib <files>... `gcc -print-libgcc-file-name` -.Ve -.Ip "\fB\-print-search-dirs\fR" 4 -.IX Item "-print-search-dirs" -Print the name of the configured installation directory and a list of -program and library directories gcc will search\-\-\-and don't do anything else. -.Sp -This is useful when gcc prints the error message -\&\fBinstallation problem, cannot exec cpp0: No such file or directory\fR. -To resolve this you either need to put \fIcpp0\fR and the other compiler -components where gcc expects to find them, or you can set the environment -variable \fB\s-1GCC_EXEC_PREFIX\s0\fR to the directory where you installed them. -Don't forget the trailing '/'. -.Ip "\fB\-dumpmachine\fR" 4 -.IX Item "-dumpmachine" -Print the compiler's target machine (for example, -\&\fBi686\-pc-linux-gnu\fR)\-\-\-and don't do anything else. -.Ip "\fB\-dumpversion\fR" 4 -.IX Item "-dumpversion" -Print the compiler version (for example, \fB3.0\fR)\-\-\-and don't do -anything else. -.Ip "\fB\-dumpspecs\fR" 4 -.IX Item "-dumpspecs" -Print the compiler's built-in specs\-\-\-and don't do anything else. (This -is used when \s-1GCC\s0 itself is being built.) -.Sh "Options That Control Optimization" -.IX Subsection "Options That Control Optimization" -These options control various sorts of optimizations: -.Ip "\fB\-O\fR" 4 -.IX Item "-O" -.PD 0 -.Ip "\fB\-O1\fR" 4 -.IX Item "-O1" -.PD -Optimize. Optimizing compilation takes somewhat more time, and a lot -more memory for a large function. -.Sp -Without \fB\-O\fR, the compiler's goal is to reduce the cost of -compilation and to make debugging produce the expected results. -Statements are independent: if you stop the program with a breakpoint -between statements, you can then assign a new value to any variable or -change the program counter to any other statement in the function and -get exactly the results you would expect from the source code. -.Sp -With \fB\-O\fR, the compiler tries to reduce code size and execution -time, without performing any optimizations that take a great deal of -compilation time. -.Ip "\fB\-O2\fR" 4 -.IX Item "-O2" -Optimize even more. \s-1GCC\s0 performs nearly all supported optimizations -that do not involve a space-speed tradeoff. The compiler does not -perform loop unrolling or function inlining when you specify \fB\-O2\fR. -As compared to \fB\-O\fR, this option increases both compilation time -and the performance of the generated code. -.Sp -\&\fB\-O2\fR turns on all optional optimizations except for loop unrolling, -function inlining, and register renaming. It also turns on the -\&\fB\-fforce-mem\fR option on all machines and frame pointer elimination -on machines where doing so does not interfere with debugging. -.Sp -Please note the warning under \fB\-fgcse\fR about -invoking \fB\-O2\fR on programs that use computed gotos. -.Ip "\fB\-O3\fR" 4 -.IX Item "-O3" -Optimize yet more. \fB\-O3\fR turns on all optimizations specified by -\&\fB\-O2\fR and also turns on the \fB\-finline-functions\fR and -\&\fB\-frename-registers\fR options. -.Ip "\fB\-O0\fR" 4 -.IX Item "-O0" -Do not optimize. -.Ip "\fB\-Os\fR" 4 -.IX Item "-Os" -Optimize for size. \fB\-Os\fR enables all \fB\-O2\fR optimizations that -do not typically increase code size. It also performs further -optimizations designed to reduce code size. -.Sp -If you use multiple \fB\-O\fR options, with or without level numbers, -the last such option is the one that is effective. -.PP -Options of the form \fB\-f\fR\fIflag\fR specify machine-independent -flags. Most flags have both positive and negative forms; the negative -form of \fB\-ffoo\fR would be \fB\-fno-foo\fR. In the table below, -only one of the forms is listed\-\-\-the one which is not the default. -You can figure out the other form by either removing \fBno-\fR or -adding it. -.Ip "\fB\-ffloat-store\fR" 4 -.IX Item "-ffloat-store" -Do not store floating point variables in registers, and inhibit other -options that might change whether a floating point value is taken from a -register or memory. -.Sp -This option prevents undesirable excess precision on machines such as -the 68000 where the floating registers (of the 68881) keep more -precision than a \f(CW\*(C`double\*(C'\fR is supposed to have. Similarly for the -x86 architecture. For most programs, the excess precision does only -good, but a few programs rely on the precise definition of \s-1IEEE\s0 floating -point. Use \fB\-ffloat-store\fR for such programs, after modifying -them to store all pertinent intermediate computations into variables. -.Ip "\fB\-fno-default-inline\fR" 4 -.IX Item "-fno-default-inline" -Do not make member functions inline by default merely because they are -defined inside the class scope (\*(C+ only). Otherwise, when you specify -\&\fB\-O\fR, member functions defined inside class scope are compiled -inline by default; i.e., you don't need to add \fBinline\fR in front of -the member function name. -.Ip "\fB\-fno-defer-pop\fR" 4 -.IX Item "-fno-defer-pop" -Always pop the arguments to each function call as soon as that function -returns. For machines which must pop arguments after a function call, -the compiler normally lets arguments accumulate on the stack for several -function calls and pops them all at once. -.Ip "\fB\-fforce-mem\fR" 4 -.IX Item "-fforce-mem" -Force memory operands to be copied into registers before doing -arithmetic on them. This produces better code by making all memory -references potential common subexpressions. When they are not common -subexpressions, instruction combination should eliminate the separate -register-load. The \fB\-O2\fR option turns on this option. -.Ip "\fB\-fforce-addr\fR" 4 -.IX Item "-fforce-addr" -Force memory address constants to be copied into registers before -doing arithmetic on them. This may produce better code just as -\&\fB\-fforce-mem\fR may. -.Ip "\fB\-fomit-frame-pointer\fR" 4 -.IX Item "-fomit-frame-pointer" -Don't keep the frame pointer in a register for functions that -don't need one. This avoids the instructions to save, set up and -restore frame pointers; it also makes an extra register available -in many functions. \fBIt also makes debugging impossible on -some machines.\fR -.Sp -On some machines, such as the \s-1VAX\s0, this flag has no effect, because -the standard calling sequence automatically handles the frame pointer -and nothing is saved by pretending it doesn't exist. The -machine-description macro \f(CW\*(C`FRAME_POINTER_REQUIRED\*(C'\fR controls -whether a target machine supports this flag. -.Ip "\fB\-foptimize-sibling-calls\fR" 4 -.IX Item "-foptimize-sibling-calls" -Optimize sibling and tail recursive calls. -.Ip "\fB\-ftrapv\fR" 4 -.IX Item "-ftrapv" -This option generates traps for signed overflow on addition, subtraction, -multiplication operations. -.Ip "\fB\-fno-inline\fR" 4 -.IX Item "-fno-inline" -Don't pay attention to the \f(CW\*(C`inline\*(C'\fR keyword. Normally this option -is used to keep the compiler from expanding any functions inline. -Note that if you are not optimizing, no functions can be expanded inline. -.Ip "\fB\-finline-functions\fR" 4 -.IX Item "-finline-functions" -Integrate all simple functions into their callers. The compiler -heuristically decides which functions are simple enough to be worth -integrating in this way. -.Sp -If all calls to a given function are integrated, and the function is -declared \f(CW\*(C`static\*(C'\fR, then the function is normally not output as -assembler code in its own right. -.Ip "\fB\-finline-limit=\fR\fIn\fR" 4 -.IX Item "-finline-limit=n" -By default, gcc limits the size of functions that can be inlined. This flag -allows the control of this limit for functions that are explicitly marked as -inline (ie marked with the inline keyword or defined within the class -definition in c++). \fIn\fR is the size of functions that can be inlined in -number of pseudo instructions (not counting parameter handling). The default -value of \fIn\fR is 600. -Increasing this value can result in more inlined code at -the cost of compilation time and memory consumption. Decreasing usually makes -the compilation faster and less code will be inlined (which presumably -means slower programs). This option is particularly useful for programs that -use inlining heavily such as those based on recursive templates with \*(C+. -.Sp -\&\fINote:\fR pseudo instruction represents, in this particular context, an -abstract measurement of function's size. In no way, it represents a count -of assembly instructions and as such its exact meaning might change from one -release to an another. -.Ip "\fB\-fkeep-inline-functions\fR" 4 -.IX Item "-fkeep-inline-functions" -Even if all calls to a given function are integrated, and the function -is declared \f(CW\*(C`static\*(C'\fR, nevertheless output a separate run-time -callable version of the function. This switch does not affect -\&\f(CW\*(C`extern inline\*(C'\fR functions. -.Ip "\fB\-fkeep-static-consts\fR" 4 -.IX Item "-fkeep-static-consts" -Emit variables declared \f(CW\*(C`static const\*(C'\fR when optimization isn't turned -on, even if the variables aren't referenced. -.Sp -\&\s-1GCC\s0 enables this option by default. If you want to force the compiler to -check if the variable was referenced, regardless of whether or not -optimization is turned on, use the \fB\-fno-keep-static-consts\fR option. -.Ip "\fB\-fmerge-constants\fR" 4 -.IX Item "-fmerge-constants" -Attempt to merge identical constants (string constants and floating point -constants) accross compilation units. -.Sp -This option is default for optimized compilation if assembler and linker -support it. Use \fB\-fno-merge-constants\fR to inhibit this behavior. -.Ip "\fB\-fmerge-all-constants\fR" 4 -.IX Item "-fmerge-all-constants" -Attempt to merge identical constants and identical variables. -.Sp -This option implies \fB\-fmerge-constants\fR. In addition to -\&\fB\-fmerge-constants\fR this considers e.g. even constant initialized -arrays or initialized constant variables with integral or floating point -types. Languages like C or \*(C+ require each non-automatic variable to -have distinct location, so using this option will result in non-conforming -behavior. -.Ip "\fB\-fno-branch-count-reg\fR" 4 -.IX Item "-fno-branch-count-reg" -Do not use ``decrement and branch'' instructions on a count register, -but instead generate a sequence of instructions that decrement a -register, compare it against zero, then branch based upon the result. -This option is only meaningful on architectures that support such -instructions, which include x86, PowerPC, \s-1IA-64\s0 and S/390. -.Ip "\fB\-fno-function-cse\fR" 4 -.IX Item "-fno-function-cse" -Do not put function addresses in registers; make each instruction that -calls a constant function contain the function's address explicitly. -.Sp -This option results in less efficient code, but some strange hacks -that alter the assembler output may be confused by the optimizations -performed when this option is not used. -.Ip "\fB\-ffast-math\fR" 4 -.IX Item "-ffast-math" -Sets \fB\-fno-math-errno\fR, \fB\-funsafe-math-optimizations\fR, and \fB\-fno-trapping-math\fR. -.Sp -This option causes the preprocessor macro \f(CW\*(C`_\|_FAST_MATH_\|_\*(C'\fR to be defined. -.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 -an exact implementation of \s-1IEEE\s0 or \s-1ISO\s0 rules/specifications for -math functions. -.Ip "\fB\-fno-math-errno\fR" 4 -.IX Item "-fno-math-errno" -Do not set \s-1ERRNO\s0 after calling math functions that are executed -with a single instruction, e.g., sqrt. A program that relies on -\&\s-1IEEE\s0 exceptions for math error handling may want to use this flag -for speed while maintaining \s-1IEEE\s0 arithmetic compatibility. -.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 -an exact implementation of \s-1IEEE\s0 or \s-1ISO\s0 rules/specifications for -math functions. -.Sp -The default is \fB\-fmath-errno\fR. -.Ip "\fB\-funsafe-math-optimizations\fR" 4 -.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. 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 -an exact implementation of \s-1IEEE\s0 or \s-1ISO\s0 rules/specifications for -math functions. -.Sp -The default is \fB\-fno-unsafe-math-optimizations\fR. -.Ip "\fB\-fno-trapping-math\fR" 4 -.IX Item "-fno-trapping-math" -Compile code assuming that floating-point operations cannot generate -user-visible traps. Setting this option may allow faster code -if one relies on ``non-stop'' \s-1IEEE\s0 arithmetic, for example. -.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 -an exact implementation of \s-1IEEE\s0 or \s-1ISO\s0 rules/specifications for -math functions. -.Sp -The default is \fB\-ftrapping-math\fR. -.Ip "\fB\-fbounds-check\fR" 4 -.IX Item "-fbounds-check" -For front-ends that support it, generate additional code to check that -indices used to access arrays are within the declared range. This is -currenly only supported by the Java and Fortran 77 front-ends, where -this option defaults to true and false respectively. -.PP -The following options control specific optimizations. The \fB\-O2\fR -option turns on all of these optimizations except \fB\-funroll-loops\fR -and \fB\-funroll-all-loops\fR. On most machines, the \fB\-O\fR option -turns on the \fB\-fthread-jumps\fR and \fB\-fdelayed-branch\fR options, -but specific machines may handle it differently. -.PP -You can use the following flags in the rare cases when ``fine-tuning'' -of optimizations to be performed is desired. -.PP -Not all of the optimizations performed by \s-1GCC\s0 have \fB\-f\fR options -to control them. -.Ip "\fB\-fstrength-reduce\fR" 4 -.IX Item "-fstrength-reduce" -Perform the optimizations of loop strength reduction and -elimination of iteration variables. -.Ip "\fB\-fthread-jumps\fR" 4 -.IX Item "-fthread-jumps" -Perform optimizations where we check to see if a jump branches to a -location where another comparison subsumed by the first is found. If -so, the first branch is redirected to either the destination of the -second branch or a point immediately following it, depending on whether -the condition is known to be true or false. -.Ip "\fB\-fcse-follow-jumps\fR" 4 -.IX Item "-fcse-follow-jumps" -In common subexpression elimination, scan through jump instructions -when the target of the jump is not reached by any other path. For -example, when \s-1CSE\s0 encounters an \f(CW\*(C`if\*(C'\fR statement with an -\&\f(CW\*(C`else\*(C'\fR clause, \s-1CSE\s0 will follow the jump when the condition -tested is false. -.Ip "\fB\-fcse-skip-blocks\fR" 4 -.IX Item "-fcse-skip-blocks" -This is similar to \fB\-fcse-follow-jumps\fR, but causes \s-1CSE\s0 to -follow jumps which conditionally skip over blocks. When \s-1CSE\s0 -encounters a simple \f(CW\*(C`if\*(C'\fR statement with no else clause, -\&\fB\-fcse-skip-blocks\fR causes \s-1CSE\s0 to follow the jump around the -body of the \f(CW\*(C`if\*(C'\fR. -.Ip "\fB\-frerun-cse-after-loop\fR" 4 -.IX Item "-frerun-cse-after-loop" -Re-run common subexpression elimination after loop optimizations has been -performed. -.Ip "\fB\-frerun-loop-opt\fR" 4 -.IX Item "-frerun-loop-opt" -Run the loop optimizer twice. -.Ip "\fB\-fgcse\fR" 4 -.IX Item "-fgcse" -Perform a global common subexpression elimination pass. -This pass also performs global constant and copy propagation. -.Sp -\&\fINote:\fR When compiling a program using computed gotos, a \s-1GCC\s0 -extension, you may get better runtime performance if you disable -the global common subexpression elmination pass by adding -\&\fB\-fno-gcse\fR to the command line. -.Ip "\fB\-fgcse-lm\fR" 4 -.IX Item "-fgcse-lm" -When \fB\-fgcse-lm\fR is enabled, global common subexpression elimination will -attempt to move loads which are only killed by stores into themselves. This -allows a loop containing a load/store sequence to be changed to a load outside -the loop, and a copy/store within the loop. -.Ip "\fB\-fgcse-sm\fR" 4 -.IX Item "-fgcse-sm" -When \fB\-fgcse-sm\fR is enabled, A store motion pass is run after global common -subexpression elimination. This pass will attempt to move stores out of loops. -When used in conjunction with \fB\-fgcse-lm\fR, loops containing a load/store sequence -can be changed to a load before the loop and a store after the loop. -.Ip "\fB\-fdelete-null-pointer-checks\fR" 4 -.IX Item "-fdelete-null-pointer-checks" -Use global dataflow analysis to identify and eliminate useless checks -for null pointers. The compiler assumes that dereferencing a null -pointer would have halted the program. If a pointer is checked after -it has already been dereferenced, it cannot be null. -.Sp -In some environments, this assumption is not true, and programs can -safely dereference null pointers. Use -\&\fB\-fno-delete-null-pointer-checks\fR to disable this optimization -for programs which depend on that behavior. -.Ip "\fB\-fexpensive-optimizations\fR" 4 -.IX Item "-fexpensive-optimizations" -Perform a number of minor optimizations that are relatively expensive. -.Ip "\fB\-foptimize-register-move\fR" 4 -.IX Item "-foptimize-register-move" -.PD 0 -.Ip "\fB\-fregmove\fR" 4 -.IX Item "-fregmove" -.PD -Attempt to reassign register numbers in move instructions and as -operands of other simple instructions in order to maximize the amount of -register tying. This is especially helpful on machines with two-operand -instructions. \s-1GCC\s0 enables this optimization by default with \fB\-O2\fR -or higher. -.Sp -Note \fB\-fregmove\fR and \fB\-foptimize-register-move\fR are the same -optimization. -.Ip "\fB\-fdelayed-branch\fR" 4 -.IX Item "-fdelayed-branch" -If supported for the target machine, attempt to reorder instructions -to exploit instruction slots available after delayed branch -instructions. -.Ip "\fB\-fschedule-insns\fR" 4 -.IX Item "-fschedule-insns" -If supported for the target machine, attempt to reorder instructions to -eliminate execution stalls due to required data being unavailable. This -helps machines that have slow floating point or memory load instructions -by allowing other instructions to be issued until the result of the load -or floating point instruction is required. -.Ip "\fB\-fschedule-insns2\fR" 4 -.IX Item "-fschedule-insns2" -Similar to \fB\-fschedule-insns\fR, but requests an additional pass of -instruction scheduling after register allocation has been done. This is -especially useful on machines with a relatively small number of -registers and where memory load instructions take more than one cycle. -.Ip "\fB\-fno-sched-interblock\fR" 4 -.IX Item "-fno-sched-interblock" -Don't schedule instructions across basic blocks. This is normally -enabled by default when scheduling before register allocation, i.e. -with \fB\-fschedule-insns\fR or at \fB\-O2\fR or higher. -.Ip "\fB\-fno-sched-spec\fR" 4 -.IX Item "-fno-sched-spec" -Don't allow speculative motion of non-load instructions. This is normally -enabled by default when scheduling before register allocation, i.e. -with \fB\-fschedule-insns\fR or at \fB\-O2\fR or higher. -.Ip "\fB\-fsched-spec-load\fR" 4 -.IX Item "-fsched-spec-load" -Allow speculative motion of some load instructions. This only makes -sense when scheduling before register allocation, i.e. with -\&\fB\-fschedule-insns\fR or at \fB\-O2\fR or higher. -.Ip "\fB\-fsched-spec-load-dangerous\fR" 4 -.IX Item "-fsched-spec-load-dangerous" -Allow speculative motion of more load instructions. This only makes -sense when scheduling before register allocation, i.e. with -\&\fB\-fschedule-insns\fR or at \fB\-O2\fR or higher. -.Ip "\fB\-ffunction-sections\fR" 4 -.IX Item "-ffunction-sections" -.PD 0 -.Ip "\fB\-fdata-sections\fR" 4 -.IX Item "-fdata-sections" -.PD -Place each function or data item into its own section in the output -file if the target supports arbitrary sections. The name of the -function or the name of the data item determines the section's name -in the output file. -.Sp -Use these options on systems where the linker can perform optimizations -to improve locality of reference in the instruction space. \s-1HPPA\s0 -processors running \s-1HP-UX\s0 and Sparc processors running Solaris 2 have -linkers with such optimizations. Other systems using the \s-1ELF\s0 object format -as well as \s-1AIX\s0 may have these optimizations in the future. -.Sp -Only use these options when there are significant benefits from doing -so. When you specify these options, the assembler and linker will -create larger object and executable files and will also be slower. -You will not be able to use \f(CW\*(C`gprof\*(C'\fR on all systems if you -specify this option and you may have problems with debugging if -you specify both this option and \fB\-g\fR. -.Ip "\fB\-fcaller-saves\fR" 4 -.IX Item "-fcaller-saves" -Enable values to be allocated in registers that will be clobbered by -function calls, by emitting extra instructions to save and restore the -registers around such calls. Such allocation is done only when it -seems to result in better code than would otherwise be produced. -.Sp -This option is always enabled by default on certain machines, usually -those which have no call-preserved registers to use instead. -.Sp -For all machines, optimization level 2 and higher enables this flag by -default. -.Ip "\fB\-funroll-loops\fR" 4 -.IX Item "-funroll-loops" -Unroll loops whose number of iterations can be determined at compile -time or upon entry to the loop. \fB\-funroll-loops\fR implies both -\&\fB\-fstrength-reduce\fR and \fB\-frerun-cse-after-loop\fR. This -option makes code larger, and may or may not make it run faster. -.Ip "\fB\-funroll-all-loops\fR" 4 -.IX Item "-funroll-all-loops" -Unroll all loops, even if their number of iterations is uncertain when -the loop is entered. This usually makes programs run more slowly. -\&\fB\-funroll-all-loops\fR implies the same options as -\&\fB\-funroll-loops\fR, -.Ip "\fB\-fprefetch-loop-arrays\fR" 4 -.IX Item "-fprefetch-loop-arrays" -If supported by the target machine, generate instructions to prefetch -memory to improve the performance of loops that access large arrays. -.Ip "\fB\-fmove-all-movables\fR" 4 -.IX Item "-fmove-all-movables" -Forces all invariant computations in loops to be moved -outside the loop. -.Ip "\fB\-freduce-all-givs\fR" 4 -.IX Item "-freduce-all-givs" -Forces all general-induction variables in loops to be -strength-reduced. -.Sp -\&\fINote:\fR When compiling programs written in Fortran, -\&\fB\-fmove-all-movables\fR and \fB\-freduce-all-givs\fR are enabled -by default when you use the optimizer. -.Sp -These options may generate better or worse code; results are highly -dependent on the structure of loops within the source code. -.Sp -These two options are intended to be removed someday, once -they have helped determine the efficacy of various -approaches to improving loop optimizations. -.Sp -Please let us (<\fBgcc@gcc.gnu.org\fR> and <\fBfortran@gnu.org\fR>) -know how use of these options affects -the performance of your production code. -We're very interested in code that runs \fIslower\fR -when these options are \fIenabled\fR. -.Ip "\fB\-fno-peephole\fR" 4 -.IX Item "-fno-peephole" -.PD 0 -.Ip "\fB\-fno-peephole2\fR" 4 -.IX Item "-fno-peephole2" -.PD -Disable any machine-specific peephole optimizations. The difference -between \fB\-fno-peephole\fR and \fB\-fno-peephole2\fR is in how they -are implemented in the compiler; some targets use one, some use the -other, a few use both. -.Ip "\fB\-fbranch-probabilities\fR" 4 -.IX Item "-fbranch-probabilities" -After running a program compiled with \fB\-fprofile-arcs\fR, you can compile it a second time using -\&\fB\-fbranch-probabilities\fR, to improve optimizations based on -the number of times each branch was taken. When the program -compiled with \fB\-fprofile-arcs\fR exits it saves arc execution -counts to a file called \fI\fIsourcename\fI.da\fR for each source -file The information in this data file is very dependent on the -structure of the generated code, so you must use the same source code -and the same optimization options for both compilations. -.Sp -With \fB\-fbranch-probabilities\fR, \s-1GCC\s0 puts a \fB\s-1REG_EXEC_COUNT\s0\fR -note on the first instruction of each basic block, and a -\&\fB\s-1REG_BR_PROB\s0\fR note on each \fB\s-1JUMP_INSN\s0\fR and \fB\s-1CALL_INSN\s0\fR. -These can be used to improve optimization. Currently, they are only -used in one place: in \fIreorg.c\fR, instead of guessing which path a -branch is mostly to take, the \fB\s-1REG_BR_PROB\s0\fR values are used to -exactly determine which path is taken more often. -.Ip "\fB\-fno-guess-branch-probability\fR" 4 -.IX Item "-fno-guess-branch-probability" -Do not guess branch probabilities using a randomized model. -.Sp -Sometimes gcc will opt to use a randomized model to guess branch -probabilities, when none are available from either profiling feedback -(\fB\-fprofile-arcs\fR) or \fB_\|_builtin_expect\fR. This means that -different runs of the compiler on the same program may produce different -object code. -.Sp -In a hard real-time system, people don't want different runs of the -compiler to produce code that has different behavior; minimizing -non-determinism is of paramount import. This switch allows users to -reduce non-determinism, possibly at the expense of inferior -optimization. -.Ip "\fB\-fstrict-aliasing\fR" 4 -.IX Item "-fstrict-aliasing" -Allows the compiler to assume the strictest aliasing rules applicable to -the language being compiled. For C (and \*(C+), this activates -optimizations based on the type of expressions. In particular, an -object of one type is assumed never to reside at the same address as an -object of a different type, unless the types are almost the same. For -example, an \f(CW\*(C`unsigned int\*(C'\fR can alias an \f(CW\*(C`int\*(C'\fR, but not a -\&\f(CW\*(C`void*\*(C'\fR or a \f(CW\*(C`double\*(C'\fR. A character type may alias any other -type. -.Sp -Pay special attention to code like this: -.Sp -.Vb 4 -\& union a_union { -\& int i; -\& double d; -\& }; -.Ve -.Vb 5 -\& int f() { -\& a_union t; -\& t.d = 3.0; -\& return t.i; -\& } -.Ve -The practice of reading from a different union member than the one most -recently written to (called ``type-punning'') is common. Even with -\&\fB\-fstrict-aliasing\fR, type-punning is allowed, provided the memory -is accessed through the union type. So, the code above will work as -expected. However, this code might not: -.Sp -.Vb 7 -\& int f() { -\& a_union t; -\& int* ip; -\& t.d = 3.0; -\& ip = &t.i; -\& return *ip; -\& } -.Ve -Every language that wishes to perform language-specific alias analysis -should define a function that computes, given an \f(CW\*(C`tree\*(C'\fR -node, an alias set for the node. Nodes in different alias sets are not -allowed to alias. For an example, see the C front-end function -\&\f(CW\*(C`c_get_alias_set\*(C'\fR. -.Ip "\fB\-falign-functions\fR" 4 -.IX Item "-falign-functions" -.PD 0 -.Ip "\fB\-falign-functions=\fR\fIn\fR" 4 -.IX Item "-falign-functions=n" -.PD -Align the start of functions to the next power-of-two greater than -\&\fIn\fR, skipping up to \fIn\fR bytes. For instance, -\&\fB\-falign-functions=32\fR aligns functions to the next 32\-byte -boundary, but \fB\-falign-functions=24\fR would align to the next -32\-byte boundary only if this can be done by skipping 23 bytes or less. -.Sp -\&\fB\-fno-align-functions\fR and \fB\-falign-functions=1\fR are -equivalent and mean that functions will not be aligned. -.Sp -Some assemblers only support this flag when \fIn\fR is a power of two; -in that case, it is rounded up. -.Sp -If \fIn\fR is not specified, use a machine-dependent default. -.Ip "\fB\-falign-labels\fR" 4 -.IX Item "-falign-labels" -.PD 0 -.Ip "\fB\-falign-labels=\fR\fIn\fR" 4 -.IX Item "-falign-labels=n" -.PD -Align all branch targets to a power-of-two boundary, skipping up to -\&\fIn\fR bytes like \fB\-falign-functions\fR. This option can easily -make code slower, because it must insert dummy operations for when the -branch target is reached in the usual flow of the code. -.Sp -If \fB\-falign-loops\fR or \fB\-falign-jumps\fR are applicable and -are greater than this value, then their values are used instead. -.Sp -If \fIn\fR is not specified, use a machine-dependent default which is -very likely to be \fB1\fR, meaning no alignment. -.Ip "\fB\-falign-loops\fR" 4 -.IX Item "-falign-loops" -.PD 0 -.Ip "\fB\-falign-loops=\fR\fIn\fR" 4 -.IX Item "-falign-loops=n" -.PD -Align loops to a power-of-two boundary, skipping up to \fIn\fR bytes -like \fB\-falign-functions\fR. The hope is that the loop will be -executed many times, which will make up for any execution of the dummy -operations. -.Sp -If \fIn\fR is not specified, use a machine-dependent default. -.Ip "\fB\-falign-jumps\fR" 4 -.IX Item "-falign-jumps" -.PD 0 -.Ip "\fB\-falign-jumps=\fR\fIn\fR" 4 -.IX Item "-falign-jumps=n" -.PD -Align branch targets to a power-of-two boundary, for branch targets -where the targets can only be reached by jumping, skipping up to \fIn\fR -bytes like \fB\-falign-functions\fR. In this case, no dummy operations -need be executed. -.Sp -If \fIn\fR is not specified, use a machine-dependent default. -.Ip "\fB\-fssa\fR" 4 -.IX Item "-fssa" -Perform optimizations in static single assignment form. Each function's -flow graph is translated into \s-1SSA\s0 form, optimizations are performed, and -the flow graph is translated back from \s-1SSA\s0 form. Users should not -specify this option, since it is not yet ready for production use. -.Ip "\fB\-fssa-ccp\fR" 4 -.IX Item "-fssa-ccp" -Perform Sparse Conditional Constant Propagation in \s-1SSA\s0 form. Requires -\&\fB\-fssa\fR. Like \fB\-fssa\fR, this is an experimental feature. -.Ip "\fB\-fssa-dce\fR" 4 -.IX Item "-fssa-dce" -Perform aggressive dead-code elimination in \s-1SSA\s0 form. Requires \fB\-fssa\fR. -Like \fB\-fssa\fR, this is an experimental feature. -.Ip "\fB\-fsingle-precision-constant\fR" 4 -.IX Item "-fsingle-precision-constant" -Treat floating point constant as single precision constant instead of -implicitly converting it to double precision constant. -.Ip "\fB\-frename-registers\fR" 4 -.IX Item "-frename-registers" -Attempt to avoid false dependencies in scheduled code by making use -of registers left over after register allocation. This optimization -will most benefit processors with lots of registers. It can, however, -make debugging impossible, since variables will no longer stay in -a ``home register''. -.Ip "\fB\-fno-cprop-registers\fR" 4 -.IX Item "-fno-cprop-registers" -After register allocation and post-register allocation instruction splitting, -we perform a copy-propagation pass to try to reduce scheduling dependencies -and occasionally eliminate the copy. -.Ip "\fB\*(--param\fR \fIname\fR\fB=\fR\fIvalue\fR" 4 -.IX Item "param name=value" -In some places, \s-1GCC\s0 uses various constants to control the amount of -optimization that is done. For example, \s-1GCC\s0 will not inline functions -that contain more that a certain number of instructions. You can -control some of these constants on the command-line using the -\&\fB\*(--param\fR option. -.Sp -In each case, the \fIvalue\fR is an integer. The allowable choices for -\&\fIname\fR are given in the following table: -.RS 4 -.Ip "\fBmax-delay-slot-insn-search\fR" 4 -.IX Item "max-delay-slot-insn-search" -The maximum number of instructions to consider when looking for an -instruction to fill a delay slot. If more than this arbitrary number of -instructions is searched, the time savings from filling the delay slot -will be minimal so stop searching. Increasing values mean more -aggressive optimization, making the compile time increase with probably -small improvement in executable run time. -.Ip "\fBmax-delay-slot-live-search\fR" 4 -.IX Item "max-delay-slot-live-search" -When trying to fill delay slots, the maximum number of instructions to -consider when searching for a block with valid live register -information. Increasing this arbitrarily chosen value means more -aggressive optimization, increasing the compile time. This parameter -should be removed when the delay slot code is rewritten to maintain the -control-flow graph. -.Ip "\fBmax-gcse-memory\fR" 4 -.IX Item "max-gcse-memory" -The approximate maximum amount of memory that will be allocated in -order to perform the global common subexpression elimination -optimization. If more memory than specified is required, the -optimization will not be done. -.Ip "\fBmax-gcse-passes\fR" 4 -.IX Item "max-gcse-passes" -The maximum number of passes of \s-1GCSE\s0 to run. -.Ip "\fBmax-pending-list-length\fR" 4 -.IX Item "max-pending-list-length" -The maximum number of pending dependencies scheduling will allow -before flushing the current state and starting over. Large functions -with few branches or calls can create excessively large lists which -needlessly consume memory and resources. -.Ip "\fBmax-inline-insns\fR" 4 -.IX Item "max-inline-insns" -If an function contains more than this many instructions, it -will not be inlined. This option is precisely equivalent to -\&\fB\-finline-limit\fR. -.RE -.RS 4 -.RE -.Sh "Options Controlling the Preprocessor" -.IX Subsection "Options Controlling the Preprocessor" -These options control the C preprocessor, which is run on each C source -file before actual compilation. -.PP -If you use the \fB\-E\fR option, nothing is done except preprocessing. -Some of these options make sense only together with \fB\-E\fR because -they cause the preprocessor output to be unsuitable for actual -compilation. -.PP -You can use \fB\-Wp,\fR\fIoption\fR to bypass the compiler driver -and pass \fIoption\fR directly through to the preprocessor. If -\&\fIoption\fR contains commas, it is split into multiple options at the -commas. However, many options are modified, translated or interpreted -by the compiler driver before being passed to the preprocessor, and -\&\fB\-Wp\fR forcibly bypasses this phase. The preprocessor's direct -interface is undocumented and subject to change, so whenever possible -you should avoid using \fB\-Wp\fR and let the driver handle the -options instead. -.Ip "\fB\-D\fR \fIname\fR" 4 -.IX Item "-D name" -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 -.IX Item "-D name=definition" -Predefine \fIname\fR as a macro, with definition \fIdefinition\fR. -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. -.Sp -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 will need -to quote the option. With \fBsh\fR and \fBcsh\fR, -\&\fB\-D'\fR\fIname\fR\fB(\fR\fIargs...\fR\fB)=\fR\fIdefinition\fR\fB'\fR works. -.Sp -\&\fB\-D\fR and \fB\-U\fR options are processed in the order they -are given on the command line. All \fB\-imacros\fR \fIfile\fR and -\&\fB\-include\fR \fIfile\fR options are processed after all -\&\fB\-D\fR and \fB\-U\fR options. -.Ip "\fB\-U\fR \fIname\fR" 4 -.IX Item "-U name" -Cancel any previous definition of \fIname\fR, either built in or -provided with a \fB\-D\fR option. -.Ip "\fB\-undef\fR" 4 -.IX Item "-undef" -Do not predefine any system-specific macros. The common predefined -macros remain defined. -.Ip "\fB\-I\fR \fIdir\fR" 4 -.IX Item "-I dir" -Add the directory \fIdir\fR to the list of directories to be searched -for header files. -Directories named by \fB\-I\fR are searched before the standard -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 -.IX Item "-o file" -Write output to \fIfile\fR. This is the same as specifying \fIfile\fR -as the second non-option argument to \fBcpp\fR. \fBgcc\fR has a -different interpretation of a second non-option argument, so you must -use \fB\-o\fR to specify the output file. -.Ip "\fB\-Wall\fR" 4 -.IX Item "-Wall" -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 -.IX Item "-Wcomment" -.PD 0 -.Ip "\fB\-Wcomments\fR" 4 -.IX Item "-Wcomments" -.PD -Warn whenever a comment-start sequence \fB/*\fR appears in a \fB/*\fR -comment, or whenever a backslash-newline appears in a \fB//\fR comment. -(Both forms have the same effect.) -.Ip "\fB\-Wtrigraphs\fR" 4 -.IX Item "-Wtrigraphs" -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 -.IX Item "-Wtraditional" -Warn about certain constructs that behave differently in traditional and -\&\s-1ISO\s0 C. Also warn about \s-1ISO\s0 C constructs that have no traditional C -equivalent, and problematic constructs which should be avoided. -.Ip "\fB\-Wimport\fR" 4 -.IX Item "-Wimport" -Warn the first time \fB#import\fR is used. -.Ip "\fB\-Wundef\fR" 4 -.IX Item "-Wundef" -Warn whenever an identifier which is not a macro is encountered in an -\&\fB#if\fR directive, outside of \fBdefined\fR. Such identifiers are -replaced with zero. -.Ip "\fB\-Werror\fR" 4 -.IX Item "-Werror" -Make all warnings into hard errors. Source code which triggers warnings -will be rejected. -.Ip "\fB\-Wsystem-headers\fR" 4 -.IX Item "-Wsystem-headers" -Issue warnings for code in system headers. These are normally unhelpful -in finding bugs in your own code, therefore suppressed. If you are -responsible for the system library, you may want to see them. -.Ip "\fB\-w\fR" 4 -.IX Item "-w" -Suppress all warnings, including those which \s-1GNU\s0 \s-1CPP\s0 issues by default. -.Ip "\fB\-pedantic\fR" 4 -.IX Item "-pedantic" -Issue all the mandatory diagnostics listed in the C standard. Some of -them are left out by default, since they trigger frequently on harmless -code. -.Ip "\fB\-pedantic-errors\fR" 4 -.IX Item "-pedantic-errors" -Issue all the mandatory diagnostics, and make all mandatory diagnostics -into errors. This includes mandatory diagnostics that \s-1GCC\s0 issues -without \fB\-pedantic\fR but treats as warnings. -.Ip "\fB\-M\fR" 4 -.IX Item "-M" -Instead of outputting the result of preprocessing, output a rule -suitable for \fBmake\fR describing the dependencies of the main -source file. The preprocessor outputs one \fBmake\fR rule containing -the object file name for that source file, a colon, and the names of all -the included files, including those coming from \fB\-include\fR or -\&\fB\-imacros\fR command line options. -.Sp -Unless specified explicitly (with \fB\-MT\fR or \fB\-MQ\fR), the -object file name consists of the basename of the source file with any -suffix replaced with object file suffix. If there are many included -files then the rule is split into several lines using \fB\e\fR\-newline. -The rule has no commands. -.Sp -This option does not suppress the preprocessor's debug output, such as -\&\fB\-dM\fR. To avoid mixing such debug output with the dependency -rules you should explicitly specify the dependency output file with -\&\fB\-MF\fR, or use an environment variable like -\&\fB\s-1DEPENDENCIES_OUTPUT\s0\fR. Debug output -will still be sent to the regular output stream as normal. -.Sp -Passing \fB\-M\fR to the driver implies \fB\-E\fR. -.Ip "\fB\-MM\fR" 4 -.IX Item "-MM" -Like \fB\-M\fR 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. -.Sp -This implies that the choice of angle brackets or double quotes in an -\&\fB#include\fR directive does not in itself determine whether that -header will appear in \fB\-MM\fR dependency output. This is a -slight change in semantics from \s-1GCC\s0 versions 3.0 and earlier. -.Ip "\fB\-MF\fR \fIfile\fR" 4 -.IX Item "-MF file" -@anchor{\-MF} -When used with \fB\-M\fR or \fB\-MM\fR, specifies a -file to write the dependencies to. If no \fB\-MF\fR switch is given -the preprocessor sends the rules to the same place it would have sent -preprocessed output. -.Sp -When used with the driver options \fB\-MD\fR or \fB\-MMD\fR, -\&\fB\-MF\fR overrides the default dependency output file. -.Ip "\fB\-MG\fR" 4 -.IX Item "-MG" -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. -.Sp -This feature is used in automatic updating of makefiles. -.Ip "\fB\-MP\fR" 4 -.IX Item "-MP" -This option instructs \s-1CPP\s0 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 \fBmake\fR gives if you remove header -files without updating the \fIMakefile\fR to match. -.Sp -This is typical output: -.Sp -.Vb 1 -\& test.o: test.c test.h -.Ve -.Vb 1 -\& test.h: -.Ve -.Ip "\fB\-MT\fR \fItarget\fR" 4 -.IX Item "-MT target" -Change the target of the rule emitted by dependency generation. By -default \s-1CPP\s0 takes the name of the main input file, including any path, -deletes any file suffix such as \fB.c\fR, and appends the platform's -usual object suffix. The result is the target. -.Sp -An \fB\-MT\fR option will set the target to be exactly the string you -specify. If you want multiple targets, you can specify them as a single -argument to \fB\-MT\fR, or use multiple \fB\-MT\fR options. -.Sp -For example, \fB\-MT\ '$(objpfx)foo.o'\fR might give -.Sp -.Vb 1 -\& $(objpfx)foo.o: foo.c -.Ve -.Ip "\fB\-MQ\fR \fItarget\fR" 4 -.IX Item "-MQ target" -Same as \fB\-MT\fR, but it quotes any characters which are special to -Make. \fB\-MQ\ '$(objpfx)foo.o'\fR gives -.Sp -.Vb 1 -\& $$(objpfx)foo.o: foo.c -.Ve -The default target is automatically quoted, as if it were given with -\&\fB\-MQ\fR. -.Ip "\fB\-MD\fR" 4 -.IX Item "-MD" -\&\fB\-MD\fR is equivalent to \fB\-M \-MF\fR \fIfile\fR, except that -\&\fB\-E\fR is not implied. The driver determines \fIfile\fR based on -whether an \fB\-o\fR option is given. If it is, the driver uses its -argument but with a suffix of \fI.d\fR, otherwise it take the -basename of the input file and applies a \fI.d\fR suffix. -.Sp -If \fB\-MD\fR is used in conjunction with \fB\-E\fR, any -\&\fB\-o\fR switch is understood to specify the dependency output file -(but \f(CW@pxref\fR{\-MF}), but if used without \fB\-E\fR, each \fB\-o\fR -is understood to specify a target object file. -.Sp -Since \fB\-E\fR is not implied, \fB\-MD\fR can be used to generate -a dependency output file as a side-effect of the compilation process. -.Ip "\fB\-MMD\fR" 4 -.IX Item "-MMD" -Like \fB\-MD\fR except mention only user header files, not system -\&\-header files. -.Ip "\fB\-x c\fR" 4 -.IX Item "-x c" -.PD 0 -.Ip "\fB\-x c++\fR" 4 -.IX Item "-x c++" -.Ip "\fB\-x objective-c\fR" 4 -.IX Item "-x objective-c" -.Ip "\fB\-x assembler-with-cpp\fR" 4 -.IX Item "-x assembler-with-cpp" -.PD -Specify the source language: C, \*(C+, Objective-C, or assembly. This has -nothing to do with standards conformance or extensions; it merely -selects which base syntax to expect. If you give none of these options, -cpp will deduce the language from the extension of the source file: -\&\fB.c\fR, \fB.cc\fR, \fB.m\fR, or \fB.S\fR. Some other common -extensions for \*(C+ and assembly are also recognized. If cpp does not -recognize the extension, it will treat the file as C; this is the most -generic mode. -.Sp -\&\fBNote:\fR Previous versions of cpp accepted a \fB\-lang\fR option -which selected both the language and the standards conformance level. -This option has been removed, because it conflicts with the \fB\-l\fR -option. -.Ip "\fB\-std=\fR\fIstandard\fR" 4 -.IX Item "-std=standard" -.PD 0 -.Ip "\fB\-ansi\fR" 4 -.IX Item "-ansi" -.PD -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. -.Sp -\&\fIstandard\fR -may be one of: -.RS 4 -.if n .Ip "\f(CW""""iso9899:1990""""\fR" 4 -.el .Ip "\f(CWiso9899:1990\fR" 4 -.IX Item "iso9899:1990" -.PD 0 -.if n .Ip "\f(CW""""c89""""\fR" 4 -.el .Ip "\f(CWc89\fR" 4 -.IX Item "c89" -.PD -The \s-1ISO\s0 C standard from 1990. \fBc89\fR is the customary shorthand for -this version of the standard. -.Sp -The \fB\-ansi\fR option is equivalent to \fB\-std=c89\fR. -.if n .Ip "\f(CW""""iso9899:199409""""\fR" 4 -.el .Ip "\f(CWiso9899:199409\fR" 4 -.IX Item "iso9899:199409" -The 1990 C standard, as amended in 1994. -.if n .Ip "\f(CW""""iso9899:1999""""\fR" 4 -.el .Ip "\f(CWiso9899:1999\fR" 4 -.IX Item "iso9899:1999" -.PD 0 -.if n .Ip "\f(CW""""c99""""\fR" 4 -.el .Ip "\f(CWc99\fR" 4 -.IX Item "c99" -.if n .Ip "\f(CW""""iso9899:199x""""\fR" 4 -.el .Ip "\f(CWiso9899:199x\fR" 4 -.IX Item "iso9899:199x" -.if n .Ip "\f(CW""""c9x""""\fR" 4 -.el .Ip "\f(CWc9x\fR" 4 -.IX Item "c9x" -.PD -The revised \s-1ISO\s0 C standard, published in December 1999. Before -publication, this was known as C9X. -.if n .Ip "\f(CW""""gnu89""""\fR" 4 -.el .Ip "\f(CWgnu89\fR" 4 -.IX Item "gnu89" -The 1990 C standard plus \s-1GNU\s0 extensions. This is the default. -.if n .Ip "\f(CW""""gnu99""""\fR" 4 -.el .Ip "\f(CWgnu99\fR" 4 -.IX Item "gnu99" -.PD 0 -.if n .Ip "\f(CW""""gnu9x""""\fR" 4 -.el .Ip "\f(CWgnu9x\fR" 4 -.IX Item "gnu9x" -.PD -The 1999 C standard plus \s-1GNU\s0 extensions. -.RE -.RS 4 -.RE -.Ip "\fB\-I-\fR" 4 -.IX Item "-I-" -Split the include path. Any directories specified with \fB\-I\fR -options before \fB\-I-\fR are searched only for headers requested with -\&\f(CW\*(C`#include\ "\f(CIfile\f(CW"\*(C'\fR; they are not searched for -\&\f(CW\*(C`#include\ <\f(CIfile\f(CW>\*(C'\fR. If additional directories are -specified with \fB\-I\fR options after the \fB\-I-\fR, those -directories are searched for all \fB#include\fR directives. -.Sp -In addition, \fB\-I-\fR inhibits the use of the directory of the current -file directory as the first search directory for \f(CW\*(C`#include\ "\f(CIfile\f(CW"\*(C'\fR. -.Ip "\fB\-nostdinc\fR" 4 -.IX Item "-nostdinc" -Do not search the standard system directories for header files. -Only the directories you have specified with \fB\-I\fR options -(and the directory of the current file, if appropriate) are searched. -.Ip "\fB\-nostdinc++\fR" 4 -.IX Item "-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.) -.Ip "\fB\-include\fR \fIfile\fR" 4 -.IX Item "-include file" -Process \fIfile\fR as if \f(CW\*(C`#include "file"\*(C'\fR appeared as the first -line of the primary source file. However, the first directory searched -for \fIfile\fR is the preprocessor's working directory \fIinstead of\fR -the directory containing the main source file. If not found there, it -is searched for in the remainder of the \f(CW\*(C`#include "..."\*(C'\fR search -chain as normal. -.Sp -If multiple \fB\-include\fR options are given, the files are included -in the order they appear on the command line. -.Ip "\fB\-imacros\fR \fIfile\fR" 4 -.IX Item "-imacros file" -Exactly like \fB\-include\fR, except that any output produced by -scanning \fIfile\fR is thrown away. Macros it defines remain defined. -This allows you to acquire all the macros from a header without also -processing its declarations. -.Sp -All files specified by \fB\-imacros\fR are processed before all files -specified by \fB\-include\fR. -.Ip "\fB\-idirafter\fR \fIdir\fR" 4 -.IX Item "-idirafter dir" -Search \fIdir\fR for header files, but do it \fIafter\fR all -directories specified with \fB\-I\fR and the standard system directories -have been exhausted. \fIdir\fR is treated as a system include directory. -.Ip "\fB\-iprefix\fR \fIprefix\fR" 4 -.IX Item "-iprefix prefix" -Specify \fIprefix\fR as the prefix for subsequent \fB\-iwithprefix\fR -options. If the prefix represents a directory, you should include the -final \fB/\fR. -.Ip "\fB\-iwithprefix\fR \fIdir\fR" 4 -.IX Item "-iwithprefix dir" -.PD 0 -.Ip "\fB\-iwithprefixbefore\fR \fIdir\fR" 4 -.IX Item "-iwithprefixbefore dir" -.PD -Append \fIdir\fR to the prefix specified previously with -\&\fB\-iprefix\fR, and add the resulting directory to the include search -path. \fB\-iwithprefixbefore\fR puts it in the same place \fB\-I\fR -would; \fB\-iwithprefix\fR puts it where \fB\-idirafter\fR would. -.Sp -Use of these options is discouraged. -.Ip "\fB\-isystem\fR \fIdir\fR" 4 -.IX Item "-isystem dir" -Search \fIdir\fR for header files, after all directories specified by -\&\fB\-I\fR but before the standard system directories. Mark it -as a system directory, so that it gets the same special treatment as -is applied to the standard system directories. -.Ip "\fB\-fpreprocessed\fR" 4 -.IX Item "-fpreprocessed" -Indicate to the preprocessor that the input file has already been -preprocessed. This suppresses things like macro expansion, trigraph -conversion, escaped newline splicing, and processing of most directives. -The preprocessor still recognizes and removes comments, so that you can -pass a file preprocessed with \fB\-C\fR to the compiler without -problems. In this mode the integrated preprocessor is little more than -a tokenizer for the front ends. -.Sp -\&\fB\-fpreprocessed\fR is implicit if the input file has one of the -extensions \fB.i\fR, \fB.ii\fR or \fB.mi\fR. These are the -extensions that \s-1GCC\s0 uses for preprocessed files created by -\&\fB\-save-temps\fR. -.Ip "\fB\-ftabstop=\fR\fIwidth\fR" 4 -.IX Item "-ftabstop=width" -Set the distance between tab stops. This helps the preprocessor report -correct column numbers in warnings or errors, even if tabs appear on the -line. If the value is less than 1 or greater than 100, the option is -ignored. The default is 8. -.Ip "\fB\-fno-show-column\fR" 4 -.IX Item "-fno-show-column" -Do not print column numbers in diagnostics. This may be necessary if -diagnostics are being scanned by a program that does not understand the -column numbers, such as \fBdejagnu\fR. -.Ip "\fB\-A\fR \fIpredicate\fR\fB=\fR\fIanswer\fR" 4 -.IX Item "-A predicate=answer" -Make an assertion with the predicate \fIpredicate\fR and answer -\&\fIanswer\fR. This form is preferred to the older form \fB\-A\fR -\&\fIpredicate\fR\fB(\fR\fIanswer\fR\fB)\fR, which is still supported, because -it does not use shell special characters. -.Ip "\fB\-A -\fR\fIpredicate\fR\fB=\fR\fIanswer\fR" 4 -.IX Item "-A -predicate=answer" -Cancel an assertion with the predicate \fIpredicate\fR and answer -\&\fIanswer\fR. -.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 -.IX Item "-dCHARS" -\&\fI\s-1CHARS\s0\fR is a sequence of one or more of the following characters, -and must not be preceded by a space. Other characters are interpreted -by the compiler proper, or reserved for future versions of \s-1GCC\s0, and so -are silently ignored. If you specify characters whose behavior -conflicts, the result is undefined. -.RS 4 -.Ip "\fBM\fR" 4 -.IX Item "M" -Instead of the normal output, generate a list of \fB#define\fR -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 \fIfoo.h\fR, the command -.Sp -.Vb 1 -\& touch foo.h; cpp -dM foo.h -.Ve -will show all the predefined macros. -.Ip "\fBD\fR" 4 -.IX Item "D" -Like \fBM\fR except in two respects: it does \fInot\fR include the -predefined macros, and it outputs \fIboth\fR the \fB#define\fR -directives and the result of preprocessing. Both kinds of output go to -the standard output file. -.Ip "\fBN\fR" 4 -.IX Item "N" -Like \fBD\fR, but emit only the macro names, not their expansions. -.Ip "\fBI\fR" 4 -.IX Item "I" -Output \fB#include\fR directives in addition to the result of -preprocessing. -.RE -.RS 4 -.RE -.Ip "\fB\-P\fR" 4 -.IX Item "-P" -Inhibit generation of linemarkers in the output from the preprocessor. -This might be useful when running the preprocessor on something that is -not C code, and will be sent to a program which might be confused by the -linemarkers. -.Ip "\fB\-C\fR" 4 -.IX Item "-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. -.Sp -You should be prepared for side effects when using \fB\-C\fR; 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 \fB#\fR. -.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 -.IX Item "-trigraphs" -Process trigraph sequences. -These are three-character sequences, all starting with \fB??\fR, that -are defined by \s-1ISO\s0 C to stand for single characters. For example, -\&\fB??/\fR stands for \fB\e\fR, so \fB'??/n'\fR is a character -constant for a newline. By default, \s-1GCC\s0 ignores trigraphs, but in -standard-conforming modes it converts them. See the \fB\-std\fR and -\&\fB\-ansi\fR options. -.Sp -The nine trigraphs and their replacements are -.Sp -.Vb 2 -\& Trigraph: ??( ??) ??< ??> ??= ??/ ??' ??! ??- -\& Replacement: [ ] { } # \e ^ | ~ -.Ve -.Ip "\fB\-remap\fR" 4 -.IX Item "-remap" -Enable special code to work around file systems which only permit very -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" -.PD 0 -.Ip "\fB\*(--help\fR" 4 -.IX Item "help" -.Ip "\fB\*(--target-help\fR" 4 -.IX Item "target-help" -.PD -Print text describing all the command line options instead of -preprocessing anything. -.Ip "\fB\-v\fR" 4 -.IX Item "-v" -Verbose mode. Print out \s-1GNU\s0 \s-1CPP\s0's version number at the beginning of -execution, and report the final form of the include path. -.Ip "\fB\-H\fR" 4 -.IX Item "-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 -\&\fB#include\fR stack it is. -.Ip "\fB\-version\fR" 4 -.IX Item "-version" -.PD 0 -.Ip "\fB\*(--version\fR" 4 -.IX Item "version" -.PD -Print out \s-1GNU\s0 \s-1CPP\s0's version number. With one dash, proceed to -preprocess as normal. With two dashes, exit immediately. -.Sh "Passing Options to the Assembler" -.IX Subsection "Passing Options to the Assembler" -You can pass options to the assembler. -.Ip "\fB\-Wa,\fR\fIoption\fR" 4 -.IX Item "-Wa,option" -Pass \fIoption\fR as an option to the assembler. If \fIoption\fR -contains commas, it is split into multiple options at the commas. -.Sh "Options for Linking" -.IX Subsection "Options for Linking" -These options come into play when the compiler links object files into -an executable output file. They are meaningless if the compiler is -not doing a link step. -.Ip "\fIobject-file-name\fR" 4 -.IX Item "object-file-name" -A file name that does not end in a special recognized suffix is -considered to name an object file or library. (Object files are -distinguished from libraries by the linker according to the file -contents.) If linking is done, these object files are used as input -to the linker. -.Ip "\fB\-c\fR" 4 -.IX Item "-c" -.PD 0 -.Ip "\fB\-S\fR" 4 -.IX Item "-S" -.Ip "\fB\-E\fR" 4 -.IX Item "-E" -.PD -If any of these options is used, then the linker is not run, and -object file names should not be used as arguments. -.Ip "\fB\-l\fR\fIlibrary\fR" 4 -.IX Item "-llibrary" -.PD 0 -.Ip "\fB\-l\fR \fIlibrary\fR" 4 -.IX Item "-l library" -.PD -Search the library named \fIlibrary\fR when linking. (The second -alternative with the library as a separate argument is only for -\&\s-1POSIX\s0 compliance and is not recommended.) -.Sp -It makes a difference where in the command you write this option; the -linker searches and processes libraries and object files in the order they -are specified. Thus, \fBfoo.o \-lz bar.o\fR searches library \fBz\fR -after file \fIfoo.o\fR but before \fIbar.o\fR. If \fIbar.o\fR refers -to functions in \fBz\fR, those functions may not be loaded. -.Sp -The linker searches a standard list of directories for the library, -which is actually a file named \fIlib\fIlibrary\fI.a\fR. The linker -then uses this file as if it had been specified precisely by name. -.Sp -The directories searched include several standard system directories -plus any that you specify with \fB\-L\fR. -.Sp -Normally the files found this way are library files\-\-\-archive files -whose members are object files. The linker handles an archive file by -scanning through it for members which define symbols that have so far -been referenced but not defined. But if the file that is found is an -ordinary object file, it is linked in the usual fashion. The only -difference between using an \fB\-l\fR option and specifying a file name -is that \fB\-l\fR surrounds \fIlibrary\fR with \fBlib\fR and \fB.a\fR -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. -.Ip "\fB\-nostartfiles\fR" 4 -.IX Item "-nostartfiles" -Do not use the standard system startup files when linking. -The standard system libraries are used normally, unless \fB\-nostdlib\fR -or \fB\-nodefaultlibs\fR is used. -.Ip "\fB\-nodefaultlibs\fR" 4 -.IX Item "-nodefaultlibs" -Do not use the standard system libraries when linking. -Only the libraries you specify will be passed to the linker. -The standard startup files are used normally, unless \fB\-nostartfiles\fR -is used. The compiler may generate calls to memcmp, memset, and memcpy -for System V (and \s-1ISO\s0 C) environments or to bcopy and bzero for -\&\s-1BSD\s0 environments. These entries are usually resolved by entries in -libc. These entry points should be supplied through some other -mechanism when this option is specified. -.Ip "\fB\-nostdlib\fR" 4 -.IX Item "-nostdlib" -Do not use the standard system startup files or libraries when linking. -No startup files and only the libraries you specify will be passed to -the linker. The compiler may generate calls to memcmp, memset, and memcpy -for System V (and \s-1ISO\s0 C) environments or to bcopy and bzero for -\&\s-1BSD\s0 environments. These entries are usually resolved by entries in -libc. These entry points should be supplied through some other -mechanism when this option is specified. -.Sp -One of the standard libraries bypassed by \fB\-nostdlib\fR and -\&\fB\-nodefaultlibs\fR is \fIlibgcc.a\fR, a library of internal subroutines -that \s-1GCC\s0 uses to overcome shortcomings of particular machines, or special -needs for some languages. -.Sp -In most cases, you need \fIlibgcc.a\fR even when you want to avoid -other standard libraries. In other words, when you specify \fB\-nostdlib\fR -or \fB\-nodefaultlibs\fR you should usually specify \fB\-lgcc\fR as well. -This ensures that you have no unresolved references to internal \s-1GCC\s0 -library subroutines. (For example, \fB_\|_main\fR, used to ensure \*(C+ -constructors will be called.) -.Ip "\fB\-s\fR" 4 -.IX Item "-s" -Remove all symbol table and relocation information from the executable. -.Ip "\fB\-static\fR" 4 -.IX Item "-static" -On systems that support dynamic linking, this prevents linking with the shared -libraries. On other systems, this option has no effect. -.Ip "\fB\-shared\fR" 4 -.IX Item "-shared" -Produce a shared object which can then be linked with other objects to -form an executable. Not all systems support this option. For predictable -results, you must also specify the same set of options that were used to -generate code (\fB\-fpic\fR, \fB\-fPIC\fR, or model suboptions) -when you specify this option.[1] -.Ip "\fB\-shared-libgcc\fR" 4 -.IX Item "-shared-libgcc" -.PD 0 -.Ip "\fB\-static-libgcc\fR" 4 -.IX Item "-static-libgcc" -.PD -On systems that provide \fIlibgcc\fR as a shared library, these options -force the use of either the shared or static version respectively. -If no shared version of \fIlibgcc\fR was built when the compiler was -configured, these options have no effect. -.Sp -There are several situations in which an application should use the -shared \fIlibgcc\fR instead of the static version. The most common -of these is when the application wishes to throw and catch exceptions -across different shared libraries. In that case, each of the libraries -as well as the application itself should use the shared \fIlibgcc\fR. -.Sp -Therefore, the G++ and \s-1GCJ\s0 drivers automatically add -\&\fB\-shared-libgcc\fR whenever you build a shared library or a main -executable, because \*(C+ and Java programs typically use exceptions, so -this is the right thing to do. -.Sp -If, instead, you use the \s-1GCC\s0 driver to create shared libraries, you may -find that they will not always be linked with the shared \fIlibgcc\fR. -If \s-1GCC\s0 finds, at its configuration time, that you have a \s-1GNU\s0 linker that -does not support option \fB\*(--eh-frame-hdr\fR, it will link the shared -version of \fIlibgcc\fR into shared libraries by default. Otherwise, -it will take advantage of the linker and optimize away the linking with -the shared version of \fIlibgcc\fR, linking with the static version of -libgcc by default. This allows exceptions to propagate through such -shared libraries, without incurring relocation costs at library load -time. -.Sp -However, if a library or main executable is supposed to throw or catch -exceptions, you must link it using the G++ or \s-1GCJ\s0 driver, as appropriate -for the languages used in the program, or using the option -\&\fB\-shared-libgcc\fR, such that it is linked with the shared -\&\fIlibgcc\fR. -.Ip "\fB\-symbolic\fR" 4 -.IX Item "-symbolic" -Bind references to global symbols when building a shared object. Warn -about any unresolved references (unless overridden by the link editor -option \fB\-Xlinker \-z \-Xlinker defs\fR). Only a few systems support -this option. -.Ip "\fB\-Xlinker\fR \fIoption\fR" 4 -.IX Item "-Xlinker option" -Pass \fIoption\fR as an option to the linker. You can use this to -supply system-specific linker options which \s-1GCC\s0 does not know how to -recognize. -.Sp -If you want to pass an option that takes an argument, you must use -\&\fB\-Xlinker\fR twice, once for the option and once for the argument. -For example, to pass \fB\-assert definitions\fR, you must write -\&\fB\-Xlinker \-assert \-Xlinker definitions\fR. It does not work to write -\&\fB\-Xlinker \*(L"\-assert definitions\*(R"\fR, because this passes the entire -string as a single argument, which is not what the linker expects. -.Ip "\fB\-Wl,\fR\fIoption\fR" 4 -.IX Item "-Wl,option" -Pass \fIoption\fR as an option to the linker. If \fIoption\fR contains -commas, it is split into multiple options at the commas. -.Ip "\fB\-u\fR \fIsymbol\fR" 4 -.IX Item "-u symbol" -Pretend the symbol \fIsymbol\fR is undefined, to force linking of -library modules to define it. You can use \fB\-u\fR multiple times with -different symbols to force loading of additional library modules. -.Sh "Options for Directory Search" -.IX Subsection "Options for Directory Search" -These options specify directories to search for header files, for -libraries and for parts of the compiler: -.Ip "\fB\-I\fR\fIdir\fR" 4 -.IX Item "-Idir" -Add the directory \fIdir\fR to the head of the list of directories to be -searched for header files. This can be used to override a system header -file, substituting your own version, since these directories are -searched before the system header file directories. However, you should -not use this option to add directories that contain vendor-supplied -system header files (use \fB\-isystem\fR for that). If you use more than -one \fB\-I\fR option, the directories are scanned in left-to-right -order; the standard system directories come after. -.Sp -If a standard system include directory, or a directory specified with -\&\fB\-isystem\fR, is also specified with \fB\-I\fR, the \fB\-I\fR -option will be ignored. The directory will still be searched but as a -system directory at its normal position in the system include chain. -This is to ensure that \s-1GCC\s0's procedure to fix buggy system headers and -the ordering for the include_next directive are not inadvertantly changed. -If you really need to change the search order for system directories, -use the \fB\-nostdinc\fR and/or \fB\-isystem\fR options. -.Ip "\fB\-I-\fR" 4 -.IX Item "-I-" -Any directories you specify with \fB\-I\fR options before the \fB\-I-\fR -option are searched only for the case of \fB#include "\fR\fIfile\fR\fB"\fR; -they are not searched for \fB#include <\fR\fIfile\fR\fB>\fR. -.Sp -If additional directories are specified with \fB\-I\fR options after -the \fB\-I-\fR, these directories are searched for all \fB#include\fR -directives. (Ordinarily \fIall\fR \fB\-I\fR directories are used -this way.) -.Sp -In addition, the \fB\-I-\fR option inhibits the use of the current -directory (where the current input file came from) as the first search -directory for \fB#include "\fR\fIfile\fR\fB"\fR. There is no way to -override this effect of \fB\-I-\fR. With \fB\-I.\fR you can specify -searching the directory which was current when the compiler was -invoked. That is not exactly the same as what the preprocessor does -by default, but it is often satisfactory. -.Sp -\&\fB\-I-\fR does not inhibit the use of the standard system directories -for header files. Thus, \fB\-I-\fR and \fB\-nostdinc\fR are -independent. -.Ip "\fB\-L\fR\fIdir\fR" 4 -.IX Item "-Ldir" -Add directory \fIdir\fR to the list of directories to be searched -for \fB\-l\fR. -.Ip "\fB\-B\fR\fIprefix\fR" 4 -.IX Item "-Bprefix" -This option specifies where to find the executables, libraries, -include files, and data files of the compiler itself. -.Sp -The compiler driver program runs one or more of the subprograms -\&\fIcpp\fR, \fIcc1\fR, \fIas\fR and \fIld\fR. It tries -\&\fIprefix\fR as a prefix for each program it tries to run, both with and -without \fImachine\fR\fB/\fR\fIversion\fR\fB/\fR. -.Sp -For each subprogram to be run, the compiler driver first tries the -\&\fB\-B\fR prefix, if any. If that name is not found, or if \fB\-B\fR -was not specified, the driver tries two standard prefixes, which are -\&\fI/usr/lib/gcc/\fR and \fI/usr/local/lib/gcc-lib/\fR. If neither of -those results in a file name that is found, the unmodified program -name is searched for using the directories specified in your -\&\fB\s-1PATH\s0\fR environment variable. -.Sp -The compiler will check to see if the path provided by the \fB\-B\fR -refers to a directory, and if necessary it will add a directory -separator character at the end of the path. -.Sp -\&\fB\-B\fR prefixes that effectively specify directory names also apply -to libraries in the linker, because the compiler translates these -options into \fB\-L\fR options for the linker. They also apply to -includes files in the preprocessor, because the compiler translates these -options into \fB\-isystem\fR options for the preprocessor. In this case, -the compiler appends \fBinclude\fR to the prefix. -.Sp -The run-time support file \fIlibgcc.a\fR can also be searched for using -the \fB\-B\fR prefix, if needed. If it is not found there, the two -standard prefixes above are tried, and that is all. The file is left -out of the link if it is not found by those means. -.Sp -Another way to specify a prefix much like the \fB\-B\fR prefix is to use -the environment variable \fB\s-1GCC_EXEC_PREFIX\s0\fR. -.Sp -As a special kludge, if the path provided by \fB\-B\fR is -\&\fI[dir/]stage\fIN\fI/\fR, where \fIN\fR is a number in the range 0 to -9, then it will be replaced by \fI[dir/]include\fR. This is to help -with boot-strapping the compiler. -.Ip "\fB\-specs=\fR\fIfile\fR" 4 -.IX Item "-specs=file" -Process \fIfile\fR after the compiler reads in the standard \fIspecs\fR -file, in order to override the defaults that the \fIgcc\fR driver -program uses when determining what switches to pass to \fIcc1\fR, -\&\fIcc1plus\fR, \fIas\fR, \fIld\fR, etc. More than one -\&\fB\-specs=\fR\fIfile\fR can be specified on the command line, and they -are processed in order, from left to right. -.Sh "Specifying Target Machine and Compiler Version" -.IX Subsection "Specifying Target Machine and Compiler Version" -By default, \s-1GCC\s0 compiles code for the same type of machine that you -are using. However, it can also be installed as a cross-compiler, to -compile for some other type of machine. In fact, several different -configurations of \s-1GCC\s0, for different target machines, can be -installed side by side. Then you specify which one to use with the -\&\fB\-b\fR option. -.PP -In addition, older and newer versions of \s-1GCC\s0 can be installed side -by side. One of them (probably the newest) will be the default, but -you may sometimes wish to use another. -.Ip "\fB\-b\fR \fImachine\fR" 4 -.IX Item "-b machine" -The argument \fImachine\fR specifies the target machine for compilation. -This is useful when you have installed \s-1GCC\s0 as a cross-compiler. -.Sp -The value to use for \fImachine\fR is the same as was specified as the -machine type when configuring \s-1GCC\s0 as a cross-compiler. For -example, if a cross-compiler was configured with \fBconfigure -i386v\fR, meaning to compile for an 80386 running System V, then you -would specify \fB\-b i386v\fR to run that cross compiler. -.Sp -When you do not specify \fB\-b\fR, it normally means to compile for -the same type of machine that you are using. -.Ip "\fB\-V\fR \fIversion\fR" 4 -.IX Item "-V version" -The argument \fIversion\fR specifies which version of \s-1GCC\s0 to run. -This is useful when multiple versions are installed. For example, -\&\fIversion\fR might be \fB2.0\fR, meaning to run \s-1GCC\s0 version 2.0. -.Sp -The default version, when you do not specify \fB\-V\fR, is the last -version of \s-1GCC\s0 that you installed. -.PP -The \fB\-b\fR and \fB\-V\fR options actually work by controlling part of -the file name used for the executable files and libraries used for -compilation. A given version of \s-1GCC\s0, for a given target machine, is -normally kept in the directory \fI/usr/local/lib/gcc-lib/\fImachine\fI/\fIversion\fI\fR. -.PP -Thus, sites can customize the effect of \fB\-b\fR or \fB\-V\fR either by -changing the names of these directories or adding alternate names (or -symbolic links). If in directory \fI/usr/local/lib/gcc-lib/\fR the -file \fI80386\fR is a link to the file \fIi386v\fR, then \fB\-b -80386\fR becomes an alias for \fB\-b i386v\fR. -.PP -In one respect, the \fB\-b\fR or \fB\-V\fR do not completely change -to a different compiler: the top-level driver program \fBgcc\fR -that you originally invoked continues to run and invoke the other -executables (preprocessor, compiler per se, assembler and linker) -that do the real work. However, since no real work is done in the -driver program, it usually does not matter that the driver program -in use is not the one for the specified target. It is common for the -interface to the other executables to change incompatibly between -compiler versions, so unless the version specified is very close to that -of the driver (for example, \fB\-V 3.0\fR with a driver program from \s-1GCC\s0 -version 3.0.1), use of \fB\-V\fR may not work; for example, using -\&\fB\-V 2.95.2\fR will not work with a driver program from \s-1GCC\s0 3.0. -.PP -The only way that the driver program depends on the target machine is -in the parsing and handling of special machine-specific options. -However, this is controlled by a file which is found, along with the -other executables, in the directory for the specified version and -target machine. As a result, a single installed driver program adapts -to any specified target machine, and sufficiently similar compiler -versions. -.PP -The driver program executable does control one significant thing, -however: the default version and target machine. Therefore, you can -install different instances of the driver program, compiled for -different targets or versions, under different names. -.PP -For example, if the driver for version 2.0 is installed as \fBogcc\fR -and that for version 2.1 is installed as \fBgcc\fR, then the command -\&\fBgcc\fR will use version 2.1 by default, while \fBogcc\fR will use -2.0 by default. However, you can choose either version with either -command with the \fB\-V\fR option. -.Sh "Hardware Models and Configurations" -.IX Subsection "Hardware Models and Configurations" -Earlier we discussed the standard option \fB\-b\fR which chooses among -different installed compilers for completely different target -machines, such as \s-1VAX\s0 vs. 68000 vs. 80386. -.PP -In addition, each of these target machine types can have its own -special options, starting with \fB\-m\fR, to choose among various -hardware models or configurations\-\-\-for example, 68010 vs 68020, -floating coprocessor or none. A single installed version of the -compiler can compile for any model or configuration, according to the -options specified. -.PP -Some configurations of the compiler also support additional special -options, usually for compatibility with other compilers on the same -platform. -.PP -These options are defined by the macro \f(CW\*(C`TARGET_SWITCHES\*(C'\fR in the -machine description. The default for the options is also defined by -that macro, which enables you to change the defaults. -.PP -.I "M680x0 Options" -.IX Subsection "M680x0 Options" -.PP -These are the \fB\-m\fR options defined for the 68000 series. The default -values for these options depends on which style of 68000 was selected when -the compiler was configured; the defaults for the most common choices are -given below. -.Ip "\fB\-m68000\fR" 4 -.IX Item "-m68000" -.PD 0 -.Ip "\fB\-mc68000\fR" 4 -.IX Item "-mc68000" -.PD -Generate output for a 68000. This is the default -when the compiler is configured for 68000\-based systems. -.Sp -Use this option for microcontrollers with a 68000 or \s-1EC000\s0 core, -including the 68008, 68302, 68306, 68307, 68322, 68328 and 68356. -.Ip "\fB\-m68020\fR" 4 -.IX Item "-m68020" -.PD 0 -.Ip "\fB\-mc68020\fR" 4 -.IX Item "-mc68020" -.PD -Generate output for a 68020. This is the default -when the compiler is configured for 68020\-based systems. -.Ip "\fB\-m68881\fR" 4 -.IX Item "-m68881" -Generate output containing 68881 instructions for floating point. -This is the default for most 68020 systems unless \fB\*(--nfp\fR was -specified when the compiler was configured. -.Ip "\fB\-m68030\fR" 4 -.IX Item "-m68030" -Generate output for a 68030. This is the default when the compiler is -configured for 68030\-based systems. -.Ip "\fB\-m68040\fR" 4 -.IX Item "-m68040" -Generate output for a 68040. This is the default when the compiler is -configured for 68040\-based systems. -.Sp -This option inhibits the use of 68881/68882 instructions that have to be -emulated by software on the 68040. Use this option if your 68040 does not -have code to emulate those instructions. -.Ip "\fB\-m68060\fR" 4 -.IX Item "-m68060" -Generate output for a 68060. This is the default when the compiler is -configured for 68060\-based systems. -.Sp -This option inhibits the use of 68020 and 68881/68882 instructions that -have to be emulated by software on the 68060. Use this option if your 68060 -does not have code to emulate those instructions. -.Ip "\fB\-mcpu32\fR" 4 -.IX Item "-mcpu32" -Generate output for a \s-1CPU32\s0. This is the default -when the compiler is configured for CPU32\-based systems. -.Sp -Use this option for microcontrollers with a -\&\s-1CPU32\s0 or \s-1CPU32+\s0 core, including the 68330, 68331, 68332, 68333, 68334, -68336, 68340, 68341, 68349 and 68360. -.Ip "\fB\-m5200\fR" 4 -.IX Item "-m5200" -Generate output for a 520X ``coldfire'' family cpu. This is the default -when the compiler is configured for 520X-based systems. -.Sp -Use this option for microcontroller with a 5200 core, including -the \s-1MCF5202\s0, \s-1MCF5203\s0, \s-1MCF5204\s0 and \s-1MCF5202\s0. -.Ip "\fB\-m68020\-40\fR" 4 -.IX Item "-m68020-40" -Generate output for a 68040, without using any of the new instructions. -This results in code which can run relatively efficiently on either a -68020/68881 or a 68030 or a 68040. The generated code does use the -68881 instructions that are emulated on the 68040. -.Ip "\fB\-m68020\-60\fR" 4 -.IX Item "-m68020-60" -Generate output for a 68060, without using any of the new instructions. -This results in code which can run relatively efficiently on either a -68020/68881 or a 68030 or a 68040. The generated code does use the -68881 instructions that are emulated on the 68060. -.Ip "\fB\-mfpa\fR" 4 -.IX Item "-mfpa" -Generate output containing Sun \s-1FPA\s0 instructions for floating point. -.Ip "\fB\-msoft-float\fR" 4 -.IX Item "-msoft-float" -Generate output containing library calls for floating point. -\&\fBWarning:\fR the requisite libraries are not available for all m68k -targets. Normally the facilities of the machine's usual C compiler are -used, but this can't be done directly in cross-compilation. You must -make your own arrangements to provide suitable library functions for -cross-compilation. The embedded targets \fBm68k-*\-aout\fR and -\&\fBm68k-*\-coff\fR do provide software floating point support. -.Ip "\fB\-mshort\fR" 4 -.IX Item "-mshort" -Consider type \f(CW\*(C`int\*(C'\fR to be 16 bits wide, like \f(CW\*(C`short int\*(C'\fR. -.Ip "\fB\-mnobitfield\fR" 4 -.IX Item "-mnobitfield" -Do not use the bit-field instructions. The \fB\-m68000\fR, \fB\-mcpu32\fR -and \fB\-m5200\fR options imply \fB\-mnobitfield\fR. -.Ip "\fB\-mbitfield\fR" 4 -.IX Item "-mbitfield" -Do use the bit-field instructions. The \fB\-m68020\fR option implies -\&\fB\-mbitfield\fR. This is the default if you use a configuration -designed for a 68020. -.Ip "\fB\-mrtd\fR" 4 -.IX Item "-mrtd" -Use a different function-calling convention, in which functions -that take a fixed number of arguments return with the \f(CW\*(C`rtd\*(C'\fR -instruction, which pops their arguments while returning. This -saves one instruction in the caller since there is no need to pop -the arguments there. -.Sp -This calling convention is incompatible with the one normally -used on Unix, so you cannot use it if you need to call libraries -compiled with the Unix compiler. -.Sp -Also, you must provide function prototypes for all functions that -take variable numbers of arguments (including \f(CW\*(C`printf\*(C'\fR); -otherwise incorrect code will be generated for calls to those -functions. -.Sp -In addition, seriously incorrect code will result if you call a -function with too many arguments. (Normally, extra arguments are -harmlessly ignored.) -.Sp -The \f(CW\*(C`rtd\*(C'\fR instruction is supported by the 68010, 68020, 68030, -68040, 68060 and \s-1CPU32\s0 processors, but not by the 68000 or 5200. -.Ip "\fB\-malign-int\fR" 4 -.IX Item "-malign-int" -.PD 0 -.Ip "\fB\-mno-align-int\fR" 4 -.IX Item "-mno-align-int" -.PD -Control whether \s-1GCC\s0 aligns \f(CW\*(C`int\*(C'\fR, \f(CW\*(C`long\*(C'\fR, \f(CW\*(C`long long\*(C'\fR, -\&\f(CW\*(C`float\*(C'\fR, \f(CW\*(C`double\*(C'\fR, and \f(CW\*(C`long double\*(C'\fR variables on a 32\-bit -boundary (\fB\-malign-int\fR) or a 16\-bit boundary (\fB\-mno-align-int\fR). -Aligning variables on 32\-bit boundaries produces code that runs somewhat -faster on processors with 32\-bit busses at the expense of more memory. -.Sp -\&\fBWarning:\fR if you use the \fB\-malign-int\fR switch, \s-1GCC\s0 will -align structures containing the above types differently than -most published application binary interface specifications for the m68k. -.Ip "\fB\-mpcrel\fR" 4 -.IX Item "-mpcrel" -Use the pc-relative addressing mode of the 68000 directly, instead of -using a global offset table. At present, this option implies \fB\-fpic\fR, -allowing at most a 16\-bit offset for pc-relative addressing. \fB\-fPIC\fR is -not presently supported with \fB\-mpcrel\fR, though this could be supported for -68020 and higher processors. -.Ip "\fB\-mno-strict-align\fR" 4 -.IX Item "-mno-strict-align" -.PD 0 -.Ip "\fB\-mstrict-align\fR" 4 -.IX Item "-mstrict-align" -.PD -Do not (do) assume that unaligned memory references will be handled by -the system. -.PP -.I "M68hc1x Options" -.IX Subsection "M68hc1x Options" -.PP -These are the \fB\-m\fR options defined for the 68hc11 and 68hc12 -microcontrollers. The default values for these options depends on -which style of microcontroller was selected when the compiler was configured; -the defaults for the most common choices are given below. -.Ip "\fB\-m6811\fR" 4 -.IX Item "-m6811" -.PD 0 -.Ip "\fB\-m68hc11\fR" 4 -.IX Item "-m68hc11" -.PD -Generate output for a 68HC11. This is the default -when the compiler is configured for 68HC11\-based systems. -.Ip "\fB\-m6812\fR" 4 -.IX Item "-m6812" -.PD 0 -.Ip "\fB\-m68hc12\fR" 4 -.IX Item "-m68hc12" -.PD -Generate output for a 68HC12. This is the default -when the compiler is configured for 68HC12\-based systems. -.Ip "\fB\-mauto-incdec\fR" 4 -.IX Item "-mauto-incdec" -Enable the use of 68HC12 pre and post auto-increment and auto-decrement -addressing modes. -.Ip "\fB\-mshort\fR" 4 -.IX Item "-mshort" -Consider type \f(CW\*(C`int\*(C'\fR to be 16 bits wide, like \f(CW\*(C`short int\*(C'\fR. -.Ip "\fB\-msoft-reg-count=\fR\fIcount\fR" 4 -.IX Item "-msoft-reg-count=count" -Specify the number of pseudo-soft registers which are used for the -code generation. The maximum number is 32. Using more pseudo-soft -register may or may not result in better code depending on the program. -The default is 4 for 68HC11 and 2 for 68HC12. -.PP -.I "\s-1VAX\s0 Options" -.IX Subsection "VAX Options" -.PP -These \fB\-m\fR options are defined for the \s-1VAX:\s0 -.Ip "\fB\-munix\fR" 4 -.IX Item "-munix" -Do not output certain jump instructions (\f(CW\*(C`aobleq\*(C'\fR and so on) -that the Unix assembler for the \s-1VAX\s0 cannot handle across long -ranges. -.Ip "\fB\-mgnu\fR" 4 -.IX Item "-mgnu" -Do output those jump instructions, on the assumption that you -will assemble with the \s-1GNU\s0 assembler. -.Ip "\fB\-mg\fR" 4 -.IX Item "-mg" -Output code for g-format floating point numbers instead of d-format. -.PP -.I "\s-1SPARC\s0 Options" -.IX Subsection "SPARC Options" -.PP -These \fB\-m\fR switches are supported on the \s-1SPARC:\s0 -.Ip "\fB\-mno-app-regs\fR" 4 -.IX Item "-mno-app-regs" -.PD 0 -.Ip "\fB\-mapp-regs\fR" 4 -.IX Item "-mapp-regs" -.PD -Specify \fB\-mapp-regs\fR to generate output using the global registers -2 through 4, which the \s-1SPARC\s0 \s-1SVR4\s0 \s-1ABI\s0 reserves for applications. This -is the default. -.Sp -To be fully \s-1SVR4\s0 \s-1ABI\s0 compliant at the cost of some performance loss, -specify \fB\-mno-app-regs\fR. You should compile libraries and system -software with this option. -.Ip "\fB\-mfpu\fR" 4 -.IX Item "-mfpu" -.PD 0 -.Ip "\fB\-mhard-float\fR" 4 -.IX Item "-mhard-float" -.PD -Generate output containing floating point instructions. This is the -default. -.Ip "\fB\-mno-fpu\fR" 4 -.IX Item "-mno-fpu" -.PD 0 -.Ip "\fB\-msoft-float\fR" 4 -.IX Item "-msoft-float" -.PD -Generate output containing library calls for floating point. -\&\fBWarning:\fR the requisite libraries are not available for all \s-1SPARC\s0 -targets. Normally the facilities of the machine's usual C compiler are -used, but this cannot be done directly in cross-compilation. You must make -your own arrangements to provide suitable library functions for -cross-compilation. The embedded targets \fBsparc-*\-aout\fR and -\&\fBsparclite-*\-*\fR do provide software floating point support. -.Sp -\&\fB\-msoft-float\fR changes the calling convention in the output file; -therefore, it is only useful if you compile \fIall\fR of a program with -this option. In particular, you need to compile \fIlibgcc.a\fR, the -library that comes with \s-1GCC\s0, with \fB\-msoft-float\fR in order for -this to work. -.Ip "\fB\-mhard-quad-float\fR" 4 -.IX Item "-mhard-quad-float" -Generate output containing quad-word (long double) floating point -instructions. -.Ip "\fB\-msoft-quad-float\fR" 4 -.IX Item "-msoft-quad-float" -Generate output containing library calls for quad-word (long double) -floating point instructions. The functions called are those specified -in the \s-1SPARC\s0 \s-1ABI\s0. This is the default. -.Sp -As of this writing, there are no sparc implementations that have hardware -support for the quad-word floating point instructions. They all invoke -a trap handler for one of these instructions, and then the trap handler -emulates the effect of the instruction. Because of the trap handler overhead, -this is much slower than calling the \s-1ABI\s0 library routines. Thus the -\&\fB\-msoft-quad-float\fR option is the default. -.Ip "\fB\-mno-flat\fR" 4 -.IX Item "-mno-flat" -.PD 0 -.Ip "\fB\-mflat\fR" 4 -.IX Item "-mflat" -.PD -With \fB\-mflat\fR, the compiler does not generate save/restore instructions -and will use a ``flat'' or single register window calling convention. -This model uses \f(CW%i7\fR as the frame pointer and is compatible with the normal -register window model. Code from either may be intermixed. -The local registers and the input registers (0\*(--5) are still treated as -``call saved'' registers and will be saved on the stack as necessary. -.Sp -With \fB\-mno-flat\fR (the default), the compiler emits save/restore -instructions (except for leaf functions) and is the normal mode of operation. -.Ip "\fB\-mno-unaligned-doubles\fR" 4 -.IX Item "-mno-unaligned-doubles" -.PD 0 -.Ip "\fB\-munaligned-doubles\fR" 4 -.IX Item "-munaligned-doubles" -.PD -Assume that doubles have 8 byte alignment. This is the default. -.Sp -With \fB\-munaligned-doubles\fR, \s-1GCC\s0 assumes that doubles have 8 byte -alignment only if they are contained in another type, or if they have an -absolute address. Otherwise, it assumes they have 4 byte alignment. -Specifying this option avoids some rare compatibility problems with code -generated by other compilers. It is not the default because it results -in a performance loss, especially for floating point code. -.Ip "\fB\-mno-faster-structs\fR" 4 -.IX Item "-mno-faster-structs" -.PD 0 -.Ip "\fB\-mfaster-structs\fR" 4 -.IX Item "-mfaster-structs" -.PD -With \fB\-mfaster-structs\fR, the compiler assumes that structures -should have 8 byte alignment. This enables the use of pairs of -\&\f(CW\*(C`ldd\*(C'\fR and \f(CW\*(C`std\*(C'\fR instructions for copies in structure -assignment, in place of twice as many \f(CW\*(C`ld\*(C'\fR and \f(CW\*(C`st\*(C'\fR pairs. -However, the use of this changed alignment directly violates the Sparc -\&\s-1ABI\s0. Thus, it's intended only for use on targets where the developer -acknowledges that their resulting code will not be directly in line with -the rules of the \s-1ABI\s0. -.Ip "\fB\-mv8\fR" 4 -.IX Item "-mv8" -.PD 0 -.Ip "\fB\-msparclite\fR" 4 -.IX Item "-msparclite" -.PD -These two options select variations on the \s-1SPARC\s0 architecture. -.Sp -By default (unless specifically configured for the Fujitsu SPARClite), -\&\s-1GCC\s0 generates code for the v7 variant of the \s-1SPARC\s0 architecture. -.Sp -\&\fB\-mv8\fR will give you \s-1SPARC\s0 v8 code. The only difference from v7 -code is that the compiler emits the integer multiply and integer -divide instructions which exist in \s-1SPARC\s0 v8 but not in \s-1SPARC\s0 v7. -.Sp -\&\fB\-msparclite\fR will give you SPARClite code. This adds the integer -multiply, integer divide step and scan (\f(CW\*(C`ffs\*(C'\fR) instructions which -exist in SPARClite but not in \s-1SPARC\s0 v7. -.Sp -These options are deprecated and will be deleted in a future \s-1GCC\s0 release. -They have been replaced with \fB\-mcpu=xxx\fR. -.Ip "\fB\-mcypress\fR" 4 -.IX Item "-mcypress" -.PD 0 -.Ip "\fB\-msupersparc\fR" 4 -.IX Item "-msupersparc" -.PD -These two options select the processor for which the code is optimized. -.Sp -With \fB\-mcypress\fR (the default), the compiler optimizes code for the -Cypress \s-1CY7C602\s0 chip, as used in the SparcStation/SparcServer 3xx series. -This is also appropriate for the older SparcStation 1, 2, \s-1IPX\s0 etc. -.Sp -With \fB\-msupersparc\fR the compiler optimizes code for the SuperSparc cpu, as -used in the SparcStation 10, 1000 and 2000 series. This flag also enables use -of the full \s-1SPARC\s0 v8 instruction set. -.Sp -These options are deprecated and will be deleted in a future \s-1GCC\s0 release. -They have been replaced with \fB\-mcpu=xxx\fR. -.Ip "\fB\-mcpu=\fR\fIcpu_type\fR" 4 -.IX Item "-mcpu=cpu_type" -Set the instruction set, register set, and instruction scheduling parameters -for machine type \fIcpu_type\fR. Supported values for \fIcpu_type\fR are -\&\fBv7\fR, \fBcypress\fR, \fBv8\fR, \fBsupersparc\fR, \fBsparclite\fR, -\&\fBhypersparc\fR, \fBsparclite86x\fR, \fBf930\fR, \fBf934\fR, -\&\fBsparclet\fR, \fBtsc701\fR, \fBv9\fR, and \fBultrasparc\fR. -.Sp -Default instruction scheduling parameters are used for values that select -an architecture and not an implementation. These are \fBv7\fR, \fBv8\fR, -\&\fBsparclite\fR, \fBsparclet\fR, \fBv9\fR. -.Sp -Here is a list of each supported architecture and their supported -implementations. -.Sp -.Vb 5 -\& v7: cypress -\& v8: supersparc, hypersparc -\& sparclite: f930, f934, sparclite86x -\& sparclet: tsc701 -\& v9: ultrasparc -.Ve -.Ip "\fB\-mtune=\fR\fIcpu_type\fR" 4 -.IX Item "-mtune=cpu_type" -Set the instruction scheduling parameters for machine type -\&\fIcpu_type\fR, but do not set the instruction set or register set that the -option \fB\-mcpu=\fR\fIcpu_type\fR would. -.Sp -The same values for \fB\-mcpu=\fR\fIcpu_type\fR can be used for -\&\fB\-mtune=\fR\fIcpu_type\fR, but the only useful values are those -that select a particular cpu implementation. Those are \fBcypress\fR, -\&\fBsupersparc\fR, \fBhypersparc\fR, \fBf930\fR, \fBf934\fR, -\&\fBsparclite86x\fR, \fBtsc701\fR, and \fBultrasparc\fR. -.PP -These \fB\-m\fR switches are supported in addition to the above -on the \s-1SPARCLET\s0 processor. -.Ip "\fB\-mlittle-endian\fR" 4 -.IX Item "-mlittle-endian" -Generate code for a processor running in little-endian mode. -.Ip "\fB\-mlive-g0\fR" 4 -.IX Item "-mlive-g0" -Treat register \f(CW\*(C`%g0\*(C'\fR as a normal register. -\&\s-1GCC\s0 will continue to clobber it as necessary but will not assume -it always reads as 0. -.Ip "\fB\-mbroken-saverestore\fR" 4 -.IX Item "-mbroken-saverestore" -Generate code that does not use non-trivial forms of the \f(CW\*(C`save\*(C'\fR and -\&\f(CW\*(C`restore\*(C'\fR instructions. Early versions of the \s-1SPARCLET\s0 processor do -not correctly handle \f(CW\*(C`save\*(C'\fR and \f(CW\*(C`restore\*(C'\fR instructions used with -arguments. They correctly handle them used without arguments. A \f(CW\*(C`save\*(C'\fR -instruction used without arguments increments the current window pointer -but does not allocate a new stack frame. It is assumed that the window -overflow trap handler will properly handle this case as will interrupt -handlers. -.PP -These \fB\-m\fR switches are supported in addition to the above -on \s-1SPARC\s0 V9 processors in 64\-bit environments. -.Ip "\fB\-mlittle-endian\fR" 4 -.IX Item "-mlittle-endian" -Generate code for a processor running in little-endian mode. -.Ip "\fB\-m32\fR" 4 -.IX Item "-m32" -.PD 0 -.Ip "\fB\-m64\fR" 4 -.IX Item "-m64" -.PD -Generate code for a 32\-bit or 64\-bit environment. -The 32\-bit environment sets int, long and pointer to 32 bits. -The 64\-bit environment sets int to 32 bits and long and pointer -to 64 bits. -.Ip "\fB\-mcmodel=medlow\fR" 4 -.IX Item "-mcmodel=medlow" -Generate code for the Medium/Low code model: the program must be linked -in the low 32 bits of the address space. Pointers are 64 bits. -Programs can be statically or dynamically linked. -.Ip "\fB\-mcmodel=medmid\fR" 4 -.IX Item "-mcmodel=medmid" -Generate code for the Medium/Middle code model: the program must be linked -in the low 44 bits of the address space, the text segment must be less than -2G bytes, and data segment must be within 2G of the text segment. -Pointers are 64 bits. -.Ip "\fB\-mcmodel=medany\fR" 4 -.IX Item "-mcmodel=medany" -Generate code for the Medium/Anywhere code model: the program may be linked -anywhere in the address space, the text segment must be less than -2G bytes, and data segment must be within 2G of the text segment. -Pointers are 64 bits. -.Ip "\fB\-mcmodel=embmedany\fR" 4 -.IX Item "-mcmodel=embmedany" -Generate code for the Medium/Anywhere code model for embedded systems: -assume a 32\-bit text and a 32\-bit data segment, both starting anywhere -(determined at link time). Register \f(CW%g4\fR points to the base of the -data segment. Pointers are still 64 bits. -Programs are statically linked, \s-1PIC\s0 is not supported. -.Ip "\fB\-mstack-bias\fR" 4 -.IX Item "-mstack-bias" -.PD 0 -.Ip "\fB\-mno-stack-bias\fR" 4 -.IX Item "-mno-stack-bias" -.PD -With \fB\-mstack-bias\fR, \s-1GCC\s0 assumes that the stack pointer, and -frame pointer if present, are offset by \-2047 which must be added back -when making stack frame references. -Otherwise, assume no such offset is present. -.PP -.I "Convex Options" -.IX Subsection "Convex Options" -.PP -These \fB\-m\fR options are defined for Convex: -.Ip "\fB\-mc1\fR" 4 -.IX Item "-mc1" -Generate output for C1. The code will run on any Convex machine. -The preprocessor symbol \f(CW\*(C`_\|_convex_\|_c1_\|_\*(C'\fR is defined. -.Ip "\fB\-mc2\fR" 4 -.IX Item "-mc2" -Generate output for C2. Uses instructions not available on C1. -Scheduling and other optimizations are chosen for max performance on C2. -The preprocessor symbol \f(CW\*(C`_\|_convex_c2_\|_\*(C'\fR is defined. -.Ip "\fB\-mc32\fR" 4 -.IX Item "-mc32" -Generate output for C32xx. Uses instructions not available on C1. -Scheduling and other optimizations are chosen for max performance on C32. -The preprocessor symbol \f(CW\*(C`_\|_convex_c32_\|_\*(C'\fR is defined. -.Ip "\fB\-mc34\fR" 4 -.IX Item "-mc34" -Generate output for C34xx. Uses instructions not available on C1. -Scheduling and other optimizations are chosen for max performance on C34. -The preprocessor symbol \f(CW\*(C`_\|_convex_c34_\|_\*(C'\fR is defined. -.Ip "\fB\-mc38\fR" 4 -.IX Item "-mc38" -Generate output for C38xx. Uses instructions not available on C1. -Scheduling and other optimizations are chosen for max performance on C38. -The preprocessor symbol \f(CW\*(C`_\|_convex_c38_\|_\*(C'\fR is defined. -.Ip "\fB\-margcount\fR" 4 -.IX Item "-margcount" -Generate code which puts an argument count in the word preceding each -argument list. This is compatible with regular \s-1CC\s0, and a few programs -may need the argument count word. \s-1GDB\s0 and other source-level debuggers -do not need it; this info is in the symbol table. -.Ip "\fB\-mnoargcount\fR" 4 -.IX Item "-mnoargcount" -Omit the argument count word. This is the default. -.Ip "\fB\-mvolatile-cache\fR" 4 -.IX Item "-mvolatile-cache" -Allow volatile references to be cached. This is the default. -.Ip "\fB\-mvolatile-nocache\fR" 4 -.IX Item "-mvolatile-nocache" -Volatile references bypass the data cache, going all the way to memory. -This is only needed for multi-processor code that does not use standard -synchronization instructions. Making non-volatile references to volatile -locations will not necessarily work. -.Ip "\fB\-mlong32\fR" 4 -.IX Item "-mlong32" -Type long is 32 bits, the same as type int. This is the default. -.Ip "\fB\-mlong64\fR" 4 -.IX Item "-mlong64" -Type long is 64 bits, the same as type long long. This option is useless, -because no library support exists for it. -.PP -.I "\s-1AMD29K\s0 Options" -.IX Subsection "AMD29K Options" -.PP -These \fB\-m\fR options are defined for the \s-1AMD\s0 Am29000: -.Ip "\fB\-mdw\fR" 4 -.IX Item "-mdw" -Generate code that assumes the \f(CW\*(C`DW\*(C'\fR bit is set, i.e., that byte and -halfword operations are directly supported by the hardware. This is the -default. -.Ip "\fB\-mndw\fR" 4 -.IX Item "-mndw" -Generate code that assumes the \f(CW\*(C`DW\*(C'\fR bit is not set. -.Ip "\fB\-mbw\fR" 4 -.IX Item "-mbw" -Generate code that assumes the system supports byte and halfword write -operations. This is the default. -.Ip "\fB\-mnbw\fR" 4 -.IX Item "-mnbw" -Generate code that assumes the systems does not support byte and -halfword write operations. \fB\-mnbw\fR implies \fB\-mndw\fR. -.Ip "\fB\-msmall\fR" 4 -.IX Item "-msmall" -Use a small memory model that assumes that all function addresses are -either within a single 256 \s-1KB\s0 segment or at an absolute address of less -than 256k. This allows the \f(CW\*(C`call\*(C'\fR instruction to be used instead -of a \f(CW\*(C`const\*(C'\fR, \f(CW\*(C`consth\*(C'\fR, \f(CW\*(C`calli\*(C'\fR sequence. -.Ip "\fB\-mnormal\fR" 4 -.IX Item "-mnormal" -Use the normal memory model: Generate \f(CW\*(C`call\*(C'\fR instructions only when -calling functions in the same file and \f(CW\*(C`calli\*(C'\fR instructions -otherwise. This works if each file occupies less than 256 \s-1KB\s0 but allows -the entire executable to be larger than 256 \s-1KB\s0. This is the default. -.Ip "\fB\-mlarge\fR" 4 -.IX Item "-mlarge" -Always use \f(CW\*(C`calli\*(C'\fR instructions. Specify this option if you expect -a single file to compile into more than 256 \s-1KB\s0 of code. -.Ip "\fB\-m29050\fR" 4 -.IX Item "-m29050" -Generate code for the Am29050. -.Ip "\fB\-m29000\fR" 4 -.IX Item "-m29000" -Generate code for the Am29000. This is the default. -.Ip "\fB\-mkernel-registers\fR" 4 -.IX Item "-mkernel-registers" -Generate references to registers \f(CW\*(C`gr64\-gr95\*(C'\fR instead of to -registers \f(CW\*(C`gr96\-gr127\*(C'\fR. This option can be used when compiling -kernel code that wants a set of global registers disjoint from that used -by user-mode code. -.Sp -Note that when this option is used, register names in \fB\-f\fR flags -must use the normal, user-mode, names. -.Ip "\fB\-muser-registers\fR" 4 -.IX Item "-muser-registers" -Use the normal set of global registers, \f(CW\*(C`gr96\-gr127\*(C'\fR. This is the -default. -.Ip "\fB\-mstack-check\fR" 4 -.IX Item "-mstack-check" -.PD 0 -.Ip "\fB\-mno-stack-check\fR" 4 -.IX Item "-mno-stack-check" -.PD -Insert (or do not insert) a call to \f(CW\*(C`_\|_msp_check\*(C'\fR after each stack -adjustment. This is often used for kernel code. -.Ip "\fB\-mstorem-bug\fR" 4 -.IX Item "-mstorem-bug" -.PD 0 -.Ip "\fB\-mno-storem-bug\fR" 4 -.IX Item "-mno-storem-bug" -.PD -\&\fB\-mstorem-bug\fR handles 29k processors which cannot handle the -separation of a mtsrim insn and a storem instruction (most 29000 chips -to date, but not the 29050). -.Ip "\fB\-mno-reuse-arg-regs\fR" 4 -.IX Item "-mno-reuse-arg-regs" -.PD 0 -.Ip "\fB\-mreuse-arg-regs\fR" 4 -.IX Item "-mreuse-arg-regs" -.PD -\&\fB\-mno-reuse-arg-regs\fR tells the compiler to only use incoming argument -registers for copying out arguments. This helps detect calling a function -with fewer arguments than it was declared with. -.Ip "\fB\-mno-impure-text\fR" 4 -.IX Item "-mno-impure-text" -.PD 0 -.Ip "\fB\-mimpure-text\fR" 4 -.IX Item "-mimpure-text" -.PD -\&\fB\-mimpure-text\fR, used in addition to \fB\-shared\fR, tells the compiler to -not pass \fB\-assert pure-text\fR to the linker when linking a shared object. -.Ip "\fB\-msoft-float\fR" 4 -.IX Item "-msoft-float" -Generate output containing library calls for floating point. -\&\fBWarning:\fR the requisite libraries are not part of \s-1GCC\s0. -Normally the facilities of the machine's usual C compiler are used, but -this can't be done directly in cross-compilation. You must make your -own arrangements to provide suitable library functions for -cross-compilation. -.Ip "\fB\-mno-multm\fR" 4 -.IX Item "-mno-multm" -Do not generate multm or multmu instructions. This is useful for some embedded -systems which do not have trap handlers for these instructions. -.PP -.I "\s-1ARM\s0 Options" -.IX Subsection "ARM Options" -.PP -These \fB\-m\fR options are defined for Advanced \s-1RISC\s0 Machines (\s-1ARM\s0) -architectures: -.Ip "\fB\-mapcs-frame\fR" 4 -.IX Item "-mapcs-frame" -Generate a stack frame that is compliant with the \s-1ARM\s0 Procedure Call -Standard for all functions, even if this is not strictly necessary for -correct execution of the code. Specifying \fB\-fomit-frame-pointer\fR -with this option will cause the stack frames not to be generated for -leaf functions. The default is \fB\-mno-apcs-frame\fR. -.Ip "\fB\-mapcs\fR" 4 -.IX Item "-mapcs" -This is a synonym for \fB\-mapcs-frame\fR. -.Ip "\fB\-mapcs-26\fR" 4 -.IX Item "-mapcs-26" -Generate code for a processor running with a 26\-bit program counter, -and conforming to the function calling standards for the \s-1APCS\s0 26\-bit -option. This option replaces the \fB\-m2\fR and \fB\-m3\fR options -of previous releases of the compiler. -.Ip "\fB\-mapcs-32\fR" 4 -.IX Item "-mapcs-32" -Generate code for a processor running with a 32\-bit program counter, -and conforming to the function calling standards for the \s-1APCS\s0 32\-bit -option. This option replaces the \fB\-m6\fR option of previous releases -of the compiler. -.Ip "\fB\-mthumb-interwork\fR" 4 -.IX Item "-mthumb-interwork" -Generate code which supports calling between the \s-1ARM\s0 and Thumb -instruction sets. Without this option the two instruction sets cannot -be reliably used inside one program. The default is -\&\fB\-mno-thumb-interwork\fR, since slightly larger code is generated -when \fB\-mthumb-interwork\fR is specified. -.Ip "\fB\-mno-sched-prolog\fR" 4 -.IX Item "-mno-sched-prolog" -Prevent the reordering of instructions in the function prolog, or the -merging of those instruction with the instructions in the function's -body. This means that all functions will start with a recognizable set -of instructions (or in fact one of a choice from a small set of -different function prologues), and this information can be used to -locate the start if functions inside an executable piece of code. The -default is \fB\-msched-prolog\fR. -.Ip "\fB\-mhard-float\fR" 4 -.IX Item "-mhard-float" -Generate output containing floating point instructions. This is the -default. -.Ip "\fB\-msoft-float\fR" 4 -.IX Item "-msoft-float" -Generate output containing library calls for floating point. -\&\fBWarning:\fR the requisite libraries are not available for all \s-1ARM\s0 -targets. Normally the facilities of the machine's usual C compiler are -used, but this cannot be done directly in cross-compilation. You must make -your own arrangements to provide suitable library functions for -cross-compilation. -.Sp -\&\fB\-msoft-float\fR changes the calling convention in the output file; -therefore, it is only useful if you compile \fIall\fR of a program with -this option. In particular, you need to compile \fIlibgcc.a\fR, the -library that comes with \s-1GCC\s0, with \fB\-msoft-float\fR in order for -this to work. -.Ip "\fB\-mlittle-endian\fR" 4 -.IX Item "-mlittle-endian" -Generate code for a processor running in little-endian mode. This is -the default for all standard configurations. -.Ip "\fB\-mbig-endian\fR" 4 -.IX Item "-mbig-endian" -Generate code for a processor running in big-endian mode; the default is -to compile code for a little-endian processor. -.Ip "\fB\-mwords-little-endian\fR" 4 -.IX Item "-mwords-little-endian" -This option only applies when generating code for big-endian processors. -Generate code for a little-endian word order but a big-endian byte -order. That is, a byte order of the form \fB32107654\fR. Note: this -option should only be used if you require compatibility with code for -big-endian \s-1ARM\s0 processors generated by versions of the compiler prior to -2.8. -.Ip "\fB\-malignment-traps\fR" 4 -.IX Item "-malignment-traps" -Generate code that will not trap if the \s-1MMU\s0 has alignment traps enabled. -On \s-1ARM\s0 architectures prior to ARMv4, there were no instructions to -access half-word objects stored in memory. However, when reading from -memory a feature of the \s-1ARM\s0 architecture allows a word load to be used, -even if the address is unaligned, and the processor core will rotate the -data as it is being loaded. This option tells the compiler that such -misaligned accesses will cause a \s-1MMU\s0 trap and that it should instead -synthesise the access as a series of byte accesses. The compiler can -still use word accesses to load half-word data if it knows that the -address is aligned to a word boundary. -.Sp -This option is ignored when compiling for \s-1ARM\s0 architecture 4 or later, -since these processors have instructions to directly access half-word -objects in memory. -.Ip "\fB\-mno-alignment-traps\fR" 4 -.IX Item "-mno-alignment-traps" -Generate code that assumes that the \s-1MMU\s0 will not trap unaligned -accesses. This produces better code when the target instruction set -does not have half-word memory operations (i.e. implementations prior to -ARMv4). -.Sp -Note that you cannot use this option to access unaligned word objects, -since the processor will only fetch one 32\-bit aligned object from -memory. -.Sp -The default setting for most targets is \fB\-mno-alignment-traps\fR, since -this produces better code when there are no half-word memory -instructions available. -.Ip "\fB\-mshort-load-bytes\fR" 4 -.IX Item "-mshort-load-bytes" -.PD 0 -.Ip "\fB\-mno-short-load-words\fR" 4 -.IX Item "-mno-short-load-words" -.PD -These are deprecated aliases for \fB\-malignment-traps\fR. -.Ip "\fB\-mno-short-load-bytes\fR" 4 -.IX Item "-mno-short-load-bytes" -.PD 0 -.Ip "\fB\-mshort-load-words\fR" 4 -.IX Item "-mshort-load-words" -.PD -This are deprecated aliases for \fB\-mno-alignment-traps\fR. -.Ip "\fB\-mbsd\fR" 4 -.IX Item "-mbsd" -This option only applies to \s-1RISC\s0 iX. Emulate the native BSD-mode -compiler. This is the default if \fB\-ansi\fR is not specified. -.Ip "\fB\-mxopen\fR" 4 -.IX Item "-mxopen" -This option only applies to \s-1RISC\s0 iX. Emulate the native X/Open-mode -compiler. -.Ip "\fB\-mno-symrename\fR" 4 -.IX Item "-mno-symrename" -This option only applies to \s-1RISC\s0 iX. Do not run the assembler -post-processor, \fBsymrename\fR, after code has been assembled. -Normally it is necessary to modify some of the standard symbols in -preparation for linking with the \s-1RISC\s0 iX C library; this option -suppresses this pass. The post-processor is never run when the -compiler is built for cross-compilation. -.Ip "\fB\-mcpu=\fR\fIname\fR" 4 -.IX Item "-mcpu=name" -This specifies the name of the target \s-1ARM\s0 processor. \s-1GCC\s0 uses this name -to determine what kind of instructions it can emit when generating -assembly code. Permissible names are: \fBarm2\fR, \fBarm250\fR, -\&\fBarm3\fR, \fBarm6\fR, \fBarm60\fR, \fBarm600\fR, \fBarm610\fR, -\&\fBarm620\fR, \fBarm7\fR, \fBarm7m\fR, \fBarm7d\fR, \fBarm7dm\fR, -\&\fBarm7di\fR, \fBarm7dmi\fR, \fBarm70\fR, \fBarm700\fR, -\&\fBarm700i\fR, \fBarm710\fR, \fBarm710c\fR, \fBarm7100\fR, -\&\fBarm7500\fR, \fBarm7500fe\fR, \fBarm7tdmi\fR, \fBarm8\fR, -\&\fBstrongarm\fR, \fBstrongarm110\fR, \fBstrongarm1100\fR, -\&\fBarm8\fR, \fBarm810\fR, \fBarm9\fR, \fBarm9e\fR, \fBarm920\fR, -\&\fBarm920t\fR, \fBarm940t\fR, \fBarm9tdmi\fR, \fBarm10tdmi\fR, -\&\fBarm1020t\fR, \fBxscale\fR. -.Ip "\fB\-mtune=\fR\fIname\fR" 4 -.IX Item "-mtune=name" -This option is very similar to the \fB\-mcpu=\fR option, except that -instead of specifying the actual target processor type, and hence -restricting which instructions can be used, it specifies that \s-1GCC\s0 should -tune the performance of the code as if the target were of the type -specified in this option, but still choosing the instructions that it -will generate based on the cpu specified by a \fB\-mcpu=\fR option. -For some \s-1ARM\s0 implementations better performance can be obtained by using -this option. -.Ip "\fB\-march=\fR\fIname\fR" 4 -.IX Item "-march=name" -This specifies the name of the target \s-1ARM\s0 architecture. \s-1GCC\s0 uses this -name to determine what kind of instructions it can emit when generating -assembly code. This option can be used in conjunction with or instead -of the \fB\-mcpu=\fR option. Permissible names are: \fBarmv2\fR, -\&\fBarmv2a\fR, \fBarmv3\fR, \fBarmv3m\fR, \fBarmv4\fR, \fBarmv4t\fR, -\&\fBarmv5\fR, \fBarmv5t\fR, \fBarmv5te\fR. -.Ip "\fB\-mfpe=\fR\fInumber\fR" 4 -.IX Item "-mfpe=number" -.PD 0 -.Ip "\fB\-mfp=\fR\fInumber\fR" 4 -.IX Item "-mfp=number" -.PD -This specifies the version of the floating point emulation available on -the target. Permissible values are 2 and 3. \fB\-mfp=\fR is a synonym -for \fB\-mfpe=\fR, for compatibility with older versions of \s-1GCC\s0. -.Ip "\fB\-mstructure-size-boundary=\fR\fIn\fR" 4 -.IX Item "-mstructure-size-boundary=n" -The size of all structures and unions will be rounded up to a multiple -of the number of bits set by this option. Permissible values are 8 and -32. The default value varies for different toolchains. For the \s-1COFF\s0 -targeted toolchain the default value is 8. Specifying the larger number -can produce faster, more efficient code, but can also increase the size -of the program. The two values are potentially incompatible. Code -compiled with one value cannot necessarily expect to work with code or -libraries compiled with the other value, if they exchange information -using structures or unions. -.Ip "\fB\-mabort-on-noreturn\fR" 4 -.IX Item "-mabort-on-noreturn" -Generate a call to the function \f(CW\*(C`abort\*(C'\fR at the end of a -\&\f(CW\*(C`noreturn\*(C'\fR function. It will be executed if the function tries to -return. -.Ip "\fB\-mlong-calls\fR" 4 -.IX Item "-mlong-calls" -.PD 0 -.Ip "\fB\-mno-long-calls\fR" 4 -.IX Item "-mno-long-calls" -.PD -Tells the compiler to perform function calls by first loading the -address of the function into a register and then performing a subroutine -call on this register. This switch is needed if the target function -will lie outside of the 64 megabyte addressing range of the offset based -version of subroutine call instruction. -.Sp -Even if this switch is enabled, not all function calls will be turned -into long calls. The heuristic is that static functions, functions -which have the \fBshort-call\fR attribute, functions that are inside -the scope of a \fB#pragma no_long_calls\fR directive and functions whose -definitions have already been compiled within the current compilation -unit, will not be turned into long calls. The exception to this rule is -that weak function definitions, functions with the \fBlong-call\fR -attribute or the \fBsection\fR attribute, and functions that are within -the scope of a \fB#pragma long_calls\fR directive, will always be -turned into long calls. -.Sp -This feature is not enabled by default. Specifying -\&\fB\-mno-long-calls\fR will restore the default behavior, as will -placing the function calls within the scope of a \fB#pragma -long_calls_off\fR directive. Note these switches have no effect on how -the compiler generates code to handle function calls via function -pointers. -.Ip "\fB\-mnop-fun-dllimport\fR" 4 -.IX Item "-mnop-fun-dllimport" -Disable support for the \f(CW\*(C`dllimport\*(C'\fR attribute. -.Ip "\fB\-msingle-pic-base\fR" 4 -.IX Item "-msingle-pic-base" -Treat the register used for \s-1PIC\s0 addressing as read-only, rather than -loading it in the prologue for each function. The run-time system is -responsible for initializing this register with an appropriate value -before execution begins. -.Ip "\fB\-mpic-register=\fR\fIreg\fR" 4 -.IX Item "-mpic-register=reg" -Specify the register to be used for \s-1PIC\s0 addressing. The default is R10 -unless stack-checking is enabled, when R9 is used. -.Ip "\fB\-mpoke-function-name\fR" 4 -.IX Item "-mpoke-function-name" -Write the name of each function into the text section, directly -preceding the function prologue. The generated code is similar to this: -.Sp -.Vb 9 -\& t0 -\& .ascii "arm_poke_function_name", 0 -\& .align -\& t1 -\& .word 0xff000000 + (t1 - t0) -\& arm_poke_function_name -\& mov ip, sp -\& stmfd sp!, {fp, ip, lr, pc} -\& sub fp, ip, #4 -.Ve -When performing a stack backtrace, code can inspect the value of -\&\f(CW\*(C`pc\*(C'\fR stored at \f(CW\*(C`fp + 0\*(C'\fR. If the trace function then looks at -location \f(CW\*(C`pc \- 12\*(C'\fR and the top 8 bits are set, then we know that -there is a function name embedded immediately preceding this location -and has length \f(CW\*(C`((pc[\-3]) & 0xff000000)\*(C'\fR. -.Ip "\fB\-mthumb\fR" 4 -.IX Item "-mthumb" -Generate code for the 16\-bit Thumb instruction set. The default is to -use the 32\-bit \s-1ARM\s0 instruction set. -.Ip "\fB\-mtpcs-frame\fR" 4 -.IX Item "-mtpcs-frame" -Generate a stack frame that is compliant with the Thumb Procedure Call -Standard for all non-leaf functions. (A leaf function is one that does -not call any other functions.) The default is \fB\-mno-tpcs-frame\fR. -.Ip "\fB\-mtpcs-leaf-frame\fR" 4 -.IX Item "-mtpcs-leaf-frame" -Generate a stack frame that is compliant with the Thumb Procedure Call -Standard for all leaf functions. (A leaf function is one that does -not call any other functions.) The default is \fB\-mno-apcs-leaf-frame\fR. -.Ip "\fB\-mcallee-super-interworking\fR" 4 -.IX Item "-mcallee-super-interworking" -Gives all externally visible functions in the file being compiled an \s-1ARM\s0 -instruction set header which switches to Thumb mode before executing the -rest of the function. This allows these functions to be called from -non-interworking code. -.Ip "\fB\-mcaller-super-interworking\fR" 4 -.IX Item "-mcaller-super-interworking" -Allows calls via function pointers (including virtual functions) to -execute correctly regardless of whether the target code has been -compiled for interworking or not. There is a small overhead in the cost -of executing a function pointer if this option is enabled. -.PP -.I "\s-1MN10200\s0 Options" -.IX Subsection "MN10200 Options" -.PP -These \fB\-m\fR options are defined for Matsushita \s-1MN10200\s0 architectures: -.Ip "\fB\-mrelax\fR" 4 -.IX Item "-mrelax" -Indicate to the linker that it should perform a relaxation optimization pass -to shorten branches, calls and absolute memory addresses. This option only -has an effect when used on the command line for the final link step. -.Sp -This option makes symbolic debugging impossible. -.PP -.I "\s-1MN10300\s0 Options" -.IX Subsection "MN10300 Options" -.PP -These \fB\-m\fR options are defined for Matsushita \s-1MN10300\s0 architectures: -.Ip "\fB\-mmult-bug\fR" 4 -.IX Item "-mmult-bug" -Generate code to avoid bugs in the multiply instructions for the \s-1MN10300\s0 -processors. This is the default. -.Ip "\fB\-mno-mult-bug\fR" 4 -.IX Item "-mno-mult-bug" -Do not generate code to avoid bugs in the multiply instructions for the -\&\s-1MN10300\s0 processors. -.Ip "\fB\-mam33\fR" 4 -.IX Item "-mam33" -Generate code which uses features specific to the \s-1AM33\s0 processor. -.Ip "\fB\-mno-am33\fR" 4 -.IX Item "-mno-am33" -Do not generate code which uses features specific to the \s-1AM33\s0 processor. This -is the default. -.Ip "\fB\-mno-crt0\fR" 4 -.IX Item "-mno-crt0" -Do not link in the C run-time initialization object file. -.Ip "\fB\-mrelax\fR" 4 -.IX Item "-mrelax" -Indicate to the linker that it should perform a relaxation optimization pass -to shorten branches, calls and absolute memory addresses. This option only -has an effect when used on the command line for the final link step. -.Sp -This option makes symbolic debugging impossible. -.PP -.I "M32R/D Options" -.IX Subsection "M32R/D Options" -.PP -These \fB\-m\fR options are defined for Mitsubishi M32R/D architectures: -.Ip "\fB\-m32rx\fR" 4 -.IX Item "-m32rx" -Generate code for the M32R/X. -.Ip "\fB\-m32r\fR" 4 -.IX Item "-m32r" -Generate code for the M32R. This is the default. -.Ip "\fB\-mcode-model=small\fR" 4 -.IX Item "-mcode-model=small" -Assume all objects live in the lower 16MB of memory (so that their addresses -can be loaded with the \f(CW\*(C`ld24\*(C'\fR instruction), and assume all subroutines -are reachable with the \f(CW\*(C`bl\*(C'\fR instruction. -This is the default. -.Sp -The addressability of a particular object can be set with the -\&\f(CW\*(C`model\*(C'\fR attribute. -.Ip "\fB\-mcode-model=medium\fR" 4 -.IX Item "-mcode-model=medium" -Assume objects may be anywhere in the 32\-bit address space (the compiler -will generate \f(CW\*(C`seth/add3\*(C'\fR instructions to load their addresses), and -assume all subroutines are reachable with the \f(CW\*(C`bl\*(C'\fR instruction. -.Ip "\fB\-mcode-model=large\fR" 4 -.IX Item "-mcode-model=large" -Assume objects may be anywhere in the 32\-bit address space (the compiler -will generate \f(CW\*(C`seth/add3\*(C'\fR instructions to load their addresses), and -assume subroutines may not be reachable with the \f(CW\*(C`bl\*(C'\fR instruction -(the compiler will generate the much slower \f(CW\*(C`seth/add3/jl\*(C'\fR -instruction sequence). -.Ip "\fB\-msdata=none\fR" 4 -.IX Item "-msdata=none" -Disable use of the small data area. Variables will be put into -one of \fB.data\fR, \fBbss\fR, or \fB.rodata\fR (unless the -\&\f(CW\*(C`section\*(C'\fR attribute has been specified). -This is the default. -.Sp -The small data area consists of sections \fB.sdata\fR and \fB.sbss\fR. -Objects may be explicitly put in the small data area with the -\&\f(CW\*(C`section\*(C'\fR attribute using one of these sections. -.Ip "\fB\-msdata=sdata\fR" 4 -.IX Item "-msdata=sdata" -Put small global and static data in the small data area, but do not -generate special code to reference them. -.Ip "\fB\-msdata=use\fR" 4 -.IX Item "-msdata=use" -Put small global and static data in the small data area, and generate -special instructions to reference them. -.Ip "\fB\-G\fR \fInum\fR" 4 -.IX Item "-G num" -Put global and static objects less than or equal to \fInum\fR bytes -into the small data or bss sections instead of the normal data or bss -sections. The default value of \fInum\fR is 8. -The \fB\-msdata\fR option must be set to one of \fBsdata\fR or \fBuse\fR -for this option to have any effect. -.Sp -All modules should be compiled with the same \fB\-G\fR \fInum\fR value. -Compiling with different values of \fInum\fR may or may not work; if it -doesn't the linker will give an error message\-\-\-incorrect code will not be -generated. -.PP -.I "M88K Options" -.IX Subsection "M88K Options" -.PP -These \fB\-m\fR options are defined for Motorola 88k architectures: -.Ip "\fB\-m88000\fR" 4 -.IX Item "-m88000" -Generate code that works well on both the m88100 and the -m88110. -.Ip "\fB\-m88100\fR" 4 -.IX Item "-m88100" -Generate code that works best for the m88100, but that also -runs on the m88110. -.Ip "\fB\-m88110\fR" 4 -.IX Item "-m88110" -Generate code that works best for the m88110, and may not run -on the m88100. -.Ip "\fB\-mbig-pic\fR" 4 -.IX Item "-mbig-pic" -Obsolete option to be removed from the next revision. -Use \fB\-fPIC\fR. -.Ip "\fB\-midentify-revision\fR" 4 -.IX Item "-midentify-revision" -Include an \f(CW\*(C`ident\*(C'\fR directive in the assembler output recording the -source file name, compiler name and version, timestamp, and compilation -flags used. -.Ip "\fB\-mno-underscores\fR" 4 -.IX Item "-mno-underscores" -In assembler output, emit symbol names without adding an underscore -character at the beginning of each name. The default is to use an -underscore as prefix on each name. -.Ip "\fB\-mocs-debug-info\fR" 4 -.IX Item "-mocs-debug-info" -.PD 0 -.Ip "\fB\-mno-ocs-debug-info\fR" 4 -.IX Item "-mno-ocs-debug-info" -.PD -Include (or omit) additional debugging information (about registers used -in each stack frame) as specified in the 88open Object Compatibility -Standard, ``\s-1OCS\s0''. This extra information allows debugging of code that -has had the frame pointer eliminated. The default for \s-1DG/UX\s0, SVr4, and -Delta 88 SVr3.2 is to include this information; other 88k configurations -omit this information by default. -.Ip "\fB\-mocs-frame-position\fR" 4 -.IX Item "-mocs-frame-position" -When emitting \s-1COFF\s0 debugging information for automatic variables and -parameters stored on the stack, use the offset from the canonical frame -address, which is the stack pointer (register 31) on entry to the -function. The \s-1DG/UX\s0, SVr4, Delta88 SVr3.2, and \s-1BCS\s0 configurations use -\&\fB\-mocs-frame-position\fR; other 88k configurations have the default -\&\fB\-mno-ocs-frame-position\fR. -.Ip "\fB\-mno-ocs-frame-position\fR" 4 -.IX Item "-mno-ocs-frame-position" -When emitting \s-1COFF\s0 debugging information for automatic variables and -parameters stored on the stack, use the offset from the frame pointer -register (register 30). When this option is in effect, the frame -pointer is not eliminated when debugging information is selected by the -\&\-g switch. -.Ip "\fB\-moptimize-arg-area\fR" 4 -.IX Item "-moptimize-arg-area" -Save space by reorganizing the stack frame. This option generates code -that does not agree with the 88open specifications, but uses less -memory. -.Ip "\fB\-mno-optimize-arg-area\fR" 4 -.IX Item "-mno-optimize-arg-area" -Do not reorganize the stack frame to save space. This is the default. -The generated conforms to the specification, but uses more memory. -.Ip "\fB\-mshort-data-\fR\fInum\fR" 4 -.IX Item "-mshort-data-num" -Generate smaller data references by making them relative to \f(CW\*(C`r0\*(C'\fR, -which allows loading a value using a single instruction (rather than the -usual two). You control which data references are affected by -specifying \fInum\fR with this option. For example, if you specify -\&\fB\-mshort-data-512\fR, then the data references affected are those -involving displacements of less than 512 bytes. -\&\fB\-mshort-data-\fR\fInum\fR is not effective for \fInum\fR greater -than 64k. -.Ip "\fB\-mserialize-volatile\fR" 4 -.IX Item "-mserialize-volatile" -.PD 0 -.Ip "\fB\-mno-serialize-volatile\fR" 4 -.IX Item "-mno-serialize-volatile" -.PD -Do, or don't, generate code to guarantee sequential consistency -of volatile memory references. By default, consistency is -guaranteed. -.Sp -The order of memory references made by the \s-1MC88110\s0 processor does -not always match the order of the instructions requesting those -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-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-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. -.Sp -The extra code generated to guarantee consistency may affect the -performance of your application. If you know that you can safely -forgo this guarantee, you may use \fB\-mno-serialize-volatile\fR. -.Ip "\fB\-msvr4\fR" 4 -.IX Item "-msvr4" -.PD 0 -.Ip "\fB\-msvr3\fR" 4 -.IX Item "-msvr3" -.PD -Turn on (\fB\-msvr4\fR) or off (\fB\-msvr3\fR) compiler extensions -related to System V release 4 (SVr4). This controls the following: -.RS 4 -.Ip "1." 4 -Which variant of the assembler syntax to emit. -.Ip "2." 4 -\&\fB\-msvr4\fR makes the C preprocessor recognize \fB#pragma weak\fR -that is used on System V release 4. -.Ip "3." 4 -\&\fB\-msvr4\fR makes \s-1GCC\s0 issue additional declaration directives used in -SVr4. -.RE -.RS 4 -.Sp -\&\fB\-msvr4\fR is the default for the m88k-motorola-sysv4 and -m88k-dg-dgux m88k configurations. \fB\-msvr3\fR is the default for all -other m88k configurations. -.RE -.Ip "\fB\-mversion-03.00\fR" 4 -.IX Item "-mversion-03.00" -This option is obsolete, and is ignored. -.Ip "\fB\-mno-check-zero-division\fR" 4 -.IX Item "-mno-check-zero-division" -.PD 0 -.Ip "\fB\-mcheck-zero-division\fR" 4 -.IX Item "-mcheck-zero-division" -.PD -Do, or don't, generate code to guarantee that integer division by -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-1GCC\s0 -generates code that explicitly checks for zero-valued divisors -and traps with exception number 503 when one is detected. Use of -\&\fB\-mno-check-zero-division\fR suppresses such checking for code -generated to run on an \s-1MC88100\s0 processor. -.Sp -\&\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, no -explicit checks for zero-valued divisors are generated, and both -\&\fB\-mcheck-zero-division\fR and \fB\-mno-check-zero-division\fR are -ignored. -.Ip "\fB\-muse-div-instruction\fR" 4 -.IX Item "-muse-div-instruction" -Use the div instruction for signed integer division on the -\&\s-1MC88100\s0 processor. By default, the div instruction is not used. -.Sp -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-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 -cost in both time and space. To the extent that your code's -important signed integer division operations are performed on two -nonnegative operands, it may be desirable to use the div -instruction directly. -.Sp -On the \s-1MC88110\s0 processor the div instruction (also known as the -divs instruction) processes negative operands without trapping to -the operating system. When \fB\-m88110\fR is specified, -\&\fB\-muse-div-instruction\fR is ignored, and the div instruction is used -for signed integer division. -.Sp -Note that the result of dividing \f(CW\*(C`INT_MIN\*(C'\fR by \-1 is undefined. In -particular, the behavior of such a division with and without -\&\fB\-muse-div-instruction\fR may differ. -.Ip "\fB\-mtrap-large-shift\fR" 4 -.IX Item "-mtrap-large-shift" -.PD 0 -.Ip "\fB\-mhandle-large-shift\fR" 4 -.IX Item "-mhandle-large-shift" -.PD -Include code to detect bit-shifts of more than 31 bits; respectively, -trap such shifts or emit code to handle them properly. By default \s-1GCC\s0 -makes no special provision for large bit shifts. -.Ip "\fB\-mwarn-passed-structs\fR" 4 -.IX Item "-mwarn-passed-structs" -Warn when a function passes a struct as an argument or result. -Structure-passing conventions have changed during the evolution of the C -language, and are often the source of portability problems. By default, -\&\s-1GCC\s0 issues no such warning. -.PP -.I "\s-1IBM\s0 \s-1RS/6000\s0 and PowerPC Options" -.IX Subsection "IBM RS/6000 and PowerPC Options" -.PP -These \fB\-m\fR options are defined for the \s-1IBM\s0 \s-1RS/6000\s0 and PowerPC: -.Ip "\fB\-mpower\fR" 4 -.IX Item "-mpower" -.PD 0 -.Ip "\fB\-mno-power\fR" 4 -.IX Item "-mno-power" -.Ip "\fB\-mpower2\fR" 4 -.IX Item "-mpower2" -.Ip "\fB\-mno-power2\fR" 4 -.IX Item "-mno-power2" -.Ip "\fB\-mpowerpc\fR" 4 -.IX Item "-mpowerpc" -.Ip "\fB\-mno-powerpc\fR" 4 -.IX Item "-mno-powerpc" -.Ip "\fB\-mpowerpc-gpopt\fR" 4 -.IX Item "-mpowerpc-gpopt" -.Ip "\fB\-mno-powerpc-gpopt\fR" 4 -.IX Item "-mno-powerpc-gpopt" -.Ip "\fB\-mpowerpc-gfxopt\fR" 4 -.IX Item "-mpowerpc-gfxopt" -.Ip "\fB\-mno-powerpc-gfxopt\fR" 4 -.IX Item "-mno-powerpc-gfxopt" -.Ip "\fB\-mpowerpc64\fR" 4 -.IX Item "-mpowerpc64" -.Ip "\fB\-mno-powerpc64\fR" 4 -.IX Item "-mno-powerpc64" -.PD -\&\s-1GCC\s0 supports two related instruction set architectures for the -\&\s-1RS/6000\s0 and PowerPC. The \fI\s-1POWER\s0\fR instruction set are those -instructions supported by the \fBrios\fR chip set used in the original -\&\s-1RS/6000\s0 systems and the \fIPowerPC\fR instruction set is the -architecture of the Motorola MPC5xx, MPC6xx, MPC8xx microprocessors, and -the \s-1IBM\s0 4xx microprocessors. -.Sp -Neither architecture is a subset of the other. However there is a -large common subset of instructions supported by both. An \s-1MQ\s0 -register is included in processors supporting the \s-1POWER\s0 architecture. -.Sp -You use these options to specify which instructions are available on the -processor you are using. The default value of these options is -determined when configuring \s-1GCC\s0. Specifying the -\&\fB\-mcpu=\fR\fIcpu_type\fR overrides the specification of these -options. We recommend you use the \fB\-mcpu=\fR\fIcpu_type\fR option -rather than the options listed above. -.Sp -The \fB\-mpower\fR option allows \s-1GCC\s0 to generate instructions that -are found only in the \s-1POWER\s0 architecture and to use the \s-1MQ\s0 register. -Specifying \fB\-mpower2\fR implies \fB\-power\fR and also allows \s-1GCC\s0 -to generate instructions that are present in the \s-1POWER2\s0 architecture but -not the original \s-1POWER\s0 architecture. -.Sp -The \fB\-mpowerpc\fR option allows \s-1GCC\s0 to generate instructions that -are found only in the 32\-bit subset of the PowerPC architecture. -Specifying \fB\-mpowerpc-gpopt\fR implies \fB\-mpowerpc\fR and also allows -\&\s-1GCC\s0 to use the optional PowerPC architecture instructions in the -General Purpose group, including floating-point square root. Specifying -\&\fB\-mpowerpc-gfxopt\fR implies \fB\-mpowerpc\fR and also allows \s-1GCC\s0 to -use the optional PowerPC architecture instructions in the Graphics -group, including floating-point select. -.Sp -The \fB\-mpowerpc64\fR option allows \s-1GCC\s0 to generate the additional -64\-bit instructions that are found in the full PowerPC64 architecture -and to treat GPRs as 64\-bit, doubleword quantities. \s-1GCC\s0 defaults to -\&\fB\-mno-powerpc64\fR. -.Sp -If you specify both \fB\-mno-power\fR and \fB\-mno-powerpc\fR, \s-1GCC\s0 -will use only the instructions in the common subset of both -architectures plus some special \s-1AIX\s0 common-mode calls, and will not use -the \s-1MQ\s0 register. Specifying both \fB\-mpower\fR and \fB\-mpowerpc\fR -permits \s-1GCC\s0 to use any instruction from either architecture and to -allow use of the \s-1MQ\s0 register; specify this for the Motorola \s-1MPC601\s0. -.Ip "\fB\-mnew-mnemonics\fR" 4 -.IX Item "-mnew-mnemonics" -.PD 0 -.Ip "\fB\-mold-mnemonics\fR" 4 -.IX Item "-mold-mnemonics" -.PD -Select which mnemonics to use in the generated assembler code. With -\&\fB\-mnew-mnemonics\fR, \s-1GCC\s0 uses the assembler mnemonics defined for -the PowerPC architecture. With \fB\-mold-mnemonics\fR it uses the -assembler mnemonics defined for the \s-1POWER\s0 architecture. Instructions -defined in only one architecture have only one mnemonic; \s-1GCC\s0 uses that -mnemonic irrespective of which of these options is specified. -.Sp -\&\s-1GCC\s0 defaults to the mnemonics appropriate for the architecture in -use. Specifying \fB\-mcpu=\fR\fIcpu_type\fR sometimes overrides the -value of these option. Unless you are building a cross-compiler, you -should normally not specify either \fB\-mnew-mnemonics\fR or -\&\fB\-mold-mnemonics\fR, but should instead accept the default. -.Ip "\fB\-mcpu=\fR\fIcpu_type\fR" 4 -.IX Item "-mcpu=cpu_type" -Set architecture type, register usage, choice of mnemonics, and -instruction scheduling parameters for machine type \fIcpu_type\fR. -Supported values for \fIcpu_type\fR are \fBrios\fR, \fBrios1\fR, -\&\fBrsc\fR, \fBrios2\fR, \fBrs64a\fR, \fB601\fR, \fB602\fR, -\&\fB603\fR, \fB603e\fR, \fB604\fR, \fB604e\fR, \fB620\fR, -\&\fB630\fR, \fB740\fR, \fB7400\fR, \fB7450\fR, \fB750\fR, -\&\fBpower\fR, \fBpower2\fR, \fBpowerpc\fR, \fB403\fR, \fB505\fR, -\&\fB801\fR, \fB821\fR, \fB823\fR, and \fB860\fR and \fBcommon\fR. -.Sp -\&\fB\-mcpu=common\fR selects a completely generic processor. Code -generated under this option will run on any \s-1POWER\s0 or PowerPC processor. -\&\s-1GCC\s0 will use only the instructions in the common subset of both -architectures, and will not use the \s-1MQ\s0 register. \s-1GCC\s0 assumes a generic -processor model for scheduling purposes. -.Sp -\&\fB\-mcpu=power\fR, \fB\-mcpu=power2\fR, \fB\-mcpu=powerpc\fR, and -\&\fB\-mcpu=powerpc64\fR specify generic \s-1POWER\s0, \s-1POWER2\s0, pure 32\-bit -PowerPC (i.e., not \s-1MPC601\s0), and 64\-bit PowerPC architecture machine -types, with an appropriate, generic processor model assumed for -scheduling purposes. -.Sp -The other options specify a specific processor. Code generated under -those options will run best on that processor, and may not run at all on -others. -.Sp -The \fB\-mcpu\fR options automatically enable or disable other -\&\fB\-m\fR options as follows: -.RS 4 -.Ip "\fBcommon\fR" 4 -.IX Item "common" -\&\fB\-mno-power\fR, \fB\-mno-powerc\fR -.Ip "\fBpower\fR" 4 -.IX Item "power" -.PD 0 -.Ip "\fBpower2\fR" 4 -.IX Item "power2" -.Ip "\fBrios1\fR" 4 -.IX Item "rios1" -.Ip "\fBrios2\fR" 4 -.IX Item "rios2" -.Ip "\fBrsc\fR" 4 -.IX Item "rsc" -.PD -\&\fB\-mpower\fR, \fB\-mno-powerpc\fR, \fB\-mno-new-mnemonics\fR -.Ip "\fBpowerpc\fR" 4 -.IX Item "powerpc" -.PD 0 -.Ip "\fBrs64a\fR" 4 -.IX Item "rs64a" -.Ip "\fB602\fR" 4 -.IX Item "602" -.Ip "\fB603\fR" 4 -.IX Item "603" -.Ip "\fB603e\fR" 4 -.IX Item "603e" -.Ip "\fB604\fR" 4 -.IX Item "604" -.Ip "\fB620\fR" 4 -.IX Item "620" -.Ip "\fB630\fR" 4 -.IX Item "630" -.Ip "\fB740\fR" 4 -.IX Item "740" -.Ip "\fB7400\fR" 4 -.IX Item "7400" -.Ip "\fB7450\fR" 4 -.IX Item "7450" -.Ip "\fB750\fR" 4 -.IX Item "750" -.Ip "\fB505\fR" 4 -.IX Item "505" -.PD -\&\fB\-mno-power\fR, \fB\-mpowerpc\fR, \fB\-mnew-mnemonics\fR -.Ip "\fB601\fR" 4 -.IX Item "601" -\&\fB\-mpower\fR, \fB\-mpowerpc\fR, \fB\-mnew-mnemonics\fR -.Ip "\fB403\fR" 4 -.IX Item "403" -.PD 0 -.Ip "\fB821\fR" 4 -.IX Item "821" -.Ip "\fB860\fR" 4 -.IX Item "860" -.PD -\&\fB\-mno-power\fR, \fB\-mpowerpc\fR, \fB\-mnew-mnemonics\fR, \fB\-msoft-float\fR -.RE -.RS 4 -.RE -.Ip "\fB\-mtune=\fR\fIcpu_type\fR" 4 -.IX Item "-mtune=cpu_type" -Set the instruction scheduling parameters for machine type -\&\fIcpu_type\fR, but do not set the architecture type, register usage, or -choice of mnemonics, as \fB\-mcpu=\fR\fIcpu_type\fR would. The same -values for \fIcpu_type\fR are used for \fB\-mtune\fR as for -\&\fB\-mcpu\fR. If both are specified, the code generated will use the -architecture, registers, and mnemonics set by \fB\-mcpu\fR, but the -scheduling parameters set by \fB\-mtune\fR. -.Ip "\fB\-maltivec\fR" 4 -.IX Item "-maltivec" -.PD 0 -.Ip "\fB\-mno-altivec\fR" 4 -.IX Item "-mno-altivec" -.PD -These switches enable or disable the use of built-in functions that -allow access to the AltiVec instruction set. You may also need to set -\&\fB\-mabi=altivec\fR to adjust the current \s-1ABI\s0 with AltiVec \s-1ABI\s0 -enhancements. -.Ip "\fB\-mfull-toc\fR" 4 -.IX Item "-mfull-toc" -.PD 0 -.Ip "\fB\-mno-fp-in-toc\fR" 4 -.IX Item "-mno-fp-in-toc" -.Ip "\fB\-mno-sum-in-toc\fR" 4 -.IX Item "-mno-sum-in-toc" -.Ip "\fB\-mminimal-toc\fR" 4 -.IX Item "-mminimal-toc" -.PD -Modify generation of the \s-1TOC\s0 (Table Of Contents), which is created for -every executable file. The \fB\-mfull-toc\fR option is selected by -default. In that case, \s-1GCC\s0 will allocate at least one \s-1TOC\s0 entry for -each unique non-automatic variable reference in your program. \s-1GCC\s0 -will also place floating-point constants in the \s-1TOC\s0. However, only -16,384 entries are available in the \s-1TOC\s0. -.Sp -If you receive a linker error message that saying you have overflowed -the available \s-1TOC\s0 space, you can reduce the amount of \s-1TOC\s0 space used -with the \fB\-mno-fp-in-toc\fR and \fB\-mno-sum-in-toc\fR options. -\&\fB\-mno-fp-in-toc\fR prevents \s-1GCC\s0 from putting floating-point -constants in the \s-1TOC\s0 and \fB\-mno-sum-in-toc\fR forces \s-1GCC\s0 to -generate code to calculate the sum of an address and a constant at -run-time instead of putting that sum into the \s-1TOC\s0. You may specify one -or both of these options. Each causes \s-1GCC\s0 to produce very slightly -slower and larger code at the expense of conserving \s-1TOC\s0 space. -.Sp -If you still run out of space in the \s-1TOC\s0 even when you specify both of -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. -.Ip "\fB\-maix64\fR" 4 -.IX Item "-maix64" -.PD 0 -.Ip "\fB\-maix32\fR" 4 -.IX Item "-maix32" -.PD -Enable 64\-bit \s-1AIX\s0 \s-1ABI\s0 and calling convention: 64\-bit pointers, 64\-bit -\&\f(CW\*(C`long\*(C'\fR type, and the infrastructure needed to support them. -Specifying \fB\-maix64\fR implies \fB\-mpowerpc64\fR and -\&\fB\-mpowerpc\fR, while \fB\-maix32\fR disables the 64\-bit \s-1ABI\s0 and -implies \fB\-mno-powerpc64\fR. \s-1GCC\s0 defaults to \fB\-maix32\fR. -.Ip "\fB\-mxl-call\fR" 4 -.IX Item "-mxl-call" -.PD 0 -.Ip "\fB\-mno-xl-call\fR" 4 -.IX Item "-mno-xl-call" -.PD -On \s-1AIX\s0, pass floating-point arguments to prototyped functions beyond the -register save area (\s-1RSA\s0) on the stack in addition to argument FPRs. The -\&\s-1AIX\s0 calling convention was extended but not initially documented to -handle an obscure K&R C case of calling a function that takes the -address of its arguments with fewer arguments than declared. \s-1AIX\s0 \s-1XL\s0 -compilers access floating point arguments which do not fit in the -\&\s-1RSA\s0 from the stack when a subroutine is compiled without -optimization. Because always storing floating-point arguments on the -stack is inefficient and rarely needed, this option is not enabled by -default and only is necessary when calling subroutines compiled by \s-1AIX\s0 -\&\s-1XL\s0 compilers without optimization. -.Ip "\fB\-mpe\fR" 4 -.IX Item "-mpe" -Support \fI\s-1IBM\s0 \s-1RS/6000\s0 \s-1SP\s0\fR \fIParallel Environment\fR (\s-1PE\s0). Link an -application written to use message passing with special startup code to -enable the application to run. The system must have \s-1PE\s0 installed in the -standard location (\fI/usr/lpp/ppe.poe/\fR), or the \fIspecs\fR file -must be overridden with the \fB\-specs=\fR option to specify the -appropriate directory location. The Parallel Environment does not -support threads, so the \fB\-mpe\fR option and the \fB\-pthread\fR -option are incompatible. -.Ip "\fB\-msoft-float\fR" 4 -.IX Item "-msoft-float" -.PD 0 -.Ip "\fB\-mhard-float\fR" 4 -.IX Item "-mhard-float" -.PD -Generate code that does not use (uses) the floating-point register set. -Software floating point emulation is provided if you use the -\&\fB\-msoft-float\fR option, and pass the option to \s-1GCC\s0 when linking. -.Ip "\fB\-mmultiple\fR" 4 -.IX Item "-mmultiple" -.PD 0 -.Ip "\fB\-mno-multiple\fR" 4 -.IX Item "-mno-multiple" -.PD -Generate code that uses (does not use) the load multiple word -instructions and the store multiple word instructions. These -instructions are generated by default on \s-1POWER\s0 systems, and not -generated on PowerPC systems. Do not use \fB\-mmultiple\fR on little -endian PowerPC systems, since those instructions do not work when the -processor is in little endian mode. The exceptions are \s-1PPC740\s0 and -\&\s-1PPC750\s0 which permit the instructions usage in little endian mode. -.Ip "\fB\-mstring\fR" 4 -.IX Item "-mstring" -.PD 0 -.Ip "\fB\-mno-string\fR" 4 -.IX Item "-mno-string" -.PD -Generate code that uses (does not use) the load string instructions -and the store string word instructions to save multiple registers and -do small block moves. These instructions are generated by default on -\&\s-1POWER\s0 systems, and not generated on PowerPC systems. Do not use -\&\fB\-mstring\fR on little endian PowerPC systems, since those -instructions do not work when the processor is in little endian mode. -The exceptions are \s-1PPC740\s0 and \s-1PPC750\s0 which permit the instructions -usage in little endian mode. -.Ip "\fB\-mupdate\fR" 4 -.IX Item "-mupdate" -.PD 0 -.Ip "\fB\-mno-update\fR" 4 -.IX Item "-mno-update" -.PD -Generate code that uses (does not use) the load or store instructions -that update the base register to the address of the calculated memory -location. These instructions are generated by default. If you use -\&\fB\-mno-update\fR, there is a small window between the time that the -stack pointer is updated and the address of the previous frame is -stored, which means code that walks the stack frame across interrupts or -signals may get corrupted data. -.Ip "\fB\-mfused-madd\fR" 4 -.IX Item "-mfused-madd" -.PD 0 -.Ip "\fB\-mno-fused-madd\fR" 4 -.IX Item "-mno-fused-madd" -.PD -Generate code that uses (does not use) the floating point multiply and -accumulate instructions. These instructions are generated by default if -hardware floating is used. -.Ip "\fB\-mno-bit-align\fR" 4 -.IX Item "-mno-bit-align" -.PD 0 -.Ip "\fB\-mbit-align\fR" 4 -.IX Item "-mbit-align" -.PD -On System V.4 and embedded PowerPC systems do not (do) force structures -and unions that contain bit-fields to be aligned to the base type of the -bit-field. -.Sp -For example, by default a structure containing nothing but 8 -\&\f(CW\*(C`unsigned\*(C'\fR bit-fields of length 1 would be aligned to a 4 byte -boundary and have a size of 4 bytes. By using \fB\-mno-bit-align\fR, -the structure would be aligned to a 1 byte boundary and be one byte in -size. -.Ip "\fB\-mno-strict-align\fR" 4 -.IX Item "-mno-strict-align" -.PD 0 -.Ip "\fB\-mstrict-align\fR" 4 -.IX Item "-mstrict-align" -.PD -On System V.4 and embedded PowerPC systems do not (do) assume that -unaligned memory references will be handled by the system. -.Ip "\fB\-mrelocatable\fR" 4 -.IX Item "-mrelocatable" -.PD 0 -.Ip "\fB\-mno-relocatable\fR" 4 -.IX Item "-mno-relocatable" -.PD -On embedded PowerPC systems generate code that allows (does not allow) -the program to be relocated to a different address at runtime. If you -use \fB\-mrelocatable\fR on any module, all objects linked together must -be compiled with \fB\-mrelocatable\fR or \fB\-mrelocatable-lib\fR. -.Ip "\fB\-mrelocatable-lib\fR" 4 -.IX Item "-mrelocatable-lib" -.PD 0 -.Ip "\fB\-mno-relocatable-lib\fR" 4 -.IX Item "-mno-relocatable-lib" -.PD -On embedded PowerPC systems generate code that allows (does not allow) -the program to be relocated to a different address at runtime. Modules -compiled with \fB\-mrelocatable-lib\fR can be linked with either modules -compiled without \fB\-mrelocatable\fR and \fB\-mrelocatable-lib\fR or -with modules compiled with the \fB\-mrelocatable\fR options. -.Ip "\fB\-mno-toc\fR" 4 -.IX Item "-mno-toc" -.PD 0 -.Ip "\fB\-mtoc\fR" 4 -.IX Item "-mtoc" -.PD -On System V.4 and embedded PowerPC systems do not (do) assume that -register 2 contains a pointer to a global area pointing to the addresses -used in the program. -.Ip "\fB\-mlittle\fR" 4 -.IX Item "-mlittle" -.PD 0 -.Ip "\fB\-mlittle-endian\fR" 4 -.IX Item "-mlittle-endian" -.PD -On System V.4 and embedded PowerPC systems compile code for the -processor in little endian mode. The \fB\-mlittle-endian\fR option is -the same as \fB\-mlittle\fR. -.Ip "\fB\-mbig\fR" 4 -.IX Item "-mbig" -.PD 0 -.Ip "\fB\-mbig-endian\fR" 4 -.IX Item "-mbig-endian" -.PD -On System V.4 and embedded PowerPC systems compile code for the -processor in big endian mode. The \fB\-mbig-endian\fR option is -the same as \fB\-mbig\fR. -.Ip "\fB\-mcall-sysv\fR" 4 -.IX Item "-mcall-sysv" -On System V.4 and embedded PowerPC systems compile code using calling -conventions that adheres to the March 1995 draft of the System V -Application Binary Interface, PowerPC processor supplement. This is the -default unless you configured \s-1GCC\s0 using \fBpowerpc-*\-eabiaix\fR. -.Ip "\fB\-mcall-sysv-eabi\fR" 4 -.IX Item "-mcall-sysv-eabi" -Specify both \fB\-mcall-sysv\fR and \fB\-meabi\fR options. -.Ip "\fB\-mcall-sysv-noeabi\fR" 4 -.IX Item "-mcall-sysv-noeabi" -Specify both \fB\-mcall-sysv\fR and \fB\-mno-eabi\fR options. -.Ip "\fB\-mcall-aix\fR" 4 -.IX Item "-mcall-aix" -On System V.4 and embedded PowerPC systems compile code using calling -conventions that are similar to those used on \s-1AIX\s0. This is the -default if you configured \s-1GCC\s0 using \fBpowerpc-*\-eabiaix\fR. -.Ip "\fB\-mcall-solaris\fR" 4 -.IX Item "-mcall-solaris" -On System V.4 and embedded PowerPC systems compile code for the Solaris -operating system. -.Ip "\fB\-mcall-linux\fR" 4 -.IX Item "-mcall-linux" -On System V.4 and embedded PowerPC systems compile code for the -Linux-based \s-1GNU\s0 system. -.Ip "\fB\-mcall-gnu\fR" 4 -.IX Item "-mcall-gnu" -On System V.4 and embedded PowerPC systems compile code for the -Hurd-based \s-1GNU\s0 system. -.Ip "\fB\-mcall-netbsd\fR" 4 -.IX Item "-mcall-netbsd" -On System V.4 and embedded PowerPC systems compile code for the -NetBSD operating system. -.Ip "\fB\-maix-struct-return\fR" 4 -.IX Item "-maix-struct-return" -Return all structures in memory (as specified by the \s-1AIX\s0 \s-1ABI\s0). -.Ip "\fB\-msvr4\-struct-return\fR" 4 -.IX Item "-msvr4-struct-return" -Return structures smaller than 8 bytes in registers (as specified by the -\&\s-1SVR4\s0 \s-1ABI\s0). -.Ip "\fB\-mabi=altivec\fR" 4 -.IX Item "-mabi=altivec" -Extend the current \s-1ABI\s0 with AltiVec \s-1ABI\s0 extensions. This does not -change the default \s-1ABI\s0, instead it adds the AltiVec \s-1ABI\s0 extensions to -the current \s-1ABI\s0. -.Ip "\fB\-mabi=no-altivec\fR" 4 -.IX Item "-mabi=no-altivec" -Disable AltiVec \s-1ABI\s0 extensions for the current \s-1ABI\s0. -.Ip "\fB\-mprototype\fR" 4 -.IX Item "-mprototype" -.PD 0 -.Ip "\fB\-mno-prototype\fR" 4 -.IX Item "-mno-prototype" -.PD -On System V.4 and embedded PowerPC systems assume that all calls to -variable argument functions are properly prototyped. Otherwise, the -compiler must insert an instruction before every non prototyped call to -set or clear bit 6 of the condition code register (\fI\s-1CR\s0\fR) to -indicate whether floating point values were passed in the floating point -registers in case the function takes a variable arguments. With -\&\fB\-mprototype\fR, only calls to prototyped variable argument functions -will set or clear the bit. -.Ip "\fB\-msim\fR" 4 -.IX Item "-msim" -On embedded PowerPC systems, assume that the startup module is called -\&\fIsim-crt0.o\fR and that the standard C libraries are \fIlibsim.a\fR and -\&\fIlibc.a\fR. This is the default for \fBpowerpc-*\-eabisim\fR. -configurations. -.Ip "\fB\-mmvme\fR" 4 -.IX Item "-mmvme" -On embedded PowerPC systems, assume that the startup module is called -\&\fIcrt0.o\fR and the standard C libraries are \fIlibmvme.a\fR and -\&\fIlibc.a\fR. -.Ip "\fB\-mads\fR" 4 -.IX Item "-mads" -On embedded PowerPC systems, assume that the startup module is called -\&\fIcrt0.o\fR and the standard C libraries are \fIlibads.a\fR and -\&\fIlibc.a\fR. -.Ip "\fB\-myellowknife\fR" 4 -.IX Item "-myellowknife" -On embedded PowerPC systems, assume that the startup module is called -\&\fIcrt0.o\fR and the standard C libraries are \fIlibyk.a\fR and -\&\fIlibc.a\fR. -.Ip "\fB\-mvxworks\fR" 4 -.IX Item "-mvxworks" -On System V.4 and embedded PowerPC systems, specify that you are -compiling for a VxWorks system. -.Ip "\fB\-memb\fR" 4 -.IX Item "-memb" -On embedded PowerPC systems, set the \fI\s-1PPC_EMB\s0\fR bit in the \s-1ELF\s0 flags -header to indicate that \fBeabi\fR extended relocations are used. -.Ip "\fB\-meabi\fR" 4 -.IX Item "-meabi" -.PD 0 -.Ip "\fB\-mno-eabi\fR" 4 -.IX Item "-mno-eabi" -.PD -On System V.4 and embedded PowerPC systems do (do not) adhere to the -Embedded Applications Binary Interface (eabi) which is a set of -modifications to the System V.4 specifications. Selecting \fB\-meabi\fR -means that the stack is aligned to an 8 byte boundary, a function -\&\f(CW\*(C`_\|_eabi\*(C'\fR is called to from \f(CW\*(C`main\*(C'\fR to set up the eabi -environment, and the \fB\-msdata\fR option can use both \f(CW\*(C`r2\*(C'\fR and -\&\f(CW\*(C`r13\*(C'\fR to point to two separate small data areas. Selecting -\&\fB\-mno-eabi\fR means that the stack is aligned to a 16 byte boundary, -do not call an initialization function from \f(CW\*(C`main\*(C'\fR, and the -\&\fB\-msdata\fR option will only use \f(CW\*(C`r13\*(C'\fR to point to a single -small data area. The \fB\-meabi\fR option is on by default if you -configured \s-1GCC\s0 using one of the \fBpowerpc*\-*\-eabi*\fR options. -.Ip "\fB\-msdata=eabi\fR" 4 -.IX Item "-msdata=eabi" -On System V.4 and embedded PowerPC systems, put small initialized -\&\f(CW\*(C`const\*(C'\fR global and static data in the \fB.sdata2\fR section, which -is pointed to by register \f(CW\*(C`r2\*(C'\fR. Put small initialized -non-\f(CW\*(C`const\*(C'\fR global and static data in the \fB.sdata\fR section, -which is pointed to by register \f(CW\*(C`r13\*(C'\fR. Put small uninitialized -global and static data in the \fB.sbss\fR section, which is adjacent to -the \fB.sdata\fR section. The \fB\-msdata=eabi\fR option is -incompatible with the \fB\-mrelocatable\fR option. The -\&\fB\-msdata=eabi\fR option also sets the \fB\-memb\fR option. -.Ip "\fB\-msdata=sysv\fR" 4 -.IX Item "-msdata=sysv" -On System V.4 and embedded PowerPC systems, put small global and static -data in the \fB.sdata\fR section, which is pointed to by register -\&\f(CW\*(C`r13\*(C'\fR. Put small uninitialized global and static data in the -\&\fB.sbss\fR section, which is adjacent to the \fB.sdata\fR section. -The \fB\-msdata=sysv\fR option is incompatible with the -\&\fB\-mrelocatable\fR option. -.Ip "\fB\-msdata=default\fR" 4 -.IX Item "-msdata=default" -.PD 0 -.Ip "\fB\-msdata\fR" 4 -.IX Item "-msdata" -.PD -On System V.4 and embedded PowerPC systems, if \fB\-meabi\fR is used, -compile code the same as \fB\-msdata=eabi\fR, otherwise compile code the -same as \fB\-msdata=sysv\fR. -.Ip "\fB\-msdata-data\fR" 4 -.IX Item "-msdata-data" -On System V.4 and embedded PowerPC systems, put small global and static -data in the \fB.sdata\fR section. Put small uninitialized global and -static data in the \fB.sbss\fR section. Do not use register \f(CW\*(C`r13\*(C'\fR -to address small data however. This is the default behavior unless -other \fB\-msdata\fR options are used. -.Ip "\fB\-msdata=none\fR" 4 -.IX Item "-msdata=none" -.PD 0 -.Ip "\fB\-mno-sdata\fR" 4 -.IX Item "-mno-sdata" -.PD -On embedded PowerPC systems, put all initialized global and static data -in the \fB.data\fR section, and all uninitialized data in the -\&\fB.bss\fR section. -.Ip "\fB\-G\fR \fInum\fR" 4 -.IX Item "-G num" -On embedded PowerPC systems, put global and static items less than or -equal to \fInum\fR bytes into the small data or bss sections instead of -the normal data or bss section. By default, \fInum\fR is 8. The -\&\fB\-G\fR \fInum\fR switch is also passed to the linker. -All modules should be compiled with the same \fB\-G\fR \fInum\fR value. -.Ip "\fB\-mregnames\fR" 4 -.IX Item "-mregnames" -.PD 0 -.Ip "\fB\-mno-regnames\fR" 4 -.IX Item "-mno-regnames" -.PD -On System V.4 and embedded PowerPC systems do (do not) emit register -names in the assembly language output using symbolic forms. -.Ip "\fB\-pthread\fR" 4 -.IX Item "-pthread" -Adds support for multithreading with the \fIpthreads\fR library. -This option sets flags for both the preprocessor and linker. -.PP -.I "\s-1IBM\s0 \s-1RT\s0 Options" -.IX Subsection "IBM RT Options" -.PP -These \fB\-m\fR options are defined for the \s-1IBM\s0 \s-1RT\s0 \s-1PC:\s0 -.Ip "\fB\-min-line-mul\fR" 4 -.IX Item "-min-line-mul" -Use an in-line code sequence for integer multiplies. This is the -default. -.Ip "\fB\-mcall-lib-mul\fR" 4 -.IX Item "-mcall-lib-mul" -Call \f(CW\*(C`lmul$$\*(C'\fR for integer multiples. -.Ip "\fB\-mfull-fp-blocks\fR" 4 -.IX Item "-mfull-fp-blocks" -Generate full-size floating point data blocks, including the minimum -amount of scratch space recommended by \s-1IBM\s0. This is the default. -.Ip "\fB\-mminimum-fp-blocks\fR" 4 -.IX Item "-mminimum-fp-blocks" -Do not include extra scratch space in floating point data blocks. This -results in smaller code, but slower execution, since scratch space must -be allocated dynamically. -.Ip "\fB\-mfp-arg-in-fpregs\fR" 4 -.IX Item "-mfp-arg-in-fpregs" -Use a calling sequence incompatible with the \s-1IBM\s0 calling convention in -which floating point arguments are passed in floating point registers. -Note that \f(CW\*(C`varargs.h\*(C'\fR and \f(CW\*(C`stdarg.h\*(C'\fR will not work with -floating point operands if this option is specified. -.Ip "\fB\-mfp-arg-in-gregs\fR" 4 -.IX Item "-mfp-arg-in-gregs" -Use the normal calling convention for floating point arguments. This is -the default. -.Ip "\fB\-mhc-struct-return\fR" 4 -.IX Item "-mhc-struct-return" -Return structures of more than one word in memory, rather than in a -register. This provides compatibility with the MetaWare HighC (hc) -compiler. Use the option \fB\-fpcc-struct-return\fR for compatibility -with the Portable C Compiler (pcc). -.Ip "\fB\-mnohc-struct-return\fR" 4 -.IX Item "-mnohc-struct-return" -Return some structures of more than one word in registers, when -convenient. This is the default. For compatibility with the -IBM-supplied compilers, use the option \fB\-fpcc-struct-return\fR or the -option \fB\-mhc-struct-return\fR. -.PP -.I "\s-1MIPS\s0 Options" -.IX Subsection "MIPS Options" -.PP -These \fB\-m\fR options are defined for the \s-1MIPS\s0 family of computers: -.Ip "\fB\-march=\fR\fIcpu-type\fR" 4 -.IX Item "-march=cpu-type" -Assume the defaults for the machine type \fIcpu-type\fR when generating -instructions. The choices for \fIcpu-type\fR are \fBr2000\fR, \fBr3000\fR, -\&\fBr3900\fR, \fBr4000\fR, \fBr4100\fR, \fBr4300\fR, \fBr4400\fR, -\&\fBr4600\fR, \fBr4650\fR, \fBr5000\fR, \fBr6000\fR, \fBr8000\fR, -and \fBorion\fR. Additionally, the \fBr2000\fR, \fBr3000\fR, -\&\fBr4000\fR, \fBr5000\fR, and \fBr6000\fR can be abbreviated as -\&\fBr2k\fR (or \fBr2K\fR), \fBr3k\fR, etc. -.Ip "\fB\-mtune=\fR\fIcpu-type\fR" 4 -.IX Item "-mtune=cpu-type" -Assume the defaults for the machine type \fIcpu-type\fR when scheduling -instructions. The choices for \fIcpu-type\fR are \fBr2000\fR, \fBr3000\fR, -\&\fBr3900\fR, \fBr4000\fR, \fBr4100\fR, \fBr4300\fR, \fBr4400\fR, -\&\fBr4600\fR, \fBr4650\fR, \fBr5000\fR, \fBr6000\fR, \fBr8000\fR, -and \fBorion\fR. Additionally, the \fBr2000\fR, \fBr3000\fR, -\&\fBr4000\fR, \fBr5000\fR, and \fBr6000\fR can be abbreviated as -\&\fBr2k\fR (or \fBr2K\fR), \fBr3k\fR, etc. While picking a specific -\&\fIcpu-type\fR will schedule things appropriately for that particular -chip, the compiler will not generate any code that does not meet level 1 -of the \s-1MIPS\s0 \s-1ISA\s0 (instruction set architecture) without a \fB\-mipsX\fR -or \fB\-mabi\fR switch being used. -.Ip "\fB\-mcpu=\fR\fIcpu-type\fR" 4 -.IX Item "-mcpu=cpu-type" -This is identical to specifying both \fB\-march\fR and \fB\-mtune\fR. -.Ip "\fB\-mips1\fR" 4 -.IX Item "-mips1" -Issue instructions from level 1 of the \s-1MIPS\s0 \s-1ISA\s0. This is the default. -\&\fBr3000\fR is the default \fIcpu-type\fR at this \s-1ISA\s0 level. -.Ip "\fB\-mips2\fR" 4 -.IX Item "-mips2" -Issue instructions from level 2 of the \s-1MIPS\s0 \s-1ISA\s0 (branch likely, square -root instructions). \fBr6000\fR is the default \fIcpu-type\fR at this -\&\s-1ISA\s0 level. -.Ip "\fB\-mips3\fR" 4 -.IX Item "-mips3" -Issue instructions from level 3 of the \s-1MIPS\s0 \s-1ISA\s0 (64\-bit instructions). -\&\fBr4000\fR is the default \fIcpu-type\fR at this \s-1ISA\s0 level. -.Ip "\fB\-mips4\fR" 4 -.IX Item "-mips4" -Issue instructions from level 4 of the \s-1MIPS\s0 \s-1ISA\s0 (conditional move, -prefetch, enhanced \s-1FPU\s0 instructions). \fBr8000\fR is the default -\&\fIcpu-type\fR at this \s-1ISA\s0 level. -.Ip "\fB\-mfp32\fR" 4 -.IX Item "-mfp32" -Assume that 32 32\-bit floating point registers are available. This is -the default. -.Ip "\fB\-mfp64\fR" 4 -.IX Item "-mfp64" -Assume that 32 64\-bit floating point registers are available. This is -the default when the \fB\-mips3\fR option is used. -.Ip "\fB\-mfused-madd\fR" 4 -.IX Item "-mfused-madd" -.PD 0 -.Ip "\fB\-mno-fused-madd\fR" 4 -.IX Item "-mno-fused-madd" -.PD -Generate code that uses (does not use) the floating point multiply and -accumulate instructions, when they are available. These instructions -are generated by default if they are available, but this may be -undesirable if the extra precision causes problems or on certain chips -in the mode where denormals are rounded to zero where denormals -generated by multiply and accumulate instructions cause exceptions -anyway. -.Ip "\fB\-mgp32\fR" 4 -.IX Item "-mgp32" -Assume that 32 32\-bit general purpose registers are available. This is -the default. -.Ip "\fB\-mgp64\fR" 4 -.IX Item "-mgp64" -Assume that 32 64\-bit general purpose registers are available. This is -the default when the \fB\-mips3\fR option is used. -.Ip "\fB\-mint64\fR" 4 -.IX Item "-mint64" -Force int and long types to be 64 bits wide. See \fB\-mlong32\fR for an -explanation of the default, and the width of pointers. -.Ip "\fB\-mlong64\fR" 4 -.IX Item "-mlong64" -Force long types to be 64 bits wide. See \fB\-mlong32\fR for an -explanation of the default, and the width of pointers. -.Ip "\fB\-mlong32\fR" 4 -.IX Item "-mlong32" -Force long, int, and pointer types to be 32 bits wide. -.Sp -If none of \fB\-mlong32\fR, \fB\-mlong64\fR, or \fB\-mint64\fR are set, -the size of ints, longs, and pointers depends on the \s-1ABI\s0 and \s-1ISA\s0 chosen. -For \fB\-mabi=32\fR, and \fB\-mabi=n32\fR, ints and longs are 32 bits -wide. For \fB\-mabi=64\fR, ints are 32 bits, and longs are 64 bits wide. -For \fB\-mabi=eabi\fR and either \fB\-mips1\fR or \fB\-mips2\fR, ints -and longs are 32 bits wide. For \fB\-mabi=eabi\fR and higher ISAs, ints -are 32 bits, and longs are 64 bits wide. The width of pointer types is -the smaller of the width of longs or the width of general purpose -registers (which in turn depends on the \s-1ISA\s0). -.Ip "\fB\-mabi=32\fR" 4 -.IX Item "-mabi=32" -.PD 0 -.Ip "\fB\-mabi=o64\fR" 4 -.IX Item "-mabi=o64" -.Ip "\fB\-mabi=n32\fR" 4 -.IX Item "-mabi=n32" -.Ip "\fB\-mabi=64\fR" 4 -.IX Item "-mabi=64" -.Ip "\fB\-mabi=eabi\fR" 4 -.IX Item "-mabi=eabi" -.PD -Generate code for the indicated \s-1ABI\s0. The default instruction level is -\&\fB\-mips1\fR for \fB32\fR, \fB\-mips3\fR for \fBn32\fR, and -\&\fB\-mips4\fR otherwise. Conversely, with \fB\-mips1\fR or -\&\fB\-mips2\fR, the default \s-1ABI\s0 is \fB32\fR; otherwise, the default \s-1ABI\s0 -is \fB64\fR. -.Ip "\fB\-mmips-as\fR" 4 -.IX Item "-mmips-as" -Generate code for the \s-1MIPS\s0 assembler, and invoke \fImips-tfile\fR to -add normal debug information. This is the default for all -platforms except for the \s-1OSF/1\s0 reference platform, using the OSF/rose -object format. If the either of the \fB\-gstabs\fR or \fB\-gstabs+\fR -switches are used, the \fImips-tfile\fR program will encapsulate the -stabs within \s-1MIPS\s0 \s-1ECOFF\s0. -.Ip "\fB\-mgas\fR" 4 -.IX Item "-mgas" -Generate code for the \s-1GNU\s0 assembler. This is the default on the \s-1OSF/1\s0 -reference platform, using the OSF/rose object format. Also, this is -the default if the configure option \fB\*(--with-gnu-as\fR is used. -.Ip "\fB\-msplit-addresses\fR" 4 -.IX Item "-msplit-addresses" -.PD 0 -.Ip "\fB\-mno-split-addresses\fR" 4 -.IX Item "-mno-split-addresses" -.PD -Generate code to load the high and low parts of address constants separately. -This allows \s-1GCC\s0 to optimize away redundant loads of the high order -bits of addresses. This optimization requires \s-1GNU\s0 as and \s-1GNU\s0 ld. -This optimization is enabled by default for some embedded targets where -\&\s-1GNU\s0 as and \s-1GNU\s0 ld are standard. -.Ip "\fB\-mrnames\fR" 4 -.IX Item "-mrnames" -.PD 0 -.Ip "\fB\-mno-rnames\fR" 4 -.IX Item "-mno-rnames" -.PD -The \fB\-mrnames\fR switch says to output code using the \s-1MIPS\s0 software -names for the registers, instead of the hardware names (ie, \fIa0\fR -instead of \fI$4\fR). The only known assembler that supports this option -is the Algorithmics assembler. -.Ip "\fB\-mgpopt\fR" 4 -.IX Item "-mgpopt" -.PD 0 -.Ip "\fB\-mno-gpopt\fR" 4 -.IX Item "-mno-gpopt" -.PD -The \fB\-mgpopt\fR switch says to write all of the data declarations -before the instructions in the text section, this allows the \s-1MIPS\s0 -assembler to generate one word memory references instead of using two -words for short global or static data items. This is on by default if -optimization is selected. -.Ip "\fB\-mstats\fR" 4 -.IX Item "-mstats" -.PD 0 -.Ip "\fB\-mno-stats\fR" 4 -.IX Item "-mno-stats" -.PD -For each non-inline function processed, the \fB\-mstats\fR switch -causes the compiler to emit one line to the standard error file to -print statistics about the program (number of registers saved, stack -size, etc.). -.Ip "\fB\-mmemcpy\fR" 4 -.IX Item "-mmemcpy" -.PD 0 -.Ip "\fB\-mno-memcpy\fR" 4 -.IX Item "-mno-memcpy" -.PD -The \fB\-mmemcpy\fR switch makes all block moves call the appropriate -string function (\fBmemcpy\fR or \fBbcopy\fR) instead of possibly -generating inline code. -.Ip "\fB\-mmips-tfile\fR" 4 -.IX Item "-mmips-tfile" -.PD 0 -.Ip "\fB\-mno-mips-tfile\fR" 4 -.IX Item "-mno-mips-tfile" -.PD -The \fB\-mno-mips-tfile\fR switch causes the compiler not -postprocess the object file with the \fImips-tfile\fR program, -after the \s-1MIPS\s0 assembler has generated it to add debug support. If -\&\fImips-tfile\fR is not run, then no local variables will be -available to the debugger. In addition, \fIstage2\fR and -\&\fIstage3\fR objects will have the temporary file names passed to the -assembler embedded in the object file, which means the objects will -not compare the same. The \fB\-mno-mips-tfile\fR switch should only -be used when there are bugs in the \fImips-tfile\fR program that -prevents compilation. -.Ip "\fB\-msoft-float\fR" 4 -.IX Item "-msoft-float" -Generate output containing library calls for floating point. -\&\fBWarning:\fR the requisite libraries are not part of \s-1GCC\s0. -Normally the facilities of the machine's usual C compiler are used, but -this can't be done directly in cross-compilation. You must make your -own arrangements to provide suitable library functions for -cross-compilation. -.Ip "\fB\-mhard-float\fR" 4 -.IX Item "-mhard-float" -Generate output containing floating point instructions. This is the -default if you use the unmodified sources. -.Ip "\fB\-mabicalls\fR" 4 -.IX Item "-mabicalls" -.PD 0 -.Ip "\fB\-mno-abicalls\fR" 4 -.IX Item "-mno-abicalls" -.PD -Emit (or do not emit) the pseudo operations \fB.abicalls\fR, -\&\fB.cpload\fR, and \fB.cprestore\fR that some System V.4 ports use for -position independent code. -.Ip "\fB\-mlong-calls\fR" 4 -.IX Item "-mlong-calls" -.PD 0 -.Ip "\fB\-mno-long-calls\fR" 4 -.IX Item "-mno-long-calls" -.PD -Do all calls with the \fB\s-1JALR\s0\fR instruction, which requires -loading up a function's address into a register before the call. -You need to use this switch, if you call outside of the current -512 megabyte segment to functions that are not through pointers. -.Ip "\fB\-mhalf-pic\fR" 4 -.IX Item "-mhalf-pic" -.PD 0 -.Ip "\fB\-mno-half-pic\fR" 4 -.IX Item "-mno-half-pic" -.PD -Put pointers to extern references into the data section and load them -up, rather than put the references in the text section. -.Ip "\fB\-membedded-pic\fR" 4 -.IX Item "-membedded-pic" -.PD 0 -.Ip "\fB\-mno-embedded-pic\fR" 4 -.IX Item "-mno-embedded-pic" -.PD -Generate \s-1PIC\s0 code suitable for some embedded systems. All calls are -made using \s-1PC\s0 relative address, and all data is addressed using the \f(CW$gp\fR -register. No more than 65536 bytes of global data may be used. This -requires \s-1GNU\s0 as and \s-1GNU\s0 ld which do most of the work. This currently -only works on targets which use \s-1ECOFF\s0; it does not work with \s-1ELF\s0. -.Ip "\fB\-membedded-data\fR" 4 -.IX Item "-membedded-data" -.PD 0 -.Ip "\fB\-mno-embedded-data\fR" 4 -.IX Item "-mno-embedded-data" -.PD -Allocate variables to the read-only data section first if possible, then -next in the small data section if possible, otherwise in data. This gives -slightly slower code than the default, but reduces the amount of \s-1RAM\s0 required -when executing, and thus may be preferred for some embedded systems. -.Ip "\fB\-muninit-const-in-rodata\fR" 4 -.IX Item "-muninit-const-in-rodata" -.PD 0 -.Ip "\fB\-mno-uninit-const-in-rodata\fR" 4 -.IX Item "-mno-uninit-const-in-rodata" -.PD -When used together with \fB\-membedded-data\fR, it will always store uninitialized -const variables in the read-only data section. -.Ip "\fB\-msingle-float\fR" 4 -.IX Item "-msingle-float" -.PD 0 -.Ip "\fB\-mdouble-float\fR" 4 -.IX Item "-mdouble-float" -.PD -The \fB\-msingle-float\fR switch tells gcc to assume that the floating -point coprocessor only supports single precision operations, as on the -\&\fBr4650\fR chip. The \fB\-mdouble-float\fR switch permits gcc to use -double precision operations. This is the default. -.Ip "\fB\-mmad\fR" 4 -.IX Item "-mmad" -.PD 0 -.Ip "\fB\-mno-mad\fR" 4 -.IX Item "-mno-mad" -.PD -Permit use of the \fBmad\fR, \fBmadu\fR and \fBmul\fR instructions, -as on the \fBr4650\fR chip. -.Ip "\fB\-m4650\fR" 4 -.IX Item "-m4650" -Turns on \fB\-msingle-float\fR, \fB\-mmad\fR, and, at least for now, -\&\fB\-mcpu=r4650\fR. -.Ip "\fB\-mips16\fR" 4 -.IX Item "-mips16" -.PD 0 -.Ip "\fB\-mno-mips16\fR" 4 -.IX Item "-mno-mips16" -.PD -Enable 16\-bit instructions. -.Ip "\fB\-mentry\fR" 4 -.IX Item "-mentry" -Use the entry and exit pseudo ops. This option can only be used with -\&\fB\-mips16\fR. -.Ip "\fB\-EL\fR" 4 -.IX Item "-EL" -Compile code for the processor in little endian mode. -The requisite libraries are assumed to exist. -.Ip "\fB\-EB\fR" 4 -.IX Item "-EB" -Compile code for the processor in big endian mode. -The requisite libraries are assumed to exist. -.Ip "\fB\-G\fR \fInum\fR" 4 -.IX Item "-G num" -Put global and static items less than or equal to \fInum\fR bytes into -the small data or bss sections instead of the normal data or bss -section. This allows the assembler to emit one word memory reference -instructions based on the global pointer (\fIgp\fR or \fI$28\fR), -instead of the normal two words used. By default, \fInum\fR is 8 when -the \s-1MIPS\s0 assembler is used, and 0 when the \s-1GNU\s0 assembler is used. The -\&\fB\-G\fR \fInum\fR switch is also passed to the assembler and linker. -All modules should be compiled with the same \fB\-G\fR \fInum\fR -value. -.Ip "\fB\-nocpp\fR" 4 -.IX Item "-nocpp" -Tell the \s-1MIPS\s0 assembler to not run its preprocessor over user -assembler files (with a \fB.s\fR suffix) when assembling them. -.Ip "\fB\-mfix7000\fR" 4 -.IX Item "-mfix7000" -Pass an option to gas which will cause nops to be inserted if -the read of the destination register of an mfhi or mflo instruction -occurs in the following two instructions. -.Ip "\fB\-no-crt0\fR" 4 -.IX Item "-no-crt0" -Do not include the default crt0. -.Ip "\fB\-mflush-func=\fR\fIfunc\fR" 4 -.IX Item "-mflush-func=func" -.PD 0 -.Ip "\fB\-mno-flush-func\fR" 4 -.IX Item "-mno-flush-func" -.PD -Specifies the function to call to flush the I and D caches, or to not -call any such function. If called, the function must take the same -arguments as the common \f(CW\*(C`_flush_func()\*(C'\fR, that is, the address of the -memory range for which the cache is being flushed, the size of the -memory range, and the number 3 (to flush both caches). The default -depends on the target gcc was configured for, but commonly is either -\&\fB_flush_func\fR or \fB_\|_cpu_flush\fR. -.PP -These options are defined by the macro -\&\f(CW\*(C`TARGET_SWITCHES\*(C'\fR in the machine description. The default for the -options is also defined by that macro, which enables you to change the -defaults. -.PP -.I "Intel 386 and \s-1AMD\s0 x86\-64 Options" -.IX Subsection "Intel 386 and AMD x86-64 Options" -.PP -These \fB\-m\fR options are defined for the i386 and x86\-64 family of -computers: -.Ip "\fB\-mcpu=\fR\fIcpu-type\fR" 4 -.IX Item "-mcpu=cpu-type" -Tune to \fIcpu-type\fR everything applicable about the generated code, except -for the \s-1ABI\s0 and the set of available instructions. The choices for -\&\fIcpu-type\fR are \fBi386\fR, \fBi486\fR, \fBi586\fR, \fBi686\fR, -\&\fBpentium\fR, \fBpentium-mmx\fR, \fBpentiumpro\fR, \fBpentium2\fR, -\&\fBpentium3\fR, \fBpentium4\fR, \fBk6\fR, \fBk6\-2\fR, \fBk6\-3\fR, -\&\fBathlon\fR, \fBathlon-tbird\fR, \fBathlon-4\fR, \fBathlon-xp\fR -and \fBathlon-mp\fR. -.Sp -While picking a specific \fIcpu-type\fR will schedule things appropriately -for that particular chip, the compiler will not generate any code that -does not run on the i386 without the \fB\-march=\fR\fIcpu-type\fR option -being used. \fBi586\fR is equivalent to \fBpentium\fR and \fBi686\fR -is equivalent to \fBpentiumpro\fR. \fBk6\fR and \fBathlon\fR are the -\&\s-1AMD\s0 chips as opposed to the Intel ones. -.Ip "\fB\-march=\fR\fIcpu-type\fR" 4 -.IX Item "-march=cpu-type" -Generate instructions for the machine type \fIcpu-type\fR. The choices -for \fIcpu-type\fR are the same as for \fB\-mcpu\fR. Moreover, -specifying \fB\-march=\fR\fIcpu-type\fR implies \fB\-mcpu=\fR\fIcpu-type\fR. -.Ip "\fB\-m386\fR" 4 -.IX Item "-m386" -.PD 0 -.Ip "\fB\-m486\fR" 4 -.IX Item "-m486" -.Ip "\fB\-mpentium\fR" 4 -.IX Item "-mpentium" -.Ip "\fB\-mpentiumpro\fR" 4 -.IX Item "-mpentiumpro" -.PD -These options are synonyms for \fB\-mcpu=i386\fR, \fB\-mcpu=i486\fR, -\&\fB\-mcpu=pentium\fR, and \fB\-mcpu=pentiumpro\fR respectively. -These synonyms are deprecated. -.Ip "\fB\-mfpmath=\fR\fIunit\fR" 4 -.IX Item "-mfpmath=unit" -generate floating point arithmetics for selected unit \fIunit\fR. the choices -for \fIunit\fR are: -.RS 4 -.Ip "\fB387\fR" 4 -.IX Item "387" -Use the standard 387 floating point coprocessor present majority of chips and -emulated otherwise. Code compiled with this option will run almost everywhere. -The temporary results are computed in 80bit precesion instead of precision -specified by the type resulting in slightly different results compared to most -of other chips. See \fB\-ffloat-store\fR for more detailed description. -.Sp -This is the default choice for i386 compiler. -.Ip "\fBsse\fR" 4 -.IX Item "sse" -Use scalar floating point instructions present in the \s-1SSE\s0 instruction set. -This instruction set is supported by Pentium3 and newer chips, in the \s-1AMD\s0 line -by Athlon-4, Athlon-xp and Athlon-mp chips. The earlier version of \s-1SSE\s0 -instruction set supports only single precision arithmetics, thus the double and -extended precision arithmetics is still done using 387. Later version, present -only in Pentium4 and the future \s-1AMD\s0 x86\-64 chips supports double precision -arithmetics too. -.Sp -For i387 you need to use \fB\-march=\fR\fIcpu-type\fR, \fB\-msse\fR or -\&\fB\-msse2\fR switches to enable \s-1SSE\s0 extensions and make this option -effective. For x86\-64 compiler, these extensions are enabled by default. -.Sp -The resulting code should be considerably faster in majority of cases and avoid -the numerical instability problems of 387 code, but may break some existing -code that expects temporaries to be 80bit. -.Sp -This is the default choice for x86\-64 compiler. -.Ip "\fBsse,387\fR" 4 -.IX Item "sse,387" -Attempt to utilize both instruction sets at once. This effectivly double the -amount of available registers and on chips with separate execution units for -387 and \s-1SSE\s0 the execution resources too. Use this option with care, as it is -still experimental, because gcc register allocator does not model separate -functional units well resulting in instable performance. -.RE -.RS 4 -.RE -.Ip "\fB\-masm=\fR\fIdialect\fR" 4 -.IX Item "-masm=dialect" -Output asm instructions using selected \fIdialect\fR. Supported choices are -\&\fBintel\fR or \fBatt\fR (the default one). -.Ip "\fB\-mieee-fp\fR" 4 -.IX Item "-mieee-fp" -.PD 0 -.Ip "\fB\-mno-ieee-fp\fR" 4 -.IX Item "-mno-ieee-fp" -.PD -Control whether or not the compiler uses \s-1IEEE\s0 floating point -comparisons. These handle correctly the case where the result of a -comparison is unordered. -.Ip "\fB\-msoft-float\fR" 4 -.IX Item "-msoft-float" -Generate output containing library calls for floating point. -\&\fBWarning:\fR the requisite libraries are not part of \s-1GCC\s0. -Normally the facilities of the machine's usual C compiler are used, but -this can't be done directly in cross-compilation. You must make your -own arrangements to provide suitable library functions for -cross-compilation. -.Sp -On machines where a function returns floating point results in the 80387 -register stack, some floating point opcodes may be emitted even if -\&\fB\-msoft-float\fR is used. -.Ip "\fB\-mno-fp-ret-in-387\fR" 4 -.IX Item "-mno-fp-ret-in-387" -Do not use the \s-1FPU\s0 registers for return values of functions. -.Sp -The usual calling convention has functions return values of types -\&\f(CW\*(C`float\*(C'\fR and \f(CW\*(C`double\*(C'\fR in an \s-1FPU\s0 register, even if there -is no \s-1FPU\s0. The idea is that the operating system should emulate -an \s-1FPU\s0. -.Sp -The option \fB\-mno-fp-ret-in-387\fR causes such values to be returned -in ordinary \s-1CPU\s0 registers instead. -.Ip "\fB\-mno-fancy-math-387\fR" 4 -.IX Item "-mno-fancy-math-387" -Some 387 emulators do not support the \f(CW\*(C`sin\*(C'\fR, \f(CW\*(C`cos\*(C'\fR and -\&\f(CW\*(C`sqrt\*(C'\fR instructions for the 387. Specify this option to avoid -generating those instructions. This option is the default on FreeBSD, -OpenBSD and NetBSD. This option is overridden when \fB\-march\fR -indicates that the target cpu will always have an \s-1FPU\s0 and so the -instruction will not need emulation. As of revision 2.6.1, these -instructions are not generated unless you also use the -\&\fB\-funsafe-math-optimizations\fR switch. -.Ip "\fB\-malign-double\fR" 4 -.IX Item "-malign-double" -.PD 0 -.Ip "\fB\-mno-align-double\fR" 4 -.IX Item "-mno-align-double" -.PD -Control whether \s-1GCC\s0 aligns \f(CW\*(C`double\*(C'\fR, \f(CW\*(C`long double\*(C'\fR, and -\&\f(CW\*(C`long long\*(C'\fR variables on a two word boundary or a one word -boundary. Aligning \f(CW\*(C`double\*(C'\fR variables on a two word boundary will -produce code that runs somewhat faster on a \fBPentium\fR at the -expense of more memory. -.Sp -\&\fBWarning:\fR if you use the \fB\-malign-double\fR switch, -structures containing the above types will be aligned differently than -the published application binary interface specifications for the 386 -and will not be binary compatible with structures in code compiled -without that switch. -.Ip "\fB\-m128bit-long-double\fR" 4 -.IX Item "-m128bit-long-double" -Control the size of \f(CW\*(C`long double\*(C'\fR type. i386 application binary interface -specify the size to be 12 bytes, while modern architectures (Pentium and newer) -prefer \f(CW\*(C`long double\*(C'\fR aligned to 8 or 16 byte boundary. This is -impossible to reach with 12 byte long doubles in the array accesses. -.Sp -\&\fBWarning:\fR if you use the \fB\-m128bit-long-double\fR switch, the -structures and arrays containing \f(CW\*(C`long double\*(C'\fR will change their size as -well as function calling convention for function taking \f(CW\*(C`long double\*(C'\fR -will be modified. -.Ip "\fB\-m96bit-long-double\fR" 4 -.IX Item "-m96bit-long-double" -Set the size of \f(CW\*(C`long double\*(C'\fR to 96 bits as required by the i386 -application binary interface. This is the default. -.Ip "\fB\-msvr3\-shlib\fR" 4 -.IX Item "-msvr3-shlib" -.PD 0 -.Ip "\fB\-mno-svr3\-shlib\fR" 4 -.IX Item "-mno-svr3-shlib" -.PD -Control whether \s-1GCC\s0 places uninitialized local variables into the -\&\f(CW\*(C`bss\*(C'\fR or \f(CW\*(C`data\*(C'\fR segments. \fB\-msvr3\-shlib\fR places them -into \f(CW\*(C`bss\*(C'\fR. These options are meaningful only on System V Release 3. -.Ip "\fB\-mrtd\fR" 4 -.IX Item "-mrtd" -Use a different function-calling convention, in which functions that -take a fixed number of arguments return with the \f(CW\*(C`ret\*(C'\fR \fInum\fR -instruction, which pops their arguments while returning. This saves one -instruction in the caller since there is no need to pop the arguments -there. -.Sp -You can specify that an individual function is called with this calling -sequence with the function attribute \fBstdcall\fR. You can also -override the \fB\-mrtd\fR option by using the function attribute -\&\fBcdecl\fR. -.Sp -\&\fBWarning:\fR this calling convention is incompatible with the one -normally used on Unix, so you cannot use it if you need to call -libraries compiled with the Unix compiler. -.Sp -Also, you must provide function prototypes for all functions that -take variable numbers of arguments (including \f(CW\*(C`printf\*(C'\fR); -otherwise incorrect code will be generated for calls to those -functions. -.Sp -In addition, seriously incorrect code will result if you call a -function with too many arguments. (Normally, extra arguments are -harmlessly ignored.) -.Ip "\fB\-mregparm=\fR\fInum\fR" 4 -.IX Item "-mregparm=num" -Control how many registers are used to pass integer arguments. By -default, no registers are used to pass arguments, and at most 3 -registers can be used. You can control this behavior for a specific -function by using the function attribute \fBregparm\fR. -.Sp -\&\fBWarning:\fR if you use this switch, and -\&\fInum\fR is nonzero, then you must build all modules with the same -value, including any libraries. This includes the system libraries and -startup modules. -.Ip "\fB\-mpreferred-stack-boundary=\fR\fInum\fR" 4 -.IX Item "-mpreferred-stack-boundary=num" -Attempt to keep the stack boundary aligned to a 2 raised to \fInum\fR -byte boundary. If \fB\-mpreferred-stack-boundary\fR is not specified, -the default is 4 (16 bytes or 128 bits), except when optimizing for code -size (\fB\-Os\fR), in which case the default is the minimum correct -alignment (4 bytes for x86, and 8 bytes for x86\-64). -.Sp -On Pentium and PentiumPro, \f(CW\*(C`double\*(C'\fR and \f(CW\*(C`long double\*(C'\fR values -should be aligned to an 8 byte boundary (see \fB\-malign-double\fR) or -suffer significant run time performance penalties. On Pentium \s-1III\s0, the -Streaming \s-1SIMD\s0 Extension (\s-1SSE\s0) data type \f(CW\*(C`_\|_m128\*(C'\fR suffers similar -penalties if it is not 16 byte aligned. -.Sp -To ensure proper alignment of this values on the stack, the stack boundary -must be as aligned as that required by any value stored on the stack. -Further, every function must be generated such that it keeps the stack -aligned. Thus calling a function compiled with a higher preferred -stack boundary from a function compiled with a lower preferred stack -boundary will most likely misalign the stack. It is recommended that -libraries that use callbacks always use the default setting. -.Sp -This extra alignment does consume extra stack space, and generally -increases code size. Code that is sensitive to stack space usage, such -as embedded systems and operating system kernels, may want to reduce the -preferred alignment to \fB\-mpreferred-stack-boundary=2\fR. -.Ip "\fB\-mmmx\fR" 4 -.IX Item "-mmmx" -.PD 0 -.Ip "\fB\-mno-mmx\fR" 4 -.IX Item "-mno-mmx" -.Ip "\fB\-msse\fR" 4 -.IX Item "-msse" -.Ip "\fB\-mno-sse\fR" 4 -.IX Item "-mno-sse" -.Ip "\fB\-msse2\fR" 4 -.IX Item "-msse2" -.Ip "\fB\-mno-sse2\fR" 4 -.IX Item "-mno-sse2" -.Ip "\fB\-m3dnow\fR" 4 -.IX Item "-m3dnow" -.Ip "\fB\-mno-3dnow\fR" 4 -.IX Item "-mno-3dnow" -.PD -These switches enable or disable the use of built-in functions that allow -direct access to the \s-1MMX\s0, \s-1SSE\s0 and 3Dnow extensions of the instruction set. -.Sp -To have \s-1SSE/SSE2\s0 instructions generated automatically from floating-point code, -see \fB\-mfpmath=sse\fR. -.Ip "\fB\-mpush-args\fR" 4 -.IX Item "-mpush-args" -.PD 0 -.Ip "\fB\-mno-push-args\fR" 4 -.IX Item "-mno-push-args" -.PD -Use \s-1PUSH\s0 operations to store outgoing parameters. This method is shorter -and usually equally fast as method using \s-1SUB/MOV\s0 operations and is enabled -by default. In some cases disabling it may improve performance because of -improved scheduling and reduced dependencies. -.Ip "\fB\-maccumulate-outgoing-args\fR" 4 -.IX Item "-maccumulate-outgoing-args" -If enabled, the maximum amount of space required for outgoing arguments will be -computed in the function prologue. This is faster on most modern CPUs -because of reduced dependencies, improved scheduling and reduced stack usage -when preferred stack boundary is not equal to 2. The drawback is a notable -increase in code size. This switch implies \fB\-mno-push-args\fR. -.Ip "\fB\-mthreads\fR" 4 -.IX Item "-mthreads" -Support thread-safe exception handling on \fBMingw32\fR. Code that relies -on thread-safe exception handling must compile and link all code with the -\&\fB\-mthreads\fR option. When compiling, \fB\-mthreads\fR defines -\&\fB\-D_MT\fR; when linking, it links in a special thread helper library -\&\fB\-lmingwthrd\fR which cleans up per thread exception handling data. -.Ip "\fB\-mno-align-stringops\fR" 4 -.IX Item "-mno-align-stringops" -Do not align destination of inlined string operations. This switch reduces -code size and improves performance in case the destination is already aligned, -but gcc don't know about it. -.Ip "\fB\-minline-all-stringops\fR" 4 -.IX Item "-minline-all-stringops" -By default \s-1GCC\s0 inlines string operations only when destination is known to be -aligned at least to 4 byte boundary. This enables more inlining, increase code -size, but may improve performance of code that depends on fast memcpy, strlen -and memset for short lengths. -.Ip "\fB\-momit-leaf-frame-pointer\fR" 4 -.IX Item "-momit-leaf-frame-pointer" -Don't keep the frame pointer in a register for leaf functions. This -avoids the instructions to save, set up and restore frame pointers and -makes an extra register available in leaf functions. The option -\&\fB\-fomit-frame-pointer\fR removes the frame pointer for all functions -which might make debugging harder. -.PP -These \fB\-m\fR switches are supported in addition to the above -on \s-1AMD\s0 x86\-64 processors in 64\-bit environments. -.Ip "\fB\-m32\fR" 4 -.IX Item "-m32" -.PD 0 -.Ip "\fB\-m64\fR" 4 -.IX Item "-m64" -.PD -Generate code for a 32\-bit or 64\-bit environment. -The 32\-bit environment sets int, long and pointer to 32 bits and -generates code that runs on any i386 system. -The 64\-bit environment sets int to 32 bits and long and pointer -to 64 bits and generates code for \s-1AMD\s0's x86\-64 architecture. -.Ip "\fB\-mno-red-zone\fR" 4 -.IX Item "-mno-red-zone" -Do not use a so called red zone for x86\-64 code. The red zone is mandated -by the x86\-64 \s-1ABI\s0, it is a 128\-byte area beyond the location of the -stack pointer that will not be modified by signal or interrupt handlers -and therefore can be used for temporary data without adjusting the stack -pointer. The flag \fB\-mno-red-zone\fR disables this red zone. -.Ip "\fB\-mcmodel=small\fR" 4 -.IX Item "-mcmodel=small" -Generate code for the small code model: the program and its symbols must -be linked in the lower 2 \s-1GB\s0 of the address space. Pointers are 64 bits. -Programs can be statically or dynamically linked. This is the default -code model. -.Ip "\fB\-mcmodel=kernel\fR" 4 -.IX Item "-mcmodel=kernel" -Generate code for the kernel code model. The kernel runs in the -negative 2 \s-1GB\s0 of the address space. -This model has to be used for Linux kernel code. -.Ip "\fB\-mcmodel=medium\fR" 4 -.IX Item "-mcmodel=medium" -Generate code for the medium model: The program is linked in the lower 2 -\&\s-1GB\s0 of the address space but symbols can be located anywhere in the -address space. Programs can be statically or dynamically linked, but -building of shared libraries are not supported with the medium model. -.Ip "\fB\-mcmodel=large\fR" 4 -.IX Item "-mcmodel=large" -Generate code for the large model: This model makes no assumptions -about addresses and sizes of sections. Currently \s-1GCC\s0 does not implement -this model. -.PP -.I "\s-1HPPA\s0 Options" -.IX Subsection "HPPA Options" -.PP -These \fB\-m\fR options are defined for the \s-1HPPA\s0 family of computers: -.Ip "\fB\-march=\fR\fIarchitecture-type\fR" 4 -.IX Item "-march=architecture-type" -Generate code for the specified architecture. The choices for -\&\fIarchitecture-type\fR are \fB1.0\fR for \s-1PA\s0 1.0, \fB1.1\fR for \s-1PA\s0 -1.1, and \fB2.0\fR for \s-1PA\s0 2.0 processors. Refer to -\&\fI/usr/lib/sched.models\fR on an \s-1HP-UX\s0 system to determine the proper -architecture option for your machine. Code compiled for lower numbered -architectures will run on higher numbered architectures, but not the -other way around. -.Sp -\&\s-1PA\s0 2.0 support currently requires gas snapshot 19990413 or later. The -next release of binutils (current is 2.9.1) will probably contain \s-1PA\s0 2.0 -support. -.Ip "\fB\-mpa-risc-1\-0\fR" 4 -.IX Item "-mpa-risc-1-0" -.PD 0 -.Ip "\fB\-mpa-risc-1\-1\fR" 4 -.IX Item "-mpa-risc-1-1" -.Ip "\fB\-mpa-risc-2\-0\fR" 4 -.IX Item "-mpa-risc-2-0" -.PD -Synonyms for \fB\-march=1.0\fR, \fB\-march=1.1\fR, and \fB\-march=2.0\fR respectively. -.Ip "\fB\-mbig-switch\fR" 4 -.IX Item "-mbig-switch" -Generate code suitable for big switch tables. Use this option only if -the assembler/linker complain about out of range branches within a switch -table. -.Ip "\fB\-mjump-in-delay\fR" 4 -.IX Item "-mjump-in-delay" -Fill delay slots of function calls with unconditional jump instructions -by modifying the return pointer for the function call to be the target -of the conditional jump. -.Ip "\fB\-mdisable-fpregs\fR" 4 -.IX Item "-mdisable-fpregs" -Prevent floating point registers from being used in any manner. This is -necessary for compiling kernels which perform lazy context switching of -floating point registers. If you use this option and attempt to perform -floating point operations, the compiler will abort. -.Ip "\fB\-mdisable-indexing\fR" 4 -.IX Item "-mdisable-indexing" -Prevent the compiler from using indexing address modes. This avoids some -rather obscure problems when compiling \s-1MIG\s0 generated code under \s-1MACH\s0. -.Ip "\fB\-mno-space-regs\fR" 4 -.IX Item "-mno-space-regs" -Generate code that assumes the target has no space registers. This allows -\&\s-1GCC\s0 to generate faster indirect calls and use unscaled index address modes. -.Sp -Such code is suitable for level 0 \s-1PA\s0 systems and kernels. -.Ip "\fB\-mfast-indirect-calls\fR" 4 -.IX Item "-mfast-indirect-calls" -Generate code that assumes calls never cross space boundaries. This -allows \s-1GCC\s0 to emit code which performs faster indirect calls. -.Sp -This option will not work in the presence of shared libraries or nested -functions. -.Ip "\fB\-mlong-load-store\fR" 4 -.IX Item "-mlong-load-store" -Generate 3\-instruction load and store sequences as sometimes required by -the \s-1HP-UX\s0 10 linker. This is equivalent to the \fB+k\fR option to -the \s-1HP\s0 compilers. -.Ip "\fB\-mportable-runtime\fR" 4 -.IX Item "-mportable-runtime" -Use the portable calling conventions proposed by \s-1HP\s0 for \s-1ELF\s0 systems. -.Ip "\fB\-mgas\fR" 4 -.IX Item "-mgas" -Enable the use of assembler directives only \s-1GAS\s0 understands. -.Ip "\fB\-mschedule=\fR\fIcpu-type\fR" 4 -.IX Item "-mschedule=cpu-type" -Schedule code according to the constraints for the machine type -\&\fIcpu-type\fR. The choices for \fIcpu-type\fR are \fB700\fR -\&\fB7100\fR, \fB7100LC\fR, \fB7200\fR, and \fB8000\fR. Refer to -\&\fI/usr/lib/sched.models\fR on an \s-1HP-UX\s0 system to determine the -proper scheduling option for your machine. -.Ip "\fB\-mlinker-opt\fR" 4 -.IX Item "-mlinker-opt" -Enable the optimization pass in the \s-1HPUX\s0 linker. Note this makes symbolic -debugging impossible. It also triggers a bug in the \s-1HPUX\s0 8 and \s-1HPUX\s0 9 linkers -in which they give bogus error messages when linking some programs. -.Ip "\fB\-msoft-float\fR" 4 -.IX Item "-msoft-float" -Generate output containing library calls for floating point. -\&\fBWarning:\fR the requisite libraries are not available for all \s-1HPPA\s0 -targets. Normally the facilities of the machine's usual C compiler are -used, but this cannot be done directly in cross-compilation. You must make -your own arrangements to provide suitable library functions for -cross-compilation. The embedded target \fBhppa1.1\-*\-pro\fR -does provide software floating point support. -.Sp -\&\fB\-msoft-float\fR changes the calling convention in the output file; -therefore, it is only useful if you compile \fIall\fR of a program with -this option. In particular, you need to compile \fIlibgcc.a\fR, the -library that comes with \s-1GCC\s0, with \fB\-msoft-float\fR in order for -this to work. -.PP -.I "Intel 960 Options" -.IX Subsection "Intel 960 Options" -.PP -These \fB\-m\fR options are defined for the Intel 960 implementations: -.Ip "\fB\-m\fR\fIcpu-type\fR" 4 -.IX Item "-mcpu-type" -Assume the defaults for the machine type \fIcpu-type\fR for some of -the other options, including instruction scheduling, floating point -support, and addressing modes. The choices for \fIcpu-type\fR are -\&\fBka\fR, \fBkb\fR, \fBmc\fR, \fBca\fR, \fBcf\fR, -\&\fBsa\fR, and \fBsb\fR. -The default is -\&\fBkb\fR. -.Ip "\fB\-mnumerics\fR" 4 -.IX Item "-mnumerics" -.PD 0 -.Ip "\fB\-msoft-float\fR" 4 -.IX Item "-msoft-float" -.PD -The \fB\-mnumerics\fR option indicates that the processor does support -floating-point instructions. The \fB\-msoft-float\fR option indicates -that floating-point support should not be assumed. -.Ip "\fB\-mleaf-procedures\fR" 4 -.IX Item "-mleaf-procedures" -.PD 0 -.Ip "\fB\-mno-leaf-procedures\fR" 4 -.IX Item "-mno-leaf-procedures" -.PD -Do (or do not) attempt to alter leaf procedures to be callable with the -\&\f(CW\*(C`bal\*(C'\fR instruction as well as \f(CW\*(C`call\*(C'\fR. This will result in more -efficient code for explicit calls when the \f(CW\*(C`bal\*(C'\fR instruction can be -substituted by the assembler or linker, but less efficient code in other -cases, such as calls via function pointers, or using a linker that doesn't -support this optimization. -.Ip "\fB\-mtail-call\fR" 4 -.IX Item "-mtail-call" -.PD 0 -.Ip "\fB\-mno-tail-call\fR" 4 -.IX Item "-mno-tail-call" -.PD -Do (or do not) make additional attempts (beyond those of the -machine-independent portions of the compiler) to optimize tail-recursive -calls into branches. You may not want to do this because the detection of -cases where this is not valid is not totally complete. The default is -\&\fB\-mno-tail-call\fR. -.Ip "\fB\-mcomplex-addr\fR" 4 -.IX Item "-mcomplex-addr" -.PD 0 -.Ip "\fB\-mno-complex-addr\fR" 4 -.IX Item "-mno-complex-addr" -.PD -Assume (or do not assume) that the use of a complex addressing mode is a -win on this implementation of the i960. Complex addressing modes may not -be worthwhile on the K-series, but they definitely are on the C-series. -The default is currently \fB\-mcomplex-addr\fR for all processors except -the \s-1CB\s0 and \s-1CC\s0. -.Ip "\fB\-mcode-align\fR" 4 -.IX Item "-mcode-align" -.PD 0 -.Ip "\fB\-mno-code-align\fR" 4 -.IX Item "-mno-code-align" -.PD -Align code to 8\-byte boundaries for faster fetching (or don't bother). -Currently turned on by default for C-series implementations only. -.Ip "\fB\-mic-compat\fR" 4 -.IX Item "-mic-compat" -.PD 0 -.Ip "\fB\-mic2.0\-compat\fR" 4 -.IX Item "-mic2.0-compat" -.Ip "\fB\-mic3.0\-compat\fR" 4 -.IX Item "-mic3.0-compat" -.PD -Enable compatibility with iC960 v2.0 or v3.0. -.Ip "\fB\-masm-compat\fR" 4 -.IX Item "-masm-compat" -.PD 0 -.Ip "\fB\-mintel-asm\fR" 4 -.IX Item "-mintel-asm" -.PD -Enable compatibility with the iC960 assembler. -.Ip "\fB\-mstrict-align\fR" 4 -.IX Item "-mstrict-align" -.PD 0 -.Ip "\fB\-mno-strict-align\fR" 4 -.IX Item "-mno-strict-align" -.PD -Do not permit (do permit) unaligned accesses. -.Ip "\fB\-mold-align\fR" 4 -.IX Item "-mold-align" -Enable structure-alignment compatibility with Intel's gcc release version -1.3 (based on gcc 1.37). This option implies \fB\-mstrict-align\fR. -.Ip "\fB\-mlong-double-64\fR" 4 -.IX Item "-mlong-double-64" -Implement type \fBlong double\fR as 64\-bit floating point numbers. -Without the option \fBlong double\fR is implemented by 80\-bit -floating point numbers. The only reason we have it because there is -no 128\-bit \fBlong double\fR support in \fBfp-bit.c\fR yet. So it -is only useful for people using soft-float targets. Otherwise, we -should recommend against use of it. -.PP -.I "\s-1DEC\s0 Alpha Options" -.IX Subsection "DEC Alpha Options" -.PP -These \fB\-m\fR options are defined for the \s-1DEC\s0 Alpha implementations: -.Ip "\fB\-mno-soft-float\fR" 4 -.IX Item "-mno-soft-float" -.PD 0 -.Ip "\fB\-msoft-float\fR" 4 -.IX Item "-msoft-float" -.PD -Use (do not use) the hardware floating-point instructions for -floating-point operations. When \fB\-msoft-float\fR is specified, -functions in \fIlibgcc.a\fR will be used to perform floating-point -operations. Unless they are replaced by routines that emulate the -floating-point operations, or compiled in such a way as to call such -emulations routines, these routines will issue floating-point -operations. If you are compiling for an Alpha without floating-point -operations, you must ensure that the library is built so as not to call -them. -.Sp -Note that Alpha implementations without floating-point operations are -required to have floating-point registers. -.Ip "\fB\-mfp-reg\fR" 4 -.IX Item "-mfp-reg" -.PD 0 -.Ip "\fB\-mno-fp-regs\fR" 4 -.IX Item "-mno-fp-regs" -.PD -Generate code that uses (does not use) the floating-point register set. -\&\fB\-mno-fp-regs\fR implies \fB\-msoft-float\fR. If the floating-point -register set is not used, floating point operands are passed in integer -registers as if they were integers and floating-point results are passed -in \f(CW\*(C`$0\*(C'\fR instead of \f(CW\*(C`$f0\*(C'\fR. This is a non-standard calling sequence, -so any function with a floating-point argument or return value called by code -compiled with \fB\-mno-fp-regs\fR must also be compiled with that -option. -.Sp -A typical use of this option is building a kernel that does not use, -and hence need not save and restore, any floating-point registers. -.Ip "\fB\-mieee\fR" 4 -.IX Item "-mieee" -The Alpha architecture implements floating-point hardware optimized for -maximum performance. It is mostly compliant with the \s-1IEEE\s0 floating -point standard. However, for full compliance, software assistance is -required. This option generates code fully \s-1IEEE\s0 compliant code -\&\fIexcept\fR that the \fIinexact-flag\fR is not maintained (see below). -If this option is turned on, the preprocessor macro \f(CW\*(C`_IEEE_FP\*(C'\fR is -defined during compilation. The resulting code is less efficient but is -able to correctly support denormalized numbers and exceptional \s-1IEEE\s0 -values such as not-a-number and plus/minus infinity. Other Alpha -compilers call this option \fB\-ieee_with_no_inexact\fR. -.Ip "\fB\-mieee-with-inexact\fR" 4 -.IX Item "-mieee-with-inexact" -This is like \fB\-mieee\fR except the generated code also maintains -the \s-1IEEE\s0 \fIinexact-flag\fR. Turning on this option causes the -generated code to implement fully-compliant \s-1IEEE\s0 math. In addition to -\&\f(CW\*(C`_IEEE_FP\*(C'\fR, \f(CW\*(C`_IEEE_FP_EXACT\*(C'\fR is defined as a preprocessor -macro. On some Alpha implementations the resulting code may execute -significantly slower than the code generated by default. Since there is -very little code that depends on the \fIinexact-flag\fR, you should -normally not specify this option. Other Alpha compilers call this -option \fB\-ieee_with_inexact\fR. -.Ip "\fB\-mfp-trap-mode=\fR\fItrap-mode\fR" 4 -.IX Item "-mfp-trap-mode=trap-mode" -This option controls what floating-point related traps are enabled. -Other Alpha compilers call this option \fB\-fptm\fR \fItrap-mode\fR. -The trap mode can be set to one of four values: -.RS 4 -.Ip "\fBn\fR" 4 -.IX Item "n" -This is the default (normal) setting. The only traps that are enabled -are the ones that cannot be disabled in software (e.g., division by zero -trap). -.Ip "\fBu\fR" 4 -.IX Item "u" -In addition to the traps enabled by \fBn\fR, underflow traps are enabled -as well. -.Ip "\fBsu\fR" 4 -.IX Item "su" -Like \fBsu\fR, but the instructions are marked to be safe for software -completion (see Alpha architecture manual for details). -.Ip "\fBsui\fR" 4 -.IX Item "sui" -Like \fBsu\fR, but inexact traps are enabled as well. -.RE -.RS 4 -.RE -.Ip "\fB\-mfp-rounding-mode=\fR\fIrounding-mode\fR" 4 -.IX Item "-mfp-rounding-mode=rounding-mode" -Selects the \s-1IEEE\s0 rounding mode. Other Alpha compilers call this option -\&\fB\-fprm\fR \fIrounding-mode\fR. The \fIrounding-mode\fR can be one -of: -.RS 4 -.Ip "\fBn\fR" 4 -.IX Item "n" -Normal \s-1IEEE\s0 rounding mode. Floating point numbers are rounded towards -the nearest machine number or towards the even machine number in case -of a tie. -.Ip "\fBm\fR" 4 -.IX Item "m" -Round towards minus infinity. -.Ip "\fBc\fR" 4 -.IX Item "c" -Chopped rounding mode. Floating point numbers are rounded towards zero. -.Ip "\fBd\fR" 4 -.IX Item "d" -Dynamic rounding mode. A field in the floating point control register -(\fIfpcr\fR, see Alpha architecture reference manual) controls the -rounding mode in effect. The C library initializes this register for -rounding towards plus infinity. Thus, unless your program modifies the -\&\fIfpcr\fR, \fBd\fR corresponds to round towards plus infinity. -.RE -.RS 4 -.RE -.Ip "\fB\-mtrap-precision=\fR\fItrap-precision\fR" 4 -.IX Item "-mtrap-precision=trap-precision" -In the Alpha architecture, floating point traps are imprecise. This -means without software assistance it is impossible to recover from a -floating trap and program execution normally needs to be terminated. -\&\s-1GCC\s0 can generate code that can assist operating system trap handlers -in determining the exact location that caused a floating point trap. -Depending on the requirements of an application, different levels of -precisions can be selected: -.RS 4 -.Ip "\fBp\fR" 4 -.IX Item "p" -Program precision. This option is the default and means a trap handler -can only identify which program caused a floating point exception. -.Ip "\fBf\fR" 4 -.IX Item "f" -Function precision. The trap handler can determine the function that -caused a floating point exception. -.Ip "\fBi\fR" 4 -.IX Item "i" -Instruction precision. The trap handler can determine the exact -instruction that caused a floating point exception. -.RE -.RS 4 -.Sp -Other Alpha compilers provide the equivalent options called -\&\fB\-scope_safe\fR and \fB\-resumption_safe\fR. -.RE -.Ip "\fB\-mieee-conformant\fR" 4 -.IX Item "-mieee-conformant" -This option marks the generated code as \s-1IEEE\s0 conformant. You must not -use this option unless you also specify \fB\-mtrap-precision=i\fR and either -\&\fB\-mfp-trap-mode=su\fR or \fB\-mfp-trap-mode=sui\fR. Its only effect -is to emit the line \fB.eflag 48\fR in the function prologue of the -generated assembly file. Under \s-1DEC\s0 Unix, this has the effect that -IEEE-conformant math library routines will be linked in. -.Ip "\fB\-mbuild-constants\fR" 4 -.IX Item "-mbuild-constants" -Normally \s-1GCC\s0 examines a 32\- or 64\-bit integer constant to -see if it can construct it from smaller constants in two or three -instructions. If it cannot, it will output the constant as a literal and -generate code to load it from the data segment at runtime. -.Sp -Use this option to require \s-1GCC\s0 to construct \fIall\fR integer constants -using code, even if it takes more instructions (the maximum is six). -.Sp -You would typically use this option to build a shared library dynamic -loader. Itself a shared library, it must relocate itself in memory -before it can find the variables and constants in its own data segment. -.Ip "\fB\-malpha-as\fR" 4 -.IX Item "-malpha-as" -.PD 0 -.Ip "\fB\-mgas\fR" 4 -.IX Item "-mgas" -.PD -Select whether to generate code to be assembled by the vendor-supplied -assembler (\fB\-malpha-as\fR) or by the \s-1GNU\s0 assembler \fB\-mgas\fR. -.Ip "\fB\-mbwx\fR" 4 -.IX Item "-mbwx" -.PD 0 -.Ip "\fB\-mno-bwx\fR" 4 -.IX Item "-mno-bwx" -.Ip "\fB\-mcix\fR" 4 -.IX Item "-mcix" -.Ip "\fB\-mno-cix\fR" 4 -.IX Item "-mno-cix" -.Ip "\fB\-mfix\fR" 4 -.IX Item "-mfix" -.Ip "\fB\-mno-fix\fR" 4 -.IX Item "-mno-fix" -.Ip "\fB\-mmax\fR" 4 -.IX Item "-mmax" -.Ip "\fB\-mno-max\fR" 4 -.IX Item "-mno-max" -.PD -Indicate whether \s-1GCC\s0 should generate code to use the optional \s-1BWX\s0, -\&\s-1CIX\s0, \s-1FIX\s0 and \s-1MAX\s0 instruction sets. The default is to use the instruction -sets supported by the \s-1CPU\s0 type specified via \fB\-mcpu=\fR option or that -of the \s-1CPU\s0 on which \s-1GCC\s0 was built if none was specified. -.Ip "\fB\-mfloat-vax\fR" 4 -.IX Item "-mfloat-vax" -.PD 0 -.Ip "\fB\-mfloat-ieee\fR" 4 -.IX Item "-mfloat-ieee" -.PD -Generate code that uses (does not use) \s-1VAX\s0 F and G floating point -arithmetic instead of \s-1IEEE\s0 single and double precision. -.Ip "\fB\-mexplicit-relocs\fR" 4 -.IX Item "-mexplicit-relocs" -.PD 0 -.Ip "\fB\-mno-explicit-relocs\fR" 4 -.IX Item "-mno-explicit-relocs" -.PD -Older Alpha assemblers provided no way to generate symbol relocations -except via assembler macros. Use of these macros does not allow -optimial instruction scheduling. \s-1GNU\s0 binutils as of version 2.12 -supports a new syntax that allows the compiler to explicitly mark -which relocations should apply to which instructions. This option -is mostly useful for debugging, as \s-1GCC\s0 detects the capabilities of -the assembler when it is built and sets the default accordingly. -.Ip "\fB\-msmall-data\fR" 4 -.IX Item "-msmall-data" -.PD 0 -.Ip "\fB\-mlarge-data\fR" 4 -.IX Item "-mlarge-data" -.PD -When \fB\-mexplicit-relocs\fR is in effect, static data is -accessed via \fIgp-relative\fR relocations. When \fB\-msmall-data\fR -is used, objects 8 bytes long or smaller are placed in a \fIsmall data area\fR -(the \f(CW\*(C`.sdata\*(C'\fR and \f(CW\*(C`.sbss\*(C'\fR sections) and are accessed via -16\-bit relocations off of the \f(CW\*(C`$gp\*(C'\fR register. This limits the -size of the small data area to 64KB, but allows the variables to be -directly accessed via a single instruction. -.Sp -The default is \fB\-mlarge-data\fR. With this option the data area -is limited to just below 2GB. Programs that require more than 2GB of -data must use \f(CW\*(C`malloc\*(C'\fR or \f(CW\*(C`mmap\*(C'\fR to allocate the data in the -heap instead of in the program's data segment. -.Sp -When generating code for shared libraries, \fB\-fpic\fR implies -\&\fB\-msmall-data\fR and \fB\-fPIC\fR implies \fB\-mlarge-data\fR. -.Ip "\fB\-mcpu=\fR\fIcpu_type\fR" 4 -.IX Item "-mcpu=cpu_type" -Set the instruction set and instruction scheduling parameters for -machine type \fIcpu_type\fR. You can specify either the \fB\s-1EV\s0\fR -style name or the corresponding chip number. \s-1GCC\s0 supports scheduling -parameters for the \s-1EV4\s0, \s-1EV5\s0 and \s-1EV6\s0 family of processors and will -choose the default values for the instruction set from the processor -you specify. If you do not specify a processor type, \s-1GCC\s0 will default -to the processor on which the compiler was built. -.Sp -Supported values for \fIcpu_type\fR are -.RS 4 -.Ip "\fBev4\fR" 4 -.IX Item "ev4" -.PD 0 -.Ip "\fBev45\fR" 4 -.IX Item "ev45" -.Ip "\fB21064\fR" 4 -.IX Item "21064" -.PD -Schedules as an \s-1EV4\s0 and has no instruction set extensions. -.Ip "\fBev5\fR" 4 -.IX Item "ev5" -.PD 0 -.Ip "\fB21164\fR" 4 -.IX Item "21164" -.PD -Schedules as an \s-1EV5\s0 and has no instruction set extensions. -.Ip "\fBev56\fR" 4 -.IX Item "ev56" -.PD 0 -.Ip "\fB21164a\fR" 4 -.IX Item "21164a" -.PD -Schedules as an \s-1EV5\s0 and supports the \s-1BWX\s0 extension. -.Ip "\fBpca56\fR" 4 -.IX Item "pca56" -.PD 0 -.Ip "\fB21164pc\fR" 4 -.IX Item "21164pc" -.Ip "\fB21164PC\fR" 4 -.IX Item "21164PC" -.PD -Schedules as an \s-1EV5\s0 and supports the \s-1BWX\s0 and \s-1MAX\s0 extensions. -.Ip "\fBev6\fR" 4 -.IX Item "ev6" -.PD 0 -.Ip "\fB21264\fR" 4 -.IX Item "21264" -.PD -Schedules as an \s-1EV6\s0 and supports the \s-1BWX\s0, \s-1FIX\s0, and \s-1MAX\s0 extensions. -.Ip "\fBev67\fR" 4 -.IX Item "ev67" -.PD 0 -.Ip "\fB21264a\fR" 4 -.IX Item "21264a" -.PD -Schedules as an \s-1EV6\s0 and supports the \s-1BWX\s0, \s-1CIX\s0, \s-1FIX\s0, and \s-1MAX\s0 extensions. -.RE -.RS 4 -.RE -.Ip "\fB\-mtune=\fR\fIcpu_type\fR" 4 -.IX Item "-mtune=cpu_type" -Set only the instruction scheduling parameters for machine type -\&\fIcpu_type\fR. The instruction set is not changed. -.Ip "\fB\-mmemory-latency=\fR\fItime\fR" 4 -.IX Item "-mmemory-latency=time" -Sets the latency the scheduler should assume for typical memory -references as seen by the application. This number is highly -dependent on the memory access patterns used by the application -and the size of the external cache on the machine. -.Sp -Valid options for \fItime\fR are -.RS 4 -.Ip "\fInumber\fR" 4 -.IX Item "number" -A decimal number representing clock cycles. -.Ip "\fBL1\fR" 4 -.IX Item "L1" -.PD 0 -.Ip "\fBL2\fR" 4 -.IX Item "L2" -.Ip "\fBL3\fR" 4 -.IX Item "L3" -.Ip "\fBmain\fR" 4 -.IX Item "main" -.PD -The compiler contains estimates of the number of clock cycles for -``typical'' \s-1EV4\s0 & \s-1EV5\s0 hardware for the Level 1, 2 & 3 caches -(also called Dcache, Scache, and Bcache), as well as to main memory. -Note that L3 is only valid for \s-1EV5\s0. -.RE -.RS 4 -.RE -.PP -.I "\s-1DEC\s0 Alpha/VMS Options" -.IX Subsection "DEC Alpha/VMS Options" -.PP -These \fB\-m\fR options are defined for the \s-1DEC\s0 Alpha/VMS implementations: -.Ip "\fB\-mvms-return-codes\fR" 4 -.IX Item "-mvms-return-codes" -Return \s-1VMS\s0 condition codes from main. The default is to return \s-1POSIX\s0 -style condition (e.g. error) codes. -.PP -.I "Clipper Options" -.IX Subsection "Clipper Options" -.PP -These \fB\-m\fR options are defined for the Clipper implementations: -.Ip "\fB\-mc300\fR" 4 -.IX Item "-mc300" -Produce code for a C300 Clipper processor. This is the default. -.Ip "\fB\-mc400\fR" 4 -.IX Item "-mc400" -Produce code for a C400 Clipper processor, i.e. use floating point -registers f8\*(--f15. -.PP -.I "H8/300 Options" -.IX Subsection "H8/300 Options" -.PP -These \fB\-m\fR options are defined for the H8/300 implementations: -.Ip "\fB\-mrelax\fR" 4 -.IX Item "-mrelax" -Shorten some address references at link time, when possible; uses the -linker option \fB\-relax\fR. -.Ip "\fB\-mh\fR" 4 -.IX Item "-mh" -Generate code for the H8/300H. -.Ip "\fB\-ms\fR" 4 -.IX Item "-ms" -Generate code for the H8/S. -.Ip "\fB\-ms2600\fR" 4 -.IX Item "-ms2600" -Generate code for the H8/S2600. This switch must be used with \fB\-ms\fR. -.Ip "\fB\-mint32\fR" 4 -.IX Item "-mint32" -Make \f(CW\*(C`int\*(C'\fR data 32 bits by default. -.Ip "\fB\-malign-300\fR" 4 -.IX Item "-malign-300" -On the H8/300H and H8/S, use the same alignment rules as for the H8/300. -The default for the H8/300H and H8/S is to align longs and floats on 4 -byte boundaries. -\&\fB\-malign-300\fR causes them to be aligned on 2 byte boundaries. -This option has no effect on the H8/300. -.PP -.I "\s-1SH\s0 Options" -.IX Subsection "SH Options" -.PP -These \fB\-m\fR options are defined for the \s-1SH\s0 implementations: -.Ip "\fB\-m1\fR" 4 -.IX Item "-m1" -Generate code for the \s-1SH1\s0. -.Ip "\fB\-m2\fR" 4 -.IX Item "-m2" -Generate code for the \s-1SH2\s0. -.Ip "\fB\-m3\fR" 4 -.IX Item "-m3" -Generate code for the \s-1SH3\s0. -.Ip "\fB\-m3e\fR" 4 -.IX Item "-m3e" -Generate code for the SH3e. -.Ip "\fB\-m4\-nofpu\fR" 4 -.IX Item "-m4-nofpu" -Generate code for the \s-1SH4\s0 without a floating-point unit. -.Ip "\fB\-m4\-single-only\fR" 4 -.IX Item "-m4-single-only" -Generate code for the \s-1SH4\s0 with a floating-point unit that only -supports single-precision arithmetic. -.Ip "\fB\-m4\-single\fR" 4 -.IX Item "-m4-single" -Generate code for the \s-1SH4\s0 assuming the floating-point unit is in -single-precision mode by default. -.Ip "\fB\-m4\fR" 4 -.IX Item "-m4" -Generate code for the \s-1SH4\s0. -.Ip "\fB\-mb\fR" 4 -.IX Item "-mb" -Compile code for the processor in big endian mode. -.Ip "\fB\-ml\fR" 4 -.IX Item "-ml" -Compile code for the processor in little endian mode. -.Ip "\fB\-mdalign\fR" 4 -.IX Item "-mdalign" -Align doubles at 64\-bit boundaries. Note that this changes the calling -conventions, and thus some functions from the standard C library will -not work unless you recompile it first with \fB\-mdalign\fR. -.Ip "\fB\-mrelax\fR" 4 -.IX Item "-mrelax" -Shorten some address references at link time, when possible; uses the -linker option \fB\-relax\fR. -.Ip "\fB\-mbigtable\fR" 4 -.IX Item "-mbigtable" -Use 32\-bit offsets in \f(CW\*(C`switch\*(C'\fR tables. The default is to use -16\-bit offsets. -.Ip "\fB\-mfmovd\fR" 4 -.IX Item "-mfmovd" -Enable the use of the instruction \f(CW\*(C`fmovd\*(C'\fR. -.Ip "\fB\-mhitachi\fR" 4 -.IX Item "-mhitachi" -Comply with the calling conventions defined by Hitachi. -.Ip "\fB\-mnomacsave\fR" 4 -.IX Item "-mnomacsave" -Mark the \f(CW\*(C`MAC\*(C'\fR register as call-clobbered, even if -\&\fB\-mhitachi\fR is given. -.Ip "\fB\-mieee\fR" 4 -.IX Item "-mieee" -Increase IEEE-compliance of floating-point code. -.Ip "\fB\-misize\fR" 4 -.IX Item "-misize" -Dump instruction size and location in the assembly code. -.Ip "\fB\-mpadstruct\fR" 4 -.IX Item "-mpadstruct" -This option is deprecated. It pads structures to multiple of 4 bytes, -which is incompatible with the \s-1SH\s0 \s-1ABI\s0. -.Ip "\fB\-mspace\fR" 4 -.IX Item "-mspace" -Optimize for space instead of speed. Implied by \fB\-Os\fR. -.Ip "\fB\-mprefergot\fR" 4 -.IX Item "-mprefergot" -When generating position-independent code, emit function calls using -the Global Offset Table instead of the Procedure Linkage Table. -.Ip "\fB\-musermode\fR" 4 -.IX Item "-musermode" -Generate a library function call to invalidate instruction cache -entries, after fixing up a trampoline. This library function call -doesn't assume it can write to the whole memory address space. This -is the default when the target is \f(CW\*(C`sh\-*\-linux*\*(C'\fR. -.PP -.I "Options for System V" -.IX Subsection "Options for System V" -.PP -These additional options are available on System V Release 4 for -compatibility with other compilers on those systems: -.Ip "\fB\-G\fR" 4 -.IX Item "-G" -Create a shared object. -It is recommended that \fB\-symbolic\fR or \fB\-shared\fR be used instead. -.Ip "\fB\-Qy\fR" 4 -.IX Item "-Qy" -Identify the versions of each tool used by the compiler, in a -\&\f(CW\*(C`.ident\*(C'\fR assembler directive in the output. -.Ip "\fB\-Qn\fR" 4 -.IX Item "-Qn" -Refrain from adding \f(CW\*(C`.ident\*(C'\fR directives to the output file (this is -the default). -.Ip "\fB\-YP,\fR\fIdirs\fR" 4 -.IX Item "-YP,dirs" -Search the directories \fIdirs\fR, and no others, for libraries -specified with \fB\-l\fR. -.Ip "\fB\-Ym,\fR\fIdir\fR" 4 -.IX Item "-Ym,dir" -Look in the directory \fIdir\fR to find the M4 preprocessor. -The assembler uses this option. -.PP -.I "TMS320C3x/C4x Options" -.IX Subsection "TMS320C3x/C4x Options" -.PP -These \fB\-m\fR options are defined for TMS320C3x/C4x implementations: -.Ip "\fB\-mcpu=\fR\fIcpu_type\fR" 4 -.IX Item "-mcpu=cpu_type" -Set the instruction set, register set, and instruction scheduling -parameters for machine type \fIcpu_type\fR. Supported values for -\&\fIcpu_type\fR are \fBc30\fR, \fBc31\fR, \fBc32\fR, \fBc40\fR, and -\&\fBc44\fR. The default is \fBc40\fR to generate code for the -\&\s-1TMS320C40\s0. -.Ip "\fB\-mbig-memory\fR" 4 -.IX Item "-mbig-memory" -.PD 0 -.Ip "\fB\-mbig\fR" 4 -.IX Item "-mbig" -.Ip "\fB\-msmall-memory\fR" 4 -.IX Item "-msmall-memory" -.Ip "\fB\-msmall\fR" 4 -.IX Item "-msmall" -.PD -Generates code for the big or small memory model. The small memory -model assumed that all data fits into one 64K word page. At run-time -the data page (\s-1DP\s0) register must be set to point to the 64K page -containing the .bss and .data program sections. The big memory model is -the default and requires reloading of the \s-1DP\s0 register for every direct -memory access. -.Ip "\fB\-mbk\fR" 4 -.IX Item "-mbk" -.PD 0 -.Ip "\fB\-mno-bk\fR" 4 -.IX Item "-mno-bk" -.PD -Allow (disallow) allocation of general integer operands into the block -count register \s-1BK\s0. -.Ip "\fB\-mdb\fR" 4 -.IX Item "-mdb" -.PD 0 -.Ip "\fB\-mno-db\fR" 4 -.IX Item "-mno-db" -.PD -Enable (disable) generation of code using decrement and branch, -\&\fIDBcond\fR\|(D), instructions. This is enabled by default for the C4x. To be -on the safe side, this is disabled for the C3x, since the maximum -iteration count on the C3x is 2^{23 + 1} (but who iterates loops more than -2^{23} times on the C3x?). Note that \s-1GCC\s0 will try to reverse a loop so -that it can utilise the decrement and branch instruction, but will give -up if there is more than one memory reference in the loop. Thus a loop -where the loop counter is decremented can generate slightly more -efficient code, in cases where the \s-1RPTB\s0 instruction cannot be utilised. -.Ip "\fB\-mdp-isr-reload\fR" 4 -.IX Item "-mdp-isr-reload" -.PD 0 -.Ip "\fB\-mparanoid\fR" 4 -.IX Item "-mparanoid" -.PD -Force the \s-1DP\s0 register to be saved on entry to an interrupt service -routine (\s-1ISR\s0), reloaded to point to the data section, and restored on -exit from the \s-1ISR\s0. This should not be required unless someone has -violated the small memory model by modifying the \s-1DP\s0 register, say within -an object library. -.Ip "\fB\-mmpyi\fR" 4 -.IX Item "-mmpyi" -.PD 0 -.Ip "\fB\-mno-mpyi\fR" 4 -.IX Item "-mno-mpyi" -.PD -For the C3x use the 24\-bit \s-1MPYI\s0 instruction for integer multiplies -instead of a library call to guarantee 32\-bit results. Note that if one -of the operands is a constant, then the multiplication will be performed -using shifts and adds. If the \fB\-mmpyi\fR option is not specified for the C3x, -then squaring operations are performed inline instead of a library call. -.Ip "\fB\-mfast-fix\fR" 4 -.IX Item "-mfast-fix" -.PD 0 -.Ip "\fB\-mno-fast-fix\fR" 4 -.IX Item "-mno-fast-fix" -.PD -The C3x/C4x \s-1FIX\s0 instruction to convert a floating point value to an -integer value chooses the nearest integer less than or equal to the -floating point value rather than to the nearest integer. Thus if the -floating point number is negative, the result will be incorrectly -truncated an additional code is necessary to detect and correct this -case. This option can be used to disable generation of the additional -code required to correct the result. -.Ip "\fB\-mrptb\fR" 4 -.IX Item "-mrptb" -.PD 0 -.Ip "\fB\-mno-rptb\fR" 4 -.IX Item "-mno-rptb" -.PD -Enable (disable) generation of repeat block sequences using the \s-1RPTB\s0 -instruction for zero overhead looping. The \s-1RPTB\s0 construct is only used -for innermost loops that do not call functions or jump across the loop -boundaries. There is no advantage having nested \s-1RPTB\s0 loops due to the -overhead required to save and restore the \s-1RC\s0, \s-1RS\s0, and \s-1RE\s0 registers. -This is enabled by default with \fB\-O2\fR. -.Ip "\fB\-mrpts=\fR\fIcount\fR" 4 -.IX Item "-mrpts=count" -.PD 0 -.Ip "\fB\-mno-rpts\fR" 4 -.IX Item "-mno-rpts" -.PD -Enable (disable) the use of the single instruction repeat instruction -\&\s-1RPTS\s0. If a repeat block contains a single instruction, and the loop -count can be guaranteed to be less than the value \fIcount\fR, \s-1GCC\s0 will -emit a \s-1RPTS\s0 instruction instead of a \s-1RPTB\s0. If no value is specified, -then a \s-1RPTS\s0 will be emitted even if the loop count cannot be determined -at compile time. Note that the repeated instruction following \s-1RPTS\s0 does -not have to be reloaded from memory each iteration, thus freeing up the -\&\s-1CPU\s0 buses for operands. However, since interrupts are blocked by this -instruction, it is disabled by default. -.Ip "\fB\-mloop-unsigned\fR" 4 -.IX Item "-mloop-unsigned" -.PD 0 -.Ip "\fB\-mno-loop-unsigned\fR" 4 -.IX Item "-mno-loop-unsigned" -.PD -The maximum iteration count when using \s-1RPTS\s0 and \s-1RPTB\s0 (and \s-1DB\s0 on the C40) -is 2^{31 + 1} since these instructions test if the iteration count is -negative to terminate the loop. If the iteration count is unsigned -there is a possibility than the 2^{31 + 1} maximum iteration count may be -exceeded. This switch allows an unsigned iteration count. -.Ip "\fB\-mti\fR" 4 -.IX Item "-mti" -Try to emit an assembler syntax that the \s-1TI\s0 assembler (asm30) is happy -with. This also enforces compatibility with the \s-1API\s0 employed by the \s-1TI\s0 -C3x C compiler. For example, long doubles are passed as structures -rather than in floating point registers. -.Ip "\fB\-mregparm\fR" 4 -.IX Item "-mregparm" -.PD 0 -.Ip "\fB\-mmemparm\fR" 4 -.IX Item "-mmemparm" -.PD -Generate code that uses registers (stack) for passing arguments to functions. -By default, arguments are passed in registers where possible rather -than by pushing arguments on to the stack. -.Ip "\fB\-mparallel-insns\fR" 4 -.IX Item "-mparallel-insns" -.PD 0 -.Ip "\fB\-mno-parallel-insns\fR" 4 -.IX Item "-mno-parallel-insns" -.PD -Allow the generation of parallel instructions. This is enabled by -default with \fB\-O2\fR. -.Ip "\fB\-mparallel-mpy\fR" 4 -.IX Item "-mparallel-mpy" -.PD 0 -.Ip "\fB\-mno-parallel-mpy\fR" 4 -.IX Item "-mno-parallel-mpy" -.PD -Allow the generation of MPY||ADD and MPY||SUB parallel instructions, -provided \fB\-mparallel-insns\fR is also specified. These instructions have -tight register constraints which can pessimize the code generation -of large functions. -.PP -.I "V850 Options" -.IX Subsection "V850 Options" -.PP -These \fB\-m\fR options are defined for V850 implementations: -.Ip "\fB\-mlong-calls\fR" 4 -.IX Item "-mlong-calls" -.PD 0 -.Ip "\fB\-mno-long-calls\fR" 4 -.IX Item "-mno-long-calls" -.PD -Treat all calls as being far away (near). If calls are assumed to be -far away, the compiler will always load the functions address up into a -register, and call indirect through the pointer. -.Ip "\fB\-mno-ep\fR" 4 -.IX Item "-mno-ep" -.PD 0 -.Ip "\fB\-mep\fR" 4 -.IX Item "-mep" -.PD -Do not optimize (do optimize) basic blocks that use the same index -pointer 4 or more times to copy pointer into the \f(CW\*(C`ep\*(C'\fR register, and -use the shorter \f(CW\*(C`sld\*(C'\fR and \f(CW\*(C`sst\*(C'\fR instructions. The \fB\-mep\fR -option is on by default if you optimize. -.Ip "\fB\-mno-prolog-function\fR" 4 -.IX Item "-mno-prolog-function" -.PD 0 -.Ip "\fB\-mprolog-function\fR" 4 -.IX Item "-mprolog-function" -.PD -Do not use (do use) external functions to save and restore registers at -the prolog and epilog of a function. The external functions are slower, -but use less code space if more than one function saves the same number -of registers. The \fB\-mprolog-function\fR option is on by default if -you optimize. -.Ip "\fB\-mspace\fR" 4 -.IX Item "-mspace" -Try to make the code as small as possible. At present, this just turns -on the \fB\-mep\fR and \fB\-mprolog-function\fR options. -.Ip "\fB\-mtda=\fR\fIn\fR" 4 -.IX Item "-mtda=n" -Put static or global variables whose size is \fIn\fR bytes or less into -the tiny data area that register \f(CW\*(C`ep\*(C'\fR points to. The tiny data -area can hold up to 256 bytes in total (128 bytes for byte references). -.Ip "\fB\-msda=\fR\fIn\fR" 4 -.IX Item "-msda=n" -Put static or global variables whose size is \fIn\fR bytes or less into -the small data area that register \f(CW\*(C`gp\*(C'\fR points to. The small data -area can hold up to 64 kilobytes. -.Ip "\fB\-mzda=\fR\fIn\fR" 4 -.IX Item "-mzda=n" -Put static or global variables whose size is \fIn\fR bytes or less into -the first 32 kilobytes of memory. -.Ip "\fB\-mv850\fR" 4 -.IX Item "-mv850" -Specify that the target processor is the V850. -.Ip "\fB\-mbig-switch\fR" 4 -.IX Item "-mbig-switch" -Generate code suitable for big switch tables. Use this option only if -the assembler/linker complain about out of range branches within a switch -table. -.PP -.I "\s-1ARC\s0 Options" -.IX Subsection "ARC Options" -.PP -These options are defined for \s-1ARC\s0 implementations: -.Ip "\fB\-EL\fR" 4 -.IX Item "-EL" -Compile code for little endian mode. This is the default. -.Ip "\fB\-EB\fR" 4 -.IX Item "-EB" -Compile code for big endian mode. -.Ip "\fB\-mmangle-cpu\fR" 4 -.IX Item "-mmangle-cpu" -Prepend the name of the cpu to all public symbol names. -In multiple-processor systems, there are many \s-1ARC\s0 variants with different -instruction and register set characteristics. This flag prevents code -compiled for one cpu to be linked with code compiled for another. -No facility exists for handling variants that are ``almost identical''. -This is an all or nothing option. -.Ip "\fB\-mcpu=\fR\fIcpu\fR" 4 -.IX Item "-mcpu=cpu" -Compile code for \s-1ARC\s0 variant \fIcpu\fR. -Which variants are supported depend on the configuration. -All variants support \fB\-mcpu=base\fR, this is the default. -.Ip "\fB\-mtext=\fR\fItext-section\fR" 4 -.IX Item "-mtext=text-section" -.PD 0 -.Ip "\fB\-mdata=\fR\fIdata-section\fR" 4 -.IX Item "-mdata=data-section" -.Ip "\fB\-mrodata=\fR\fIreadonly-data-section\fR" 4 -.IX Item "-mrodata=readonly-data-section" -.PD -Put functions, data, and readonly data in \fItext-section\fR, -\&\fIdata-section\fR, and \fIreadonly-data-section\fR respectively -by default. This can be overridden with the \f(CW\*(C`section\*(C'\fR attribute. -.PP -.I "\s-1NS32K\s0 Options" -.IX Subsection "NS32K Options" -.PP -These are the \fB\-m\fR options defined for the 32000 series. The default -values for these options depends on which style of 32000 was selected when -the compiler was configured; the defaults for the most common choices are -given below. -.Ip "\fB\-m32032\fR" 4 -.IX Item "-m32032" -.PD 0 -.Ip "\fB\-m32032\fR" 4 -.IX Item "-m32032" -.PD -Generate output for a 32032. This is the default -when the compiler is configured for 32032 and 32016 based systems. -.Ip "\fB\-m32332\fR" 4 -.IX Item "-m32332" -.PD 0 -.Ip "\fB\-m32332\fR" 4 -.IX Item "-m32332" -.PD -Generate output for a 32332. This is the default -when the compiler is configured for 32332\-based systems. -.Ip "\fB\-m32532\fR" 4 -.IX Item "-m32532" -.PD 0 -.Ip "\fB\-m32532\fR" 4 -.IX Item "-m32532" -.PD -Generate output for a 32532. This is the default -when the compiler is configured for 32532\-based systems. -.Ip "\fB\-m32081\fR" 4 -.IX Item "-m32081" -Generate output containing 32081 instructions for floating point. -This is the default for all systems. -.Ip "\fB\-m32381\fR" 4 -.IX Item "-m32381" -Generate output containing 32381 instructions for floating point. This -also implies \fB\-m32081\fR. The 32381 is only compatible with the 32332 -and 32532 cpus. This is the default for the pc532\-netbsd configuration. -.Ip "\fB\-mmulti-add\fR" 4 -.IX Item "-mmulti-add" -Try and generate multiply-add floating point instructions \f(CW\*(C`polyF\*(C'\fR -and \f(CW\*(C`dotF\*(C'\fR. This option is only available if the \fB\-m32381\fR -option is in effect. Using these instructions requires changes to -register allocation which generally has a negative impact on -performance. This option should only be enabled when compiling code -particularly likely to make heavy use of multiply-add instructions. -.Ip "\fB\-mnomulti-add\fR" 4 -.IX Item "-mnomulti-add" -Do not try and generate multiply-add floating point instructions -\&\f(CW\*(C`polyF\*(C'\fR and \f(CW\*(C`dotF\*(C'\fR. This is the default on all platforms. -.Ip "\fB\-msoft-float\fR" 4 -.IX Item "-msoft-float" -Generate output containing library calls for floating point. -\&\fBWarning:\fR the requisite libraries may not be available. -.Ip "\fB\-mnobitfield\fR" 4 -.IX Item "-mnobitfield" -Do not use the bit-field instructions. On some machines it is faster to -use shifting and masking operations. This is the default for the pc532. -.Ip "\fB\-mbitfield\fR" 4 -.IX Item "-mbitfield" -Do use the bit-field instructions. This is the default for all platforms -except the pc532. -.Ip "\fB\-mrtd\fR" 4 -.IX Item "-mrtd" -Use a different function-calling convention, in which functions -that take a fixed number of arguments return pop their -arguments on return with the \f(CW\*(C`ret\*(C'\fR instruction. -.Sp -This calling convention is incompatible with the one normally -used on Unix, so you cannot use it if you need to call libraries -compiled with the Unix compiler. -.Sp -Also, you must provide function prototypes for all functions that -take variable numbers of arguments (including \f(CW\*(C`printf\*(C'\fR); -otherwise incorrect code will be generated for calls to those -functions. -.Sp -In addition, seriously incorrect code will result if you call a -function with too many arguments. (Normally, extra arguments are -harmlessly ignored.) -.Sp -This option takes its name from the 680x0 \f(CW\*(C`rtd\*(C'\fR instruction. -.Ip "\fB\-mregparam\fR" 4 -.IX Item "-mregparam" -Use a different function-calling convention where the first two arguments -are passed in registers. -.Sp -This calling convention is incompatible with the one normally -used on Unix, so you cannot use it if you need to call libraries -compiled with the Unix compiler. -.Ip "\fB\-mnoregparam\fR" 4 -.IX Item "-mnoregparam" -Do not pass any arguments in registers. This is the default for all -targets. -.Ip "\fB\-msb\fR" 4 -.IX Item "-msb" -It is \s-1OK\s0 to use the sb as an index register which is always loaded with -zero. This is the default for the pc532\-netbsd target. -.Ip "\fB\-mnosb\fR" 4 -.IX Item "-mnosb" -The sb register is not available for use or has not been initialized to -zero by the run time system. This is the default for all targets except -the pc532\-netbsd. It is also implied whenever \fB\-mhimem\fR or -\&\fB\-fpic\fR is set. -.Ip "\fB\-mhimem\fR" 4 -.IX Item "-mhimem" -Many ns32000 series addressing modes use displacements of up to 512MB. -If an address is above 512MB then displacements from zero can not be used. -This option causes code to be generated which can be loaded above 512MB. -This may be useful for operating systems or \s-1ROM\s0 code. -.Ip "\fB\-mnohimem\fR" 4 -.IX Item "-mnohimem" -Assume code will be loaded in the first 512MB of virtual address space. -This is the default for all platforms. -.PP -.I "\s-1AVR\s0 Options" -.IX Subsection "AVR Options" -.PP -These options are defined for \s-1AVR\s0 implementations: -.Ip "\fB\-mmcu=\fR\fImcu\fR" 4 -.IX Item "-mmcu=mcu" -Specify \s-1ATMEL\s0 \s-1AVR\s0 instruction set or \s-1MCU\s0 type. -.Sp -Instruction set avr1 is for the minimal \s-1AVR\s0 core, not supported by the C -compiler, only for assembler programs (\s-1MCU\s0 types: at90s1200, attiny10, -attiny11, attiny12, attiny15, attiny28). -.Sp -Instruction set avr2 (default) is for the classic \s-1AVR\s0 core with up to -8K program memory space (\s-1MCU\s0 types: at90s2313, at90s2323, attiny22, -at90s2333, at90s2343, at90s4414, at90s4433, at90s4434, at90s8515, -at90c8534, at90s8535). -.Sp -Instruction set avr3 is for the classic \s-1AVR\s0 core with up to 128K program -memory space (\s-1MCU\s0 types: atmega103, atmega603, at43usb320, at76c711). -.Sp -Instruction set avr4 is for the enhanced \s-1AVR\s0 core with up to 8K program -memory space (\s-1MCU\s0 types: atmega8, atmega83, atmega85). -.Sp -Instruction set avr5 is for the enhanced \s-1AVR\s0 core with up to 128K program -memory space (\s-1MCU\s0 types: atmega16, atmega161, atmega163, atmega32, atmega323, -atmega64, atmega128, at43usb355, at94k). -.Ip "\fB\-msize\fR" 4 -.IX Item "-msize" -Output instruction sizes to the asm file. -.Ip "\fB\-minit-stack=\fR\fIN\fR" 4 -.IX Item "-minit-stack=N" -Specify the initial stack address, which may be a symbol or numeric value, -\&\fB_\|_stack\fR is the default. -.Ip "\fB\-mno-interrupts\fR" 4 -.IX Item "-mno-interrupts" -Generated code is not compatible with hardware interrupts. -Code size will be smaller. -.Ip "\fB\-mcall-prologues\fR" 4 -.IX Item "-mcall-prologues" -Functions prologues/epilogues expanded as call to appropriate -subroutines. Code size will be smaller. -.Ip "\fB\-mno-tablejump\fR" 4 -.IX Item "-mno-tablejump" -Do not generate tablejump insns which sometimes increase code size. -.Ip "\fB\-mtiny-stack\fR" 4 -.IX Item "-mtiny-stack" -Change only the low 8 bits of the stack pointer. -.PP -.I "MCore Options" -.IX Subsection "MCore Options" -.PP -These are the \fB\-m\fR options defined for the Motorola M*Core -processors. -.Ip "\fB\-mhardlit\fR" 4 -.IX Item "-mhardlit" -.PD 0 -.Ip "\fB\-mhardlit\fR" 4 -.IX Item "-mhardlit" -.Ip "\fB\-mno-hardlit\fR" 4 -.IX Item "-mno-hardlit" -.PD -Inline constants into the code stream if it can be done in two -instructions or less. -.Ip "\fB\-mdiv\fR" 4 -.IX Item "-mdiv" -.PD 0 -.Ip "\fB\-mdiv\fR" 4 -.IX Item "-mdiv" -.Ip "\fB\-mno-div\fR" 4 -.IX Item "-mno-div" -.PD -Use the divide instruction. (Enabled by default). -.Ip "\fB\-mrelax-immediate\fR" 4 -.IX Item "-mrelax-immediate" -.PD 0 -.Ip "\fB\-mrelax-immediate\fR" 4 -.IX Item "-mrelax-immediate" -.Ip "\fB\-mno-relax-immediate\fR" 4 -.IX Item "-mno-relax-immediate" -.PD -Allow arbitrary sized immediates in bit operations. -.Ip "\fB\-mwide-bitfields\fR" 4 -.IX Item "-mwide-bitfields" -.PD 0 -.Ip "\fB\-mwide-bitfields\fR" 4 -.IX Item "-mwide-bitfields" -.Ip "\fB\-mno-wide-bitfields\fR" 4 -.IX Item "-mno-wide-bitfields" -.PD -Always treat bit-fields as int-sized. -.Ip "\fB\-m4byte-functions\fR" 4 -.IX Item "-m4byte-functions" -.PD 0 -.Ip "\fB\-m4byte-functions\fR" 4 -.IX Item "-m4byte-functions" -.Ip "\fB\-mno-4byte-functions\fR" 4 -.IX Item "-mno-4byte-functions" -.PD -Force all functions to be aligned to a four byte boundary. -.Ip "\fB\-mcallgraph-data\fR" 4 -.IX Item "-mcallgraph-data" -.PD 0 -.Ip "\fB\-mcallgraph-data\fR" 4 -.IX Item "-mcallgraph-data" -.Ip "\fB\-mno-callgraph-data\fR" 4 -.IX Item "-mno-callgraph-data" -.PD -Emit callgraph information. -.Ip "\fB\-mslow-bytes\fR" 4 -.IX Item "-mslow-bytes" -.PD 0 -.Ip "\fB\-mslow-bytes\fR" 4 -.IX Item "-mslow-bytes" -.Ip "\fB\-mno-slow-bytes\fR" 4 -.IX Item "-mno-slow-bytes" -.PD -Prefer word access when reading byte quantities. -.Ip "\fB\-mlittle-endian\fR" 4 -.IX Item "-mlittle-endian" -.PD 0 -.Ip "\fB\-mlittle-endian\fR" 4 -.IX Item "-mlittle-endian" -.Ip "\fB\-mbig-endian\fR" 4 -.IX Item "-mbig-endian" -.PD -Generate code for a little endian target. -.Ip "\fB\-m210\fR" 4 -.IX Item "-m210" -.PD 0 -.Ip "\fB\-m210\fR" 4 -.IX Item "-m210" -.Ip "\fB\-m340\fR" 4 -.IX Item "-m340" -.PD -Generate code for the 210 processor. -.PP -.I "\s-1IA-64\s0 Options" -.IX Subsection "IA-64 Options" -.PP -These are the \fB\-m\fR options defined for the Intel \s-1IA-64\s0 architecture. -.Ip "\fB\-mbig-endian\fR" 4 -.IX Item "-mbig-endian" -Generate code for a big endian target. This is the default for \s-1HPUX\s0. -.Ip "\fB\-mlittle-endian\fR" 4 -.IX Item "-mlittle-endian" -Generate code for a little endian target. This is the default for \s-1AIX5\s0 -and Linux. -.Ip "\fB\-mgnu-as\fR" 4 -.IX Item "-mgnu-as" -.PD 0 -.Ip "\fB\-mno-gnu-as\fR" 4 -.IX Item "-mno-gnu-as" -.PD -Generate (or don't) code for the \s-1GNU\s0 assembler. This is the default. -.Ip "\fB\-mgnu-ld\fR" 4 -.IX Item "-mgnu-ld" -.PD 0 -.Ip "\fB\-mno-gnu-ld\fR" 4 -.IX Item "-mno-gnu-ld" -.PD -Generate (or don't) code for the \s-1GNU\s0 linker. This is the default. -.Ip "\fB\-mno-pic\fR" 4 -.IX Item "-mno-pic" -Generate code that does not use a global pointer register. The result -is not position independent code, and violates the \s-1IA-64\s0 \s-1ABI\s0. -.Ip "\fB\-mvolatile-asm-stop\fR" 4 -.IX Item "-mvolatile-asm-stop" -.PD 0 -.Ip "\fB\-mno-volatile-asm-stop\fR" 4 -.IX Item "-mno-volatile-asm-stop" -.PD -Generate (or don't) a stop bit immediately before and after volatile asm -statements. -.Ip "\fB\-mb-step\fR" 4 -.IX Item "-mb-step" -Generate code that works around Itanium B step errata. -.Ip "\fB\-mregister-names\fR" 4 -.IX Item "-mregister-names" -.PD 0 -.Ip "\fB\-mno-register-names\fR" 4 -.IX Item "-mno-register-names" -.PD -Generate (or don't) \fBin\fR, \fBloc\fR, and \fBout\fR register names for -the stacked registers. This may make assembler output more readable. -.Ip "\fB\-mno-sdata\fR" 4 -.IX Item "-mno-sdata" -.PD 0 -.Ip "\fB\-msdata\fR" 4 -.IX Item "-msdata" -.PD -Disable (or enable) optimizations that use the small data section. This may -be useful for working around optimizer bugs. -.Ip "\fB\-mconstant-gp\fR" 4 -.IX Item "-mconstant-gp" -Generate code that uses a single constant global pointer value. This is -useful when compiling kernel code. -.Ip "\fB\-mauto-pic\fR" 4 -.IX Item "-mauto-pic" -Generate code that is self-relocatable. This implies \fB\-mconstant-gp\fR. -This is useful when compiling firmware code. -.Ip "\fB\-minline-divide-min-latency\fR" 4 -.IX Item "-minline-divide-min-latency" -Generate code for inline divides using the minimum latency algorithm. -.Ip "\fB\-minline-divide-max-throughput\fR" 4 -.IX Item "-minline-divide-max-throughput" -Generate code for inline divides using the maximum throughput algorithm. -.Ip "\fB\-mno-dwarf2\-asm\fR" 4 -.IX Item "-mno-dwarf2-asm" -.PD 0 -.Ip "\fB\-mdwarf2\-asm\fR" 4 -.IX Item "-mdwarf2-asm" -.PD -Don't (or do) generate assembler code for the \s-1DWARF2\s0 line number debugging -info. This may be useful when not using the \s-1GNU\s0 assembler. -.Ip "\fB\-mfixed-range=\fR\fIregister-range\fR" 4 -.IX Item "-mfixed-range=register-range" -Generate code treating the given register range as fixed registers. -A fixed register is one that the register allocator can not use. This is -useful when compiling kernel code. A register range is specified as -two registers separated by a dash. Multiple register ranges can be -specified separated by a comma. -.PP -.I "D30V Options" -.IX Subsection "D30V Options" -.PP -These \fB\-m\fR options are defined for D30V implementations: -.Ip "\fB\-mextmem\fR" 4 -.IX Item "-mextmem" -Link the \fB.text\fR, \fB.data\fR, \fB.bss\fR, \fB.strings\fR, -\&\fB.rodata\fR, \fB.rodata1\fR, \fB.data1\fR sections into external -memory, which starts at location \f(CW\*(C`0x80000000\*(C'\fR. -.Ip "\fB\-mextmemory\fR" 4 -.IX Item "-mextmemory" -Same as the \fB\-mextmem\fR switch. -.Ip "\fB\-monchip\fR" 4 -.IX Item "-monchip" -Link the \fB.text\fR section into onchip text memory, which starts at -location \f(CW\*(C`0x0\*(C'\fR. Also link \fB.data\fR, \fB.bss\fR, -\&\fB.strings\fR, \fB.rodata\fR, \fB.rodata1\fR, \fB.data1\fR sections -into onchip data memory, which starts at location \f(CW\*(C`0x20000000\*(C'\fR. -.Ip "\fB\-mno-asm-optimize\fR" 4 -.IX Item "-mno-asm-optimize" -.PD 0 -.Ip "\fB\-masm-optimize\fR" 4 -.IX Item "-masm-optimize" -.PD -Disable (enable) passing \fB\-O\fR to the assembler when optimizing. -The assembler uses the \fB\-O\fR option to automatically parallelize -adjacent short instructions where possible. -.Ip "\fB\-mbranch-cost=\fR\fIn\fR" 4 -.IX Item "-mbranch-cost=n" -Increase the internal costs of branches to \fIn\fR. Higher costs means -that the compiler will issue more instructions to avoid doing a branch. -The default is 2. -.Ip "\fB\-mcond-exec=\fR\fIn\fR" 4 -.IX Item "-mcond-exec=n" -Specify the maximum number of conditionally executed instructions that -replace a branch. The default is 4. -.PP -.I "S/390 and zSeries Options" -.IX Subsection "S/390 and zSeries Options" -.PP -These are the \fB\-m\fR options defined for the S/390 and zSeries architecture. -.Ip "\fB\-mhard-float\fR" 4 -.IX Item "-mhard-float" -.PD 0 -.Ip "\fB\-msoft-float\fR" 4 -.IX Item "-msoft-float" -.PD -Use (do not use) the hardware floating-point instructions and registers -for floating-point operations. When \fB\-msoft-float\fR is specified, -functions in \fIlibgcc.a\fR will be used to perform floating-point -operations. When \fB\-mhard-float\fR is specified, the compiler -generates \s-1IEEE\s0 floating-point instructions. This is the default. -.Ip "\fB\-mbackchain\fR" 4 -.IX Item "-mbackchain" -.PD 0 -.Ip "\fB\-mno-backchain\fR" 4 -.IX Item "-mno-backchain" -.PD -Generate (or do not generate) code which maintains an explicit -backchain within the stack frame that points to the caller's frame. -This is currently needed to allow debugging. The default is to -generate the backchain. -.Ip "\fB\-msmall-exec\fR" 4 -.IX Item "-msmall-exec" -.PD 0 -.Ip "\fB\-mno-small-exec\fR" 4 -.IX Item "-mno-small-exec" -.PD -Generate (or do not generate) code using the \f(CW\*(C`bras\*(C'\fR instruction -to do subroutine calls. -This only works reliably if the total executable size does not -exceed 64k. The default is to use the \f(CW\*(C`basr\*(C'\fR instruction instead, -which does not have this limitation. -.Ip "\fB\-m64\fR" 4 -.IX Item "-m64" -.PD 0 -.Ip "\fB\-m31\fR" 4 -.IX Item "-m31" -.PD -When \fB\-m31\fR is specified, generate code compliant to the -Linux for S/390 \s-1ABI\s0. When \fB\-m64\fR is specified, generate -code compliant to the Linux for zSeries \s-1ABI\s0. This allows \s-1GCC\s0 in -particular to generate 64\-bit instructions. For the \fBs390\fR -targets, the default is \fB\-m31\fR, while the \fBs390x\fR -targets default to \fB\-m64\fR. -.Ip "\fB\-mmvcle\fR" 4 -.IX Item "-mmvcle" -.PD 0 -.Ip "\fB\-mno-mvcle\fR" 4 -.IX Item "-mno-mvcle" -.PD -Generate (or do not generate) code using the \f(CW\*(C`mvcle\*(C'\fR instruction -to perform block moves. When \fB\-mno-mvcle\fR is specifed, -use a \f(CW\*(C`mvc\*(C'\fR loop instead. This is the default. -.Ip "\fB\-mdebug\fR" 4 -.IX Item "-mdebug" -.PD 0 -.Ip "\fB\-mno-debug\fR" 4 -.IX Item "-mno-debug" -.PD -Print (or do not print) additional debug information when compiling. -The default is to not print debug information. -.PP -.I "\s-1CRIS\s0 Options" -.IX Subsection "CRIS Options" -.PP -These options are defined specifically for the \s-1CRIS\s0 ports. -.Ip "\fB\-march=\fR\fIarchitecture-type\fR" 4 -.IX Item "-march=architecture-type" -.PD 0 -.Ip "\fB\-mcpu=\fR\fIarchitecture-type\fR" 4 -.IX Item "-mcpu=architecture-type" -.PD -Generate code for the specified architecture. The choices for -\&\fIarchitecture-type\fR are \fBv3\fR, \fBv8\fR and \fBv10\fR for -respectively \s-1ETRAX\s0\ 4, \s-1ETRAX\s0\ 100, and \s-1ETRAX\s0\ 100\ \s-1LX\s0. -Default is \fBv0\fR except for cris-axis-linux-gnu, where the default is -\&\fBv10\fR. -.Ip "\fB\-mtune=\fR\fIarchitecture-type\fR" 4 -.IX Item "-mtune=architecture-type" -Tune to \fIarchitecture-type\fR everything applicable about the generated -code, except for the \s-1ABI\s0 and the set of available instructions. The -choices for \fIarchitecture-type\fR are the same as for -\&\fB\-march=\fR\fIarchitecture-type\fR. -.Ip "\fB\-mmax-stack-frame=\fR\fIn\fR" 4 -.IX Item "-mmax-stack-frame=n" -Warn when the stack frame of a function exceeds \fIn\fR bytes. -.Ip "\fB\-melinux-stacksize=\fR\fIn\fR" 4 -.IX Item "-melinux-stacksize=n" -Only available with the \fBcris-axis-aout\fR target. Arranges for -indications in the program to the kernel loader that the stack of the -program should be set to \fIn\fR bytes. -.Ip "\fB\-metrax4\fR" 4 -.IX Item "-metrax4" -.PD 0 -.Ip "\fB\-metrax100\fR" 4 -.IX Item "-metrax100" -.PD -The options \fB\-metrax4\fR and \fB\-metrax100\fR are synonyms for -\&\fB\-march=v3\fR and \fB\-march=v8\fR respectively. -.Ip "\fB\-mpdebug\fR" 4 -.IX Item "-mpdebug" -Enable CRIS-specific verbose debug-related information in the assembly -code. This option also has the effect to turn off the \fB#NO_APP\fR -formatted-code indicator to the assembler at the beginning of the -assembly file. -.Ip "\fB\-mcc-init\fR" 4 -.IX Item "-mcc-init" -Do not use condition-code results from previous instruction; always emit -compare and test instructions before use of condition codes. -.Ip "\fB\-mno-side-effects\fR" 4 -.IX Item "-mno-side-effects" -Do not emit instructions with side-effects in addressing modes other than -post-increment. -.Ip "\fB\-mstack-align\fR" 4 -.IX Item "-mstack-align" -.PD 0 -.Ip "\fB\-mno-stack-align\fR" 4 -.IX Item "-mno-stack-align" -.Ip "\fB\-mdata-align\fR" 4 -.IX Item "-mdata-align" -.Ip "\fB\-mno-data-align\fR" 4 -.IX Item "-mno-data-align" -.Ip "\fB\-mconst-align\fR" 4 -.IX Item "-mconst-align" -.Ip "\fB\-mno-const-align\fR" 4 -.IX Item "-mno-const-align" -.PD -These options (no-options) arranges (eliminate arrangements) for the -stack-frame, individual data and constants to be aligned for the maximum -single data access size for the chosen \s-1CPU\s0 model. The default is to -arrange for 32\-bit alignment. \s-1ABI\s0 details such as structure layout are -not affected by these options. -.Ip "\fB\-m32\-bit\fR" 4 -.IX Item "-m32-bit" -.PD 0 -.Ip "\fB\-m16\-bit\fR" 4 -.IX Item "-m16-bit" -.Ip "\fB\-m8\-bit\fR" 4 -.IX Item "-m8-bit" -.PD -Similar to the stack- data- and const-align options above, these options -arrange for stack-frame, writable data and constants to all be 32\-bit, -16\-bit or 8\-bit aligned. The default is 32\-bit alignment. -.Ip "\fB\-mno-prologue-epilogue\fR" 4 -.IX Item "-mno-prologue-epilogue" -.PD 0 -.Ip "\fB\-mprologue-epilogue\fR" 4 -.IX Item "-mprologue-epilogue" -.PD -With \fB\-mno-prologue-epilogue\fR, the normal function prologue and -epilogue that sets up the stack-frame are omitted and no return -instructions or return sequences are generated in the code. Use this -option only together with visual inspection of the compiled code: no -warnings or errors are generated when call-saved registers must be saved, -or storage for local variable needs to be allocated. -.Ip "\fB\-mno-gotplt\fR" 4 -.IX Item "-mno-gotplt" -.PD 0 -.Ip "\fB\-mgotplt\fR" 4 -.IX Item "-mgotplt" -.PD -With \fB\-fpic\fR and \fB\-fPIC\fR, don't generate (do generate) -instruction sequences that load addresses for functions from the \s-1PLT\s0 part -of the \s-1GOT\s0 rather than (traditional on other architectures) calls to the -\&\s-1PLT\s0. The default is \fB\-mgotplt\fR. -.Ip "\fB\-maout\fR" 4 -.IX Item "-maout" -Legacy no-op option only recognized with the cris-axis-aout target. -.Ip "\fB\-melf\fR" 4 -.IX Item "-melf" -Legacy no-op option only recognized with the cris-axis-elf and -cris-axis-linux-gnu targets. -.Ip "\fB\-melinux\fR" 4 -.IX Item "-melinux" -Only recognized with the cris-axis-aout target, where it selects a -GNU/linux-like multilib, include files and instruction set for -\&\fB\-march=v8\fR. -.Ip "\fB\-mlinux\fR" 4 -.IX Item "-mlinux" -Legacy no-op option only recognized with the cris-axis-linux-gnu target. -.Ip "\fB\-sim\fR" 4 -.IX Item "-sim" -This option, recognized for the cris-axis-aout and cris-axis-elf arranges -to link with input-output functions from a simulator library. Code, -initialized data and zero-initialized data are allocated consecutively. -.Ip "\fB\-sim2\fR" 4 -.IX Item "-sim2" -Like \fB\-sim\fR, but pass linker options to locate initialized data at -0x40000000 and zero-initialized data at 0x80000000. -.PP -.I "\s-1MMIX\s0 Options" -.IX Subsection "MMIX Options" -.PP -These options are defined for the \s-1MMIX:\s0 -.Ip "\fB\-mlibfuncs\fR" 4 -.IX Item "-mlibfuncs" -.PD 0 -.Ip "\fB\-mno-libfuncs\fR" 4 -.IX Item "-mno-libfuncs" -.PD -Specify that intrinsic library functions are being compiled, passing all -values in registers, no matter the size. -.Ip "\fB\-mepsilon\fR" 4 -.IX Item "-mepsilon" -.PD 0 -.Ip "\fB\-mno-epsilon\fR" 4 -.IX Item "-mno-epsilon" -.PD -Generate floating-point comparison instructions that compare with respect -to the \f(CW\*(C`rE\*(C'\fR epsilon register. -.Ip "\fB\-mabi=mmixware\fR" 4 -.IX Item "-mabi=mmixware" -.PD 0 -.Ip "\fB\-mabi=gnu\fR" 4 -.IX Item "-mabi=gnu" -.PD -Generate code that passes function parameters and return values that (in -the called function) are seen as registers \f(CW\*(C`$0\*(C'\fR and up, as opposed to -the \s-1GNU\s0 \s-1ABI\s0 which uses global registers \f(CW\*(C`$231\*(C'\fR and up. -.Ip "\fB\-mzero-extend\fR" 4 -.IX Item "-mzero-extend" -.PD 0 -.Ip "\fB\-mno-zero-extend\fR" 4 -.IX Item "-mno-zero-extend" -.PD -When reading data from memory in sizes shorter than 64 bits, use (do not -use) zero-extending load instructions by default, rather than -sign-extending ones. -.Ip "\fB\-mknuthdiv\fR" 4 -.IX Item "-mknuthdiv" -.PD 0 -.Ip "\fB\-mno-knuthdiv\fR" 4 -.IX Item "-mno-knuthdiv" -.PD -Make the result of a division yielding a remainder have the same sign as -the divisor. With the default, \fB\-mno-knuthdiv\fR, the sign of the -remainder follows the sign of the dividend. Both methods are -arithmetically valid, the latter being almost exclusively used. -.Ip "\fB\-mtoplevel-symbols\fR" 4 -.IX Item "-mtoplevel-symbols" -.PD 0 -.Ip "\fB\-mno-toplevel-symbols\fR" 4 -.IX Item "-mno-toplevel-symbols" -.PD -Prepend (do not prepend) a \fB:\fR to all global symbols, so the assembly -code can be used with the \f(CW\*(C`PREFIX\*(C'\fR assembly directive. -.Ip "\fB\-melf\fR" 4 -.IX Item "-melf" -Generate an executable in the \s-1ELF\s0 format, rather than the default -\&\fBmmo\fR format used by the \fBmmix\fR simulator. -.Ip "\fB\-mbranch-predict\fR" 4 -.IX Item "-mbranch-predict" -.PD 0 -.Ip "\fB\-mno-branch-predict\fR" 4 -.IX Item "-mno-branch-predict" -.PD -Use (do not use) the probable-branch instructions, when static branch -prediction indicates a probable branch. -.Ip "\fB\-mbase-addresses\fR" 4 -.IX Item "-mbase-addresses" -.PD 0 -.Ip "\fB\-mno-base-addresses\fR" 4 -.IX Item "-mno-base-addresses" -.PD -Generate (do not generate) code that uses \fIbase addresses\fR. Using a -base address automatically generates a request (handled by the assembler -and the linker) for a constant to be set up in a global register. The -register is used for one or more base address requests within the range 0 -to 255 from the value held in the register. The generally leads to short -and fast code, but the number of different data items that can be -addressed is limited. This means that a program that uses lots of static -data may require \fB\-mno-base-addresses\fR. -.PP -.I "\s-1PDP-11\s0 Options" -.IX Subsection "PDP-11 Options" -.PP -These options are defined for the \s-1PDP-11:\s0 -.Ip "\fB\-mfpu\fR" 4 -.IX Item "-mfpu" -Use hardware \s-1FPP\s0 floating point. This is the default. (\s-1FIS\s0 floating -point on the \s-1PDP-11/40\s0 is not supported.) -.Ip "\fB\-msoft-float\fR" 4 -.IX Item "-msoft-float" -Do not use hardware floating point. -.Ip "\fB\-mac0\fR" 4 -.IX Item "-mac0" -Return floating-point results in ac0 (fr0 in Unix assembler syntax). -.Ip "\fB\-mno-ac0\fR" 4 -.IX Item "-mno-ac0" -Return floating-point results in memory. This is the default. -.Ip "\fB\-m40\fR" 4 -.IX Item "-m40" -Generate code for a \s-1PDP-11/40\s0. -.Ip "\fB\-m45\fR" 4 -.IX Item "-m45" -Generate code for a \s-1PDP-11/45\s0. This is the default. -.Ip "\fB\-m10\fR" 4 -.IX Item "-m10" -Generate code for a \s-1PDP-11/10\s0. -.Ip "\fB\-mbcopy-builtin\fR" 4 -.IX Item "-mbcopy-builtin" -Use inline \f(CW\*(C`movstrhi\*(C'\fR patterns for copying memory. This is the -default. -.Ip "\fB\-mbcopy\fR" 4 -.IX Item "-mbcopy" -Do not use inline \f(CW\*(C`movstrhi\*(C'\fR patterns for copying memory. -.Ip "\fB\-mint16\fR" 4 -.IX Item "-mint16" -.PD 0 -.Ip "\fB\-mno-int32\fR" 4 -.IX Item "-mno-int32" -.PD -Use 16\-bit \f(CW\*(C`int\*(C'\fR. This is the default. -.Ip "\fB\-mint32\fR" 4 -.IX Item "-mint32" -.PD 0 -.Ip "\fB\-mno-int16\fR" 4 -.IX Item "-mno-int16" -.PD -Use 32\-bit \f(CW\*(C`int\*(C'\fR. -.Ip "\fB\-mfloat64\fR" 4 -.IX Item "-mfloat64" -.PD 0 -.Ip "\fB\-mno-float32\fR" 4 -.IX Item "-mno-float32" -.PD -Use 64\-bit \f(CW\*(C`float\*(C'\fR. This is the default. -.Ip "\fB\-mfloat32\fR" 4 -.IX Item "-mfloat32" -.PD 0 -.Ip "\fB\-mno-float64\fR" 4 -.IX Item "-mno-float64" -.PD -Use 32\-bit \f(CW\*(C`float\*(C'\fR. -.Ip "\fB\-mabshi\fR" 4 -.IX Item "-mabshi" -Use \f(CW\*(C`abshi2\*(C'\fR pattern. This is the default. -.Ip "\fB\-mno-abshi\fR" 4 -.IX Item "-mno-abshi" -Do not use \f(CW\*(C`abshi2\*(C'\fR pattern. -.Ip "\fB\-mbranch-expensive\fR" 4 -.IX Item "-mbranch-expensive" -Pretend that branches are expensive. This is for experimenting with -code generation only. -.Ip "\fB\-mbranch-cheap\fR" 4 -.IX Item "-mbranch-cheap" -Do not pretend that branches are expensive. This is the default. -.Ip "\fB\-msplit\fR" 4 -.IX Item "-msplit" -Generate code for a system with split I&D. -.Ip "\fB\-mno-split\fR" 4 -.IX Item "-mno-split" -Generate code for a system without split I&D. This is the default. -.Ip "\fB\-munix-asm\fR" 4 -.IX Item "-munix-asm" -Use Unix assembler syntax. This is the default when configured for -\&\fBpdp11\-*\-bsd\fR. -.Ip "\fB\-mdec-asm\fR" 4 -.IX Item "-mdec-asm" -Use \s-1DEC\s0 assembler syntax. This is the default when configured for any -\&\s-1PDP-11\s0 target other than \fBpdp11\-*\-bsd\fR. -.PP -.I "Xstormy16 Options" -.IX Subsection "Xstormy16 Options" -.PP -These options are defined for Xstormy16: -.Ip "\fB\-msim\fR" 4 -.IX Item "-msim" -Choose startup files and linker script suitable for the simulator. -.PP -.I "Xtensa Options" -.IX Subsection "Xtensa Options" -.PP -The Xtensa architecture is designed to support many different -configurations. The compiler's default options can be set to match a -particular Xtensa configuration by copying a configuration file into the -\&\s-1GCC\s0 sources when building \s-1GCC\s0. The options below may be used to -override the default options. -.Ip "\fB\-mbig-endian\fR" 4 -.IX Item "-mbig-endian" -.PD 0 -.Ip "\fB\-mlittle-endian\fR" 4 -.IX Item "-mlittle-endian" -.PD -Specify big-endian or little-endian byte ordering for the target Xtensa -processor. -.Ip "\fB\-mdensity\fR" 4 -.IX Item "-mdensity" -.PD 0 -.Ip "\fB\-mno-density\fR" 4 -.IX Item "-mno-density" -.PD -Enable or disable use of the optional Xtensa code density instructions. -.Ip "\fB\-mmac16\fR" 4 -.IX Item "-mmac16" -.PD 0 -.Ip "\fB\-mno-mac16\fR" 4 -.IX Item "-mno-mac16" -.PD -Enable or disable use of the Xtensa \s-1MAC16\s0 option. When enabled, \s-1GCC\s0 -will generate \s-1MAC16\s0 instructions from standard C code, with the -limitation that it will use neither the \s-1MR\s0 register file nor any -instruction that operates on the \s-1MR\s0 registers. When this option is -disabled, \s-1GCC\s0 will translate 16\-bit multiply/accumulate operations to a -combination of core instructions and library calls, depending on whether -any other multiplier options are enabled. -.Ip "\fB\-mmul16\fR" 4 -.IX Item "-mmul16" -.PD 0 -.Ip "\fB\-mno-mul16\fR" 4 -.IX Item "-mno-mul16" -.PD -Enable or disable use of the 16\-bit integer multiplier option. When -enabled, the compiler will generate 16\-bit multiply instructions for -multiplications of 16 bits or smaller in standard C code. When this -option is disabled, the compiler will either use 32\-bit multiply or -\&\s-1MAC16\s0 instructions if they are available or generate library calls to -perform the multiply operations using shifts and adds. -.Ip "\fB\-mmul32\fR" 4 -.IX Item "-mmul32" -.PD 0 -.Ip "\fB\-mno-mul32\fR" 4 -.IX Item "-mno-mul32" -.PD -Enable or disable use of the 32\-bit integer multiplier option. When -enabled, the compiler will generate 32\-bit multiply instructions for -multiplications of 32 bits or smaller in standard C code. When this -option is disabled, the compiler will generate library calls to perform -the multiply operations using either shifts and adds or 16\-bit multiply -instructions if they are available. -.Ip "\fB\-mnsa\fR" 4 -.IX Item "-mnsa" -.PD 0 -.Ip "\fB\-mno-nsa\fR" 4 -.IX Item "-mno-nsa" -.PD -Enable or disable use of the optional normalization shift amount -(\f(CW\*(C`NSA\*(C'\fR) instructions to implement the built-in \f(CW\*(C`ffs\*(C'\fR function. -.Ip "\fB\-mminmax\fR" 4 -.IX Item "-mminmax" -.PD 0 -.Ip "\fB\-mno-minmax\fR" 4 -.IX Item "-mno-minmax" -.PD -Enable or disable use of the optional minimum and maximum value -instructions. -.Ip "\fB\-msext\fR" 4 -.IX Item "-msext" -.PD 0 -.Ip "\fB\-mno-sext\fR" 4 -.IX Item "-mno-sext" -.PD -Enable or disable use of the optional sign extend (\f(CW\*(C`SEXT\*(C'\fR) -instruction. -.Ip "\fB\-mbooleans\fR" 4 -.IX Item "-mbooleans" -.PD 0 -.Ip "\fB\-mno-booleans\fR" 4 -.IX Item "-mno-booleans" -.PD -Enable or disable support for the boolean register file used by Xtensa -coprocessors. This is not typically useful by itself but may be -required for other options that make use of the boolean registers (e.g., -the floating-point option). -.Ip "\fB\-mhard-float\fR" 4 -.IX Item "-mhard-float" -.PD 0 -.Ip "\fB\-msoft-float\fR" 4 -.IX Item "-msoft-float" -.PD -Enable or disable use of the floating-point option. When enabled, \s-1GCC\s0 -generates floating-point instructions for 32\-bit \f(CW\*(C`float\*(C'\fR -operations. When this option is disabled, \s-1GCC\s0 generates library calls -to emulate 32\-bit floating-point operations using integer instructions. -Regardless of this option, 64\-bit \f(CW\*(C`double\*(C'\fR operations are always -emulated with calls to library functions. -.Ip "\fB\-mfused-madd\fR" 4 -.IX Item "-mfused-madd" -.PD 0 -.Ip "\fB\-mno-fused-madd\fR" 4 -.IX Item "-mno-fused-madd" -.PD -Enable or disable use of fused multiply/add and multiply/subtract -instructions in the floating-point option. This has no effect if the -floating-point option is not also enabled. Disabling fused multiply/add -and multiply/subtract instructions forces the compiler to use separate -instructions for the multiply and add/subtract operations. This may be -desirable in some cases where strict \s-1IEEE\s0 754\-compliant results are -required: the fused multiply add/subtract instructions do not round the -intermediate result, thereby producing results with \fImore\fR bits of -precision than specified by the \s-1IEEE\s0 standard. Disabling fused multiply -add/subtract instructions also ensures that the program output is not -sensitive to the compiler's ability to combine multiply and add/subtract -operations. -.Ip "\fB\-mserialize-volatile\fR" 4 -.IX Item "-mserialize-volatile" -.PD 0 -.Ip "\fB\-mno-serialize-volatile\fR" 4 -.IX Item "-mno-serialize-volatile" -.PD -When this option is enabled, \s-1GCC\s0 inserts \f(CW\*(C`MEMW\*(C'\fR instructions before -\&\f(CW\*(C`volatile\*(C'\fR memory references to guarantee sequential consistency. -The default is \fB\-mserialize-volatile\fR. Use -\&\fB\-mno-serialize-volatile\fR to omit the \f(CW\*(C`MEMW\*(C'\fR instructions. -.Ip "\fB\-mtext-section-literals\fR" 4 -.IX Item "-mtext-section-literals" -.PD 0 -.Ip "\fB\-mno-text-section-literals\fR" 4 -.IX Item "-mno-text-section-literals" -.PD -Control the treatment of literal pools. The default is -\&\fB\-mno-text-section-literals\fR, which places literals in a separate -section in the output file. This allows the literal pool to be placed -in a data \s-1RAM/ROM\s0, and it also allows the linker to combine literal -pools from separate object files to remove redundant literals and -improve code size. With \fB\-mtext-section-literals\fR, the literals -are interspersed in the text section in order to keep them as close as -possible to their references. This may be necessary for large assembly -files. -.Ip "\fB\-mtarget-align\fR" 4 -.IX Item "-mtarget-align" -.PD 0 -.Ip "\fB\-mno-target-align\fR" 4 -.IX Item "-mno-target-align" -.PD -When this option is enabled, \s-1GCC\s0 instructs the assembler to -automatically align instructions to reduce branch penalties at the -expense of some code density. The assembler attempts to widen density -instructions to align branch targets and the instructions following call -instructions. If there are not enough preceding safe density -instructions to align a target, no widening will be performed. The -default is \fB\-mtarget-align\fR. These options do not affect the -treatment of auto-aligned instructions like \f(CW\*(C`LOOP\*(C'\fR, which the -assembler will always align, either by widening density instructions or -by inserting no-op instructions. -.Ip "\fB\-mlongcalls\fR" 4 -.IX Item "-mlongcalls" -.PD 0 -.Ip "\fB\-mno-longcalls\fR" 4 -.IX Item "-mno-longcalls" -.PD -When this option is enabled, \s-1GCC\s0 instructs the assembler to translate -direct calls to indirect calls unless it can determine that the target -of a direct call is in the range allowed by the call instruction. This -translation typically occurs for calls to functions in other source -files. Specifically, the assembler translates a direct \f(CW\*(C`CALL\*(C'\fR -instruction into an \f(CW\*(C`L32R\*(C'\fR followed by a \f(CW\*(C`CALLX\*(C'\fR instruction. -The default is \fB\-mno-longcalls\fR. This option should be used in -programs where the call target can potentially be out of range. This -option is implemented in the assembler, not the compiler, so the -assembly code generated by \s-1GCC\s0 will still show direct call -instructions\-\-\-look at the disassembled object code to see the actual -instructions. Note that the assembler will use an indirect call for -every cross-file call, not just those that really will be out of range. -.Sh "Options for Code Generation Conventions" -.IX Subsection "Options for Code Generation Conventions" -These machine-independent options control the interface conventions -used in code generation. -.PP -Most of them have both positive and negative forms; the negative form -of \fB\-ffoo\fR would be \fB\-fno-foo\fR. In the table below, only -one of the forms is listed\-\-\-the one which is not the default. You -can figure out the other form by either removing \fBno-\fR or adding -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-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-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 -properly with exception handlers written in \*(C+. You may also wish to -disable this option if you are compiling older \*(C+ programs that don't -use exception handling. -.Ip "\fB\-fnon-call-exceptions\fR" 4 -.IX Item "-fnon-call-exceptions" -Generate code that allows trapping instructions to throw exceptions. -Note that this requires platform-specific runtime support that does -not exist everywhere. Moreover, it only allows \fItrapping\fR -instructions to throw exceptions, i.e. memory references or floating -point instructions. It does not allow exceptions to be thrown from -arbitrary signal handlers such as \f(CW\*(C`SIGALRM\*(C'\fR. -.Ip "\fB\-funwind-tables\fR" 4 -.IX Item "-funwind-tables" -Similar to \fB\-fexceptions\fR, except that it will just generate any needed -static data, but will not affect the generated code in any other way. -You will normally not enable this option; instead, a language processor -that needs this handling would enable it on your behalf. -.Ip "\fB\-fasynchronous-unwind-tables\fR" 4 -.IX Item "-fasynchronous-unwind-tables" -Generate unwind table in dwarf2 format, if supported by target machine. The -table is exact at each instruction boundary, so it can be used for stack -unwinding from asynchronous events (such as debugger or garbage collector). -.Ip "\fB\-fpcc-struct-return\fR" 4 -.IX Item "-fpcc-struct-return" -Return ``short'' \f(CW\*(C`struct\*(C'\fR and \f(CW\*(C`union\*(C'\fR values in memory like -longer ones, rather than in registers. This convention is less -efficient, but it has the advantage of allowing intercallability between -GCC-compiled files and files compiled with other compilers, particularly -the Portable C Compiler (pcc). -.Sp -The precise convention for returning structures in memory depends -on the target configuration macros. -.Sp -Short structures and unions are those whose size and alignment match -that of some integer type. -.Sp -\&\fBWarning:\fR code compiled with the \fB\-fpcc-struct-return\fR -switch is not binary compatible with code compiled with the -\&\fB\-freg-struct-return\fR switch. -Use it to conform to a non-default application binary interface. -.Ip "\fB\-freg-struct-return\fR" 4 -.IX Item "-freg-struct-return" -Return \f(CW\*(C`struct\*(C'\fR and \f(CW\*(C`union\*(C'\fR values in registers when possible. -This is more efficient for small structures than -\&\fB\-fpcc-struct-return\fR. -.Sp -If you specify neither \fB\-fpcc-struct-return\fR nor -\&\fB\-freg-struct-return\fR, \s-1GCC\s0 defaults to whichever convention is -standard for the target. If there is no standard convention, \s-1GCC\s0 -defaults to \fB\-fpcc-struct-return\fR, except on targets where \s-1GCC\s0 is -the principal compiler. In those cases, we can choose the standard, and -we chose the more efficient register return alternative. -.Sp -\&\fBWarning:\fR code compiled with the \fB\-freg-struct-return\fR -switch is not binary compatible with code compiled with the -\&\fB\-fpcc-struct-return\fR switch. -Use it to conform to a non-default application binary interface. -.Ip "\fB\-fshort-enums\fR" 4 -.IX Item "-fshort-enums" -Allocate to an \f(CW\*(C`enum\*(C'\fR type only as many bytes as it needs for the -declared range of possible values. Specifically, the \f(CW\*(C`enum\*(C'\fR type -will be equivalent to the smallest integer type which has enough room. -.Sp -\&\fBWarning:\fR the \fB\-fshort-enums\fR switch causes \s-1GCC\s0 to generate -code that is not binary compatible with code generated without that switch. -Use it to conform to a non-default application binary interface. -.Ip "\fB\-fshort-double\fR" 4 -.IX Item "-fshort-double" -Use the same size for \f(CW\*(C`double\*(C'\fR as for \f(CW\*(C`float\*(C'\fR. -.Sp -\&\fBWarning:\fR the \fB\-fshort-double\fR switch causes \s-1GCC\s0 to generate -code that is not binary compatible with code generated without that switch. -Use it to conform to a non-default application binary interface. -.Ip "\fB\-fshort-wchar\fR" 4 -.IX Item "-fshort-wchar" -Override the underlying type for \fBwchar_t\fR to be \fBshort -unsigned int\fR instead of the default for the target. This option is -useful for building programs to run under \s-1WINE\s0. -.Sp -\&\fBWarning:\fR the \fB\-fshort-wchar\fR switch causes \s-1GCC\s0 to generate -code that is not binary compatible with code generated without that switch. -Use it to conform to a non-default application binary interface. -.Ip "\fB\-fshared-data\fR" 4 -.IX Item "-fshared-data" -Requests that the data and non-\f(CW\*(C`const\*(C'\fR variables of this -compilation be shared data rather than private data. The distinction -makes sense only on certain operating systems, where shared data is -shared between processes running the same program, while private data -exists in one copy per process. -.Ip "\fB\-fno-common\fR" 4 -.IX Item "-fno-common" -In C, allocate even uninitialized global variables in the data section of the -object file, rather than generating them as common blocks. This has the -effect that if the same variable is declared (without \f(CW\*(C`extern\*(C'\fR) in -two different compilations, you will get an error when you link them. -The only reason this might be useful is if you wish to verify that the -program will work on other systems which always work this way. -.Ip "\fB\-fno-ident\fR" 4 -.IX Item "-fno-ident" -Ignore the \fB#ident\fR directive. -.Ip "\fB\-fno-gnu-linker\fR" 4 -.IX Item "-fno-gnu-linker" -Do not output global initializations (such as \*(C+ constructors and -destructors) in the form used by the \s-1GNU\s0 linker (on systems where the \s-1GNU\s0 -linker is the standard method of handling them). Use this option when -you want to use a non-GNU linker, which also requires using the -\&\fBcollect2\fR program to make sure the system linker includes -constructors and destructors. (\fBcollect2\fR is included in the \s-1GCC\s0 -distribution.) For systems which \fImust\fR use \fBcollect2\fR, the -compiler driver \fBgcc\fR is configured to do this automatically. -.Ip "\fB\-finhibit-size-directive\fR" 4 -.IX Item "-finhibit-size-directive" -Don't output a \f(CW\*(C`.size\*(C'\fR assembler directive, or anything else that -would cause trouble if the function is split in the middle, and the -two halves are placed at locations far apart in memory. This option is -used when compiling \fIcrtstuff.c\fR; you should not need to use it -for anything else. -.Ip "\fB\-fverbose-asm\fR" 4 -.IX Item "-fverbose-asm" -Put extra commentary information in the generated assembly code to -make it more readable. This option is generally only of use to those -who actually need to read the generated assembly code (perhaps while -debugging the compiler itself). -.Sp -\&\fB\-fno-verbose-asm\fR, the default, causes the -extra information to be omitted and is useful when comparing two assembler -files. -.Ip "\fB\-fvolatile\fR" 4 -.IX Item "-fvolatile" -Consider all memory references through pointers to be volatile. -.Ip "\fB\-fvolatile-global\fR" 4 -.IX Item "-fvolatile-global" -Consider all memory references to extern and global data items to -be volatile. \s-1GCC\s0 does not consider static data items to be volatile -because of this switch. -.Ip "\fB\-fvolatile-static\fR" 4 -.IX Item "-fvolatile-static" -Consider all memory references to static data to be volatile. -.Ip "\fB\-fpic\fR" 4 -.IX Item "-fpic" -Generate position-independent code (\s-1PIC\s0) suitable for use in a shared -library, if supported for the target machine. Such code accesses all -constant addresses through a global offset table (\s-1GOT\s0). The dynamic -loader resolves the \s-1GOT\s0 entries when the program starts (the dynamic -loader is not part of \s-1GCC\s0; it is part of the operating system). If -the \s-1GOT\s0 size for the linked executable exceeds a machine-specific -maximum size, you get an error message from the linker indicating that -\&\fB\-fpic\fR does not work; in that case, recompile with \fB\-fPIC\fR -instead. (These maximums are 16k on the m88k, 8k on the Sparc, and 32k -on the m68k and \s-1RS/6000\s0. The 386 has no such limit.) -.Sp -Position-independent code requires special support, and therefore works -only on certain machines. For the 386, \s-1GCC\s0 supports \s-1PIC\s0 for System V -but not for the Sun 386i. Code generated for the \s-1IBM\s0 \s-1RS/6000\s0 is always -position-independent. -.Ip "\fB\-fPIC\fR" 4 -.IX Item "-fPIC" -If supported for the target machine, emit position-independent code, -suitable for dynamic linking and avoiding any limit on the size of the -global offset table. This option makes a difference on the m68k, m88k, -and the Sparc. -.Sp -Position-independent code requires special support, and therefore works -only on certain machines. -.Ip "\fB\-ffixed-\fR\fIreg\fR" 4 -.IX Item "-ffixed-reg" -Treat the register named \fIreg\fR as a fixed register; generated code -should never refer to it (except perhaps as a stack pointer, frame -pointer or in some other fixed role). -.Sp -\&\fIreg\fR must be the name of a register. The register names accepted -are machine-specific and are defined in the \f(CW\*(C`REGISTER_NAMES\*(C'\fR -macro in the machine description macro file. -.Sp -This flag does not have a negative form, because it specifies a -three-way choice. -.Ip "\fB\-fcall-used-\fR\fIreg\fR" 4 -.IX Item "-fcall-used-reg" -Treat the register named \fIreg\fR as an allocable register that is -clobbered by function calls. It may be allocated for temporaries or -variables that do not live across a call. Functions compiled this way -will not save and restore the register \fIreg\fR. -.Sp -It is an error to used this flag with the frame pointer or stack pointer. -Use of this flag for other registers that have fixed pervasive roles in -the machine's execution model will produce disastrous results. -.Sp -This flag does not have a negative form, because it specifies a -three-way choice. -.Ip "\fB\-fcall-saved-\fR\fIreg\fR" 4 -.IX Item "-fcall-saved-reg" -Treat the register named \fIreg\fR as an allocable register saved by -functions. It may be allocated even for temporaries or variables that -live across a call. Functions compiled this way will save and restore -the register \fIreg\fR if they use it. -.Sp -It is an error to used this flag with the frame pointer or stack pointer. -Use of this flag for other registers that have fixed pervasive roles in -the machine's execution model will produce disastrous results. -.Sp -A different sort of disaster will result from the use of this flag for -a register in which function values may be returned. -.Sp -This flag does not have a negative form, because it specifies a -three-way choice. -.Ip "\fB\-fpack-struct\fR" 4 -.IX Item "-fpack-struct" -Pack all structure members together without holes. -.Sp -\&\fBWarning:\fR the \fB\-fpack-struct\fR switch causes \s-1GCC\s0 to generate -code that is not binary compatible with code generated without that switch. -Additionally, it makes the code suboptimial. -Use it to conform to a non-default application binary interface. -.Ip "\fB\-finstrument-functions\fR" 4 -.IX Item "-finstrument-functions" -Generate instrumentation calls for entry and exit to functions. Just -after function entry and just before function exit, the following -profiling functions will be called with the address of the current -function and its call site. (On some platforms, -\&\f(CW\*(C`_\|_builtin_return_address\*(C'\fR does not work beyond the current -function, so the call site information may not be available to the -profiling functions otherwise.) -.Sp -.Vb 4 -\& void __cyg_profile_func_enter (void *this_fn, -\& void *call_site); -\& void __cyg_profile_func_exit (void *this_fn, -\& void *call_site); -.Ve -The first argument is the address of the start of the current function, -which may be looked up exactly in the symbol table. -.Sp -This instrumentation is also done for functions expanded inline in other -functions. The profiling calls will indicate where, conceptually, the -inline function is entered and exited. This means that addressable -versions of such functions must be available. If all your uses of a -function are expanded inline, this may mean an additional expansion of -code size. If you use \fBextern inline\fR in your C code, an -addressable version of such functions must be provided. (This is -normally the case anyways, but if you get lucky and the optimizer always -expands the functions inline, you might have gotten away without -providing static copies.) -.Sp -A function may be given the attribute \f(CW\*(C`no_instrument_function\*(C'\fR, in -which case this instrumentation will not be done. This can be used, for -example, for the profiling functions listed above, high-priority -interrupt routines, and any functions from which the profiling functions -cannot safely be called (perhaps signal handlers, if the profiling -routines generate output or allocate memory). -.Ip "\fB\-fstack-check\fR" 4 -.IX Item "-fstack-check" -Generate code to verify that you do not go beyond the boundary of the -stack. You should specify this flag if you are running in an -environment with multiple threads, but only rarely need to specify it in -a single-threaded environment since stack overflow is automatically -detected on nearly all systems if there is only one stack. -.Sp -Note that this switch does not actually cause checking to be done; the -operating system must do that. The switch causes generation of code -to ensure that the operating system sees the stack being extended. -.Ip "\fB\-fstack-limit-register=\fR\fIreg\fR" 4 -.IX Item "-fstack-limit-register=reg" -.PD 0 -.Ip "\fB\-fstack-limit-symbol=\fR\fIsym\fR" 4 -.IX Item "-fstack-limit-symbol=sym" -.Ip "\fB\-fno-stack-limit\fR" 4 -.IX Item "-fno-stack-limit" -.PD -Generate code to ensure that the stack does not grow beyond a certain value, -either the value of a register or the address of a symbol. If the stack -would grow beyond the value, a signal is raised. For most targets, -the signal is raised before the stack overruns the boundary, so -it is possible to catch the signal without taking special precautions. -.Sp -For instance, if the stack starts at absolute address \fB0x80000000\fR -and grows downwards, you can use the flags -\&\fB\-fstack-limit-symbol=_\|_stack_limit\fR and -\&\fB\-Wl,\-\-defsym,_\|_stack_limit=0x7ffe0000\fR to enforce a stack limit -of 128KB. Note that this may only work with the \s-1GNU\s0 linker. -.Ip "\fB\-fargument-alias\fR" 4 -.IX Item "-fargument-alias" -.PD 0 -.Ip "\fB\-fargument-noalias\fR" 4 -.IX Item "-fargument-noalias" -.Ip "\fB\-fargument-noalias-global\fR" 4 -.IX Item "-fargument-noalias-global" -.PD -Specify the possible relationships among parameters and between -parameters and global data. -.Sp -\&\fB\-fargument-alias\fR specifies that arguments (parameters) may -alias each other and may alias global storage.\fB\-fargument-noalias\fR specifies that arguments do not alias -each other, but may alias global storage.\fB\-fargument-noalias-global\fR specifies that arguments do not -alias each other and do not alias global storage. -.Sp -Each language will automatically use whatever option is required by -the language standard. You should not need to use these options yourself. -.Ip "\fB\-fleading-underscore\fR" 4 -.IX Item "-fleading-underscore" -This option and its counterpart, \fB\-fno-leading-underscore\fR, forcibly -change the way C symbols are represented in the object file. One use -is to help link with legacy assembly code. -.Sp -\&\fBWarning:\fR the \fB\-fleading-underscore\fR switch causes \s-1GCC\s0 to -generate code that is not binary compatible with code generated without that -switch. Use it to conform to a non-default application binary interface. -Not all targets provide complete support for this switch. -.SH "ENVIRONMENT" -.IX Header "ENVIRONMENT" -This section describes several environment variables that affect how \s-1GCC\s0 -operates. Some of them work by specifying directories or prefixes to use -when searching for various kinds of files. Some are used to specify other -aspects of the compilation environment. -.PP -Note that you can also specify places to search using options such as -\&\fB\-B\fR, \fB\-I\fR and \fB\-L\fR. These -take precedence over places specified using environment variables, which -in turn take precedence over those specified by the configuration of \s-1GCC\s0. -.Ip "\fB\s-1LANG\s0\fR" 4 -.IX Item "LANG" -.PD 0 -.Ip "\fB\s-1LC_CTYPE\s0\fR" 4 -.IX Item "LC_CTYPE" -.Ip "\fB\s-1LC_MESSAGES\s0\fR" 4 -.IX Item "LC_MESSAGES" -.Ip "\fB\s-1LC_ALL\s0\fR" 4 -.IX Item "LC_ALL" -.PD -These environment variables control the way that \s-1GCC\s0 uses -localization information that allow \s-1GCC\s0 to work with different -national conventions. \s-1GCC\s0 inspects the locale categories -\&\fB\s-1LC_CTYPE\s0\fR and \fB\s-1LC_MESSAGES\s0\fR if it has been configured to do -so. These locale categories can be set to any value supported by your -installation. A typical value is \fBen_UK\fR for English in the United -Kingdom. -.Sp -The \fB\s-1LC_CTYPE\s0\fR environment variable specifies character -classification. \s-1GCC\s0 uses it to determine the character boundaries in -a string; this is needed for some multibyte encodings that contain quote -and escape characters that would otherwise be interpreted as a string -end or escape. -.Sp -The \fB\s-1LC_MESSAGES\s0\fR environment variable specifies the language to -use in diagnostic messages. -.Sp -If the \fB\s-1LC_ALL\s0\fR environment variable is set, it overrides the value -of \fB\s-1LC_CTYPE\s0\fR and \fB\s-1LC_MESSAGES\s0\fR; otherwise, \fB\s-1LC_CTYPE\s0\fR -and \fB\s-1LC_MESSAGES\s0\fR default to the value of the \fB\s-1LANG\s0\fR -environment variable. If none of these variables are set, \s-1GCC\s0 -defaults to traditional C English behavior. -.Ip "\fB\s-1TMPDIR\s0\fR" 4 -.IX Item "TMPDIR" -If \fB\s-1TMPDIR\s0\fR is set, it specifies the directory to use for temporary -files. \s-1GCC\s0 uses temporary files to hold the output of one stage of -compilation which is to be used as input to the next stage: for example, -the output of the preprocessor, which is the input to the compiler -proper. -.Ip "\fB\s-1GCC_EXEC_PREFIX\s0\fR" 4 -.IX Item "GCC_EXEC_PREFIX" -If \fB\s-1GCC_EXEC_PREFIX\s0\fR is set, it specifies a prefix to use in the -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-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 -tries looking in the usual places for the subprogram. -.Sp -The default value of \fB\s-1GCC_EXEC_PREFIX\s0\fR is -\&\fI\fIprefix\fI/lib/gcc-lib/\fR where \fIprefix\fR is the value -of \f(CW\*(C`prefix\*(C'\fR when you ran the \fIconfigure\fR script. -.Sp -Other prefixes specified with \fB\-B\fR take precedence over this prefix. -.Sp -This prefix is also used for finding files such as \fIcrt0.o\fR that are -used for linking. -.Sp -In addition, the prefix is used in an unusual way in finding the -directories to search for header files. For each of the standard -directories whose name normally begins with \fB/usr/local/lib/gcc-lib\fR -(more precisely, with the value of \fB\s-1GCC_INCLUDE_DIR\s0\fR), \s-1GCC\s0 tries -replacing that beginning with the specified prefix to produce an -alternate directory name. Thus, with \fB\-Bfoo/\fR, \s-1GCC\s0 will search -\&\fIfoo/bar\fR where it would normally search \fI/usr/local/lib/bar\fR. -These alternate directories are searched first; the standard directories -come next. -.Ip "\fB\s-1COMPILER_PATH\s0\fR" 4 -.IX Item "COMPILER_PATH" -The value of \fB\s-1COMPILER_PATH\s0\fR is a colon-separated list of -directories, much like \fB\s-1PATH\s0\fR. \s-1GCC\s0 tries the directories thus -specified when searching for subprograms, if it can't find the -subprograms using \fB\s-1GCC_EXEC_PREFIX\s0\fR. -.Ip "\fB\s-1LIBRARY_PATH\s0\fR" 4 -.IX Item "LIBRARY_PATH" -The value of \fB\s-1LIBRARY_PATH\s0\fR is a colon-separated list of -directories, much like \fB\s-1PATH\s0\fR. When configured as a native compiler, -\&\s-1GCC\s0 tries the directories thus specified when searching for special -linker files, if it can't find them using \fB\s-1GCC_EXEC_PREFIX\s0\fR. Linking -using \s-1GCC\s0 also uses these directories when searching for ordinary -libraries for the \fB\-l\fR option (but directories specified with -\&\fB\-L\fR come first). -.Ip "\fB\s-1LANG\s0\fR" 4 -.IX Item "LANG" -This variable is used to pass locale information to the compiler. One way in -which this information is used is to determine the character set to be used -when character literals, string literals and comments are parsed in C and \*(C+. -When the compiler is configured to allow multibyte characters, -the following values for \fB\s-1LANG\s0\fR are recognized: -.RS 4 -.Ip "\fBC-JIS\fR" 4 -.IX Item "C-JIS" -Recognize \s-1JIS\s0 characters. -.Ip "\fBC-SJIS\fR" 4 -.IX Item "C-SJIS" -Recognize \s-1SJIS\s0 characters. -.Ip "\fBC-EUCJP\fR" 4 -.IX Item "C-EUCJP" -Recognize \s-1EUCJP\s0 characters. -.RE -.RS 4 -.Sp -If \fB\s-1LANG\s0\fR is not defined, or if it has some other value, then the -compiler will use mblen and mbtowc as defined by the default locale to -recognize and translate multibyte characters. -.RE -.PP -Some additional environments variables affect the behavior of the -preprocessor. -.Ip "\fB\s-1CPATH\s0\fR" 4 -.IX Item "CPATH" -.PD 0 -.Ip "\fBC_INCLUDE_PATH\fR" 4 -.IX Item "C_INCLUDE_PATH" -.Ip "\fB\s-1CPLUS_INCLUDE_PATH\s0\fR" 4 -.IX Item "CPLUS_INCLUDE_PATH" -.Ip "\fB\s-1OBJC_INCLUDE_PATH\s0\fR" 4 -.IX Item "OBJC_INCLUDE_PATH" -.PD -Each variable's value is a list of directories separated by a special -character, much like \fB\s-1PATH\s0\fR, in which to look for header files. -The special character, \f(CW\*(C`PATH_SEPARATOR\*(C'\fR, is target-dependent and -determined at \s-1GCC\s0 build time. For Windows-based targets it is a -semicolon, and for almost all other targets it is a colon. -.Sp -\&\fB\s-1CPATH\s0\fR specifies a list of directories to be searched as if -specified with \fB\-I\fR, but after any paths given with \fB\-I\fR -options on the command line. The environment variable is used -regardless of which language is being preprocessed. -.Sp -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 \fB\-isystem\fR, but after any -paths given with \fB\-isystem\fR options on the command line. -.Ip "\fB\s-1DEPENDENCIES_OUTPUT\s0\fR" 4 -.IX Item "DEPENDENCIES_OUTPUT" -@anchor{\s-1DEPENDENCIES_OUTPUT\s0} -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. -.Sp -The value of \fB\s-1DEPENDENCIES_OUTPUT\s0\fR 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 -\&\fIfile\fR\fB \fR\fItarget\fR, in which case the rules are written to -file \fIfile\fR using \fItarget\fR as the target name. -.Sp -In other words, this environment variable is equivalent to combining -the options \fB\-MM\fR and \fB\-MF\fR, -with an optional \fB\-MT\fR switch too. -.Ip "\fB\s-1SUNPRO_DEPENDENCIES\s0\fR" 4 -.IX Item "SUNPRO_DEPENDENCIES" -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. -.SH "BUGS" -.IX Header "BUGS" -For instructions on reporting bugs, see -<\fBhttp://gcc.gnu.org/bugs.html\fR>. Use of the \fBgccbug\fR -script to report bugs is recommended. -.SH "FOOTNOTES" -.IX Header "FOOTNOTES" -.Ip "1." 4 -On some systems, \fBgcc \-shared\fR -needs to build supplementary stub code for constructors to work. On -multi-libbed systems, \fBgcc \-shared\fR must select the correct support -libraries to link against. Failing to supply the correct flags may lead -to subtle defects. Supplying them in cases where they are not necessary -is innocuous. -.SH "SEE ALSO" -.IX Header "SEE ALSO" -\&\fIgpl\fR\|(7), \fIgfdl\fR\|(7), \fIfsf-funding\fR\|(7), -\&\fIcpp\fR\|(1), \fIgcov\fR\|(1), \fIg77\fR\|(1), \fIas\fR\|(1), \fIld\fR\|(1), \fIgdb\fR\|(1), \fIadb\fR\|(1), \fIdbx\fR\|(1), \fIsdb\fR\|(1) -and the Info entries for \fIgcc\fR, \fIcpp\fR, \fIg77\fR, \fIas\fR, -\&\fIld\fR, \fIbinutils\fR and \fIgdb\fR. -.SH "AUTHOR" -.IX Header "AUTHOR" -See the Info entry for \fBgcc\fR, or -<\fBhttp://gcc.gnu.org/onlinedocs/gcc/Contributors.html\fR>, -for contributors to \s-1GCC\s0. -.SH "COPYRIGHT" -.IX Header "COPYRIGHT" -Copyright (c) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, -1998, 1999, 2000, 2001, 2002, 2003 Free Software Foundation, Inc. -.PP -Permission is granted to copy, distribute and/or modify this document -under the terms of the \s-1GNU\s0 Free Documentation License, Version 1.1 or -any later version published by the Free Software Foundation; with the -Invariant Sections being ``\s-1GNU\s0 General Public License'' and ``Funding -Free Software'', the Front-Cover texts being (a) (see below), and with -the Back-Cover Texts being (b) (see below). A copy of the license is -included in the \fIgfdl\fR\|(7) man page. -.PP -(a) The \s-1FSF\s0's Front-Cover Text is: -.PP -.Vb 1 -\& A GNU Manual -.Ve -(b) The \s-1FSF\s0's Back-Cover Text is: -.PP -.Vb 3 -\& 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. -.Ve diff --git a/contrib/gcc/doc/gcov.1 b/contrib/gcc/doc/gcov.1 deleted file mode 100644 index 44d1e33c8b74..000000000000 --- a/contrib/gcc/doc/gcov.1 +++ /dev/null @@ -1,453 +0,0 @@ -.\" Automatically generated by Pod::Man version 1.15 -.\" Wed Feb 5 03:13:55 2003 -.\" -.\" Standard preamble: -.\" ====================================================================== -.de Sh \" Subsection heading -.br -.if t .Sp -.ne 5 -.PP -\fB\\$1\fR -.PP -.. -.de Sp \" Vertical space (when we can't use .PP) -.if t .sp .5v -.if n .sp -.. -.de Ip \" List item -.br -.ie \\n(.$>=3 .ne \\$3 -.el .ne 3 -.IP "\\$1" \\$2 -.. -.de Vb \" Begin verbatim text -.ft CW -.nf -.ne \\$1 -.. -.de Ve \" End verbatim text -.ft R - -.fi -.. -.\" Set up some character translations and predefined strings. \*(-- will -.\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left -.\" double quote, and \*(R" will give a right double quote. | will give a -.\" 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<> -.tr \(*W-|\(bv\*(Tr -.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p' -.ie n \{\ -. ds -- \(*W- -. ds PI pi -. if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch -. if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch -. ds L" "" -. ds R" "" -. ds C` "" -. ds C' "" -'br\} -.el\{\ -. ds -- \|\(em\| -. ds PI \(*p -. ds L" `` -. ds R" '' -'br\} -.\" -.\" 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 \nF \{\ -. de IX -. tm Index:\\$1\t\\n%\t"\\$2" -.. -. nr % 0 -. rr F -.\} -.\" -.\" For nroff, turn off justification. Always turn off hyphenation; it -.\" makes way too many mistakes in technical documents. -.hy 0 -.if n .na -.\" -.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). -.\" Fear. Run. Save yourself. No user-serviceable parts. -.bd B 3 -. \" fudge factors for nroff and troff -.if n \{\ -. ds #H 0 -. ds #V .8m -. ds #F .3m -. ds #[ \f1 -. ds #] \fP -.\} -.if t \{\ -. ds #H ((1u-(\\\\n(.fu%2u))*.13m) -. ds #V .6m -. ds #F 0 -. ds #[ \& -. ds #] \& -.\} -. \" simple accents for nroff and troff -.if n \{\ -. ds ' \& -. ds ` \& -. ds ^ \& -. ds , \& -. ds ~ ~ -. ds / -.\} -.if t \{\ -. ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u" -. ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u' -. ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u' -. ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u' -. ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u' -. ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u' -.\} -. \" troff and (daisy-wheel) nroff accents -.ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V' -.ds 8 \h'\*(#H'\(*b\h'-\*(#H' -.ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#] -.ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H' -.ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u' -.ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#] -.ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#] -.ds ae a\h'-(\w'a'u*4/10)'e -.ds Ae A\h'-(\w'A'u*4/10)'E -. \" corrections for vroff -.if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u' -.if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u' -. \" for low resolution devices (crt and lpr) -.if \n(.H>23 .if \n(.V>19 \ -\{\ -. ds : e -. ds 8 ss -. ds o a -. ds d- d\h'-1'\(ga -. ds D- D\h'-1'\(hy -. ds th \o'bp' -. ds Th \o'LP' -. ds ae ae -. ds Ae AE -.\} -.rm #[ #] #H #V #F C -.\" ====================================================================== -.\" -.IX Title "GCOV 1" -.TH GCOV 1 "gcc-3.2.2" "2003-02-05" "GNU" -.UC -.SH "NAME" -gcov \- coverage testing tool -.SH "SYNOPSIS" -.IX Header "SYNOPSIS" -gcov [\fB\-v\fR|\fB\*(--version\fR] [\fB\-h\fR|\fB\*(--help\fR] - [\fB\-b\fR|\fB\*(--branch-probabilities\fR] [\fB\-c\fR|\fB\*(--branch-counts\fR] - [\fB\-n\fR|\fB\*(--no-output\fR] [\fB\-l\fR|\fB\*(--long-file-names\fR] - [\fB\-f\fR|\fB\*(--function-summaries\fR] - [\fB\-o\fR|\fB\*(--object-directory\fR \fIdirectory\fR] \fIsourcefile\fR -.SH "DESCRIPTION" -.IX Header "DESCRIPTION" -\&\fBgcov\fR is a test coverage program. Use it in concert with \s-1GCC\s0 -to analyze your programs to help create more efficient, faster -running code. You can use \fBgcov\fR as a profiling tool to help -discover where your optimization efforts will best affect your code. You -can also use \fBgcov\fR along with the other profiling tool, -\&\fBgprof\fR, to assess which parts of your code use the greatest amount -of computing time. -.PP -Profiling tools help you analyze your code's performance. Using a -profiler such as \fBgcov\fR or \fBgprof\fR, you can find out some -basic performance statistics, such as: -.Ip "\(bu" 4 -how often each line of code executes -.Ip "\(bu" 4 -what lines of code are actually executed -.Ip "\(bu" 4 -how much computing time each section of code uses -.PP -Once you know these things about how your code works when compiled, you -can look at each module to see which modules should be optimized. -\&\fBgcov\fR helps you determine where to work on optimization. -.PP -Software developers also use coverage testing in concert with -testsuites, to make sure software is actually good enough for a release. -Testsuites can verify that a program works as expected; a coverage -program tests to see how much of the program is exercised by the -testsuite. Developers can then determine what kinds of test cases need -to be added to the testsuites to create both better testing and a better -final product. -.PP -You should compile your code without optimization if you plan to use -\&\fBgcov\fR because the optimization, by combining some lines of code -into one function, may not give you as much information as you need to -look for `hot spots' where the code is using a great deal of computer -time. Likewise, because \fBgcov\fR accumulates statistics by line (at -the lowest resolution), it works best with a programming style that -places only one statement on each line. If you use complicated macros -that expand to loops or to other control structures, the statistics are -less helpful\-\-\-they only report on the line where the macro call -appears. If your complex macros behave like functions, you can replace -them with inline functions to solve this problem. -.PP -\&\fBgcov\fR creates a logfile called \fI\fIsourcefile\fI.gcov\fR which -indicates how many times each line of a source file \fI\fIsourcefile\fI.c\fR -has executed. You can use these logfiles along with \fBgprof\fR to aid -in fine-tuning the performance of your programs. \fBgprof\fR gives -timing information you can use along with the information you get from -\&\fBgcov\fR. -.PP -\&\fBgcov\fR works only on code compiled with \s-1GCC\s0. It is not -compatible with any other profiling or test coverage mechanism. -.SH "OPTIONS" -.IX Header "OPTIONS" -.Ip "\fB\-h\fR" 4 -.IX Item "-h" -.PD 0 -.Ip "\fB\*(--help\fR" 4 -.IX Item "help" -.PD -Display help about using \fBgcov\fR (on the standard output), and -exit without doing any further processing. -.Ip "\fB\-v\fR" 4 -.IX Item "-v" -.PD 0 -.Ip "\fB\*(--version\fR" 4 -.IX Item "version" -.PD -Display the \fBgcov\fR version number (on the standard output), -and exit without doing any further processing. -.Ip "\fB\-b\fR" 4 -.IX Item "-b" -.PD 0 -.Ip "\fB\*(--branch-probabilities\fR" 4 -.IX Item "branch-probabilities" -.PD -Write branch frequencies to the output file, and write branch summary -info to the standard output. This option allows you to see how often -each branch in your program was taken. -.Ip "\fB\-c\fR" 4 -.IX Item "-c" -.PD 0 -.Ip "\fB\*(--branch-counts\fR" 4 -.IX Item "branch-counts" -.PD -Write branch frequencies as the number of branches taken, rather than -the percentage of branches taken. -.Ip "\fB\-n\fR" 4 -.IX Item "-n" -.PD 0 -.Ip "\fB\*(--no-output\fR" 4 -.IX Item "no-output" -.PD -Do not create the \fBgcov\fR output file. -.Ip "\fB\-l\fR" 4 -.IX Item "-l" -.PD 0 -.Ip "\fB\*(--long-file-names\fR" 4 -.IX Item "long-file-names" -.PD -Create long file names for included source files. For example, if the -header file \fIx.h\fR contains code, and was included in the file -\&\fIa.c\fR, then running \fBgcov\fR on the file \fIa.c\fR will produce -an output file called \fIa.c.x.h.gcov\fR instead of \fIx.h.gcov\fR. -This can be useful if \fIx.h\fR is included in multiple source files. -.Ip "\fB\-f\fR" 4 -.IX Item "-f" -.PD 0 -.Ip "\fB\*(--function-summaries\fR" 4 -.IX Item "function-summaries" -.PD -Output summaries for each function in addition to the file level summary. -.Ip "\fB\-o\fR \fIdirectory\fR" 4 -.IX Item "-o directory" -.PD 0 -.Ip "\fB\*(--object-directory\fR \fIdirectory\fR" 4 -.IX Item "object-directory directory" -.PD -The directory where the object files live. Gcov will search for \fI.bb\fR, -\&\fI.bbg\fR, and \fI.da\fR files in this directory. -.PP -When using \fBgcov\fR, you must first compile your program with two -special \s-1GCC\s0 options: \fB\-fprofile-arcs \-ftest-coverage\fR. -This tells the compiler to generate additional information needed by -gcov (basically a flow graph of the program) and also includes -additional code in the object files for generating the extra profiling -information needed by gcov. These additional files are placed in the -directory where the source code is located. -.PP -Running the program will cause profile output to be generated. For each -source file compiled with \fB\-fprofile-arcs\fR, an accompanying \fI.da\fR -file will be placed in the source directory. -.PP -Running \fBgcov\fR with your program's source file names as arguments -will now produce a listing of the code along with frequency of execution -for each line. For example, if your program is called \fItmp.c\fR, this -is what you see when you use the basic \fBgcov\fR facility: -.PP -.Vb 5 -\& $ gcc -fprofile-arcs -ftest-coverage tmp.c -\& $ a.out -\& $ gcov tmp.c -\& 87.50% of 8 source lines executed in file tmp.c -\& Creating tmp.c.gcov. -.Ve -The file \fItmp.c.gcov\fR contains output from \fBgcov\fR. -Here is a sample: -.PP -.Vb 3 -\& main() -\& { -\& 1 int i, total; -.Ve -.Vb 1 -\& 1 total = 0; -.Ve -.Vb 2 -\& 11 for (i = 0; i < 10; i++) -\& 10 total += i; -.Ve -.Vb 5 -\& 1 if (total != 45) -\& ###### printf ("Failure\en"); -\& else -\& 1 printf ("Success\en"); -\& 1 } -.Ve -When you use the \fB\-b\fR option, your output looks like this: -.PP -.Vb 6 -\& $ gcov -b tmp.c -\& 87.50% of 8 source lines executed in file tmp.c -\& 80.00% of 5 branches executed in file tmp.c -\& 80.00% of 5 branches taken at least once in file tmp.c -\& 50.00% of 2 calls executed in file tmp.c -\& Creating tmp.c.gcov. -.Ve -Here is a sample of a resulting \fItmp.c.gcov\fR file: -.PP -.Vb 3 -\& main() -\& { -\& 1 int i, total; -.Ve -.Vb 1 -\& 1 total = 0; -.Ve -.Vb 5 -\& 11 for (i = 0; i < 10; i++) -\& branch 0 taken = 91% -\& branch 1 taken = 100% -\& branch 2 taken = 100% -\& 10 total += i; -.Ve -.Vb 9 -\& 1 if (total != 45) -\& branch 0 taken = 100% -\& ###### printf ("Failure\en"); -\& call 0 never executed -\& branch 1 never executed -\& else -\& 1 printf ("Success\en"); -\& call 0 returns = 100% -\& 1 } -.Ve -For each basic block, a line is printed after the last line of the basic -block describing the branch or call that ends the basic block. There can -be multiple branches and calls listed for a single source line if there -are multiple basic blocks that end on that line. In this case, the -branches and calls are each given a number. There is no simple way to map -these branches and calls back to source constructs. In general, though, -the lowest numbered branch or call will correspond to the leftmost construct -on the source line. -.PP -For a branch, if it was executed at least once, then a percentage -indicating the number of times the branch was taken divided by the -number of times the branch was executed will be printed. Otherwise, the -message ``never executed'' is printed. -.PP -For a call, if it was executed at least once, then a percentage -indicating the number of times the call returned divided by the number -of times the call was executed will be printed. This will usually be -100%, but may be less for functions call \f(CW\*(C`exit\*(C'\fR or \f(CW\*(C`longjmp\*(C'\fR, -and thus may not return every time they are called. -.PP -The execution counts are cumulative. If the example program were -executed again without removing the \fI.da\fR file, the count for the -number of times each line in the source was executed would be added to -the results of the previous \fIrun\fR\|(s). This is potentially useful in -several ways. For example, it could be used to accumulate data over a -number of program runs as part of a test verification suite, or to -provide more accurate long-term information over a large number of -program runs. -.PP -The data in the \fI.da\fR files is saved immediately before the program -exits. For each source file compiled with \fB\-fprofile-arcs\fR, the profiling -code first attempts to read in an existing \fI.da\fR file; if the file -doesn't match the executable (differing number of basic block counts) it -will ignore the contents of the file. It then adds in the new execution -counts and finally writes the data to the file. -.Sh "Using \fBgcov\fP with \s-1GCC\s0 Optimization" -.IX Subsection "Using gcov with GCC Optimization" -If you plan to use \fBgcov\fR to help optimize your code, you must -first compile your program with two special \s-1GCC\s0 options: -\&\fB\-fprofile-arcs \-ftest-coverage\fR. Aside from that, you can use any -other \s-1GCC\s0 options; but if you want to prove that every single line -in your program was executed, you should not compile with optimization -at the same time. On some machines the optimizer can eliminate some -simple code lines by combining them with other lines. For example, code -like this: -.PP -.Vb 4 -\& if (a != b) -\& c = 1; -\& else -\& c = 0; -.Ve -can be compiled into one instruction on some machines. In this case, -there is no way for \fBgcov\fR to calculate separate execution counts -for each line because there isn't separate code for each line. Hence -the \fBgcov\fR output looks like this if you compiled the program with -optimization: -.PP -.Vb 4 -\& 100 if (a != b) -\& 100 c = 1; -\& 100 else -\& 100 c = 0; -.Ve -The output shows that this block of code, combined by optimization, -executed 100 times. In one sense this result is correct, because there -was only one instruction representing all four of these lines. However, -the output does not indicate how many times the result was 0 and how -many times the result was 1. -.SH "SEE ALSO" -.IX Header "SEE ALSO" -\&\fIgpl\fR\|(7), \fIgfdl\fR\|(7), \fIfsf-funding\fR\|(7), \fIgcc\fR\|(1) and the Info entry for \fIgcc\fR. -.SH "COPYRIGHT" -.IX Header "COPYRIGHT" -Copyright (c) 1996, 1997, 1999, 2000, 2001 Free Software Foundation, Inc. -.PP -Permission is granted to copy, distribute and/or modify this document -under the terms of the \s-1GNU\s0 Free Documentation License, Version 1.1 or -any later version published by the Free Software Foundation; with the -Invariant Sections being ``\s-1GNU\s0 General Public License'' and ``Funding -Free Software'', the Front-Cover texts being (a) (see below), and with -the Back-Cover Texts being (b) (see below). A copy of the license is -included in the \fIgfdl\fR\|(7) man page. -.PP -(a) The \s-1FSF\s0's Front-Cover Text is: -.PP -.Vb 1 -\& A GNU Manual -.Ve -(b) The \s-1FSF\s0's Back-Cover Text is: -.PP -.Vb 3 -\& 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. -.Ve diff --git a/contrib/gcc/doc/install-old.texi b/contrib/gcc/doc/install-old.texi deleted file mode 100644 index 9ce98968f91a..000000000000 --- a/contrib/gcc/doc/install-old.texi +++ /dev/null @@ -1,725 +0,0 @@ -@c Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001 Free Software Foundation, Inc. -@c This is part of the GCC manual. -@c For copying conditions, see the file install.texi. - -@ifnothtml -@comment node-name, next, previous, up -@node Old, GNU Free Documentation License, Specific, Top -@end ifnothtml -@html -<h1 align="center">Old installation documentation</h1> -@end html -@ifnothtml -@chapter Old installation documentation -@end ifnothtml - -Note most of this information is out of date and superseded by the -previous chapters of this manual. It is provided for historical -reference only, because of a lack of volunteers to merge it into the -main manual. - -@ifnothtml -@menu -* Configurations:: Configurations Supported by GNU CC. -* Cross-Compiler:: Building and installing a cross-compiler. -* VMS Install:: See below for installation on VMS. -@end menu -@end ifnothtml - -Here is the procedure for installing GNU CC on a GNU or Unix system. -See @ref{VMS Install}, for VMS systems. - -@enumerate -@item -If you have chosen a configuration for GNU CC which requires other GNU -tools (such as GAS or the GNU linker) instead of the standard system -tools, install the required tools in the build directory under the names -@file{as}, @file{ld} or whatever is appropriate. This will enable the -compiler to find the proper tools for compilation of the program -@file{enquire}. - -Alternatively, you can do subsequent compilation using a value of the -@code{PATH} environment variable such that the necessary GNU tools come -before the standard system tools. - -@item -Specify the host, build and target machine configurations. You do this -when you run the @file{configure} script. - -The @dfn{build} machine is the system which you are using, the -@dfn{host} machine is the system where you want to run the resulting -compiler (normally the build machine), and the @dfn{target} machine is -the system for which you want the compiler to generate code. - -If you are building a compiler to produce code for the machine it runs -on (a native compiler), you normally do not need to specify any operands -to @file{configure}; it will try to guess the type of machine you are on -and use that as the build, host and target machines. So you don't need -to specify a configuration when building a native compiler unless -@file{configure} cannot figure out what your configuration is or guesses -wrong. - -In those cases, specify the build machine's @dfn{configuration name} -with the @option{--host} option; the host and target will default to be -the same as the host machine. (If you are building a cross-compiler, -see @ref{Cross-Compiler}.) - -Here is an example: - -@smallexample -./configure --host=sparc-sun-sunos4.1 -@end smallexample - -A configuration name may be canonical or it may be more or less -abbreviated. - -A canonical configuration name has three parts, separated by dashes. -It looks like this: @samp{@var{cpu}-@var{company}-@var{system}}. -(The three parts may themselves contain dashes; @file{configure} -can figure out which dashes serve which purpose.) For example, -@samp{m68k-sun-sunos4.1} specifies a Sun 3. - -You can also replace parts of the configuration by nicknames or aliases. -For example, @samp{sun3} stands for @samp{m68k-sun}, so -@samp{sun3-sunos4.1} is another way to specify a Sun 3. - -You can specify a version number after any of the system types, and some -of the CPU types. In most cases, the version is irrelevant, and will be -ignored. So you might as well specify the version if you know it. - -See @ref{Configurations}, for a list of supported configuration names and -notes on many of the configurations. You should check the notes in that -section before proceeding any further with the installation of GNU CC@. - -@end enumerate - -@ifnothtml -@node Configurations, Cross-Compiler, , Old -@section Configurations Supported by GNU CC -@end ifnothtml -@html -<h2>@anchor{Configurations}Configurations Supported by GNU CC</h2> -@end html -@cindex configurations supported by GNU CC - -Here are the possible CPU types: - -@quotation -@c gmicro, fx80, spur and tahoe omitted since they don't work. -1750a, a29k, alpha, arm, avr, c@var{n}, clipper, dsp16xx, elxsi, fr30, h8300, -hppa1.0, hppa1.1, i370, i386, i486, i586, i686, i786, i860, i960, m32r, -m68000, m68k, m6811, m6812, m88k, mcore, mips, mipsel, mips64, mips64el, -mn10200, mn10300, ns32k, pdp11, powerpc, powerpcle, romp, rs6000, sh, sparc, -sparclite, sparc64, v850, vax, we32k. -@end quotation - -Here are the recognized company names. As you can see, customary -abbreviations are used rather than the longer official names. - -@c What should be done about merlin, tek*, dolphin? -@quotation -acorn, alliant, altos, apollo, apple, att, bull, -cbm, convergent, convex, crds, dec, dg, dolphin, -elxsi, encore, harris, hitachi, hp, ibm, intergraph, isi, -mips, motorola, ncr, next, ns, omron, plexus, -sequent, sgi, sony, sun, tti, unicom, wrs. -@end quotation - -The company name is meaningful only to disambiguate when the rest of -the information supplied is insufficient. You can omit it, writing -just @samp{@var{cpu}-@var{system}}, if it is not needed. For example, -@samp{vax-ultrix4.2} is equivalent to @samp{vax-dec-ultrix4.2}. - -Here is a list of system types: - -@quotation -386bsd, aix, acis, amigaos, aos, aout, aux, bosx, bsd, clix, coff, ctix, cxux, -dgux, dynix, ebmon, ecoff, elf, esix, freebsd, hms, genix, gnu, linux, -linux-gnu, hiux, hpux, iris, irix, isc, luna, lynxos, mach, minix, msdos, mvs, -netbsd, newsos, nindy, ns, osf, osfrose, ptx, riscix, riscos, rtu, sco, sim, -solaris, sunos, sym, sysv, udi, ultrix, unicos, uniplus, unos, vms, vsta, -vxworks, winnt, xenix. -@end quotation - -@noindent -You can omit the system type; then @file{configure} guesses the -operating system from the CPU and company. - -You can add a version number to the system type; this may or may not -make a difference. For example, you can write @samp{bsd4.3} or -@samp{bsd4.4} to distinguish versions of BSD@. In practice, the version -number is most needed for @samp{sysv3} and @samp{sysv4}, which are often -treated differently. - -@samp{linux-gnu} is the canonical name for the GNU/Linux target; however -GNU CC will also accept @samp{linux}. The version of the kernel in use is -not relevant on these systems. A suffix such as @samp{libc1} or @samp{aout} -distinguishes major versions of the C library; all of the suffixed versions -are obsolete. - -If you specify an impossible combination such as @samp{i860-dg-vms}, -then you may get an error message from @file{configure}, or it may -ignore part of the information and do the best it can with the rest. -@file{configure} always prints the canonical name for the alternative -that it used. GNU CC does not support all possible alternatives. - -Often a particular model of machine has a name. Many machine names are -recognized as aliases for CPU/company combinations. Thus, the machine -name @samp{sun3}, mentioned above, is an alias for @samp{m68k-sun}. -Sometimes we accept a company name as a machine name, when the name is -popularly used for a particular machine. Here is a table of the known -machine names: - -@quotation -3300, 3b1, 3b@var{n}, 7300, altos3068, altos, -apollo68, att-7300, balance, -convex-c@var{n}, crds, decstation-3100, -decstation, delta, encore, -fx2800, gmicro, hp7@var{nn}, hp8@var{nn}, -hp9k2@var{nn}, hp9k3@var{nn}, hp9k7@var{nn}, -hp9k8@var{nn}, iris4d, iris, isi68, -m3230, magnum, merlin, miniframe, -mmax, news-3600, news800, news, next, -pbd, pc532, pmax, powerpc, powerpcle, ps2, risc-news, -rtpc, sun2, sun386i, sun386, sun3, -sun4, symmetry, tower-32, tower. -@end quotation - -@noindent -Remember that a machine name specifies both the cpu type and the company -name. -If you want to install your own homemade configuration files, you can -use @samp{local} as the company name to access them. If you use -configuration @samp{@var{cpu}-local}, the configuration name -without the cpu prefix -is used to form the configuration file names. - -Thus, if you specify @samp{m68k-local}, configuration uses -files @file{m68k.md}, @file{local.h}, @file{m68k.c}, -@file{xm-local.h}, @file{t-local}, and @file{x-local}, all in the -directory @file{config/m68k}. - -Here is a list of configurations that have special treatment or special -things you must know: - -@table @samp -@item vax-dec-vms -See @ref{VMS Install}, for details on how to install GNU CC on VMS@. -@end table - -@ifnothtml -@node Cross-Compiler, VMS Install, Configurations, Old -@section Building and Installing a Cross-Compiler -@end ifnothtml -@html -<h2>@anchor{Cross-Compiler}Building and Installing a Cross-Compiler</h2> -@end html -@cindex cross-compiler, installation - -GNU CC can function as a cross-compiler for many machines, but not all. - -@itemize @bullet -@item -Cross-compilers for the Mips as target using the Mips assembler -currently do not work, because the auxiliary programs -@file{mips-tdump.c} and @file{mips-tfile.c} can't be compiled on -anything but a Mips. It does work to cross compile for a Mips -if you use the GNU assembler and linker. - -@item -Cross-compilers between machines with different floating point formats -have not all been made to work. GNU CC now has a floating point -emulator with which these can work, but each target machine description -needs to be updated to take advantage of it. - -@item -Cross-compilation between machines of different word sizes is -somewhat problematic and sometimes does not work. -@end itemize - -Since GNU CC generates assembler code, you probably need a -cross-assembler that GNU CC can run, in order to produce object files. -If you want to link on other than the target machine, you need a -cross-linker as well. You also need header files and libraries suitable -for the target machine that you can install on the host machine. - -@ifnothtml -@menu -* Steps of Cross:: Using a cross-compiler involves several steps - that may be carried out on different machines. -* Configure Cross:: Configuring a cross-compiler. -* Tools and Libraries:: Where to put the linker and assembler, and the C library. -* Cross Headers:: Finding and installing header files - for a cross-compiler. -* Build Cross:: Actually compiling the cross-compiler. -@end menu -@end ifnothtml - -@ifnothtml -@node Steps of Cross, Configure Cross, , Cross-Compiler -@subsection Steps of Cross-Compilation -@end ifnothtml -@html -<h2>Steps of Cross-Compilation</h2> -@end html - -To compile and run a program using a cross-compiler involves several -steps: - -@itemize @bullet -@item -Run the cross-compiler on the host machine to produce assembler files -for the target machine. This requires header files for the target -machine. - -@item -Assemble the files produced by the cross-compiler. You can do this -either with an assembler on the target machine, or with a -cross-assembler on the host machine. - -@item -Link those files to make an executable. You can do this either with a -linker on the target machine, or with a cross-linker on the host -machine. Whichever machine you use, you need libraries and certain -startup files (typically @file{crt@dots{}.o}) for the target machine. -@end itemize - -It is most convenient to do all of these steps on the same host machine, -since then you can do it all with a single invocation of GNU CC@. This -requires a suitable cross-assembler and cross-linker. For some targets, -the GNU assembler and linker are available. - -@ifnothtml -@node Configure Cross, Tools and Libraries, Steps of Cross, Cross-Compiler -@subsection Configuring a Cross-Compiler -@end ifnothtml -@html -<h2>Configuring a Cross-Compiler</h2> -@end html - -To build GNU CC as a cross-compiler, you start out by running -@file{configure}. Use the @option{--target=@var{target}} to specify the -target type. If @file{configure} was unable to correctly identify the -system you are running on, also specify the @option{--build=@var{build}} -option. For example, here is how to configure for a cross-compiler that -produces code for an HP 68030 system running BSD on a system that -@file{configure} can correctly identify: - -@smallexample -./configure --target=m68k-hp-bsd4.3 -@end smallexample - -@ifnothtml -@node Tools and Libraries, Cross Headers, Configure Cross, Cross-Compiler -@subsection Tools and Libraries for a Cross-Compiler -@end ifnothtml -@html -<h2>Tools and Libraries for a Cross-Compiler</h2> -@end html - -If you have a cross-assembler and cross-linker available, you should -install them now. Put them in the directory -@file{/usr/local/@var{target}/bin}. Here is a table of the tools -you should put in this directory: - -@table @file -@item as -This should be the cross-assembler. - -@item ld -This should be the cross-linker. - -@item ar -This should be the cross-archiver: a program which can manipulate -archive files (linker libraries) in the target machine's format. - -@item ranlib -This should be a program to construct a symbol table in an archive file. -@end table - -The installation of GNU CC will find these programs in that directory, -and copy or link them to the proper place to for the cross-compiler to -find them when run later. - -The easiest way to provide these files is to build the Binutils package -and GAS@. Configure them with the same @option{--host} and @option{--target} -options that you use for configuring GNU CC, then build and install -them. They install their executables automatically into the proper -directory. Alas, they do not support all the targets that GNU CC -supports. - -If you want to install libraries to use with the cross-compiler, such as -a standard C library, put them in the directory -@file{/usr/local/@var{target}/lib}; installation of GNU CC copies -all the files in that subdirectory into the proper place for GNU CC to -find them and link with them. Here's an example of copying some -libraries from a target machine: - -@example -ftp @var{target-machine} -lcd /usr/local/@var{target}/lib -cd /lib -get libc.a -cd /usr/lib -get libg.a -get libm.a -quit -@end example - -@noindent -The precise set of libraries you'll need, and their locations on -the target machine, vary depending on its operating system. - -@cindex start files -Many targets require ``start files'' such as @file{crt0.o} and -@file{crtn.o} which are linked into each executable; these too should be -placed in @file{/usr/local/@var{target}/lib}. There may be several -alternatives for @file{crt0.o}, for use with profiling or other -compilation options. Check your target's definition of -@code{STARTFILE_SPEC} to find out what start files it uses. -Here's an example of copying these files from a target machine: - -@example -ftp @var{target-machine} -lcd /usr/local/@var{target}/lib -prompt -cd /lib -mget *crt*.o -cd /usr/lib -mget *crt*.o -quit -@end example - -@ifnothtml -@node Cross Headers, Build Cross, Tools and Libraries, Cross-Compiler -@subsection Cross-Compilers and Header Files -@end ifnothtml -@html -<h2>Cross-Compilers and Header Files</h2> -@end html - -If you are cross-compiling a standalone program or a program for an -embedded system, then you may not need any header files except the few -that are part of GNU CC (and those of your program). However, if you -intend to link your program with a standard C library such as -@file{libc.a}, then you probably need to compile with the header files -that go with the library you use. - -The GNU C compiler does not come with these files, because (1) they are -system-specific, and (2) they belong in a C library, not in a compiler. - -If the GNU C library supports your target machine, then you can get the -header files from there (assuming you actually use the GNU library when -you link your program). - -If your target machine comes with a C compiler, it probably comes with -suitable header files also. If you make these files accessible from the host -machine, the cross-compiler can use them also. - -Otherwise, you're on your own in finding header files to use when -cross-compiling. - -When you have found suitable header files, you should put them in the -directory @file{/usr/local/@var{target}/include}, before building the -cross compiler. Then installation will run fixincludes properly and -install the corrected versions of the header files where the compiler -will use them. - -Provide the header files before you build the cross-compiler, because -the build stage actually runs the cross-compiler to produce parts of -@file{libgcc.a}. (These are the parts that @emph{can} be compiled with -GNU CC@.) Some of them need suitable header files. - -Here's an example showing how to copy the header files from a target -machine. On the target machine, do this: - -@example -(cd /usr/include; tar cf - .) > tarfile -@end example - -Then, on the host machine, do this: - -@example -ftp @var{target-machine} -lcd /usr/local/@var{target}/include -get tarfile -quit -tar xf tarfile -@end example - -@ifnothtml -@node Build Cross, , Cross Headers, Cross-Compiler -@subsection Actually Building the Cross-Compiler -@end ifnothtml -@html -<h2>Actually Building the Cross-Compiler</h2> -@end html - -Now you can proceed just as for compiling a single-machine compiler -through the step of building stage 1. - -If your target is exotic, you may need to provide the header file -@file{float.h}.One way to do this is to compile @file{enquire} and run -it on your target machine. The job of @file{enquire} is to run on the -target machine and figure out by experiment the nature of its floating -point representation. @file{enquire} records its findings in the header -file @file{float.h}. If you can't produce this file by running -@file{enquire} on the target machine, then you will need to come up with -a suitable @file{float.h} in some other way (or else, avoid using it in -your programs). - -Do not try to build stage 2 for a cross-compiler. It doesn't work to -rebuild GNU CC as a cross-compiler using the cross-compiler, because -that would produce a program that runs on the target machine, not on the -host. For example, if you compile a 386-to-68030 cross-compiler with -itself, the result will not be right either for the 386 (because it was -compiled into 68030 code) or for the 68030 (because it was configured -for a 386 as the host). If you want to compile GNU CC into 68030 code, -whether you compile it on a 68030 or with a cross-compiler on a 386, you -must specify a 68030 as the host when you configure it. - -To install the cross-compiler, use @samp{make install}, as usual. - -@ifnothtml -@node VMS Install, , Cross-Compiler, Old -@section Installing GNU CC on VMS -@end ifnothtml -@html -<h2>@anchor{VMS Install}Installing GNU CC on VMS</h2> -@end html -@cindex VMS installation -@cindex installing GNU CC on VMS - -The VMS version of GNU CC is distributed in a backup saveset containing -both source code and precompiled binaries. - -To install the @file{gcc} command so you can use the compiler easily, in -the same manner as you use the VMS C compiler, you must install the VMS CLD -file for GNU CC as follows: - -@enumerate -@item -Define the VMS logical names @samp{GNU_CC} and @samp{GNU_CC_INCLUDE} -to point to the directories where the GNU CC executables -(@file{gcc-cpp.exe}, @file{gcc-cc1.exe}, etc.) and the C include files are -kept respectively. This should be done with the commands: - -@smallexample -$ assign /system /translation=concealed - - disk:[gcc.] gnu_cc -$ assign /system /translation=concealed - - disk:[gcc.include.] gnu_cc_include -@end smallexample - -@noindent -with the appropriate disk and directory names. These commands can be -placed in your system startup file so they will be executed whenever -the machine is rebooted. You may, if you choose, do this via the -@file{GCC_INSTALL.COM} script in the @file{[GCC]} directory. - -@item -Install the @file{GCC} command with the command line: - -@smallexample -$ set command /table=sys$common:[syslib]dcltables - - /output=sys$common:[syslib]dcltables gnu_cc:[000000]gcc -$ install replace sys$common:[syslib]dcltables -@end smallexample - -@item -To install the help file, do the following: - -@smallexample -$ library/help sys$library:helplib.hlb gcc.hlp -@end smallexample - -@noindent -Now you can invoke the compiler with a command like @samp{gcc /verbose -file.c}, which is equivalent to the command @samp{gcc -v -c file.c} in -Unix. -@end enumerate - -If you wish to use GNU C++ you must first install GNU CC, and then -perform the following steps: - -@enumerate -@item -Define the VMS logical name @samp{GNU_GXX_INCLUDE} to point to the -directory where the preprocessor will search for the C++ header files. -This can be done with the command: - -@smallexample -$ assign /system /translation=concealed - - disk:[gcc.gxx_include.] gnu_gxx_include -@end smallexample - -@noindent -with the appropriate disk and directory name. If you are going to be -using a C++ runtime library, this is where its install procedure will install -its header files. - -@item -Obtain the file @file{gcc-cc1plus.exe}, and place this in the same -directory that @file{gcc-cc1.exe} is kept. - -The GNU C++ compiler can be invoked with a command like @samp{gcc /plus -/verbose file.cc}, which is equivalent to the command @samp{g++ -v -c -file.cc} in Unix. -@end enumerate - -We try to put corresponding binaries and sources on the VMS distribution -tape. But sometimes the binaries will be from an older version than the -sources, because we don't always have time to update them. (Use the -@samp{/version} option to determine the version number of the binaries and -compare it with the source file @file{version.c} to tell whether this is -so.) In this case, you should use the binaries you get to recompile the -sources. If you must recompile, here is how: - -@enumerate -@item -Execute the command procedure @file{vmsconfig.com} to set up the files -@file{tm.h}, @file{config.h}, @file{aux-output.c}, and @file{md.}, and -to create files @file{tconfig.h} and @file{hconfig.h}. This procedure -also creates several linker option files used by @file{make-cc1.com} and -a data file used by @file{make-l2.com}. - -@smallexample -$ @@vmsconfig.com -@end smallexample - -@item -Setup the logical names and command tables as defined above. In -addition, define the VMS logical name @samp{GNU_BISON} to point at the -to the directories where the Bison executable is kept. This should be -done with the command: - -@smallexample -$ assign /system /translation=concealed - - disk:[bison.] gnu_bison -@end smallexample - -You may, if you choose, use the @file{INSTALL_BISON.COM} script in the -@file{[BISON]} directory. - -@item -Install the @samp{BISON} command with the command line: - -@smallexample -$ set command /table=sys$common:[syslib]dcltables - - /output=sys$common:[syslib]dcltables - - gnu_bison:[000000]bison -$ install replace sys$common:[syslib]dcltables -@end smallexample - -@item -Type @samp{@@make-gcc} to recompile everything, or submit the file -@file{make-gcc.com} to a batch queue. If you wish to build the GNU C++ -compiler as well as the GNU CC compiler, you must first edit -@file{make-gcc.com} and follow the instructions that appear in the -comments. - -@item -In order to use GCC, you need a library of functions which GCC compiled code -will call to perform certain tasks, and these functions are defined in the -file @file{libgcc2.c}. To compile this you should use the command procedure -@file{make-l2.com}, which will generate the library @file{libgcc2.olb}. -@file{libgcc2.olb} should be built using the compiler built from -the same distribution that @file{libgcc2.c} came from, and -@file{make-gcc.com} will automatically do all of this for you. - -To install the library, use the following commands: - -@smallexample -$ library gnu_cc:[000000]gcclib/delete=(new,eprintf) -$ library gnu_cc:[000000]gcclib/delete=L_* -$ library libgcc2/extract=*/output=libgcc2.obj -$ library gnu_cc:[000000]gcclib libgcc2.obj -@end smallexample - -The first command simply removes old modules that will be replaced with -modules from @file{libgcc2} under different module names. The modules -@code{new} and @code{eprintf} may not actually be present in your -@file{gcclib.olb}---if the VMS librarian complains about those modules -not being present, simply ignore the message and continue on with the -next command. The second command removes the modules that came from the -previous version of the library @file{libgcc2.c}. - -Whenever you update the compiler on your system, you should also update the -library with the above procedure. - -@item -You may wish to build GCC in such a way that no files are written to the -directory where the source files reside. An example would be the when -the source files are on a read-only disk. In these cases, execute the -following DCL commands (substituting your actual path names): - -@smallexample -$ assign dua0:[gcc.build_dir.]/translation=concealed, - - dua1:[gcc.source_dir.]/translation=concealed gcc_build -$ set default gcc_build:[000000] -@end smallexample - -@noindent -where the directory @file{dua1:[gcc.source_dir]} contains the source -code, and the directory @file{dua0:[gcc.build_dir]} is meant to contain -all of the generated object files and executables. Once you have done -this, you can proceed building GCC as described above. (Keep in mind -that @file{gcc_build} is a rooted logical name, and thus the device -names in each element of the search list must be an actual physical -device name rather than another rooted logical name). - -@item -@strong{If you are building GNU CC with a previous version of GNU CC, -you also should check to see that you have the newest version of the -assembler}. In particular, GNU CC version 2 treats global constant -variables slightly differently from GNU CC version 1, and GAS version -1.38.1 does not have the patches required to work with GCC version 2. -If you use GAS 1.38.1, then @code{extern const} variables will not have -the read-only bit set, and the linker will generate warning messages -about mismatched psect attributes for these variables. These warning -messages are merely a nuisance, and can safely be ignored. - -@item -If you want to build GNU CC with the VAX C compiler, you will need to -make minor changes in @file{make-cccp.com} and @file{make-cc1.com} -to choose alternate definitions of @code{CC}, @code{CFLAGS}, and -@code{LIBS}. See comments in those files. However, you must -also have a working version of the GNU assembler (GNU as, aka GAS) as -it is used as the back end for GNU CC to produce binary object modules -and is not included in the GNU CC sources. GAS is also needed to -compile @file{libgcc2} in order to build @file{gcclib} (see above); -@file{make-l2.com} expects to be able to find it operational in -@file{gnu_cc:[000000]gnu-as.exe}. - -To use GNU CC on VMS, you need the VMS driver programs -@file{gcc.exe}, @file{gcc.com}, and @file{gcc.cld}. They are -distributed with the VMS binaries (@file{gcc-vms}) rather than the -GNU CC sources. GAS is also included in @file{gcc-vms}, as is Bison. - -Once you have successfully built GNU CC with VAX C, you should use the -resulting compiler to rebuild itself. Before doing this, be sure to -restore the @code{CC}, @code{CFLAGS}, and @code{LIBS} definitions in -@file{make-cccp.com} and @file{make-cc1.com}. The second generation -compiler will be able to take advantage of many optimizations that must -be suppressed when building with other compilers. -@end enumerate - -Under previous versions of GNU CC, the generated code would occasionally -give strange results when linked with the sharable @file{VAXCRTL} library. -Now this should work. - -Even with this version, however, GNU CC itself should not be linked with -the sharable @file{VAXCRTL}. The version of @code{qsort} in -@file{VAXCRTL} has a bug (known to be present in VMS versions V4.6 -through V5.5) which causes the compiler to fail. - -The executables are generated by @file{make-cc1.com} and -@file{make-cccp.com} use the object library version of @file{VAXCRTL} in -order to make use of the @code{qsort} routine in @file{gcclib.olb}. If -you wish to link the compiler executables with the shareable image -version of @file{VAXCRTL}, you should edit the file @file{tm.h} (created -by @file{vmsconfig.com}) to define the macro @code{QSORT_WORKAROUND}. - -@code{QSORT_WORKAROUND} is always defined when GNU CC is compiled with -VAX C, to avoid a problem in case @file{gcclib.olb} is not yet -available. diff --git a/contrib/gcc/doc/install.texi b/contrib/gcc/doc/install.texi deleted file mode 100644 index 350d365b1b5c..000000000000 --- a/contrib/gcc/doc/install.texi +++ /dev/null @@ -1,3928 +0,0 @@ -\input texinfo.tex @c -*-texinfo-*- -@c @ifnothtml -@c %**start of header -@setfilename install.info -@settitle Installing GCC -@setchapternewpage odd -@c %**end of header -@c @end ifnothtml - -@c Specify title for specific html page -@ifset indexhtml -@settitle Installing GCC -@end ifset -@ifset specifichtml -@settitle Host/Target specific installation notes for GCC -@end ifset -@ifset downloadhtml -@settitle Downloading GCC -@end ifset -@ifset configurehtml -@settitle Installing GCC: Configuration -@end ifset -@ifset buildhtml -@settitle Installing GCC: Building -@end ifset -@ifset testhtml -@settitle Installing GCC: Testing -@end ifset -@ifset finalinstallhtml -@settitle Installing GCC: Final installation -@end ifset -@ifset binarieshtml -@settitle Installing GCC: Binaries -@end ifset -@ifset oldhtml -@settitle Installing GCC: Old documentation -@end ifset -@ifset gfdlhtml -@settitle Installing GCC: GNU Free Documentation License -@end ifset - -@c Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, -@c 1999, 2000, 2001, 2002 Free Software Foundation, Inc. -@c *** Converted to texinfo by Dean Wakerley, dean@wakerley.com - -@c Include everything if we're not making html -@ifnothtml -@set indexhtml -@set specifichtml -@set downloadhtml -@set configurehtml -@set buildhtml -@set testhtml -@set finalinstallhtml -@set binarieshtml -@set oldhtml -@set gfdlhtml -@end ifnothtml - -@c Part 2 Summary Description and Copyright -@macro copyrightnotice -Copyright @copyright{} 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, -1999, 2000, 2001, 2002 Free Software Foundation, Inc. -@sp 1 -Permission is granted to copy, distribute and/or modify this document -under the terms of the GNU Free Documentation License, Version 1.1 or -any later version published by the Free Software Foundation; with no -Invariant Sections, the Front-Cover texts being (a) (see below), and -with the Back-Cover Texts being (b) (see below). A copy of the -license is included in the section entitled ``@uref{./gfdl.html,,GNU -Free Documentation License}''. - -(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. -@end macro -@ifinfo -@copyrightnotice{} -@end ifinfo - -@c Part 3 Titlepage and Copyright -@titlepage -@sp 10 -@comment The title is printed in a large font. -@center @titlefont{Installing GCC} - -@c The following two commands start the copyright page. -@page -@vskip 0pt plus 1filll -@copyrightnotice{} -@end titlepage - -@c Part 4 Top node and Master Menu -@ifinfo -@node Top, , , (dir) -@comment node-name, next, Previous, up - -@menu -* Installing GCC:: This document describes the generic installation - procedure for GCC as well as detailing some target - specific installation instructions. - -* Specific:: Host/target specific installation notes for GCC. -* Binaries:: Where to get pre-compiled binaries. - -* Old:: Old installation documentation. - -* GNU Free Documentation License:: How you can copy and share this manual. -* Concept Index:: This index has two entries. -@end menu -@end ifinfo - -@c Part 5 The Body of the Document -@c ***Installing GCC********************************************************** -@ifnothtml -@comment node-name, next, previous, up -@node Installing GCC, Binaries, , Top -@end ifnothtml -@ifset indexhtml -@ifnothtml -@chapter Installing GCC -@end ifnothtml - -The latest version of this document is always available at -@uref{http://gcc.gnu.org/install/,,http://gcc.gnu.org/install/}. - -This document describes the generic installation procedure for GCC as well -as detailing some target specific installation instructions. - -GCC includes several components that previously were separate distributions -with their own installation instructions. This document supersedes all -package specific installation instructions. - -@emph{Before} starting the build/install procedure please check the -@ifnothtml -@ref{Specific, host/target specific installation notes}. -@end ifnothtml -@ifhtml -@uref{specific.html,,host/target specific installation notes}. -@end ifhtml -We recommend you browse the entire generic installation instructions before -you proceed. - -Lists of successful builds for released versions of GCC are -available at @uref{http://gcc.gnu.org/buildstat.html}. -These lists are updated as new information becomes available. - -The installation procedure itself is broken into five steps. - -@ifinfo -@menu -* Downloading the source:: -* Configuration:: -* Building:: -* Testing:: (optional) -* Final install:: -@end menu -@end ifinfo -@ifhtml -@enumerate -@item -@uref{download.html,,Downloading the source} -@item -@uref{configure.html,,Configuration} -@item -@uref{build.html,,Building} -@item -@uref{test.html,,Testing} (optional) -@item -@uref{finalinstall.html,,Final install} -@end enumerate -@end ifhtml - -Please note that GCC does not support @samp{make uninstall} and probably -won't do so in the near future as this would open a can of worms. Instead, -we suggest that you install GCC into a directory of its own and simply -remove that directory when you do not need that specific version of GCC -any longer, and, if shared libraries are installed there as well, no -more binaries exist that use them. - -@ifhtml -There are also some @uref{old.html,,old installation instructions}, -which are mostly obsolete but still contain some information which has -not yet been merged into the main part of this manual. -@end ifhtml - -@html -<hr /> -<p> -@end html -@ifhtml -@uref{./index.html,,Return to the GCC Installation page} - -@copyrightnotice{} -@end ifhtml -@end ifset - -@c ***Downloading the source************************************************** -@ifnothtml -@comment node-name, next, previous, up -@node Downloading the source, Configuration, , Installing GCC -@end ifnothtml -@ifset downloadhtml -@ifnothtml -@chapter Downloading GCC -@end ifnothtml -@cindex Downloading GCC -@cindex Downloading the Source - -GCC is distributed via @uref{http://gcc.gnu.org/cvs.html,,CVS} and FTP -tarballs compressed with @command{gzip} or -@command{bzip2}. It is possible to download a full distribution or specific -components. - -Please refer to our @uref{http://gcc.gnu.org/releases.html,,releases web page} -for information on how to obtain GCC@. - -The full distribution includes the C, C++, Objective-C, Fortran, Java, -and Ada (in case of GCC 3.1 and later) compilers. The full distribution -also includes runtime libraries for C++, Objective-C, Fortran, and Java. -In GCC 3.0 and later versions, GNU compiler testsuites are also included -in the full distribution. - -If you choose to download specific components, you must download the core -GCC distribution plus any language specific distributions you wish to -use. The core distribution includes the C language front end as well as the -shared components. Each language has a tarball which includes the language -front end as well as the language runtime (when appropriate). - -Unpack the core distribution as well as any language specific -distributions in the same directory. - -If you also intend to build binutils (either to upgrade an existing -installation or for use in place of the corresponding tools of your -OS), unpack the binutils distribution either in the same directory or -a separate one. In the latter case, add symbolic links to any -components of the binutils you intend to build alongside the compiler -(@file{bfd}, @file{binutils}, @file{gas}, @file{gprof}, @file{ld}, -@file{opcodes}, @dots{}) to the directory containing the GCC sources. - -@html -<hr /> -<p> -@end html -@ifhtml -@uref{./index.html,,Return to the GCC Installation page} -@end ifhtml -@end ifset - -@c ***Configuration*********************************************************** -@ifnothtml -@comment node-name, next, previous, up -@node Configuration, Building, Downloading the source, Installing GCC -@end ifnothtml -@ifset configurehtml -@ifnothtml -@chapter Installing GCC: Configuration -@end ifnothtml -@cindex Configuration -@cindex Installing GCC: Configuration - -Like most GNU software, GCC must be configured before it can be built. -This document describes the recommended configuration procedure -for both native and cross targets. - -We use @var{srcdir} to refer to the toplevel source directory for -GCC; we use @var{objdir} to refer to the toplevel build/object directory. - -If you obtained the sources via CVS, @var{srcdir} must refer to the top -@file{gcc} directory, the one where the @file{MAINTAINERS} can be found, -and not its @file{gcc} subdirectory, otherwise the build will fail. - -First, we @strong{highly} recommend that GCC be built into a -separate directory than the sources which does @strong{not} reside -within the source tree. This is how we generally build GCC; building -where @var{srcdir} == @var{objdir} should still work, but doesn't -get extensive testing; building where @var{objdir} is a subdirectory -of @var{srcdir} is unsupported. - -If you have previously built GCC in the same directory for a -different target machine, do @samp{make distclean} to delete all files -that might be invalid. One of the files this deletes is -@file{Makefile}; if @samp{make distclean} complains that @file{Makefile} -does not exist, it probably means that the directory is already suitably -clean. However, with the recommended method of building in a separate -@var{objdir}, you should simply use a different @var{objdir} for each -target. - -Second, when configuring a native system, either @command{cc} or -@command{gcc} must be in your path or you must set @env{CC} in -your environment before running configure. Otherwise the configuration -scripts may fail. - -Note that the bootstrap compiler and the resulting GCC must be link -compatible, else the bootstrap will fail with linker errors about -incompatible object file formats. Several multilibed targets are -affected by this requirement, see -@ifnothtml -@ref{Specific, host/target specific installation notes}. -@end ifnothtml -@ifhtml -@uref{specific.html,,host/target specific installation notes}. -@end ifhtml - -To configure GCC: - -@example - % mkdir @var{objdir} - % cd @var{objdir} - % @var{srcdir}/configure [@var{options}] [@var{target}] -@end example - - -@heading Target specification -@itemize @bullet -@item -GCC has code to correctly determine the correct value for @var{target} -for nearly all native systems. Therefore, we highly recommend you not -provide a configure target when configuring a native compiler. - -@item -@var{target} must be specified as @option{--target=@var{target}} -when configuring a cross compiler; examples of valid targets would be -i960-rtems, m68k-coff, sh-elf, etc. - -@item -Specifying just @var{target} instead of @option{--target=@var{target}} -implies that the host defaults to @var{target}. -@end itemize - - -@heading Options specification - -Use @var{options} to override several configure time options for -GCC@. A list of supported @var{options} follows; @command{configure ---help} may list other options, but those not listed below may not -work and should not normally be used. - -@table @code -@item --prefix=@var{dirname} -Specify the toplevel installation -directory. This is the recommended way to install the tools into a directory -other than the default. The toplevel installation directory defaults to -@file{/usr/local}. - -We @strong{highly} recommend against @var{dirname} being the same or a -subdirectory of @var{objdir} or vice versa. - -These additional options control where certain parts of the distribution -are installed. Normally you should not need to use these options. -@table @code -@item --exec-prefix=@var{dirname} -Specify the toplevel installation directory for architecture-dependent -files. The default is @file{@var{prefix}}. - -@item --bindir=@var{dirname} -Specify the installation directory for the executables called by users -(such as @command{gcc} and @command{g++}). The default is -@file{@var{exec-prefix}/bin}. - -@item --libdir=@var{dirname} -Specify the installation directory for object code libraries and -internal parts of GCC@. The default is @file{@var{exec-prefix}/lib}. - -@item --with-slibdir=@var{dirname} -Specify the installation directory for the shared libgcc library. The -default is @file{@var{libdir}}. - -@item --infodir=@var{dirname} -Specify the installation directory for documentation in info format. -The default is @file{@var{prefix}/info}. - -@item --mandir=@var{dirname} -Specify the installation directory for manual pages. The default is -@file{@var{prefix}/man}. (Note that the manual pages are only extracts from -the full GCC manuals, which are provided in Texinfo format. The -@command{g77} manpage is unmaintained and may be out of date; the others -are derived by an automatic conversion process from parts of the full -manual.) - -@item --with-gxx-include-dir=@var{dirname} -Specify -the installation directory for G++ header files. The default is -@file{@var{prefix}/include/g++-v3}. - -@end table - -@item --program-prefix=@var{prefix} -GCC supports some transformations of the names of its programs when -installing them. This option prepends @var{prefix} to the names of -programs to install in @var{bindir} (see above). For example, specifying -@option{--program-prefix=foo-} would result in @samp{gcc} -being installed as @file{/usr/local/bin/foo-gcc}. - -@item --program-suffix=@var{suffix} -Appends @var{suffix} to the names of programs to install in @var{bindir} -(see above). For example, specifying @option{--program-suffix=-3.1} -would result in @samp{gcc} being installed as -@file{/usr/local/bin/gcc-3.1}. - -@item --program-transform-name=@var{pattern} -Applies the @samp{sed} script @var{pattern} to be applied to the names -of programs to install in @var{bindir} (see above). @var{pattern} has to -consist of one or more basic @samp{sed} editing commands, separated by -semicolons. For example, if you want the @samp{gcc} program name to be -transformed to the installed program @file{/usr/local/bin/myowngcc} and -the @samp{g++} program name to be transformed to -@file{/usr/local/bin/gspecial++} without changing other program names, -you could use the pattern -@option{--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/'} -to achieve this effect. - -All three options can be combined and used together, resulting in more -complex conversion patterns. As a basic rule, @var{prefix} (and -@var{suffix}) are prepended (appended) before further transformations -can happen with a special transformation script @var{pattern}. - -As currently implemented, these options only take effect for native -builds; cross compiler binaries' names are not transformed even when a -transformation is explicitly asked for by one of these options. - -For native builds, some of the installed programs are also installed -with the target alias in front of their name, as in -@samp{i686-pc-linux-gnu-gcc}. All of the above transformations happen -before the target alias is prepended to the name - so, specifying -@option{--program-prefix=foo-} and @option{program-suffix=-3.1}, the -resulting binary would be installed as -@file{/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1}. - -As a last shortcoming, none of the installed Ada programs are -transformed yet, which will be fixed in some time. - -@item --with-local-prefix=@var{dirname} -Specify the -installation directory for local include files. The default is -@file{/usr/local}. Specify this option if you want the compiler to -search directory @file{@var{dirname}/include} for locally installed -header files @emph{instead} of @file{/usr/local/include}. - -You should specify @option{--with-local-prefix} @strong{only} if your -site has a different convention (not @file{/usr/local}) for where to put -site-specific files. - -The default value for @option{--with-local-prefix} is @file{/usr/local} -regardless of the value of @option{--prefix}. Specifying -@option{--prefix} has no effect on which directory GCC searches for -local header files. This may seem counterintuitive, but actually it is -logical. - -The purpose of @option{--prefix} is to specify where to @emph{install -GCC}. The local header files in @file{/usr/local/include}---if you put -any in that directory---are not part of GCC@. They are part of other -programs---perhaps many others. (GCC installs its own header files in -another directory which is based on the @option{--prefix} value.) - -Both the local-prefix include directory and the GCC-prefix include -directory are part of GCC's "system include" directories. Although these -two directories are not fixed, they need to be searched in the proper -order for the correct processing of the include_next directive. The -local-prefix include directory is searched before the GCC-prefix -include directory. Another characteristic of system include directories -is that pedantic warnings are turned off for headers in these directories. - -Some autoconf macros add @option{-I @var{directory}} options to the -compiler command line, to ensure that directories containing installed -packages' headers are searched. When @var{directory} is one of GCC's -system include directories, GCC will ignore the option so that system -directories continue to be processed in the correct order. This -may result in a search order different from what was specified but the -directory will still be searched. - -GCC automatically searches for ordinary libraries using -@env{GCC_EXEC_PREFIX}. Thus, when the same installation prefix is -used for both GCC and packages, GCC will automatically search for -both headers and libraries. This provides a configuration that is -easy to use. GCC behaves in a manner similar to that when it is -installed as a system compiler in @file{/usr}. - -Sites that need to install multiple versions of GCC may not want to -use the above simple configuration. It is possible to use the -@option{--program-prefix}, @option{--program-suffix} and -@option{--program-transform-name} options to install multiple versions -into a single directory, but it may be simpler to use different prefixes -and the @option{--with-local-prefix} option to specify the location of the -site-specific files for each version. It will then be necessary for -users to specify explicitly the location of local site libraries -(e.g., with @env{LIBRARY_PATH}). - -The same value can be used for both @option{--with-local-prefix} and -@option{--prefix} provided it is not @file{/usr}. This can be used -to avoid the default search of @file{/usr/local/include}. - -@strong{Do not} specify @file{/usr} as the @option{--with-local-prefix}! -The directory you use for @option{--with-local-prefix} @strong{must not} -contain any of the system's standard header files. If it did contain -them, certain programs would be miscompiled (including GNU Emacs, on -certain targets), because this would override and nullify the header -file corrections made by the @command{fixincludes} script. - -Indications are that people who use this option use it based on mistaken -ideas of what it is for. People use it as if it specified where to -install part of GCC@. Perhaps they make this assumption because -installing GCC creates the directory. - -@item --enable-shared[=@var{package}[,@dots{}]] -Build shared versions of libraries, if shared libraries are supported on -the target platform. Unlike GCC 2.95.x and earlier, shared libraries -are enabled by default on all platforms that support shared libraries, -except for @samp{libobjc} which is built as a static library only by -default. - -If a list of packages is given as an argument, build shared libraries -only for the listed packages. For other packages, only static libraries -will be built. Package names currently recognized in the GCC tree are -@samp{libgcc} (also known as @samp{gcc}), @samp{libstdc++} (not -@samp{libstdc++-v3}), @samp{libffi}, @samp{zlib}, @samp{boehm-gc} and -@samp{libjava}. Note that @samp{libobjc} does not recognize itself by -any name, so, if you list package names in @option{--enable-shared}, -you will only get static Objective-C libraries. @samp{libf2c} and -@samp{libiberty} do not support shared libraries at all. - -Use @option{--disable-shared} to build only static libraries. Note that -@option{--disable-shared} does not accept a list of package names as -argument, only @option{--enable-shared} does. - -@item @anchor{with-gnu-as}--with-gnu-as -Specify that the compiler should assume that the -assembler it finds is the GNU assembler. However, this does not modify -the rules to find an assembler and will result in confusion if found -assembler is not actually the GNU assembler. (Confusion will also -result if the compiler finds the GNU assembler but has not been -configured with @option{--with-gnu-as}.) If you have more than one -assembler installed on your system, you may want to use this option in -connection with @option{--with-as=@var{pathname}}. - -The following systems are the only ones where it makes a difference -whether you use the GNU assembler. On any other system, -@option{--with-gnu-as} has no effect. - -@itemize bullet -@item @samp{hppa1.0-@var{any}-@var{any}} -@item @samp{hppa1.1-@var{any}-@var{any}} -@item @samp{i386-@var{any}-sysv} -@item @samp{i386-@var{any}-isc} -@item @samp{i860-@var{any}-bsd} -@item @samp{m68k-bull-sysv} -@item @samp{m68k-hp-hpux} -@item @samp{m68k-sony-bsd} -@item @samp{m68k-altos-sysv} -@item @samp{m68000-hp-hpux} -@item @samp{m68000-att-sysv} -@item @samp{@var{any}-lynx-lynxos} -@item @samp{mips-@var{any}} -@end itemize - -On the systems listed above (except for the HP-PA, for ISC on the -386, and for @samp{mips-sgi-irix5.*}), if you use the GNU assembler, -you should also use the GNU linker (and specify @option{--with-gnu-ld}). - -@item --with-as=@var{pathname} -Specify that the -compiler should use the assembler pointed to by @var{pathname}, rather -than the one found by the standard rules to find an assembler, which -are: -@itemize @bullet -@item -Check the -@file{@var{exec_prefix}/lib/gcc-lib/@var{target}/@var{version}} -directory, where @var{exec_prefix} defaults to @var{prefix} which -defaults to @file{/usr/local} unless overridden by the -@option{--prefix=@var{pathname}} switch described above. @var{target} is the -target system triple, such as @samp{sparc-sun-solaris2.7}, and -@var{version} denotes the GCC version, such as 3.0. -@item -Check operating system specific directories (e.g.@: @file{/usr/ccs/bin} on -Sun Solaris 2). -@end itemize -Note that these rules do not check for the value of @env{PATH}. You may -want to use @option{--with-as} if no assembler is installed in the -directories listed above, or if you have multiple assemblers installed -and want to choose one that is not found by the above rules. - -@item @anchor{with-gnu-ld}--with-gnu-ld -Same as @uref{#with-gnu-as,,@option{--with-gnu-as}} -but for linker. - - -@item --with-ld=@var{pathname} -Same as -@option{--with-as}, but for the linker. - -@item --with-stabs -Specify that stabs debugging -information should be used instead of whatever format the host normally -uses. Normally GCC uses the same debug format as the host system. - -On MIPS based systems and on Alphas, you must specify whether you want -GCC to create the normal ECOFF debugging format, or to use BSD-style -stabs passed through the ECOFF symbol table. The normal ECOFF debug -format cannot fully handle languages other than C@. BSD stabs format can -handle other languages, but it only works with the GNU debugger GDB@. - -Normally, GCC uses the ECOFF debugging format by default; if you -prefer BSD stabs, specify @option{--with-stabs} when you configure GCC@. - -No matter which default you choose when you configure GCC, the user -can use the @option{-gcoff} and @option{-gstabs+} options to specify explicitly -the debug format for a particular compilation. - -@option{--with-stabs} is meaningful on the ISC system on the 386, also, if -@option{--with-gas} is used. It selects use of stabs debugging -information embedded in COFF output. This kind of debugging information -supports C++ well; ordinary COFF debugging information does not. - -@option{--with-stabs} is also meaningful on 386 systems running SVR4. It -selects use of stabs debugging information embedded in ELF output. The -C++ compiler currently (2.6.0) does not support the DWARF debugging -information normally used on 386 SVR4 platforms; stabs provide a -workable alternative. This requires gas and gdb, as the normal SVR4 -tools can not generate or interpret stabs. - -@item --disable-multilib -Specify that multiple target -libraries to support different target variants, calling -conventions, etc should not be built. The default is to build a -predefined set of them. - -Some targets provide finer-grained control over which multilibs are built -(e.g., @option{--disable-softfloat}): -@table @code -@item arc-*-elf* -biendian. - -@item arm-*-* -fpu, 26bit, underscore, interwork, biendian, nofmult. - -@item m68*-*-* -softfloat, m68881, m68000, m68020. - -@item mips*-*-* -single-float, biendian, softfloat. - -@item powerpc*-*-*, rs6000*-*-* -aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian, -sysv, aix. - -@end table - -@item --enable-threads -Specify that the target -supports threads. This affects the Objective-C compiler and runtime -library, and exception handling for other languages like C++ and Java. -On some systems, this is the default. - -In general, the best (and, in many cases, the only known) threading -model available will be configured for use. Beware that on some -systems, gcc has not been taught what threading models are generally -available for the system. In this case, @option{--enable-threads} is an -alias for @option{--enable-threads=single}. - -@item --disable-threads -Specify that threading support should be disabled for the system. -This is an alias for @option{--enable-threads=single}. - -@item --enable-threads=@var{lib} -Specify that -@var{lib} is the thread support library. This affects the Objective-C -compiler and runtime library, and exception handling for other languages -like C++ and Java. The possibilities for @var{lib} are: - -@table @code -@item aix -AIX thread support. -@item dce -DCE thread support. -@item mach -Generic MACH thread support, known to work on NeXTSTEP@. (Please note -that the file needed to support this configuration, @file{gthr-mach.h}, is -missing and thus this setting will cause a known bootstrap failure.) -@item no -This is an alias for @samp{single}. -@item posix -Generic POSIX thread support. -@item pthreads -Same as @samp{posix} on arm*-*-linux*, *-*-chorusos* and *-*-freebsd* -only. A future release of gcc might remove this alias or extend it -to all platforms. -@item rtems -RTEMS thread support. -@item single -Disable thread support, should work for all platforms. -@item solaris -Sun Solaris 2 thread support. -@item vxworks -VxWorks thread support. -@item win32 -Microsoft Win32 API thread support. -@end table - -@item --with-cpu=@var{cpu} -Specify which cpu variant the -compiler should generate code for by default. This is currently -only supported on the some ports, specifically arm, powerpc, and -SPARC@. If configure does not recognize the model name (e.g.@: arm700, -603e, or ultrasparc) you provide, please check the configure script -for a complete list of supported models. - -@item --enable-altivec -Specify that the target supports AltiVec vector enhancements. This -option will adjust the ABI for AltiVec enhancements, as well as generate -AltiVec code when appropriate. This option is only available for -PowerPC systems. - -@item --enable-target-optspace -Specify that target -libraries should be optimized for code space instead of code speed. -This is the default for the m32r platform. - -@item --disable-cpp -Specify that a user visible @command{cpp} program should not be installed. - -@item --with-cpp-install-dir=@var{dirname} -Specify that the user visible @command{cpp} program should be installed -in @file{@var{prefix}/@var{dirname}/cpp}, in addition to @var{bindir}. - -@item --enable-maintainer-mode -The build rules that -regenerate the GCC master message catalog @file{gcc.pot} are normally -disabled. This is because it can only be rebuilt if the complete source -tree is present. If you have changed the sources and want to rebuild the -catalog, configuring with @option{--enable-maintainer-mode} will enable -this. Note that you need a recent version of the @code{gettext} tools -to do so. - -@item --enable-version-specific-runtime-libs -Specify -that runtime libraries should be installed in the compiler specific -subdirectory (@file{@var{libsubdir}}) rather than the usual places. In -addition, @samp{libstdc++}'s include files will be installed in -@file{@var{libsubdir}/include/g++} unless you overruled it by using -@option{--with-gxx-include-dir=@var{dirname}}. Using this option is -particularly useful if you intend to use several versions of GCC in -parallel. This is currently supported by @samp{libf2c} and -@samp{libstdc++}, and is the default for @samp{libobjc} which cannot be -changed in this case. - -@item --enable-languages=@var{lang1},@var{lang2},@dots{} -Specify that only a particular subset of compilers and -their runtime libraries should be built. For a list of valid values for -@var{langN} you can issue the following command in the -@file{gcc} directory of your GCC source tree:@* -@example -grep language= */config-lang.in -@end example -Currently, you can use any of the following: -@code{ada}, @code{c}, @code{c++}, @code{f77}, @code{java}, @code{objc}. -Building the Ada compiler has special requirements, see below.@* -If you do not pass this flag, all languages available in the @file{gcc} -sub-tree will be configured. Re-defining @code{LANGUAGES} when calling -@samp{make bootstrap} @strong{does not} work anymore, as those -language sub-directories might not have been configured! - -@item --disable-libgcj -Specify that the run-time libraries -used by GCJ should not be built. This is useful in case you intend -to use GCJ with some other run-time, or you're going to install it -separately, or it just happens not to build on your particular -machine. In general, if the Java front end is enabled, the GCJ -libraries will be enabled too, unless they're known to not work on -the target platform. If GCJ is enabled but @samp{libgcj} isn't built, you -may need to port it; in this case, before modifying the top-level -@file{configure.in} so that @samp{libgcj} is enabled by default on this platform, -you may use @option{--enable-libgcj} to override the default. - -@item --with-dwarf2 -Specify that the compiler should -use DWARF 2 debugging information as the default. - -@item --enable-win32-registry -@itemx --enable-win32-registry=@var{key} -@itemx --disable-win32-registry -The @option{--enable-win32-registry} option enables Windows-hosted GCC -to look up installations paths in the registry using the following key: - -@smallexample -@code{HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\@var{key}} -@end smallexample - -@var{key} defaults to GCC version number, and can be overridden by the -@option{--enable-win32-registry=@var{key}} option. Vendors and distributors -who use custom installers are encouraged to provide a different key, -perhaps one comprised of vendor name and GCC version number, to -avoid conflict with existing installations. This feature is enabled -by default, and can be disabled by @option{--disable-win32-registry} -option. This option has no effect on the other hosts. - -@item --nfp -Specify that the machine does not have a floating point unit. This -option only applies to @samp{m68k-sun-sunos@var{n}} and -@samp{m68k-isi-bsd}. On any other system, @option{--nfp} has no effect. - -@item --enable-checking -@itemx --enable-checking=@var{list} -When you specify this option, the compiler is built to perform checking -of tree node types when referencing fields of that node, and some other -internal consistency checks. This does not change the generated code, -but adds error checking within the compiler. This will slow down the -compiler and may only work properly if you are building the compiler -with GCC@. This is on by default when building from CVS or snapshots, -but off for releases. More control over the checks may be had by -specifying @var{list}; the categories of checks available are -@samp{misc}, @samp{tree}, @samp{gc}, @samp{rtl} and @samp{gcac}. The -default when @var{list} is not specified is @samp{misc,tree,gc}; the -checks @samp{rtl} and @samp{gcac} are very expensive. - -@item --enable-nls -@itemx --disable-nls -The @option{--enable-nls} option enables Native Language Support (NLS), -which lets GCC output diagnostics in languages other than American -English. Native Language Support is enabled by default if not doing a -canadian cross build. The @option{--disable-nls} option disables NLS@. - -@item --with-included-gettext -If NLS is enabled, the @option{--with-included-gettext} option causes the build -procedure to prefer its copy of GNU @command{gettext}. - -@item --with-catgets -If NLS is enabled, and if the host lacks @code{gettext} but has the -inferior @code{catgets} interface, the GCC build procedure normally -ignores @code{catgets} and instead uses GCC's copy of the GNU -@code{gettext} library. The @option{--with-catgets} option causes the -build procedure to use the host's @code{catgets} in this situation. - -@item --with-libiconv-prefix=@var{dir} -Search for libiconv header files in @file{@var{dir}/include} and -libiconv library files in @file{@var{dir}/lib}. - -@item --with-system-zlib -Use installed zlib rather than that included with GCC@. This option -only applies if the Java front end is being built. - -@item --enable-obsolete -Enable configuration for an obsoleted system. If you attempt to -configure GCC for a system (build, host, or target) which has been -obsoleted, and you do not specify this flag, configure will halt with an -error message. - -All support for systems which have been obsoleted in one release of GCC -is removed entirely in the next major release, unless someone steps -forward to maintain the port. -@end table - -Some options which only apply to building cross compilers: -@table @code -@item --with-headers=@var{dir} -Specifies a directory -which has target include files. -@emph{This option is required} when building a cross -compiler, if @file{@var{prefix}/@var{target}/sys-include} doesn't pre-exist. -These include files will be copied into the @file{gcc} install directory. -@command{fixincludes} will be run on these files to make them compatible with -GCC. -@item --with-libs=``@var{dir1} @var{dir2} @dots{} @var{dirN}'' -Specifies a list of directories which contain the target runtime -libraries. These libraries will be copied into the @file{gcc} install -directory. -@item --with-newlib -Specifies that @samp{newlib} is -being used as the target C library. This causes @code{__eprintf} to be -omitted from @file{libgcc.a} on the assumption that it will be provided by -@samp{newlib}. -@end table - -Note that each @option{--enable} option has a corresponding -@option{--disable} option and that each @option{--with} option has a -corresponding @option{--without} option. - -@html -<hr /> -<p> -@end html -@ifhtml -@uref{./index.html,,Return to the GCC Installation page} -@end ifhtml -@end ifset - -@c ***Building**************************************************************** -@ifnothtml -@comment node-name, next, previous, up -@node Building, Testing, Configuration, Installing GCC -@end ifnothtml -@ifset buildhtml -@ifnothtml -@chapter Building -@end ifnothtml -@cindex Installing GCC: Building - -Now that GCC is configured, you are ready to build the compiler and -runtime libraries. - -We @strong{highly} recommend that GCC be built using GNU make; -other versions may work, then again they might not. -GNU make is required for compiling GNAT (the Ada compiler) and the Java -runtime library. - -(For example, many broken versions of make will fail if you use the -recommended setup where @var{objdir} is different from @var{srcdir}. -Other broken versions may recompile parts of the compiler when -installing the compiler.) - -Some commands executed when making the compiler may fail (return a -nonzero status) and be ignored by @code{make}. These failures, which -are often due to files that were not found, are expected, and can safely -be ignored. - -It is normal to have compiler warnings when compiling certain files. -Unless you are a GCC developer, you can generally ignore these warnings -unless they cause compilation to fail. - -On certain old systems, defining certain environment variables such as -@env{CC} can interfere with the functioning of @command{make}. - -If you encounter seemingly strange errors when trying to build the -compiler in a directory other than the source directory, it could be -because you have previously configured the compiler in the source -directory. Make sure you have done all the necessary preparations. - -If you build GCC on a BSD system using a directory stored in an old System -V file system, problems may occur in running @command{fixincludes} if the -System V file system doesn't support symbolic links. These problems -result in a failure to fix the declaration of @code{size_t} in -@file{sys/types.h}. If you find that @code{size_t} is a signed type and -that type mismatches occur, this could be the cause. - -The solution is not to use such a directory for building GCC@. - -When building from CVS or snapshots, or if you modify parser sources, -you need the Bison parser generator installed. Any version 1.25 or -later should work; older versions may also work. If you do not modify -parser sources, releases contain the Bison-generated files and you do -not need Bison installed to build them. - -When building from CVS or snapshots, or if you modify Texinfo -documentation, you need version 4.1 or later of Texinfo installed if you -want Info documentation to be regenerated. Releases contain Info -documentation pre-built for the unmodified documentation in the release. - -@section Building a native compiler - -For a native build issue the command @samp{make bootstrap}. This -will build the entire GCC system, which includes the following steps: - -@itemize @bullet -@item -Build host tools necessary to build the compiler such as texinfo, bison, -gperf. - -@item -Build target tools for use by the compiler such as binutils (bfd, -binutils, gas, gprof, ld, and opcodes) -if they have been individually linked -or moved into the top level GCC source tree before configuring. - -@item -Perform a 3-stage bootstrap of the compiler. - -@item -Perform a comparison test of the stage2 and stage3 compilers. - -@item -Build runtime libraries using the stage3 compiler from the previous step. - -@end itemize - -If you are short on disk space you might consider @samp{make -bootstrap-lean} instead. This is identical to @samp{make -bootstrap} except that object files from the stage1 and -stage2 of the 3-stage bootstrap of the compiler are deleted as -soon as they are no longer needed. - -If you want to save additional space during the bootstrap and in -the final installation as well, you can build the compiler binaries -without debugging information as in the following example. This will save -roughly 40% of disk space both for the bootstrap and the final installation. -(Libraries will still contain debugging information.) - -@example - make CFLAGS='-O' LIBCFLAGS='-g -O2' \ - LIBCXXFLAGS='-g -O2 -fno-implicit-templates' bootstrap -@end example - -If you wish to use non-default GCC flags when compiling the stage2 and -stage3 compilers, set @code{BOOT_CFLAGS} on the command line when doing -@samp{make bootstrap}. Non-default optimization flags are less well -tested here than the default of @samp{-g -O2}, but should still work. -In a few cases, you may find that you need to specify special flags such -as @option{-msoft-float} here to complete the bootstrap; or, if the -native compiler miscompiles the stage1 compiler, you may need to work -around this, by choosing @code{BOOT_CFLAGS} to avoid the parts of the -stage1 compiler that were miscompiled, or by using @samp{make -bootstrap4} to increase the number of stages of bootstrap. - -If you used the flag @option{--enable-languages=@dots{}} to restrict -the compilers to be built, only those you've actually enabled will be -built. This will of course only build those runtime libraries, for -which the particular compiler has been built. Please note, -that re-defining @env{LANGUAGES} when calling @samp{make bootstrap} -@strong{does not} work anymore! - -If the comparison of stage2 and stage3 fails, this normally indicates -that the stage2 compiler has compiled GCC incorrectly, and is therefore -a potentially serious bug which you should investigate and report. (On -a few systems, meaningful comparison of object files is impossible; they -always appear ``different''. If you encounter this problem, you will -need to disable comparison in the @file{Makefile}.) - -@section Building a cross compiler - -We recommend reading the -@uref{http://www.objsw.com/CrossGCC/,,crossgcc FAQ} -for information about building cross compilers. - -When building a cross compiler, it is not generally possible to do a -3-stage bootstrap of the compiler. This makes for an interesting problem -as parts of GCC can only be built with GCC@. - -To build a cross compiler, we first recommend building and installing a -native compiler. You can then use the native GCC compiler to build the -cross compiler. The installed native compiler needs to be GCC version -2.95 or later. - -Assuming you have already installed a native copy of GCC and configured -your cross compiler, issue the command @command{make}, which performs the -following steps: - -@itemize @bullet -@item -Build host tools necessary to build the compiler such as texinfo, bison, -gperf. - -@item -Build target tools for use by the compiler such as binutils (bfd, -binutils, gas, gprof, ld, and opcodes) -if they have been individually linked or moved into the top level GCC source -tree before configuring. - -@item -Build the compiler (single stage only). - -@item -Build runtime libraries using the compiler from the previous step. -@end itemize - -Note that if an error occurs in any step the make process will exit. - -@section Building in parallel - -If you have a multiprocessor system you can use @samp{make bootstrap -MAKE="make -j 2" -j 2} or just @samp{make -j 2 bootstrap} -for GNU Make 3.79 and above instead of just @samp{make bootstrap} -when building GCC@. You can use a bigger number instead of two if -you like. In most cases, it won't help to use a number bigger than -the number of processors in your machine. - -@section Building the Ada compiler - -In order to build GNAT, the Ada compiler, you need a working GNAT -compiler (GNAT version 3.13 or later, or GCC version 3.1 or later), -since the Ada front end is written in Ada (with some -GNAT-specific extensions), and GNU make. - -However, you do not need a full installation of GNAT, just the GNAT -binary @file{gnat1}, a copy of @file{gnatbind}, and a compiler driver -which can deal with Ada input (by invoking the @file{gnat1} binary). -You can specify this compiler driver by setting the @env{ADAC} -environment variable at the configure step. @command{configure} can -detect the driver automatically if it has got a common name such as -@command{gcc} or @command{gnatgcc}. Of course, you still need a working -C compiler (the compiler driver can be different or not). -@command{configure} does not test whether the GNAT installation works -and has a sufficiently recent version; if too old a GNAT version is -installed, the build will fail unless @option{--enable-languages} is -used to disable building the Ada front end. - -Additional build tools (such as @command{gnatmake}) or a working GNAT -run-time library installation are usually @emph{not} required. However, -if you want to bootstrap the compiler using a minimal version of GNAT, -you have to issue the following commands before invoking @samp{make -bootstrap} (this assumes that you start with an unmodified and consistent -source distribution): - -@example - cd @var{srcdir}/gcc/ada - touch treeprs.ads [es]info.h nmake.ad[bs] -@end example - -At the moment, the GNAT library and several tools for GNAT are not built -by @samp{make bootstrap}. You have to invoke -@samp{make gnatlib_and_tools} in the @file{@var{objdir}/gcc} -subdirectory before proceeding with the next steps. - -For example, you can build a native Ada compiler by issuing the -following commands (assuming @command{make} is GNU make): - -@example - cd @var{objdir} - @var{srcdir}/configure --enable-languages=c,ada - cd @var{srcdir}/gcc/ada - touch treeprs.ads [es]info.h nmake.ad[bs] - cd @var{objdir} - make bootstrap - cd gcc - make gnatlib_and_tools - cd .. -@end example - -Currently, when compiling the Ada front end, you cannot use the parallel -build feature described in the previous section. - -@html -<hr /> -<p> -@end html -@ifhtml -@uref{./index.html,,Return to the GCC Installation page} -@end ifhtml -@end ifset - -@c ***Testing***************************************************************** -@ifnothtml -@comment node-name, next, previous, up -@node Testing, Final install, Building, Installing GCC -@end ifnothtml -@ifset testhtml -@ifnothtml -@chapter Installing GCC: Testing -@end ifnothtml -@cindex Testing -@cindex Installing GCC: Testing -@cindex Testsuite - -Before you install GCC, we encourage you to run the testsuites and to -compare your results with results from a similar configuration that have -been submitted to the -@uref{http://gcc.gnu.org/ml/gcc-testresults/,,gcc-testresults mailing list}. -This step is optional and may require you to download additional software, -but it can give you confidence in your new GCC installation or point out -problems before you install and start using your new GCC. - -First, you must have @uref{download.html,,downloaded the testsuites}. -These are part of the full distribution, but if you downloaded the -``core'' compiler plus any front ends, you must download the testsuites -separately. - -Second, you must have the testing tools installed. This includes -a @uref{http://www.gnu.org/software/dejagnu/,,current version of DejaGnu}; -dejagnu 1.3 is not sufficient. -It also includes Tcl and Expect; the DejaGnu site has links to these. - -Now you may need specific preparations: - -@itemize @bullet - -@item -The following environment variables may need to be set appropriately, as in -the following example (which assumes that DejaGnu has been installed -under @file{/usr/local}): - -@example - TCL_LIBRARY = /usr/local/share/tcl8.0 - DEJAGNULIBS = /usr/local/share/dejagnu -@end example - -On systems such as Cygwin, these paths are required to be actual -paths, not mounts or links; presumably this is due to some lack of -portability in the DejaGnu code. - -If the directories where @command{runtest} and @command{expect} were -installed are in the @env{PATH}, it should not be necessary to set these -environment variables. - -@end itemize - -Finally, you can run the testsuite (which may take a long time): -@example - cd @var{objdir}; make -k check -@end example - -The testing process will try to test as many components in the GCC -distribution as possible, including the C, C++, Objective-C and Fortran -compilers as well as the C++ and Java runtime libraries. - -While running the testsuite, DejaGnu might emit messages resembling -@samp{WARNING: Couldn't find the global config file.} or -@samp{WARNING: Couldn't find tool init file}. -These messages are harmless and do not affect the validity of the tests. - -@section How can I run the test suite on selected tests? - -As a first possibility to cut down the number of tests that are run it is -possible to use @samp{make check-gcc} or @samp{make check-g++} -in the @file{gcc} subdirectory of the object directory. To further cut down the -tests the following is possible: - -@example - make check-gcc RUNTESTFLAGS="execute.exp @var{other-options}" -@end example - -This will run all @command{gcc} execute tests in the testsuite. - -@example - make check-g++ RUNTESTFLAGS="old-deja.exp=9805* @var{other-options}" -@end example - -This will run the @command{g++} ``old-deja'' tests in the testsuite where the filename -matches @samp{9805*}. - -The @file{*.exp} files are located in the testsuite directories of the GCC -source, the most important ones being @file{compile.exp}, -@file{execute.exp}, @file{dg.exp} and @file{old-deja.exp}. -To get a list of the possible @file{*.exp} files, pipe the -output of @samp{make check} into a file and look at the -@samp{Running @dots{} .exp} lines. - -To run only the tests for a library, run @samp{make check} from the -the library's testsuite in a subdirectory of the object directory: -@file{libstdc++-v3/testsuite} or @file{libcgj/testsuite}. - -@section Additional testing for Java Class Libraries - -The @uref{http://sources.redhat.com/mauve/,,Mauve Project} provides -a suite of tests for the Java Class Libraries. This suite can be run -as part of libgcj testing by specifying the location of the Mauve tree -when invoking @samp{make}, as in @samp{make MAUVEDIR=~/mauve check}. - -@section How to interpret test results - -After the testsuite has run you'll find various @file{*.sum} and @file{*.log} -files in the testsuite subdirectories. The @file{*.log} files contain a -detailed log of the compiler invocations and the corresponding -results, the @file{*.sum} files summarize the results. These summaries list -all the tests that have been run with a corresponding status code: - -@itemize @bullet -@item -PASS: the test passed as expected -@item -XPASS: the test unexpectedly passed -@item -FAIL: the test unexpectedly failed -@item -XFAIL: the test failed as expected -@item -UNSUPPORTED: the test is not supported on this platform -@item -ERROR: the testsuite detected an error -@item -WARNING: the testsuite detected a possible problem -@end itemize - -It is normal for some tests to report unexpected failures. At the -current time our testing harness does not allow fine grained control -over whether or not a test is expected to fail. We expect to fix this -problem in future releases. - - -@section Submitting test results - -If you want to report the results to the GCC project, use the -@file{contrib/test_summary} shell script. Start it in the @var{objdir} with - -@example - @var{srcdir}/contrib/test_summary -p your_commentary.txt \ - -m gcc-testresults@@gcc.gnu.org |sh -@end example - -This script uses the @command{Mail} program to send the results, so -make sure it is in your @env{PATH}. The file @file{your_commentary.txt} is -prepended to the testsuite summary and should contain any special -remarks you have on your results or your build environment. Please -do not edit the testsuite result block or the subject line, as these -messages are automatically parsed and presented at the -@uref{http://gcc.gnu.org/testresults/,,GCC testresults} web -page. Here you can also gather information on how specific tests -behave on different platforms and compare them with your results. A -few failing testcases are possible even on released versions and you -should look here first if you think your results are unreasonable. - -@html -<hr /> -<p> -@end html -@ifhtml -@uref{./index.html,,Return to the GCC Installation page} -@end ifhtml -@end ifset - -@c ***Final install*********************************************************** -@ifnothtml -@comment node-name, next, previous, up -@node Final install, , Testing, Installing GCC -@end ifnothtml -@ifset finalinstallhtml -@ifnothtml -@chapter Installing GCC: Final installation -@end ifnothtml - -Now that GCC has been built (and optionally tested), you can install it with -@example -cd @var{objdir}; make install -@end example - -We strongly recommend to install into a target directory where there is -no previous version of GCC present. - -That step completes the installation of GCC; user level binaries can -be found in @file{@var{prefix}/bin} where @var{prefix} is the value you -specified with the @option{--prefix} to configure (or @file{/usr/local} -by default). (If you specified @option{--bindir}, that directory will -be used instead; otherwise, if you specified @option{--exec-prefix}, -@file{@var{exec-prefix}/bin} will be used.) Headers for the C++ and -Java libraries are installed in @file{@var{prefix}/include}; libraries -in @file{@var{libdir}} (normally @file{@var{prefix}/lib}); internal -parts of the compiler in @file{@var{libdir}/gcc-lib}; documentation in -info format in @file{@var{infodir}} (normally @file{@var{prefix}/info}). - -If you built a released version of GCC using @samp{make bootstrap} then please -quickly review the build status page for your release, available from -@uref{http://gcc.gnu.org/buildstat.html}. -If your system is not listed for the version of GCC that you built, -send a note to -@email{gcc@@gcc.gnu.org} indicating -that you successfully built and installed GCC. -Include the following information: - -@itemize @bullet -@item -Output from running @file{@var{srcdir}/config.guess}. Do not send us -that file itself, just the one-line output from running it. - -@item -The output of @samp{gcc -v} for your newly installed gcc. -This tells us which version of GCC you built and the options you passed to -configure. - -@item -Whether you enabled all languages or a subset of them. If you used a -full distribution then this information is part of the configure -options in the output of @samp{gcc -v}, but if you downloaded the -``core'' compiler plus additional front ends then it isn't apparent -which ones you built unless you tell us about it. - -@item -If the build was for GNU/Linux, also include: -@itemize @bullet -@item -The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3); -this information should be available from @file{/etc/issue}. - -@item -The version of the Linux kernel, available from @samp{uname --version} -or @samp{uname -a}. - -@item -The version of glibc you used; for RPM-based systems like Red Hat, -Mandrake, and SuSE type @samp{rpm -q glibc} to get the glibc version, -and on systems like Debian and Progeny use @samp{dpkg -l libc6}. -@end itemize -For other systems, you can include similar information if you think it is -relevant. - -@item -Any other information that you think would be useful to people building -GCC on the same configuration. The new entry in the build status list -will include a link to the archived copy of your message. -@end itemize - -We'd also like to know if the -@ifnothtml -@ref{Specific, host/target specific installation notes} -@end ifnothtml -@ifhtml -@uref{specific.html,,host/target specific installation notes} -@end ifhtml -didn't include your host/target information or if that information is -incomplete or out of date. Send a note to -@email{gcc@@gcc.gnu.org} telling us how the information should be changed. - -If you find a bug, please report it following our -@uref{../bugs.html,,bug reporting guidelines}. - -If you want to print the GCC manuals, do @samp{cd @var{objdir}; make -dvi}. You will need to have @command{texi2dvi} (version at least 4.1) -and @TeX{} installed. This creates a number of @file{.dvi} files in -subdirectories of @file{@var{objdir}}; these may be converted for -printing with programs such as @command{dvips}. You can also -@uref{http://www.gnu.org/order/order.html,,buy printed manuals from the -Free Software Foundation}, though such manuals may not be for the most -recent version of GCC@. - -@html -<hr /> -<p> -@end html -@ifhtml -@uref{./index.html,,Return to the GCC Installation page} -@end ifhtml -@end ifset - -@c ***Binaries**************************************************************** -@ifnothtml -@comment node-name, next, previous, up -@node Binaries, Specific, Installing GCC, Top -@end ifnothtml -@ifset binarieshtml -@ifnothtml -@chapter Installing GCC: Binaries -@end ifnothtml -@cindex Binaries -@cindex Installing GCC: Binaries - -We are often asked about pre-compiled versions of GCC@. While we cannot -provide these for all platforms, below you'll find links to binaries for -various platforms where creating them by yourself is not easy due to various -reasons. - -Please note that we did not create these binaries, nor do we -support them. If you have any problems installing them, please -contact their makers. - -@itemize -@item -AIX: -@itemize -@item -@uref{http://www.bullfreeware.com,,Bull's Freeware and Shareware Archive for AIX}; - -@item -@uref{http://aixpdslib.seas.ucla.edu,,UCLA Software Library for AIX}. -@end itemize - -@item -DOS---@uref{http://www.delorie.com/djgpp/,,DJGPP}. - -@item -Hitachi H8/300[HS]---@uref{http://h8300-hms.sourceforge.net/,,GNU -Development Tools for the Hitachi H8/300[HS] Series}. - -@item -HP-UX: -@itemize -@item -@uref{http://hpux.cae.wisc.edu/,,HP-UX Porting Center}; - -@item -@uref{ftp://sunsite.informatik.rwth-aachen.de/pub/packages/gcc_hpux/,,Binaries for HP-UX 11.00 at Aachen University of Technology}. -@end itemize - -@item -@uref{http://www.sco.com/skunkware/devtools/index.html#gcc,,SCO -OpenServer/Unixware}. - -@item -Sinix/Reliant Unix---@uref{ftp://ftp.siemens.de/sni/mr/pd/gnu/gcc,,Siemens}. - -@item -Solaris 2 (SPARC, Intel)---@uref{http://www.sunfreeware.com/,,Sunfreeware}. - -@item -SGI---@uref{http://freeware.sgi.com/,,SGI Freeware}. - -@item -Windows 95, 98, and NT: -@itemize -@item -The @uref{http://sources.redhat.com/cygwin/,,Cygwin} project; -@item -The @uref{http://www.mingw.org/,,MinGW} project. -@end itemize - -@item -@uref{ftp://ftp.thewrittenword.com/packages/free/by-name/,,The -Written Word} offers binaries for Solaris 2.5.1, 2.6, 2.7/SPARC, 2.7/Intel, -IRIX 6.2, 6.5, Digital UNIX 4.0D, HP-UX 10.20, and HP-UX 11.00. - -@end itemize - -In addition to those specific offerings, you can get a binary -distribution CD-ROM from the -@uref{http://www.fsf.org/order/order.html,,Free Software Foundation}. -It contains binaries for a number of platforms, and -includes not only GCC, but other stuff as well. The current CD does -not contain the latest version of GCC, but it should allow -bootstrapping the compiler. An updated version of that disk is in the -works. - -@html -<hr /> -<p> -@end html -@ifhtml -@uref{./index.html,,Return to the GCC Installation page} -@end ifhtml -@end ifset - -@c ***Specific**************************************************************** -@ifnothtml -@comment node-name, next, previous, up -@node Specific, Old, Binaries, Top -@end ifnothtml -@ifset specifichtml -@ifnothtml -@chapter Host/target specific installation notes for GCC -@end ifnothtml -@cindex Specific -@cindex Specific installation notes -@cindex Target specific installation -@cindex Host specific installation -@cindex Target specific installation notes - -Please read this document carefully @emph{before} installing the -GNU Compiler Collection on your machine. - -@ifhtml -@itemize -@item -@uref{#1750a-*-*,,1750a-*-*} -@item -@uref{#a29k,,a29k} -@item -@uref{#a29k-*-bsd,,a29k-*-bsd} -@item -@uref{#alpha*-*-*,,alpha*-*-*} -@item -@uref{#alpha*-dec-osf*,,alpha*-dec-osf*} -@item -@uref{#alphaev5-cray-unicosmk*,,alphaev5-cray-unicosmk*} -@item -@uref{#arc-*-elf,,arc-*-elf} -@item -@uref{#arm-*-aout,,arm-*-aout} -@item -@uref{#arm-*-elf,,arm-*-elf} -@item -@uref{#arm*-*-linux-gnu,,arm*-*-linux-gnu} -@item -@uref{#arm-*-riscix,,arm-*-riscix} -@item -@uref{#avr,,avr} -@item -@uref{#c4x,,c4x} -@item -@uref{#dos,,DOS} -@item -@uref{#dsp16xx,,dsp16xx} -@item -@uref{#elxsi-elxsi-bsd,,elxsi-elxsi-bsd} -@item -@uref{#*-*-freebsd*,,*-*-freebsd*} -@item -@uref{#h8300-hms,,h8300-hms} -@item -@uref{#hppa*-hp-hpux*,,hppa*-hp-hpux*} -@item -@uref{#hppa*-hp-hpux9,,hppa*-hp-hpux9} -@item -@uref{#hppa*-hp-hpux10,,hppa*-hp-hpux10} -@item -@uref{#hppa*-hp-hpux11,,hppa*-hp-hpux11} -@item -@uref{#i370-*-*,,i370-*-*} -@item -@uref{#*-*-linux-gnu,,*-*-linux-gnu} -@item -@uref{#ix86-*-linux*oldld,,i?86-*-linux*oldld} -@item -@uref{#ix86-*-linux*aout,,i?86-*-linux*aout} -@item -@uref{#ix86-*-linux*,,i?86-*-linux*} -@item -@uref{#ix86-*-sco,,i?86-*-sco} -@item -@uref{#ix86-*-sco3.2v4,,i?86-*-sco3.2v4} -@item -@uref{#ix86-*-sco3.2v5*,,i?86-*-sco3.2v5*} -@item -@uref{#ix86-*-udk,,i?86-*-udk} -@item -@uref{#ix86-*-isc,,i?86-*-isc} -@item -@uref{#ix86-*-esix,,i?86-*-esix} -@item -@uref{#ix86-ibm-aix,,i?86-ibm-aix} -@item -@uref{#ix86-sequent-bsd,,i?86-sequent-bsd} -@item -@uref{#ix86-sequent-ptx1*,,i?86-sequent-ptx1*, i?86-sequent-ptx2*, i?86-sequent-sysv3*} -@item -@uref{#i860-intel-osf*,,i860-intel-osf*} -@item -@uref{#ia64-*-linux,,ia64-*-linux} -@item -@uref{#*-lynx-lynxos,,*-lynx-lynxos} -@item -@uref{#*-ibm-aix*,,*-ibm-aix*} -@item -@uref{#m32r-*-elf,,m32r-*-elf} -@item -@uref{#m68000-hp-bsd,,m68000-hp-bsd} -@item -@uref{#m6811-elf,,m6811-elf} -@item -@uref{#m6812-elf,,m6812-elf} -@item -@uref{#m68k-altos,,m68k-altos} -@item -@uref{#m68k-apple-aux,,m68k-apple-aux} -@item -@uref{#m68k-att-sysv,,m68k-att-sysv} -@item -@uref{#m68k-bull-sysv,,m68k-bull-sysv} -@item -@uref{#m68k-crds-unos,,m68k-crds-unos} -@item -@uref{#m68k-hp-hpux,,m68k-hp-hpux} -@item -@uref{#m68k-*-nextstep*,,m68k-*-nextstep*} -@item -@uref{#m68k-ncr-*,,m68k-ncr-*} -@item -@uref{#m68k-sun,,m68k-sun} -@item -@uref{#m68k-sun-sunos4.1.1,,m68k-sun-sunos4.1.1} -@item -@uref{#m88k-*-svr3,,m88k-*-svr3} -@item -@uref{#m88k-*-dgux,,m88k-*-dgux} -@item -@uref{#m88k-tektronix-sysv3,,m88k-tektronix-sysv3} -@item -@uref{#mips-*-*,,mips-*-*} -@item -@uref{#mips-dec-*,,mips-dec-*} -@item -@uref{#mips-mips-bsd,,mips-mips-bsd} -@item -@uref{#mips-mips-riscos*,,mips-mips-riscos*} -@item -@uref{#mips-sgi-irix4,,mips-sgi-irix4} -@item -@uref{#mips-sgi-irix5,,mips-sgi-irix5} -@item -@uref{#mips-sgi-irix6,,mips-sgi-irix6} -@item -@uref{#mips-sony-sysv,,mips-sony-sysv} -@item -@uref{#ns32k-encore,,ns32k-encore} -@item -@uref{#ns32k-*-genix,,ns32k-*-genix} -@item -@uref{#ns32k-sequent,,ns32k-sequent} -@item -@uref{#ns32k-utek,,ns32k-utek} -@item -@uref{#powerpc*-*-*,,powerpc*-*-*, powerpc-*-sysv4} -@item -@uref{#powerpc-*-darwin*,,powerpc-*-darwin*} -@item -@uref{#powerpc-*-elf,,powerpc-*-elf, powerpc-*-sysv4} -@item -@uref{#powerpc-*-linux-gnu*,,powerpc-*-linux-gnu*} -@item -@uref{#powerpc-*-netbsd*,,powerpc-*-netbsd*} -@item -@uref{#powerpc-*-eabiaix,,powerpc-*-eabiaix} -@item -@uref{#powerpc-*-eabisim,,powerpc-*-eabisim} -@item -@uref{#powerpc-*-eabi,,powerpc-*-eabi} -@item -@uref{#powerpcle-*-elf,,powerpcle-*-elf, powerpcle-*-sysv4} -@item -@uref{#powerpcle-*-eabisim,,powerpcle-*-eabisim} -@item -@uref{#powerpcle-*-eabi,,powerpcle-*-eabi} -@item -@uref{#powerpcle-*-winnt,,powerpcle-*-winnt, powerpcle-*-pe} -@item -@uref{#romp-*-aos,,romp-*-aos, romp-*-mach} -@item -@uref{#s390-*-linux*} -@item -@uref{#s390x-*-linux*} -@item -@uref{#*-*-solaris2*,,*-*-solaris2*} -@item -@uref{#sparc-sun-solaris2*,,sparc-sun-solaris2*} -@item -@uref{#sparc-sun-solaris2.7,,sparc-sun-solaris2.7} -@item -@uref{#sparc-sun-sunos4*,,sparc-sun-sunos4*} -@item -@uref{#sparc-unknown-linux-gnulibc1,,sparc-unknown-linux-gnulibc1} -@item -@uref{#sparc-*-linux*,,sparc-*-linux*} -@item -@uref{#sparc64-*-*,,sparc64-*-*} -@item -@uref{#sparcv9-*-solaris2*,,sparcv9-*-solaris2*} -@item -@uref{#*-*-sysv*,,*-*-sysv*} -@item -@uref{#vax-dec-ultrix,,vax-dec-ultrix} -@item -@uref{#we32k-*-*,,we32k-*-*} -@item -@uref{#xtensa-*-elf,,xtensa-*-elf} -@item -@uref{#xtensa-*-linux*,,xtensa-*-linux*} -@item -@uref{#windows,,Microsoft Windows} -@item -@uref{#os2,,OS/2} -@item -@uref{#older,,Older systems} -@end itemize - -@itemize -@item -@uref{#elf_targets,,all ELF targets} (SVR4, Solaris 2, etc.) -@end itemize -@end ifhtml - - -@html -<!-- -------- host/target specific issues start here ---------------- --> -<hr /> -@end html -@heading @anchor{1750a-*-*}1750a-*-* -MIL-STD-1750A processors. This target is obsoleted in GCC 3.1. - -The MIL-STD-1750A cross configuration produces output for -@code{as1750}, an assembler/linker available under the GNU General Public -License for the 1750A@. @code{as1750} can be obtained at -@uref{ftp://ftp.fta-berlin.de/pub/crossgcc/1750gals/}. -A similarly licensed simulator for -the 1750A is available from same address. - -You should ignore a fatal error during the building of @samp{libgcc} -(@samp{libgcc} is not yet implemented for the 1750A@.) - -The @code{as1750} assembler requires the file @file{ms1750.inc}, which is -found in the directory @file{gcc/config/1750a}. - -GCC produced the same sections as the Fairchild F9450 C Compiler, -namely: - -@table @code -@item Normal -The program code section. - -@item Static -The read/write (RAM) data section. - -@item Konst -The read-only (ROM) constants section. - -@item Init -Initialization section (code to copy KREL to SREL)@. -@end table - -The smallest addressable unit is 16 bits (@code{BITS_PER_UNIT} is 16). This -means that type @code{char} is represented with a 16-bit word per character. -The 1750A's ``Load/Store Upper/Lower Byte'' instructions are not used by -GCC@. - -@html -<hr /> -@end html -@heading @anchor{a29k}a29k -AMD Am29k-family processors. These are normally used in embedded -applications. This configuration corresponds to AMD's standard calling -sequence and binary interface and is compatible with other 29k tools. - -AMD has abandoned this processor. All existing a29k targets are obsoleted -in GCC 3.1. - -You may need to make a variant of the file @file{a29k.h} for your -particular configuration. - -@html -<hr /> -@end html -@heading @anchor{a29k-*-bsd}a29k-*-bsd -AMD Am29050 used in a system running a variant of BSD Unix. - -@html -<hr /> -@end html -@heading @anchor{alpha*-*-*}alpha*-*-* - -This section contains general configuration information for all -alpha-based platforms using ELF (in particular, ignore this section for -DEC OSF/1, Digital UNIX and Tru64 UNIX)@. In addition to reading this -section, please read all other sections that match your target. - -We require binutils 2.11.2 or newer. -Previous binutils releases had a number of problems with DWARF 2 -debugging information, not the least of which is incorrect linking of -shared libraries. - -@html -<hr /> -@end html -@heading @anchor{alpha*-dec-osf*}alpha*-dec-osf* -Systems using processors that implement the DEC Alpha architecture and -are running the DEC/Compaq Unix (DEC OSF/1, Digital UNIX, or Compaq -Tru64 UNIX) operating system, for example the DEC Alpha AXP systems. - -Support for versions before @code{alpha*-dec-osf4} is obsoleted in GCC -3.1. (These are the versions which identify themselves as DEC OSF/1.) - -In Digital Unix V4.0, virtual memory exhausted bootstrap failures -may be fixed by configuring with @option{--with-gc=simple}, -reconfiguring Kernel Virtual Memory and Swap parameters -per the @command{/usr/sbin/sys_check} Tuning Suggestions, -or applying the patch in -@uref{http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html}. - -In Tru64 UNIX V5.1, Compaq introduced a new assembler that does not -currently (2001-06-13) work with @command{mips-tfile}. As a workaround, -we need to use the old assembler, invoked via the barely documented -@option{-oldas} option. To bootstrap GCC, you either need to use the -Compaq C Compiler: - -@example - % CC=cc @var{srcdir}/configure [@var{options}] [@var{target}] -@end example - -or you can use a copy of GCC 2.95.3 or higher built on Tru64 UNIX V4.0: - -@example - % CC=gcc -Wa,-oldas @var{srcdir}/configure [@var{options}] [@var{target}] -@end example - -As of GNU binutils 2.11.2, neither GNU @command{as} nor GNU @command{ld} -are supported on Tru64 UNIX, so you must not configure GCC with -@option{--with-gnu-as} or @option{--with-gnu-ld}. - -The @option{--enable-threads} options isn't supported yet. A patch is -in preparation for a future release. - -GCC writes a @samp{.verstamp} directive to the assembler output file -unless it is built as a cross-compiler. It gets the version to use from -the system header file @file{/usr/include/stamp.h}. If you install a -new version of DEC Unix, you should rebuild GCC to pick up the new version -stamp. - -Note that since the Alpha is a 64-bit architecture, cross-compilers from -32-bit machines will not generate code as efficient as that generated -when the compiler is running on a 64-bit machine because many -optimizations that depend on being able to represent a word on the -target in an integral value on the host cannot be performed. Building -cross-compilers on the Alpha for 32-bit machines has only been tested in -a few cases and may not work properly. - -@code{make compare} may fail on old versions of DEC Unix unless you add -@option{-save-temps} to @code{CFLAGS}. On these systems, the name of the -assembler input file is stored in the object file, and that makes -comparison fail if it differs between the @code{stage1} and -@code{stage2} compilations. The option @option{-save-temps} forces a -fixed name to be used for the assembler input file, instead of a -randomly chosen name in @file{/tmp}. Do not add @option{-save-temps} -unless the comparisons fail without that option. If you add -@option{-save-temps}, you will have to manually delete the @samp{.i} and -@samp{.s} files after each series of compilations. - -GCC now supports both the native (ECOFF) debugging format used by DBX -and GDB and an encapsulated STABS format for use only with GDB@. See the -discussion of the @option{--with-stabs} option of @file{configure} above -for more information on these formats and how to select them. - -There is a bug in DEC's assembler that produces incorrect line numbers -for ECOFF format when the @samp{.align} directive is used. To work -around this problem, GCC will not emit such alignment directives -while writing ECOFF format debugging information even if optimization is -being performed. Unfortunately, this has the very undesirable -side-effect that code addresses when @option{-O} is specified are -different depending on whether or not @option{-g} is also specified. - -To avoid this behavior, specify @option{-gstabs+} and use GDB instead of -DBX@. DEC is now aware of this problem with the assembler and hopes to -provide a fix shortly. - -@html -<hr /> -@end html -@heading @anchor{alphaev5-cray-unicosmk*}alphaev5-cray-unicosmk* -Cray T3E systems running Unicos/Mk. - -This port is incomplete and has many known bugs. We hope to improve the -support for this target soon. Currently, only the C front end is supported, -and it is not possible to build parallel applications. Cray modules are not -supported; in particular, Craylibs are assumed to be in -@file{/opt/ctl/craylibs/craylibs}. - -You absolutely @strong{must} use GNU make on this platform. Also, you -need to tell GCC where to find the assembler and the linker. The -simplest way to do so is by providing @option{--with-as} and -@option{--with-ld} to @file{configure}, e.g.@: - -@example - configure --with-as=/opt/ctl/bin/cam --with-ld=/opt/ctl/bin/cld \ - --enable-languages=c -@end example - -The comparison test during @samp{make bootstrap} fails on Unicos/Mk -because the assembler inserts timestamps into object files. You should -be able to work around this by doing @samp{make all} after getting this -failure. - -@html -<hr /> -@end html -@heading @anchor{arc-*-elf}arc-*-elf -Argonaut ARC processor. -This configuration is intended for embedded systems. - -@html -<hr /> -@end html -@heading @anchor{arm-*-aout}arm-*-aout -Advanced RISC Machines ARM-family processors. These are often used in -embedded applications. There are no standard Unix configurations. -This configuration corresponds to the basic instruction sequences and will -produce @file{a.out} format object modules. - -You may need to make a variant of the file @file{arm.h} for your particular -configuration. - -@html -<hr /> -@end html -@heading @anchor{arm-*-elf}arm-*-elf -This configuration is intended for embedded systems. - -@html -<hr /> -@end html -@heading @anchor{arm*-*-linux-gnu}arm*-*-linux-gnu - -We require GNU binutils 2.10 or newer. - -@html -<hr /> -@end html -@heading @anchor{arm-*-riscix}arm-*-riscix -The ARM2 or ARM3 processor running RISC iX, Acorn's port of BSD Unix. -This configuration is obsoleted in GCC 3.1. - -If you are running a version of RISC iX prior to 1.2 then you must -specify the version number during configuration. Note that the -assembler shipped with RISC iX does not support stabs debugging -information; a new version of the assembler, with stabs support -included, is now available from Acorn and via ftp -@uref{ftp://ftp.acorn.com/pub/riscix/as+xterm.tar.Z}. To enable stabs -debugging, pass @option{--with-gnu-as} to configure. - -You will need to install GNU @command{sed} before you can run configure. - -@html -<hr /> -@end html -@heading @anchor{avr}avr - -ATMEL AVR-family micro controllers. These are used in embedded -applications. There are no standard Unix configurations. -@ifnothtml -@xref{AVR Options,, AVR Options, gcc, Using and Porting the GNU Compiler -Collection (GCC)}, -@end ifnothtml -@ifhtml -See ``AVR Options'' in the main manual -@end ifhtml -for the list of supported MCU types. - -Use @samp{configure --target=avr --enable-languages="c"} to configure GCC@. - -Further installation notes and other useful information about AVR tools -can also be obtained from: - -@itemize @bullet -@item -@uref{http://home.overta.ru/users/denisc,,http://home.overta.ru/users/denisc} -@item -@uref{http://www.amelek.gda.pl/avr,,http://www.amelek.gda.pl/avr} -@end itemize - -We @emph{strongly} recommend using binutils 2.11 or newer. - -The following error: -@example - Error: register required -@end example - -indicates that you should upgrade to a newer version of the binutils. - -@html -<hr /> -@end html -@heading @anchor{c4x}c4x - -Texas Instruments TMS320C3x and TMS320C4x Floating Point Digital Signal -Processors. These are used in embedded applications. There are no -standard Unix configurations. -@ifnothtml -@xref{TMS320C3x/C4x Options,, TMS320C3x/C4x Options, gcc, Using and -Porting the GNU Compiler Collection (GCC)}, -@end ifnothtml -@ifhtml -See ``TMS320C3x/C4x Options'' in the main manual -@end ifhtml -for the list of supported MCU types. - -GCC can be configured as a cross compiler for both the C3x and C4x -architectures on the same system. Use @samp{configure --target=c4x ---enable-languages="c,c++"} to configure. - - -Further installation notes and other useful information about C4x tools -can also be obtained from: - -@itemize @bullet -@item -@uref{http://www.elec.canterbury.ac.nz/c4x/,,http://www.elec.canterbury.ac.nz/c4x/} -@end itemize - -@html -<hr /> -@end html -@heading @anchor{cris}CRIS - -CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip -series. These are used in embedded applications. - -@ifnothtml -@xref{CRIS Options,, CRIS Options, gcc, Using and Porting the GNU Compiler -Collection (GCC)}, -@end ifnothtml -@ifhtml -See ``CRIS Options'' in the main manual -@end ifhtml -for a list of CRIS-specific options. - -There are a few different CRIS targets: -@table @code -@item cris-axis-aout -Old target. Includes a multilib for the @samp{elinux} a.out-based -target. No multilibs for newer architecture variants. -@item cris-axis-elf -Mainly for monolithic embedded systems. Includes a multilib for the -@samp{v10} core used in @samp{ETRAX 100 LX}. -@item cris-axis-linux-gnu -A GNU/Linux port for the CRIS architecture, currently targeting -@samp{ETRAX 100 LX} by default. -@end table - -For @code{cris-axis-aout} and @code{cris-axis-elf} you need binutils 2.11 -or newer. For @code{cris-axis-linux-gnu} you need binutils 2.12 or newer. - -Pre-packaged tools can be obtained from -@uref{ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/}. More -information about this platform is available at -@uref{http://developer.axis.com/}. - -@html -<hr /> -@end html -@heading @anchor{dos}DOS - -Please have a look at our @uref{binaries.html,,binaries page}. - -You cannot install GCC by itself on MSDOS; it will not compile under -any MSDOS compiler except itself. You need to get the complete -compilation package DJGPP, which includes binaries as well as sources, -and includes all the necessary compilation tools and libraries. - -@html -<hr /> -@end html -@heading @anchor{dsp16xx}dsp16xx -A port to the AT&T DSP1610 family of processors. - -@html -<hr /> -@end html -@heading @anchor{*-*-freebsd*}*-*-freebsd* - -The version of binutils installed in @file{/usr/bin} is known to work unless -otherwise specified in any per-architecture notes. However, binutils -2.12.1 or greater is known to improve overall testsuite results. - -For FreeBSD 1, FreeBSD 2 or any mutant a.out versions of FreeBSD 3: All -configuration support and files as shipped with GCC 2.95 are still in -place. FreeBSD 2.2.7 has been known to bootstrap completely; however, -it is unknown which version of binutils was used (it is assumed that it -was the system copy in @file{/usr/bin}) and C++ EH failures were noted. - -Support for FreeBSD 1 is obsoleted in GCC 3.1. - -For FreeBSD using the ELF file format: DWARF 2 debugging is now the -default for all CPU architectures. It had been the default on -FreeBSD/alpha since its inception. You may use @option{-gstabs} instead -of @option{-g}, if you really want the old debugging format. There are -no known issues with mixing object files and libraries with different -debugging formats. Otherwise, this release of GCC should now match more -of the configuration used in the stock FreeBSD configuration of GCC. In -particular, @option{--enable-threads} is now configured by default. -However, as a general user, do not attempt to replace the system -compiler with this release. Known to bootstrap and check with good -results on FreeBSD 3.0, 3.4, 4.0, 4.2, 4.3, 4.4, 4.5-STABLE and 5-CURRENT@. - -In principle, @option{--enable-threads} is now compatible with -@option{--enable-libgcj} on FreeBSD@. However, it has only been built -and tested on @samp{i386-*-freebsd4.5} and @samp{alpha-*-freebsd5.0}. -The static -library may be incorrectly built (symbols are missing at link time). -There is a rare timing-based startup hang (probably involves an -assupmtion about the thread library). Multi-threaded boehm-gc (required for -libjava) exposes severe threaded signal-handling bugs on FreeBSD before -4.5-RELEASE. The alpha port may not fully bootstrap without some manual -intervention: @command{gcjh} will crash with a floating-point exception while -generating @file{java/lang/Double.h} (just copy the version built on -@samp{i386-*-freebsd*} and rerun the top-level @command{gmake} with no -arguments and it -should properly complete the bootstrap). Other CPU architectures -supported by FreeBSD will require additional configuration tuning in, at -the very least, both boehm-gc and libffi. - -Shared @file{libgcc_s.so} is now built and installed by default. - -@html -<hr /> -@end html -@heading @anchor{elxsi-elxsi-bsd}elxsi-elxsi-bsd -The Elxsi's C compiler has known limitations that prevent it from -compiling GCC@. Please contact @email{mrs@@wrs.com} for more details. - -Support for this processor is obsoleted in GCC 3.1. - -@html -<hr /> -@end html -@heading @anchor{h8300-hms}h8300-hms -Hitachi H8/300 series of processors. - -Please have a look at our @uref{binaries.html,,binaries page}. - -The calling convention and structure layout has changed in release 2.6. -All code must be recompiled. The calling convention now passes the -first three arguments in function calls in registers. Structures are no -longer a multiple of 2 bytes. - -@html -<hr /> -@end html -@heading @anchor{hppa*-hp-hpux*}hppa*-hp-hpux* - -We @emph{highly} recommend using gas/binutils 2.8 or newer on all hppa -platforms; you may encounter a variety of problems when using the HP -assembler. The HP assembler does not work with the @samp{hppa64-hp-hpux11*} -port. - -Specifically, @option{-g} does not work on HP-UX (since that system -uses a peculiar debugging format which GCC does not know about), unless you -use GAS and GDB and configure GCC with the -@uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and -@option{--with-as=@dots{}} options. - -If you wish to use the pa-risc 2.0 architecture support with a 32-bit -runtime, you must use either the HP assembler, gas/binutils 2.11 or newer, -or a recent -@uref{ftp://sources.redhat.com/pub/binutils/snapshots,,snapshot of gas}. - -More specific information to @samp{hppa*-hp-hpux*} targets follows. - -@html -<hr /> -@end html -@heading @anchor{hppa*-hp-hpux9}hppa*-hp-hpux9 - -The HP assembler has major problems on this platform. We've tried to work -around the worst of the problems. However, those workarounds may be causing -linker crashes in some circumstances; the workarounds also probably prevent -shared libraries from working. Use the GNU assembler to avoid these problems. - - -The configuration scripts for GCC will also trigger a bug in the hpux9 -shell. To avoid this problem set @env{CONFIG_SHELL} to @file{/bin/ksh} -and @env{SHELL} to @file{/bin/ksh} in your environment. - - -@html -<hr /> -@end html -@heading @anchor{hppa*-hp-hpux10}hppa*-hp-hpux10 - -For hpux10.20, we @emph{highly} recommend you pick up the latest sed patch -@code{PHCO_19798} from HP@. HP has two sites which provide patches free of -charge: - -@itemize @bullet -@item -@html -<a href="http://us-support.external.hp.com">US, Canada, Asia-Pacific, and -Latin-America</a> -@end html -@ifnothtml -@uref{http://us-support.external.hp.com,,}US, Canada, Asia-Pacific, and -Latin-America -@end ifnothtml -@item -@uref{http://europe-support.external.hp.com,,Europe} -@end itemize - -The HP assembler on these systems is much better than the hpux9 assembler, -but still has some problems. Most notably the assembler inserts timestamps -into each object file it creates, causing the 3-stage comparison test to fail -during a @samp{make bootstrap}. You should be able to continue by -saying @samp{make all} after getting the failure from @samp{make -bootstrap}. - - -@html -<hr /> -@end html -@heading @anchor{hppa*-hp-hpux11}hppa*-hp-hpux11 - -GCC 3.0 and up support HP-UX 11. On 64-bit capable systems, there -are two distinct ports. The @samp{hppa2.0w-hp-hpux11*} port generates -code for the 32-bit pa-risc runtime architecture. It uses the HP -linker and is currently the default selected by config.guess. The -optional @samp{hppa64-hp-hpux11*} port generates 64-bit code for the -pa-risc 2.0 architecture. It must be explicitly selected using the -@samp{--host=hppa64-hp-hpux11*} configure option. Different prefixes -must be used if both ports are to be installed on the same system. - -You must use GNU binutils 2.11 or above with the 32-bit port. Thread -support is not currently implemented, so @option{--enable-threads} does -not work. See: - -@itemize -@item @uref{http://gcc.gnu.org/ml/gcc-prs/2002-01/msg00551.html} -@item @uref{http://gcc.gnu.org/ml/gcc-bugs/2002-01/msg00663.html}. -@end itemize - -GCC 2.95.x is not supported under HP-UX 11 and cannot be used to -compile GCC 3.0 and up. Refer to @uref{binaries.html,,binaries} for -information about obtaining precompiled GCC binaries for HP-UX. - -GNU binutils 2.13 or later is recommended with the 64-bit port. -The HP assembler is not supported. It is @emph{highly} recommended -that the GNU linker be used as well. Either binutils must be built -prior to gcc, or a binary distribution of gcc or binutils must be -obtained for the initial builds. When starting with a HP compiler, -it is preferable to use the ANSI compiler as the bundled compiler -only supports traditional C. Bootstrapping with the bundled compiler -is tested infrequently and problems often arise because of the subtle -differences in semantics between traditional and ISO C. There also -have been problems reported with various binary distributions. This -port still is undergoing significant development. - -@html -<hr /> -@end html -@heading @anchor{i370-*-*}i370-*-* -This port is very preliminary and has many known bugs. We hope to -have a higher-quality port for this machine soon. - -@html -<hr /> -@end html -@heading @anchor{*-*-linux-gnu}*-*-linux-gnu - -If you use glibc 2.2 (or 2.1.9x), GCC 2.95.2 won't install -out-of-the-box. You'll get compile errors while building @samp{libstdc++}. -The patch @uref{glibc-2.2.patch,,glibc-2.2.patch}, that is to be -applied in the GCC source tree, fixes the compatibility problems. - -@html -@end html - -@html -<p> -@end html - -Currently Glibc 2.2.3 (and older releases) and GCC 3.0 are out of sync -since the latest exception handling changes for GCC@. Compiling glibc -with GCC 3.0 will give a binary incompatible glibc and therefore cause -lots of problems and might make your system completly unusable. This -will definitly need fixes in glibc but might also need fixes in GCC@. We -strongly advise to wait for glibc 2.2.4 and to read the release notes of -glibc 2.2.4 whether patches for GCC 3.0 are needed. You can use glibc -2.2.3 with GCC 3.0, just do not try to recompile it. - -@html -<hr /> -@end html -@heading @anchor{ix86-*-linux*oldld}i?86-*-linux*oldld -Use this configuration to generate @file{a.out} binaries on Linux-based -GNU systems if you do not have gas/binutils version 2.5.2 or later -installed. - -This configuration is obsoleted in GCC 3.1. - -@html -<hr /> -@end html -@heading @anchor{ix86-*-linux*aout}i?86-*-linux*aout -Use this configuration to generate @file{a.out} binaries on Linux-based -GNU systems. This configuration is being superseded. You must use -gas/binutils version 2.5.2 or later. - -@html -<hr /> -@end html -@heading @anchor{ix86-*-linux*}i?86-*-linux* - -You will need binutils 2.9.1.0.15 or newer for exception handling to work. - -If you receive Signal 11 errors when building on GNU/Linux, then it is -possible you have a hardware problem. Further information on this can be -found on @uref{http://www.bitwizard.nl/sig11/,,www.bitwizard.nl}. - -@html -<hr /> -@end html -@heading @anchor{ix86-*-sco}i?86-*-sco -Compilation with RCC is recommended. Also, it may be a good idea to -link with GNU malloc instead of the malloc that comes with the system. - -@html -<hr /> -@end html -@heading @anchor{ix86-*-sco3.2v4}i?86-*-sco3.2v4 -Use this configuration for SCO release 3.2 version 4. - -@html -<hr /> -@end html -@heading @anchor{ix86-*-sco3.2v5*}i?86-*-sco3.2v5* -Use this for the SCO OpenServer Release 5 family of operating systems. - -Unlike earlier versions of GCC, the ability to generate COFF with this -target is no longer provided. - -Earlier versions of GCC emitted DWARF 1 when generating ELF to allow -the system debugger to be used. That support was too burdensome to -maintain. GCC now emits only DWARF 2 for this target. This means you -may use either the UDK debugger or GDB to debug programs built by this -version of GCC@. - -Use of the @option{-march=pentiumpro} flag can result in -unrecognized opcodes when using the native assembler on OS versions before -5.0.6. (Support for P6 opcodes was added to the native ELF assembler in -that version.) While it's rather rare to see these emitted by GCC yet, -errors of the basic form: - -@example - /usr/tmp/ccaNlqBc.s:22:unknown instruction: fcomip - /usr/tmp/ccaNlqBc.s:50:unknown instruction: fucomip -@end example - -are symptoms of this problem. You may work around this by not -building affected files with that flag, by using the GNU assembler, or -by using the assembler provided with the current version of the OS@. -Users of GNU assembler should see the note below for hazards on doing -so. - -The native SCO assembler that is provided with the OS at no -charge is normally required. If, however, you must be able to use -the GNU assembler (perhaps you're compiling code with asms that -require GAS syntax) you may configure this package using the flags -@uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}}. You must -use a recent version of GNU binutils; versions past 2.9.1 seem to work -well. - -In general, the @option{--with-gnu-as} option isn't as well tested -as the native assembler. - -Look in @file{gcc/config/i386/sco5.h} (search for ``messy'') for -additional OpenServer-specific flags. - -Systems based on OpenServer before 5.0.4 (@samp{uname -X} -will tell you what you're running) require TLS597 from -@uref{ftp://ftp.sco.com/TLS/,,ftp://ftp.sco.com/TLS/} -for C++ constructors and destructors to work right. - -The system linker in (at least) 5.0.4 and 5.0.5 will sometimes -do the wrong thing for a construct that GCC will emit for PIC -code. This can be seen as execution testsuite failures when using -@option{-fPIC} on @file{921215-1.c}, @file{931002-1.c}, @file{nestfunc-1.c}, and @file{gcov-1.c}. -For 5.0.5, an updated linker that will cure this problem is -available. You must install both -@uref{ftp://ftp.sco.com/Supplements/rs505a/,,ftp://ftp.sco.com/Supplements/rs505a/} -and @uref{ftp://ftp.sco.com/SLS/,,OSS499A}. - -The dynamic linker in OpenServer 5.0.5 (earlier versions may show -the same problem) aborts on certain G77-compiled programs. It's particularly -likely to be triggered by building Fortran code with the @option{-fPIC} flag. -Although it's conceivable that the error could be triggered by other -code, only G77-compiled code has been observed to cause this abort. -If you are getting core dumps immediately upon execution of your -G77 program---and especially if it's compiled with @option{-fPIC}---try applying -@uref{sco_osr5_g77.patch,,@file{sco_osr5_g77.patch}} to your @samp{libf2c} and -rebuilding GCC@. -Affected faults, when analyzed in a debugger, will show a stack -backtrace with a fault occurring in @code{rtld()} and the program -running as @file{/usr/lib/ld.so.1}. This problem has been reported to SCO -engineering and will hopefully be addressed in later releases. - - -@html -<hr /> -@end html -@heading @anchor{ix86-*-udk}i?86-*-udk - -This target emulates the SCO Universal Development Kit and requires that -package be installed. (If it is installed, you will have a -@file{/udk/usr/ccs/bin/cc} file present.) It's very much like the -@samp{i?86-*-unixware7*} target -but is meant to be used when hosting on a system where UDK isn't the -default compiler such as OpenServer 5 or Unixware 2. This target will -generate binaries that will run on OpenServer, Unixware 2, or Unixware 7, -with the same warnings and caveats as the SCO UDK@. - -This target is a little tricky to build because we have to distinguish -it from the native tools (so it gets headers, startups, and libraries -from the right place) while making the tools not think we're actually -building a cross compiler. The easiest way to do this is with a configure -command like this: - -@example - CC=/udk/usr/ccs/bin/cc @var{/your/path/to}/gcc/configure \ - --host=i686-pc-udk --target=i686-pc-udk --program-prefix=udk- -@end example - -@emph{You should substitute @samp{i686} in the above command with the appropriate -processor for your host.} - -After the usual @samp{make bootstrap} and -@samp{make install}, you can then access the UDK-targeted GCC -tools by adding @command{udk-} before the commonly known name. For -example, to invoke the C compiler, you would use @command{udk-gcc}. -They will coexist peacefully with any native-target GCC tools you may -have installed. - - -@html -<hr /> -@end html -@heading @anchor{ix86-*-isc}i?86-*-isc -This configuration is obsoleted in GCC 3.1. - -It may be a good idea to link with GNU malloc instead of the malloc that -comes with the system. - -In ISC version 4.1, @command{sed} core dumps when building -@file{deduced.h}. Use the version of @command{sed} from version 4.0. - -@html -<hr /> -@end html -@heading @anchor{ix86-ibm-aix}i?86-ibm-aix -This configuration is obsoleted in GCC 3.1. - -You need to use GAS version 2.1 or later, and LD from -GNU binutils version 2.2 or later. - -@html -<hr /> -@end html -@heading @anchor{ix86-sequent-bsd}i?86-sequent-bsd -This configuration is obsoleted in GCC 3.1. - -Go to the Berkeley universe before compiling. - -@html -<hr /> -@end html -@heading @anchor{ix86-sequent-ptx1*}i?86-sequent-ptx1*, i?86-sequent-ptx2*, i?86-sequent-sysv3* -This configuration is obsoleted in GCC 3.1. - -You must install GNU @command{sed} before running @command{configure}. - -The @code{fixproto} shell script may trigger a bug in the system shell. -If you encounter this problem, upgrade your operating system or -use @command{bash} (the GNU shell) to run @code{fixproto}. - -@html -<hr /> -@end html -@heading @anchor{i860-intel-osf*}i860-intel-osf* -All support for the i860 processor is obsoleted in GCC 3.1. - -On the Intel Paragon (an i860 machine), if you are using operating -system version 1.0, you will get warnings or errors about redefinition -of @code{va_arg} when you build GCC@. - -If this happens, then you need to link most programs with the library -@file{iclib.a}. You must also modify @file{stdio.h} as follows: before -the lines - -@example -#if defined(__i860__) && !defined(_VA_LIST) -#include <va_list.h> -@end example - -@noindent -insert the line - -@example -#if __PGC__ -@end example - -@noindent -and after the lines - -@example -extern int vprintf(const char *, va_list ); -extern int vsprintf(char *, const char *, va_list ); -#endif -@end example - -@noindent -insert the line - -@example -#endif /* __PGC__ */ -@end example - -These problems don't exist in operating system version 1.1. - -@html -<hr /> -@end html -@heading @anchor{ia64-*-linux}ia64-*-linux -IA-64 processor (also known as IPF, or Itanium Processor Family) -running GNU/Linux. - -The toolchain is not completely finished, so requirements will continue -to change. -GCC 3.0.1 and later require glibc 2.2.4. -GCC 3.0.2 requires binutils from 2001-09-05 or later. -GCC 3.0.1 requires binutils 2.11.1 or later. - -None of the following versions of GCC has an ABI that is compatible -with any of the other versions in this list, with the exception that -Red Hat 2.96 and Trillian 000171 are compatible with each other: -3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717. -This primarily affects C++ programs and programs that create shared libraries. -Because of these ABI incompatibilities, GCC 3.0.2 is not recommended for -user programs on GNU/Linux systems built using earlier compiler releases. -GCC 3.0.2 is recommended for compiling linux, the kernel. -GCC 3.0.2 is believed to be fully ABI compliant, and hence no more major -ABI changes are expected. - -@html -<hr /> -@end html -@heading @anchor{*-lynx-lynxos}*-lynx-lynxos -LynxOS 2.2 and earlier comes with GCC 1.x already installed as -@file{/bin/gcc}. You should compile with this instead of @file{/bin/cc}. -You can tell GCC to use the GNU assembler and linker, by specifying -@samp{--with-gnu-as --with-gnu-ld} when configuring. These will produce -COFF format object files and executables; otherwise GCC will use the -installed tools, which produce @file{a.out} format executables. - -@html -<hr /> -<!-- rs6000-ibm-aix*, powerpc-ibm-aix* --> -@end html -@heading @anchor{*-ibm-aix*}*-ibm-aix* - -AIX Make frequently has problems with GCC makefiles. GNU Make 3.76 or -newer is recommended to build on this platform. - -Errors involving @code{alloca} when building GCC generally are due -to an incorrect definition of @code{CC} in the Makefile or mixing files -compiled with the native C compiler and GCC@. During the stage1 phase of -the build, the native AIX compiler @strong{must} be invoked as @command{cc} -(not @command{xlc}). Once @command{configure} has been informed of -@command{xlc}, one needs to use @samp{make distclean} to remove the -configure cache files and ensure that @env{CC} environment variable -does not provide a definition that will confuse @command{configure}. -If this error occurs during stage2 or later, then the problem most likely -is the version of Make (see above). - -The GNU Assembler incorrectly reports that it supports WEAK symbols on -AIX which causes GCC to try to utilize weak symbol functionality which -is not really supported on the platform. The native @command{as} and -@command{ld} still are recommended. The native AIX tools do -interoperate with GCC@. - -Building @file{libstdc++.a} requires a fix for a AIX Assembler bug -APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). - -@samp{libstdc++} in GCC 3.2 increments the major version number of the -shared object and GCC installation places the @file{libstdc++.a} -shared library in a common location which will overwrite the GCC 3.1 -version of the shared library. Applications either need to be -re-linked against the new shared library or the GCC 3.1 version of the -@samp{libstdc++} shared object needs to be available to the AIX -runtime loader. The GCC 3.1 @samp{libstdc++.so.4} shared object can -be installed for runtime dynamic loading using the following steps to -set the @samp{F_LOADONLY} flag in the shared object for @emph{each} -multilib @file{libstdc++.a} installed: - -Extract the shared object from each the GCC 3.1 @file{libstdc++.a} -archive: -@example - % ar -x libstdc++.a libstdc++.so.4 -@end example - -Enable the @samp{F_LOADONLY} flag so that the shared object will be -available for runtime dynamic loading, but not linking: -@example - % strip -e libstdc++.so.4 -@end example - -Archive the runtime-only shared object in the GCC 3.2 -@file{libstdc++.a} archive: -@example - % ar -q libstdc++.a libstdc++.so.4 -@end example - -Linking executables and shared libraries may produce warnings of -duplicate symbols. The assembly files generated by GCC for AIX always -have included multiple symbol definitions for certain global variable -and function declarations in the original program. The warnings should -not prevent the linker from producing a correct library or runnable -executable. - -AIX 4.3 utilizes a ``large format'' archive to support both 32-bit and -64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1 -to parse archive libraries did not handle the new format correctly. -These routines are used by GCC and result in error messages during -linking such as ``not a COFF file''. The version of the routines shipped -with AIX 4.3.1 should work for a 32-bit environment. The @option{-g} -option of the archive command may be used to create archives of 32-bit -objects using the original ``small format''. A correct version of the -routines is shipped with AIX 4.3.2 and above. - -Some versions of the AIX binder (linker) can fail with a relocation -overflow severe error when the @option{-bbigtoc} option is used to link -GCC-produced object files into an executable that overflows the TOC@. A fix -for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is -available from IBM Customer Support and from its -@uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com} -website as PTF U455193. - -The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core -with a segmentation fault when invoked by any version of GCC@. A fix for -APAR IX87327 is available from IBM Customer Support and from its -@uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com} -website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above. - -The initial assembler shipped with AIX 4.3.0 generates incorrect object -files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS -TO ASSEMBLE/BIND) is available from IBM Customer Support and from its -@uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com} -website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above. - -AIX provides National Language Support (NLS)@. Compilers and assemblers -use NLS to support locale-specific representations of various data -formats including floating-point numbers (e.g., @samp{.} vs @samp{,} for -separating decimal fractions). There have been problems reported where -GCC does not produce the same floating-point formats that the assembler -expects. If one encounters this problem, set the @env{LANG} -environment variable to @samp{C} or @samp{En_US}. - -By default, GCC for AIX 4.1 and above produces code that can be used on -both Power or PowerPC processors. - -A default can be specified with the @option{-mcpu=@var{cpu_type}} -switch and using the configure option @option{--with-cpu-@var{cpu_type}}. - -@html -<hr /> -@end html -@heading @anchor{m32r-*-elf}m32r-*-elf -Mitsubishi M32R processor. -This configuration is intended for embedded systems. - -@html -<hr /> -@end html -@heading @anchor{m68000-hp-bsd}m68000-hp-bsd -HP 9000 series 200 running BSD@. Note that the C compiler that comes -with this system cannot compile GCC; contact @email{law@@cygnus.com} -to get binaries of GCC for bootstrapping. - -@html -<hr /> -@end html -@heading @anchor{m6811-elf}m6811-elf -Motorola 68HC11 family micro controllers. These are used in embedded -applications. There are no standard Unix configurations. - -@html -<hr /> -@end html -@heading @anchor{m6812-elf}m6812-elf -Motorola 68HC12 family micro controllers. These are used in embedded -applications. There are no standard Unix configurations. - -@html -<hr /> -@end html -@heading @anchor{m68k-altos}m68k-altos -Altos 3068. This configuration is obsoleted in GCC 3.1. - -You must use the GNU assembler, linker and debugger. -Also, you must fix a kernel bug. - -@html -<hr /> -@end html -@heading @anchor{m68k-apple-aux}m68k-apple-aux -Apple Macintosh running A/UX@. -This configuration is obsoleted in GCC 3.1. - -You may configure GCC to use either the system assembler and -linker or the GNU assembler and linker. You should use the GNU configuration -if you can, especially if you also want to use G++. You enable -that configuration with the @option{--with-gnu-as} and @option{--with-gnu-ld} -options to @code{configure}. - -Note the C compiler that comes -with this system cannot compile GCC@. You can find binaries of GCC -for bootstrapping on @code{jagubox.gsfc.nasa.gov}. -You will also a patched version of @file{/bin/ld} there that -raises some of the arbitrary limits found in the original. - -@html -<hr /> -@end html -@heading @anchor{m68k-att-sysv}m68k-att-sysv -AT&T 3b1, a.k.a.@: 7300 PC@. This version of GCC cannot -be compiled with the system C compiler, which is too buggy. -You will need to get a previous version of GCC and use it to -bootstrap. Binaries are available from the OSU-CIS archive, at -@uref{ftp://archive.cis.ohio-state.edu/pub/att7300/}. - -@html -<hr /> -@end html -@heading @anchor{m68k-bull-sysv}m68k-bull-sysv -Bull DPX/2 series 200 and 300 with BOS-2.00.45 up to BOS-2.01. -This configuration is obsoleted in GCC 3.1. - -GCC works -either with native assembler or GNU assembler. You can use -GNU assembler with native COFF generation by providing @option{--with-gnu-as} to -the configure script or use GNU assembler with stabs-in-COFF encapsulation -by providing @samp{--with-gnu-as --stabs}. For any problem with the native -assembler or for availability of the DPX/2 port of GAS, contact -@email{F.Pierresteguy@@frcl.bull.fr}. - -@html -<hr /> -@end html -@heading @anchor{m68k-crds-unos}m68k-crds-unos -Use @samp{configure unos} for building on Unos. - -The Unos assembler is named @code{casm} instead of @code{as}. For some -strange reason linking @file{/bin/as} to @file{/bin/casm} changes the -behavior, and does not work. So, when installing GCC, you should -install the following script as @file{as} in the subdirectory where -the passes of GCC are installed: - -@example -#!/bin/sh -casm $* -@end example - -The default Unos library is named @file{libunos.a} instead of -@file{libc.a}. To allow GCC to function, either change all -references to @option{-lc} in @file{gcc.c} to @option{-lunos} or link -@file{/lib/libc.a} to @file{/lib/libunos.a}. - -@cindex @code{alloca}, for Unos -When compiling GCC with the standard compiler, to overcome bugs in -the support of @code{alloca}, do not use @option{-O} when making stage 2. -Then use the stage 2 compiler with @option{-O} to make the stage 3 -compiler. This compiler will have the same characteristics as the usual -stage 2 compiler on other systems. Use it to make a stage 4 compiler -and compare that with stage 3 to verify proper compilation. - -(Perhaps simply defining @code{ALLOCA} in @file{x-crds} as described in -the comments there will make the above paragraph superfluous. Please -inform us of whether this works.) - -Unos uses memory segmentation instead of demand paging, so you will need -a lot of memory. 5 Mb is barely enough if no other tasks are running. -If linking @file{cc1} fails, try putting the object files into a library -and linking from that library. - -@html -<hr /> -@end html -@heading @anchor{m68k-hp-hpux}m68k-hp-hpux -HP 9000 series 300 or 400 running HP-UX@. HP-UX version 8.0 has a bug in -the assembler that prevents compilation of GCC@. This -bug manifests itself during the first stage of compilation, while -building @file{libgcc2.a}: - -@smallexample -_floatdisf -cc1: warning: `-g' option not supported on this version of GCC -cc1: warning: `-g1' option not supported on this version of GCC -./xgcc: Internal compiler error: program as got fatal signal 11 -@end smallexample - -A patched version of the assembler is available as the file -@uref{ftp://altdorf.ai.mit.edu/archive/cph/hpux-8.0-assembler}. If you -have HP software support, the patch can also be obtained directly from -HP, as described in the following note: - -@quotation -This is the patched assembler, to patch SR#1653-010439, where the -assembler aborts on floating point constants. - -The bug is not really in the assembler, but in the shared library -version of the function ``cvtnum(3c)''. The bug on ``cvtnum(3c)'' is -SR#4701-078451. Anyway, the attached assembler uses the archive -library version of ``cvtnum(3c)'' and thus does not exhibit the bug. -@end quotation - -This patch is also known as PHCO_4484. - -In addition, if you wish to use gas, you must use -gas version 2.1 or later, and you must use the GNU linker version 2.1 or -later. Earlier versions of gas relied upon a program which converted the -gas output into the native HP-UX format, but that program has not been -kept up to date. gdb does not understand that native HP-UX format, so -you must use gas if you wish to use gdb. - -On HP-UX version 8.05, but not on 8.07 or more recent versions, the -@code{fixproto} shell script triggers a bug in the system shell. If you -encounter this problem, upgrade your operating system or use BASH (the -GNU shell) to run @code{fixproto}. This bug will cause the fixproto -program to report an error of the form: - -@example -./fixproto: sh internal 1K buffer overflow -@end example - -To fix this, you can also change the first line of the fixproto script -to look like: - -@example -#!/bin/ksh -@end example - - -@html -<hr /> -@end html -@heading @anchor{m68k-*-nextstep*}m68k-*-nextstep* -These configurations are obsoleted in GCC 3.1. - -Current GCC versions probably do not work on version 2 of the NeXT -operating system. - -On NeXTStep 3.0, the Objective-C compiler does not work, due, -apparently, to a kernel bug that it happens to trigger. This problem -does not happen on 3.1. - -You absolutely @strong{must} use GNU sed and GNU make on this platform. - - -On NeXTSTEP 3.x where x < 3 the build of GCC will abort during -stage1 with an error message like this: - -@example - _eh - /usr/tmp/ccbbsZ0U.s:987:Unknown pseudo-op: .section - /usr/tmp/ccbbsZ0U.s:987:Rest of line ignored. 1st junk character - valued 95 (_). -@end example - -The reason for this is the fact that NeXT's assembler for these -versions of the operating system does not support the @samp{.section} -pseudo op that's needed for full C++ exception functionality. - -As NeXT's assembler is a derived work from GNU as, a free -replacement that does can be obtained at -@uref{ftp://ftp.next.peak.org:/next-ftp/next/apps/devtools/as.3.3.NIHS.s.tar.gz,,ftp://ftp.next.peak.org:/next-ftp/next/apps/devtools/as.3.3.NIHS.s.tar.gz}. - -If you try to build the integrated C++ & C++ runtime libraries on this system -you will run into trouble with include files. The way to get around this is -to use the following sequence. Note you must have write permission to -the directory @var{prefix} you specified in the configuration process of GCC -for this sequence to work. - -@example - cd bld-gcc - make all-texinfo all-bison all-byacc all-binutils all-gas all-ld - cd gcc - make bootstrap - make install-headers-tar - cd .. - make bootstrap3 -@end example - -@html -<hr /> -@end html -@heading @anchor{m68k-ncr-*}m68k-ncr-* -On the Tower models 4@var{n}0 and 6@var{n}0, by default a process is not -allowed to have more than one megabyte of memory. GCC cannot compile -itself (or many other programs) with @option{-O} in that much memory. - -To solve this problem, reconfigure the kernel adding the following line -to the configuration file: - -@smallexample -MAXUMEM = 4096 -@end smallexample - - -@html -<hr /> -@end html -@heading @anchor{m68k-sun}m68k-sun -Sun 3. We do not provide a configuration file to use the Sun FPA by -default, because programs that establish signal handlers for floating -point traps inherently cannot work with the FPA@. - -@html -<hr /> -@end html -@heading @anchor{m68k-sun-sunos4.1.1}m68k-sun-sunos4.1.1 - -It is reported that you may need the GNU assembler on this platform. - - -@html -<hr /> -@end html -@heading @anchor{m88k-*-svr3}m88k-*-svr3 -Motorola m88k running the AT&T/Unisoft/Motorola V.3 reference port. -These configurations are obsoleted in GCC 3.1. - -These systems tend to use the Green Hills C, revision 1.8.5, as the -standard C compiler. There are apparently bugs in this compiler that -result in object files differences between stage 2 and stage 3. If this -happens, make the stage 4 compiler and compare it to the stage 3 -compiler. If the stage 3 and stage 4 object files are identical, this -suggests you encountered a problem with the standard C compiler; the -stage 3 and 4 compilers may be usable. - -It is best, however, to use an older version of GCC for bootstrapping -if you have one. - -@html -<hr /> -@end html -@heading @anchor{m88k-*-dgux}m88k-*-dgux -Motorola m88k running DG/UX@. -These configurations are obsoleted in GCC 3.1. - -To build 88open BCS native or cross -compilers on DG/UX, specify the configuration name as -@samp{m88k-*-dguxbcs} and build in the 88open BCS software development -environment. To build ELF native or cross compilers on DG/UX, specify -@samp{m88k-*-dgux} and build in the DG/UX ELF development environment. -You set the software development environment by issuing -@samp{sde-target} command and specifying either @samp{m88kbcs} or -@samp{m88kdguxelf} as the operand. - -If you do not specify a configuration name, @file{configure} guesses the -configuration based on the current software development environment. - -@html -<hr /> -@end html -@heading @anchor{m88k-tektronix-sysv3}m88k-tektronix-sysv3 -Tektronix XD88 running UTekV 3.2e. -These configurations are obsoleted in GCC 3.1. - -Do not turn on -optimization while building stage1 if you bootstrap with -the buggy Green Hills compiler. Also, the bundled LAI -System V NFS is buggy so if you build in an NFS mounted -directory, start from a fresh reboot, or avoid NFS all together. -Otherwise you may have trouble getting clean comparisons -between stages. - -@html -<hr /> -@end html -@heading @anchor{mips-*-*}mips-*-* -If you use the 1.31 version of the MIPS assembler (such as was shipped -with Ultrix 3.1), you will need to use the @option{-fno-delayed-branch} switch -when optimizing floating point code. Otherwise, the assembler will -complain when the GCC compiler fills a branch delay slot with a -floating point instruction, such as @code{add.d}. - -If on a MIPS system you get an error message saying ``does not have gp -sections for all it's [sic] sectons [sic]'', don't worry about it. This -happens whenever you use GAS with the MIPS linker, but there is not -really anything wrong, and it is okay to use the output file. You can -stop such warnings by installing the GNU linker. - -It would be nice to extend GAS to produce the gp tables, but they are -optional, and there should not be a warning about their absence. - -Users have reported some problems with version 2.0 of the MIPS -compiler tools that were shipped with Ultrix 4.1. Version 2.10 -which came with Ultrix 4.2 seems to work fine. - -Users have also reported some problems with version 2.20 of the -MIPS compiler tools that were shipped with RISC/os 4.x. The earlier -version 2.11 seems to work fine. - -Some versions of the MIPS linker will issue an assertion failure -when linking code that uses @code{alloca} against shared -libraries on RISC-OS 5.0, and DEC's OSF/1 systems. This is a bug -in the linker, that is supposed to be fixed in future revisions. -To protect against this, GCC passes @option{-non_shared} to the -linker unless you pass an explicit @option{-shared} or -@option{-call_shared} switch. - -@heading @anchor{mips-mips-bsd}mips-mips-bsd -MIPS machines running the MIPS operating system in BSD mode. -These configurations are obsoleted in GCC 3.1. - -It's possible that some old versions of the system lack the functions -@code{memcpy}, @code{memmove}, @code{memcmp}, and @code{memset}. If your -system lacks these, you must remove or undo the definition of -@code{TARGET_MEM_FUNCTIONS} in @file{mips-bsd.h}. - -If you use the MIPS C compiler to bootstrap, it may be necessary -to increase its table size for switch statements with the -@option{-Wf,-XNg1500} option. If you use the @option{-O2} -optimization option, you also need to use @option{-Olimit 3000}. -Both of these options are automatically generated in the -@file{Makefile} that the shell script @file{configure} builds. -If you override the @code{CC} make variable and use the MIPS -compilers, you may need to add @option{-Wf,-XNg1500 -Olimit 3000}. - -@html -<hr /> -@end html -@heading @anchor{mips-dec-*}mips-dec-* -These configurations are obsoleted in GCC 3.1. - -MIPS-based DECstations can support three different personalities: -Ultrix, DEC OSF/1, and OSF/rose. (Alpha-based DECstation products have -a configuration name beginning with @samp{alpha*-dec}.) To configure GCC -for these platforms use the following configurations: - -@table @samp -@item mips-dec-ultrix -Ultrix configuration. - -@item mips-dec-osf1 -DEC's version of OSF/1. - -@item mips-dec-osfrose -Open Software Foundation reference port of OSF/1 which uses the -OSF/rose object file format instead of ECOFF@. Normally, you -would not select this configuration. -@end table - -If you use the MIPS C compiler to bootstrap, it may be necessary -to increase its table size for switch statements with the -@option{-Wf,-XNg1500} option. If you use the @option{-O2} -optimization option, you also need to use @option{-Olimit 3000}. -Both of these options are automatically generated in the -@file{Makefile} that the shell script @file{configure} builds. -If you override the @code{CC} make variable and use the MIPS -compilers, you may need to add @option{-Wf,-XNg1500 -Olimit 3000}. - -@html -<hr /> -@end html -@heading @anchor{mips-mips-riscos*}mips-mips-riscos* -These configurations are obsoleted in GCC 3.1. - -If you use the MIPS C compiler to bootstrap, it may be necessary -to increase its table size for switch statements with the -@option{-Wf,-XNg1500} option. If you use the @option{-O2} -optimization option, you also need to use @option{-Olimit 3000}. -Both of these options are automatically generated in the -@file{Makefile} that the shell script @file{configure} builds. -If you override the @code{CC} make variable and use the MIPS -compilers, you may need to add @samp{-Wf,-XNg1500 -Olimit 3000}. - -MIPS computers running RISC-OS can support four different -personalities: default, BSD 4.3, System V.3, and System V.4 -(older versions of RISC-OS don't support V.4). To configure GCC -for these platforms use the following configurations: - -@table @samp -@item mips-mips-riscos@var{rev} -Default configuration for RISC-OS, revision @var{rev}. - -@item mips-mips-riscos@var{rev}bsd -BSD 4.3 configuration for RISC-OS, revision @var{rev}. - -@item mips-mips-riscos@var{rev}sysv4 -System V.4 configuration for RISC-OS, revision @var{rev}. - -@html -<hr /> -@end html -@item mips-mips-riscos@var{rev}sysv -System V.3 configuration for RISC-OS, revision @var{rev}. -@end table - -The revision @code{rev} mentioned above is the revision of -RISC-OS to use. You must reconfigure GCC when going from a -RISC-OS revision 4 to RISC-OS revision 5. This has the effect of -avoiding a linker bug. - -@html -<hr /> -@end html -@heading @anchor{mips-sgi-irix4}mips-sgi-irix4 -This configuration is obsoleted in GCC 3.1. - -In order to compile GCC on an SGI running IRIX 4, the ``c.hdr.lib'' -option must be installed from the CD-ROM supplied from Silicon Graphics. -This is found on the 2nd CD in release 4.0.1. - -On IRIX version 4.0.5F, and perhaps on some other versions as well, -there is an assembler bug that reorders instructions incorrectly. To -work around it, specify the target configuration -@samp{mips-sgi-irix4loser}. This configuration inhibits assembler -optimization. - -In a compiler configured with target @samp{mips-sgi-irix4}, you can turn -off assembler optimization by using the @option{-noasmopt} option. This -compiler option passes the option @option{-O0} to the assembler, to -inhibit reordering. - -The @option{-noasmopt} option can be useful for testing whether a problem -is due to erroneous assembler reordering. Even if a problem does not go -away with @option{-noasmopt}, it may still be due to assembler -reordering---perhaps GCC itself was miscompiled as a result. - -You may get the following warning on IRIX 4 platforms, it can be safely -ignored. -@example - warning: foo.o does not have gp tables for all its sections. -@end example - -@html -<hr /> -@end html -@heading @anchor{mips-sgi-irix5}mips-sgi-irix5 - -This configuration has considerable problems, which will be fixed in a -future release. - -In order to compile GCC on an SGI running IRIX 5, the ``compiler_dev.hdr'' -subsystem must be installed from the IDO CD-ROM supplied by Silicon -Graphics. It is also available for download from -@uref{http://www.sgi.com/developers/devtools/apis/ido.html,,http://www.sgi.com/developers/devtools/apis/ido.html}. - -@code{make compare} may fail on version 5 of IRIX unless you add -@option{-save-temps} to @code{CFLAGS}. On these systems, the name of the -assembler input file is stored in the object file, and that makes -comparison fail if it differs between the @code{stage1} and -@code{stage2} compilations. The option @option{-save-temps} forces a -fixed name to be used for the assembler input file, instead of a -randomly chosen name in @file{/tmp}. Do not add @option{-save-temps} -unless the comparisons fail without that option. If you do you -@option{-save-temps}, you will have to manually delete the @samp{.i} and -@samp{.s} files after each series of compilations. - -If you use the MIPS C compiler to bootstrap, it may be necessary -to increase its table size for switch statements with the -@option{-Wf,-XNg1500} option. If you use the @option{-O2} -optimization option, you also need to use @option{-Olimit 3000}. - -To enable debugging under IRIX 5, you must use GNU @command{as} 2.11.2 -or later, -and use the @option{--with-gnu-as} configure option when configuring GCC. -GNU @command{as} is distributed as part of the binutils package. -When using release 2.11.2, you need to apply a patch -@uref{http://sources.redhat.com/ml/binutils/2001-07/msg00352.html,,http://sources.redhat.com/ml/binutils/2001-07/msg00352.html} -which will be included in the next release of binutils. - -When building GCC, the build process loops rebuilding @command{cc1} over -and over again. This happens on @samp{mips-sgi-irix5.2}, and possibly -other platforms. It has been reported that this is a known bug in the -@command{make} shipped with IRIX 5.2. We recommend you use GNU -@command{make} instead of the vendor supplied @command{make} program; -however, you may have success with @command{smake} on IRIX 5.2 if you do -not have GNU @command{make} available. - -@html -<hr /> -@end html -@heading @anchor{mips-sgi-irix6}mips-sgi-irix6 - -If you are using IRIX @command{cc} as your bootstrap compiler, you must -ensure that the N32 ABI is in use. To test this, compile a simple C -file with @command{cc} and then run @command{file} on the -resulting object file. The output should look like: - -@example -test.o: ELF N32 MSB @dots{} -@end example - -If you see: - -@example -test.o: ELF 32-bit MSB @dots{} -@end example - -or - -@example -test.o: ELF 64-bit MSB @dots{} -@end example - -then your version of @command{cc} uses the O32 or N64 ABI by default. You -should set the environment variable @env{CC} to @samp{cc -n32} -before configuring GCC@. - -If you want the resulting @command{gcc} to run on old 32-bit systems -with the MIPS R4400 CPU, you need to ensure that only code for the mips3 -instruction set architecture (ISA) is generated. While GCC 3.x does -this correctly, both GCC 2.95 and SGI's MIPSpro @command{cc} may change -the ISA depending on the machine where GCC is built. Using one of them -as the bootstrap compiler may result in mips4 code, which won't run at -all on mips3-only systems. For the test program above, you should see: - -@example -test.o: ELF N32 MSB mips-3 @dots{} -@end example - -If you get: - -@example -test.o: ELF N32 MSB mips-4 @dots{} -@end example - -instead, you should set the environment variable @env{CC} to @samp{cc --n32 -mips3} or @samp{gcc -mips3} respectively before configuring GCC@. - -GCC on IRIX 6 is usually built to support both the N32 and N64 ABIs. If -you build GCC on a system that doesn't have the N64 libraries installed, -you need to configure with @option{--disable-multilib} so GCC doesn't -try to use them. Look for @file{/usr/lib64/libc.so.1} to see if you -have the 64-bit libraries installed. - -You must @emph{not} use GNU @command{as} (which isn't built anyway as of -binutils 2.11.2) on IRIX 6 platforms; doing so will only cause problems. - -GCC does not currently support generating O32 ABI binaries in the -@samp{mips-sgi-irix6} configurations. It is possible to create a GCC -with O32 ABI only support by configuring it for the @samp{mips-sgi-irix5} -target and using a patched GNU @command{as} 2.11.2 as documented in the -@uref{#mips-sgi-irix5,,@samp{mips-sgi-irix5}} section above. Using the -native assembler requires patches to GCC which will be included in a -future release. It is -expected that O32 ABI support will be available again in a future release. - -The @option{--enable-threads} option doesn't currently work, a patch is -in preparation for a future release. The @option{--enable-libgcj} -option is disabled by default: IRIX 6 uses a very low default limit -(20480) for the command line length. Although libtool contains a -workaround for this problem, at least the N64 @samp{libgcj} is known not -to build despite this, running into an internal error of the native -@command{ld}. A sure fix is to increase this limit (@samp{ncargs}) to -its maximum of 262144 bytes. If you have root access, you can use the -@command{systune} command to do this. - -GCC does not correctly pass/return structures which are -smaller than 16 bytes and which are not 8 bytes. The problem is very -involved and difficult to fix. It affects a number of other targets also, -but IRIX 6 is affected the most, because it is a 64-bit target, and 4 byte -structures are common. The exact problem is that structures are being padded -at the wrong end, e.g.@: a 4 byte structure is loaded into the lower 4 bytes -of the register when it should be loaded into the upper 4 bytes of the -register. - -GCC is consistent with itself, but not consistent with the SGI C compiler -(and the SGI supplied runtime libraries), so the only failures that can -happen are when there are library functions that take/return such -structures. There are very few such library functions. Currently this -is known to affect @code{inet_ntoa}, @code{inet_lnaof}, -@code{inet_netof}, @code{inet_makeaddr}, and @code{semctl}. Until the -bug is fixed, GCC contains workarounds for the known affected functions. - -See @uref{http://freeware.sgi.com/,,http://freeware.sgi.com/} for more -information about using GCC on IRIX platforms. - -@html -<hr /> -@end html -@heading @anchor{mips-sony-sysv}mips-sony-sysv -Sony MIPS NEWS@. This configuration is obsoleted in GCC 3.1. - -This works in NEWSOS 5.0.1, but not in 5.0.2 (which uses ELF instead of -COFF)@. In particular, the linker does not like the code generated by -GCC when shared libraries are linked in. - -@html -<hr /> -@end html -@heading @anchor{ns32k-encore}ns32k-encore -This configuration is obsoleted in GCC 3.1. - -Encore ns32000 system. Encore systems are supported only under BSD@. - -@html -<hr /> -@end html -@heading @anchor{ns32k-*-genix}ns32k-*-genix -National Semiconductor ns32000 system. This configuration is obsoleted -in GCC 3.1. - -Genix has bugs in @code{alloca} and @code{malloc}; you must get the -compiled versions of these from GNU Emacs. - -@html -<hr /> -@end html -@heading @anchor{ns32k-sequent}ns32k-sequent -This configuration is obsoleted in GCC 3.1. - -Go to the Berkeley universe before compiling. - -@html -<hr /> -@end html -@heading @anchor{ns32k-utek}ns32k-utek -UTEK ns32000 system (``merlin''). This configuration is obsoleted in -GCC 3.1. - -The C compiler that comes with this system cannot compile GCC; contact -@samp{tektronix!reed!mason} to get binaries of GCC for bootstrapping. - - -@html -<hr /> -@end html -@heading @anchor{powerpc*-*-*}powerpc-*-* - -You can specify a default version for the @option{-mcpu=@var{cpu_type}} -switch by using the configure option @option{--with-cpu-@var{cpu_type}}. - -@html -<hr /> -@end html -@heading @anchor{powerpc-*-darwin*}powerpc-*-darwin* -PowerPC running Darwin (Mac OS X kernel). - -GCC 3.0 does not support Darwin, but 3.1 and later releases will work. - -Pre-installed versions of Mac OS X may not include any developer tools, -meaning that you will not be able to build GCC from source. Tool -binaries are available at -@uref{http://www.opensource.apple.com/projects/darwin} (free -registration required). - -Versions of the assembler prior to ``cctools-364'' cannot handle the -4-argument form of @code{rlwinm} and related mask-using instructions. Darwin -1.3 (Mac OS X 10.0) uses cctools-353 for instance. To get cctools-364, -check out @file{cctools} with tag @samp{Apple-364}, build it, and -install the assembler as @file{usr/bin/as}. See -@uref{http://www.opensource.apple.com/tools/cvs/docs.html} for details. - -Also, the default stack limit of 512K is too small, and a bootstrap will -typically fail when self-compiling @file{expr.c}. Set the stack to 800K -or more, for instance by doing @samp{limit stack 800}. It's also -convenient to use the GNU preprocessor instead of Apple's during the -first stage of bootstrapping; this is automatic when doing @samp{make -bootstrap}, but to do it from the toplevel objdir you will need to say -@samp{make CC='cc -no-cpp-precomp' bootstrap}. - -Note that the version of GCC shipped by Apple typically includes a -number of extensions not available in a standard GCC release. These -extensions are generally specific to Mac programming. - -@html -<hr /> -@end html -@heading @anchor{powerpc-*-elf}powerpc-*-elf, powerpc-*-sysv4 -PowerPC system in big endian mode, running System V.4. - -@html -<hr /> -@end html -@heading @anchor{powerpc-*-linux-gnu*}powerpc-*-linux-gnu* - -You will need -@uref{ftp://ftp.kernel.org/pub/linux/devel/binutils,,binutils 2.13.90.0.10} -or newer for a working GCC@. - -@html -<hr /> -@end html -@heading @anchor{powerpc-*-netbsd*}powerpc-*-netbsd* -PowerPC system in big endian mode running NetBSD@. To build the -documentation you will need Texinfo version 4.1 (NetBSD 1.5.1 included -Texinfo version 3.12). - -@html -<hr /> -@end html -@heading @anchor{powerpc-*-eabiaix}powerpc-*-eabiaix -Embedded PowerPC system in big endian mode with @option{-mcall-aix} selected as -the default. - -@html -<hr /> -@end html -@heading @anchor{powerpc-*-eabisim}powerpc-*-eabisim -Embedded PowerPC system in big endian mode for use in running under the -PSIM simulator. - -@html -<hr /> -@end html -@heading @anchor{powerpc-*-eabi}powerpc-*-eabi -Embedded PowerPC system in big endian mode. - -@html -<hr /> -@end html -@heading @anchor{powerpcle-*-elf}powerpcle-*-elf, powerpcle-*-sysv4 -PowerPC system in little endian mode, running System V.4. - -@html -<hr /> -@end html -@heading @anchor{powerpcle-*-eabisim}powerpcle-*-eabisim -Embedded PowerPC system in little endian mode for use in running under -the PSIM simulator. - -@html -<hr /> -@end html -@heading @anchor{powerpcle-*-eabi}powerpcle-*-eabi -Embedded PowerPC system in little endian mode. - -@html -<hr /> -@end html -@heading @anchor{powerpcle-*-winnt}powerpcle-*-winnt, powerpcle-*-pe -PowerPC system in little endian mode running Windows NT@. - -@html -<hr /> -@end html -@heading @anchor{romp-*-aos}romp-*-aos, romp-*-mach -These configurations are obsoleted in GCC 3.1. - -We recommend you compile GCC with an earlier version of itself; if you -compile GCC with @command{hc}, the Metaware compiler, it will work, but -you will get mismatches between the stage 2 and stage 3 compilers in -various files. These errors are minor differences in some -floating-point constants and can be safely ignored; the stage 3 compiler -is correct. - -@html -<hr /> -@end html -@heading @anchor{s390-*-linux*}s390-*-linux* -S/390 system running Linux for S/390@. - -@html -<hr /> -@end html -@heading @anchor{s390x-*-linux*}s390x-*-linux* -zSeries system (64-bit) running Linux for zSeries@. - -@html -<hr /> -@end html -@c Please use Solaris 2 to refer to all release of Solaris, starting -@c with 2.0 until 2.6, 7, and 8. Solaris 1 was a marketing name for -@c SunOS 4 releases which we don't use to avoid confusion. Solaris -@c alone is too unspecific and must be avoided. -@heading @anchor{*-*-solaris2*}*-*-solaris2* - -Sun does not ship a C compiler with Solaris 2. To bootstrap and install -GCC you first have to install a pre-built compiler, see our -@uref{binaries.html,,binaries page} for details. - -The Solaris 2 @command{/bin/sh} will often fail to configure -@file{libstdc++-v3}, @file{boehm-gc} or -@file{libjava}. If you encounter this problem, set @env{CONFIG_SHELL} to -@command{/bin/ksh} in your environment before running @command{configure}. - -Solaris 2 comes with a number of optional OS packages. Some of these -packages are needed to use GCC fully, namely @code{SUNWarc}, -@code{SUNWbtool}, @code{SUNWesu}, @code{SUNWhea}, @code{SUNWlibm}, -@code{SUNWsprot}, and @code{SUNWtoo}. If you did not install all -optional packages when installing Solaris 2, you will need to verify that -the packages that GCC needs are installed. - -To check whether an optional package is installed, use -the @command{pkginfo} command. To add an optional package, use the -@command{pkgadd} command. For further details, see the Solaris 2 -documentation. - -Trying to use the linker and other tools in -@file{/usr/ucb} to install GCC has been observed to cause trouble. -For example, the linker may hang indefinitely. The fix is to remove -@file{/usr/ucb} from your @env{PATH}. - -All releases of GNU binutils prior to 2.11.2 have known bugs on this -platform. We recommend the use of GNU binutils 2.11.2 or the vendor -tools (Sun @command{as}, Sun @command{ld}). - -Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or -newer: @command{g++} will complain that types are missing. These headers assume -that omitting the type means @code{int}; this assumption worked for C89 but -is wrong for C++, and is now wrong for C99 also. - -@command{g++} accepts such (invalid) constructs with the option -@option{-fpermissive}; it -will assume that any missing type is @code{int} (as defined by C89). - -There are patches for Solaris 2.6 (105633-56 or newer for SPARC, -106248-42 or newer for Intel), Solaris 7 (108376-21 or newer for SPARC, -108377-20 for Intel), and Solaris 8 (108652-24 or newer for SPARC, -108653-22 for Intel) that fix this bug. - -@html -<hr /> -@end html -@heading @anchor{sparc-sun-solaris2*}sparc-sun-solaris2* - -When GCC is configured to use binutils 2.11.2 or later the binaries -produced are smaller than the ones produced using Sun's native tools; -this difference is quite significant for binaries containing debugging -information. - -Sun @command{as} 4.x is broken in that it cannot cope with long symbol names. -A typical error message might look similar to the following: - -@smallexample -/usr/ccs/bin/as: "/var/tmp/ccMsw135.s", line 11041: error: - can't compute value of an expression involving an external symbol. -@end smallexample - -This is Sun bug 4237974. This is fixed with patch 108908-02 for Solaris -2.6 and has been fixed in later (5.x) versions of the assembler, -starting with Solaris 7. - -Starting with Solaris 7, the operating system is capable of executing -64-bit SPARC V9 binaries. GCC 3.1 and later properly supports -this; the @option{-m64} option enables 64-bit code generation. -However, if all you want is code tuned for the UltraSPARC CPU, you -should try the @option{-mtune=ultrasparc} option instead, which produces -code that, unlike full 64-bit code, can still run on non-UltraSPARC -machines. - -When configuring on a Solaris 7 or later system that is running a kernel -that supports only 32-bit binaries, one must configure with -@option{--disable-multilib}, since we will not be able to build the -64-bit target libraries. - -@html -<hr /> -@end html -@heading @anchor{sparc-sun-solaris2.7}sparc-sun-solaris2.7 - -Sun patch 107058-01 (1999-01-13) for Solaris 7/SPARC triggers a bug in -the dynamic linker. This problem (Sun bug 4210064) affects GCC 2.8 -and later, including all EGCS releases. Sun formerly recommended -107058-01 for all Solaris 7 users, but around 1999-09-01 it started to -recommend it only for people who use Sun's compilers. - -Here are some workarounds to this problem: -@itemize @bullet -@item -Do not install Sun patch 107058-01 until after Sun releases a -complete patch for bug 4210064. This is the simplest course to take, -unless you must also use Sun's C compiler. Unfortunately 107058-01 -is preinstalled on some new Solaris 7-based hosts, so you may have to -back it out. - -@item -Copy the original, unpatched Solaris 7 -@command{/usr/ccs/bin/as} into -@command{/usr/local/lib/gcc-lib/sparc-sun-solaris2.7/3.1/as}, -adjusting the latter name to fit your local conventions and software -version numbers. - -@item -Install Sun patch 106950-03 (1999-05-25) or later. Nobody with -both 107058-01 and 106950-03 installed has reported the bug with GCC -and Sun's dynamic linker. This last course of action is riskiest, -for two reasons. First, you must install 106950 on all hosts that -run code generated by GCC; it doesn't suffice to install it only on -the hosts that run GCC itself. Second, Sun says that 106950-03 is -only a partial fix for bug 4210064, but Sun doesn't know whether the -partial fix is adequate for GCC@. Revision -08 or later should fix -the bug. The current (as of 2001-09-24) revision is -14, and is included in -the Solaris 7 Recommended Patch Cluster. -@end itemize - - -@html -<p> -<hr /> -@end html -@heading @anchor{sparc-sun-sunos4*}sparc-sun-sunos4* - -A bug in the SunOS 4 linker will cause it to crash when linking -@option{-fPIC} compiled objects (and will therefore not allow you to build -shared libraries). - -To fix this problem you can either use the most recent version of -binutils or get the latest SunOS 4 linker patch (patch ID 100170-10) -from Sun's patch site. - -Sometimes on a Sun 4 you may observe a crash in the program -@command{genflags} or @command{genoutput} while building GCC. This is said to -be due to a bug in @command{sh}. You can probably get around it by running -@command{genflags} or @command{genoutput} manually and then retrying the -@command{make}. - -@html -<hr /> -@end html -@heading @anchor{sparc-unknown-linux-gnulibc1}sparc-unknown-linux-gnulibc1 - -It has been reported that you might need -@uref{ftp://ftp.yggdrasil.com/private/hjl,,binutils 2.8.1.0.23} -for this platform, too. - - -@html -<hr /> -@end html -@heading @anchor{sparc-*-linux*}sparc-*-linux* - -GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4 -or newer on this platform. All earlier binutils and glibc -releases mishandled unaligned relocations on @code{sparc-*-*} targets. - - -@html -<hr /> -@end html -@heading @anchor{sparc64-*-*}sparc64-*-* - -GCC version 2.95 is not able to compile code correctly for -@code{sparc64} targets. Users of the Linux kernel, at least, -can use the @code{sparc32} program to start up a new shell -invocation with an environment that causes @command{configure} to -recognize (via @samp{uname -a}) the system as @samp{sparc-*-*} instead. - -@html -<hr /> -@end html -@heading @anchor{sparcv9-*-solaris2*}sparcv9-*-solaris2* - -The following compiler flags must be specified in the configure -step in order to bootstrap this target with the Sun compiler: - -@example - % CC="cc -xildoff -xarch=v9" @var{srcdir}/configure [@var{options}] [@var{target}] -@end example - -@option{-xildoff} turns off the incremental linker, and @option{-xarch=v9} -specifies the v9 architecture to the Sun linker and assembler. - -@html -<hr /> -@end html -@heading @anchor{#*-*-sysv*}*-*-sysv* -On System V release 3, you may get this error message -while linking: - -@smallexample -ld fatal: failed to write symbol name @var{something} - in strings table for file @var{whatever} -@end smallexample - -This probably indicates that the disk is full or your ulimit won't allow -the file to be as large as it needs to be. - -This problem can also result because the kernel parameter @code{MAXUMEM} -is too small. If so, you must regenerate the kernel and make the value -much larger. The default value is reported to be 1024; a value of 32768 -is said to work. Smaller values may also work. - -On System V, if you get an error like this, - -@example -/usr/local/lib/bison.simple: In function `yyparse': -/usr/local/lib/bison.simple:625: virtual memory exhausted -@end example - -@noindent -that too indicates a problem with disk space, ulimit, or @code{MAXUMEM}. - -On a System V release 4 system, make sure @file{/usr/bin} precedes -@file{/usr/ucb} in @code{PATH}. The @code{cc} command in -@file{/usr/ucb} uses libraries which have bugs. - -@html -<hr /> -@end html -@heading @anchor{vax-dec-ultrix}vax-dec-ultrix -Don't try compiling with VAX C (@code{vcc}). It produces incorrect code -in some cases (for example, when @code{alloca} is used). - -@html -<hr /> -@end html -@heading @anchor{we32k-*-*}we32k-*-* -These computers are also known as the 3b2, 3b5, 3b20 and other similar -names. (However, the 3b1 is actually a 68000.) -These configurations are obsoleted in GCC 3.1. - -Don't use @option{-g} when compiling with the system's compiler. The -system's linker seems to be unable to handle such a large program with -debugging information. - -The system's compiler runs out of capacity when compiling @file{stmt.c} -in GCC@. You can work around this by building @file{cpp} in GCC -first, then use that instead of the system's preprocessor with the -system's C compiler to compile @file{stmt.c}. Here is how: - -@smallexample -mv /lib/cpp /lib/cpp.att -cp cpp /lib/cpp.gnu -echo '/lib/cpp.gnu -traditional $@{1+"$@@"@}' > /lib/cpp -chmod +x /lib/cpp -@end smallexample - -The system's compiler produces bad code for some of the GCC -optimization files. So you must build the stage 2 compiler without -optimization. Then build a stage 3 compiler with optimization. -That executable should work. Here are the necessary commands: - -@smallexample -make LANGUAGES=c CC=stage1/xgcc CFLAGS="-Bstage1/ -g" -make stage2 -make CC=stage2/xgcc CFLAGS="-Bstage2/ -g -O" -@end smallexample - -You may need to raise the ULIMIT setting to build a C++ compiler, -as the file @file{cc1plus} is larger than one megabyte. - -@html -<hr /> -@end html -@heading @anchor{xtensa-*-elf}xtensa-*-elf - -This target is intended for embedded Xtensa systems using the -@samp{newlib} C library. It uses ELF but does not support shared -objects. Designed-defined instructions specified via the -Tensilica Instruction Extension (TIE) language are only supported -through inline assembly. - -The Xtensa configuration information must be specified prior to -building GCC@. The @file{gcc/config/xtensa/xtensa-config.h} header -file contains the configuration information. If you created your -own Xtensa configuration with the Xtensa Processor Generator, the -downloaded files include a customized copy of this header file, -which you can use to replace the default header file. - -@html -<hr /> -@end html -@heading @anchor{xtensa-*-linux*}xtensa-*-linux* - -This target is for Xtensa systems running GNU/Linux. It supports ELF -shared objects and the GNU C library (glibc). It also generates -position-independent code (PIC) regardless of whether the -@option{-fpic} or @option{-fPIC} options are used. In other -respects, this target is the same as the -@uref{#xtensa-*-elf,,@samp{xtensa-*-elf}} target. - -@html -<hr /> -@end html -@heading @anchor{windows}Microsoft Windows (32-bit) - -A port of GCC 2.95.x is included with the -@uref{http://www.cygwin.com/,,Cygwin environment}. - -Current (as of early 2001) snapshots of GCC will build under Cygwin -without modification. - -@html -<hr /> -@end html -@heading @anchor{os2}OS/2 - -GCC does not currently support OS/2. However, Andrew Zabolotny has been -working on a generic OS/2 port with pgcc. The current code can be found -at @uref{http://www.goof.com/pcg/os2/,,http://www.goof.com/pcg/os2/}. - -An older copy of GCC 2.8.1 is included with the EMX tools available at -@uref{ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/,, -ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/}. - -@html -<hr /> -@end html -@heading @anchor{older}Older systems - -GCC contains support files for many older (1980s and early -1990s) Unix variants. For the most part, support for these systems -has not been deliberately removed, but it has not been maintained for -several years and may suffer from bitrot. Support from some systems -has been removed from GCC 3: fx80, ns32-ns-genix, pyramid, tahoe, -gmicro, spur; most of these targets had not been updated since GCC -version 1. - -We are planning to remove support for more older systems, starting in -GCC 3.1. Each release will have a list of ``obsoleted'' systems. -Support for these systems is still present in that release, but -@command{configure} will fail unless the @option{--enable-obsolete} -option is given. Unless a maintainer steps forward, support for -these systems will be removed from the next release of GCC@. - -Support for older systems as targets for cross-compilation is less -problematic than support for them as hosts for GCC; if an enthusiast -wishes to make such a target work again (including resurrecting any -of the targets that never worked with GCC 2, starting from the last -CVS version before they were removed), patches -@uref{../contribute.html,,following the usual requirements} -would be likely to be accepted, since they should not affect the -support for more modern targets. - -Support for old systems as hosts for GCC can cause problems if the -workarounds for compiler, library and operating system bugs affect the -cleanliness or maintainability of the rest of GCC@. In some cases, to -bring GCC up on such a system, if still possible with current GCC, may -require first installing an old version of GCC which did work on that -system, and using it to compile a more recent GCC, to avoid bugs in -the vendor compiler. Old releases of GCC 1 and GCC 2 are available in -the @file{old-releases} directory on the -@uref{../mirrors.html,,GCC mirror sites}. Header bugs may generally -be avoided using @command{fixincludes}, but bugs or deficiencies in -libraries and the operating system may still cause problems. - -For some systems, old versions of GNU binutils may also be useful, -and are available from @file{pub/binutils/old-releases} on -@uref{http://sources.redhat.com/mirrors.html,,sources.redhat.com mirror sites}. - -Some of the information on specific systems above relates to -such older systems, but much of the information -about GCC on such systems (which may no longer be applicable to -current GCC) is to be found in the GCC texinfo manual. - -@html -<hr /> -@end html -@heading @anchor{elf_targets}all ELF targets (SVR4, Solaris 2, etc.) - -C++ support is significantly better on ELF targets if you use the -@uref{./configure.html#with-gnu-ld,,GNU linker}; duplicate copies of -inlines, vtables and template instantiations will be discarded -automatically. - - -@html -<hr /> -<p> -@end html -@ifhtml -@uref{./index.html,,Return to the GCC Installation page} -@end ifhtml -@end ifset - -@c ***Old documentation****************************************************** -@ifset oldhtml -@include install-old.texi -@html -<hr /> -<p> -@end html -@ifhtml -@uref{./index.html,,Return to the GCC Installation page} -@end ifhtml -@end ifset - -@c ***GFDL******************************************************************** -@ifset gfdlhtml -@include fdl.texi -@html -<hr /> -<p> -@end html -@ifhtml -@uref{./index.html,,Return to the GCC Installation page} -@end ifhtml -@end ifset - -@c *************************************************************************** -@c Part 6 The End of the Document -@ifinfo -@comment node-name, next, previous, up -@node Concept Index, , GNU Free Documentation License, Top -@end ifinfo - -@ifinfo -@unnumbered Concept Index - -@printindex cp - -@contents -@end ifinfo -@bye diff --git a/contrib/gcc/doc/install.texi2html b/contrib/gcc/doc/install.texi2html deleted file mode 100755 index 3917e2af33e8..000000000000 --- a/contrib/gcc/doc/install.texi2html +++ /dev/null @@ -1,31 +0,0 @@ -#!/bin/sh -# -# Convert the GCC install documentation from texinfo format to HTML. -# -# $SOURCEDIR and $DESTDIR, resp., refer to the directory containing -# the texinfo source and the directory to put the HTML version in. -# -# (C) 2001 Free Software Foundation -# Originally by Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>, June 2001. -# -# This script is Free Software, and it can be copied, distributed and -# modified as defined in the GNU General Public License. A copy of -# its license can be downloaded from http://www.gnu.org/copyleft/gpl.html - -SOURCEDIR=${SOURCEDIR-.} -DESTDIR=${DESTDIR-HTML} - -MAKEINFO=${MAKEINFO-makeinfo} - -if [ ! -d $DESTDIR ]; then - mkdir -p $DESTDIR -fi - -for x in index.html specific.html download.html configure.html \ - build.html test.html finalinstall.html binaries.html old.html \ - gfdl.html -do - define=`echo $x | sed -e 's/\.//g'` - echo "define = $define" - $MAKEINFO -I $SOURCEDIR -I $SOURCEDIR/include $SOURCEDIR/install.texi --html --no-split -D$define -o$DESTDIR/$x -done diff --git a/contrib/gcc/doc/vms.texi b/contrib/gcc/doc/vms.texi deleted file mode 100644 index 5ab266695a84..000000000000 --- a/contrib/gcc/doc/vms.texi +++ /dev/null @@ -1,331 +0,0 @@ -@c Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, -@c 1999, 2000, 2001 Free Software Foundation, Inc. -@c This is part of the GCC manual. -@c For copying conditions, see the file gcc.texi. - -@node VMS -@chapter Using GCC on VMS - -@c prevent bad page break with this line -Here is how to use GCC on VMS@. - -@menu -* Include Files and VMS:: Where the preprocessor looks for the include files. -* Global Declarations:: How to do globaldef, globalref and globalvalue with - GCC. -* VMS Misc:: Misc information. -@end menu - -@node Include Files and VMS -@section Include Files and VMS - -@cindex include files and VMS -@cindex VMS and include files -@cindex header files and VMS -Due to the differences between the filesystems of Unix and VMS, GCC -attempts to translate file names in @samp{#include} into names that VMS -will understand. The basic strategy is to prepend a prefix to the -specification of the include file, convert the whole filename to a VMS -filename, and then try to open the file. GCC tries various prefixes -one by one until one of them succeeds: - -@enumerate -@item -The first prefix is the @samp{GNU_CC_INCLUDE:} logical name: this is -where GNU C header files are traditionally stored. If you wish to store -header files in non-standard locations, then you can assign the logical -@samp{GNU_CC_INCLUDE} to be a search list, where each element of the -list is suitable for use with a rooted logical. - -@item -The next prefix tried is @samp{SYS$SYSROOT:[SYSLIB.]}. This is where -VAX-C header files are traditionally stored. - -@item -If the include file specification by itself is a valid VMS filename, the -preprocessor then uses this name with no prefix in an attempt to open -the include file. - -@item -If the file specification is not a valid VMS filename (i.e.@: does not -contain a device or a directory specifier, and contains a @samp{/} -character), the preprocessor tries to convert it from Unix syntax to -VMS syntax. - -Conversion works like this: the first directory name becomes a device, -and the rest of the directories are converted into VMS-format directory -names. For example, the name @file{X11/foobar.h} is -translated to @file{X11:[000000]foobar.h} or @file{X11:foobar.h}, -whichever one can be opened. This strategy allows you to assign a -logical name to point to the actual location of the header files. - -@item -If none of these strategies succeeds, the @samp{#include} fails. -@end enumerate - -Include directives of the form: - -@example -#include foobar -@end example - -@noindent -are a common source of incompatibility between VAX-C and GCC@. VAX-C -treats this much like a standard @code{#include <foobar.h>} directive. -That is incompatible with the ISO C behavior implemented by GCC: to -expand the name @code{foobar} as a macro. Macro expansion should -eventually yield one of the two standard formats for @code{#include}: - -@example -#include "@var{file}" -#include <@var{file}> -@end example - -If you have this problem, the best solution is to modify the source to -convert the @code{#include} directives to one of the two standard forms. -That will work with either compiler. If you want a quick and dirty fix, -define the file names as macros with the proper expansion, like this: - -@example -#define stdio <stdio.h> -@end example - -@noindent -This will work, as long as the name doesn't conflict with anything else -in the program. - -Another source of incompatibility is that VAX-C assumes that: - -@example -#include "foobar" -@end example - -@noindent -is actually asking for the file @file{foobar.h}. GCC does not -make this assumption, and instead takes what you ask for literally; -it tries to read the file @file{foobar}. The best way to avoid this -problem is to always specify the desired file extension in your include -directives. - -GCC for VMS is distributed with a set of include files that is -sufficient to compile most general purpose programs. Even though the -GCC distribution does not contain header files to define constants -and structures for some VMS system-specific functions, there is no -reason why you cannot use GCC with any of these functions. You first -may have to generate or create header files, either by using the public -domain utility @code{UNSDL} (which can be found on a DECUS tape), or by -extracting the relevant modules from one of the system macro libraries, -and using an editor to construct a C header file. - -A @code{#include} file name cannot contain a DECNET node name. The -preprocessor reports an I/O error if you attempt to use a node name, -whether explicitly, or implicitly via a logical name. - -@node Global Declarations -@section Global Declarations and VMS - -@findex GLOBALREF -@findex GLOBALDEF -@findex GLOBALVALUEDEF -@findex GLOBALVALUEREF -GCC does not provide the @code{globalref}, @code{globaldef} and -@code{globalvalue} keywords of VAX-C@. You can get the same effect with -an obscure feature of GAS, the GNU assembler. (This requires GAS -version 1.39 or later.) The following macros allow you to use this -feature in a fairly natural way: - -@smallexample -#ifdef __GNUC__ -#define GLOBALREF(TYPE,NAME) \ - TYPE NAME \ - asm ("_$$PsectAttributes_GLOBALSYMBOL$$" #NAME) -#define GLOBALDEF(TYPE,NAME,VALUE) \ - TYPE NAME \ - asm ("_$$PsectAttributes_GLOBALSYMBOL$$" #NAME) \ - = VALUE -#define GLOBALVALUEREF(TYPE,NAME) \ - const TYPE NAME[1] \ - asm ("_$$PsectAttributes_GLOBALVALUE$$" #NAME) -#define GLOBALVALUEDEF(TYPE,NAME,VALUE) \ - const TYPE NAME[1] \ - asm ("_$$PsectAttributes_GLOBALVALUE$$" #NAME) \ - = @{VALUE@} -#else -#define GLOBALREF(TYPE,NAME) \ - globalref TYPE NAME -#define GLOBALDEF(TYPE,NAME,VALUE) \ - globaldef TYPE NAME = VALUE -#define GLOBALVALUEDEF(TYPE,NAME,VALUE) \ - globalvalue TYPE NAME = VALUE -#define GLOBALVALUEREF(TYPE,NAME) \ - globalvalue TYPE NAME -#endif -@end smallexample - -@noindent -(The @code{_$$PsectAttributes_GLOBALSYMBOL} prefix at the start of the -name is removed by the assembler, after it has modified the attributes -of the symbol). These macros are provided in the VMS binaries -distribution in a header file @file{GNU_HACKS.H}. An example of the -usage is: - -@example -GLOBALREF (int, ijk); -GLOBALDEF (int, jkl, 0); -@end example - -The macros @code{GLOBALREF} and @code{GLOBALDEF} cannot be used -straightforwardly for arrays, since there is no way to insert the array -dimension into the declaration at the right place. However, you can -declare an array with these macros if you first define a typedef for the -array type, like this: - -@example -typedef int intvector[10]; -GLOBALREF (intvector, foo); -@end example - -Array and structure initializers will also break the macros; you can -define the initializer to be a macro of its own, or you can expand the -@code{GLOBALDEF} macro by hand. You may find a case where you wish to -use the @code{GLOBALDEF} macro with a large array, but you are not -interested in explicitly initializing each element of the array. In -such cases you can use an initializer like: @code{@{0,@}}, which will -initialize the entire array to @code{0}. - -A shortcoming of this implementation is that a variable declared with -@code{GLOBALVALUEREF} or @code{GLOBALVALUEDEF} is always an array. For -example, the declaration: - -@example -GLOBALVALUEREF(int, ijk); -@end example - -@noindent -declares the variable @code{ijk} as an array of type @code{int [1]}. -This is done because a globalvalue is actually a constant; its ``value'' -is what the linker would normally consider an address. That is not how -an integer value works in C, but it is how an array works. So treating -the symbol as an array name gives consistent results---with the -exception that the value seems to have the wrong type. @strong{Don't -try to access an element of the array.} It doesn't have any elements. -The array ``address'' may not be the address of actual storage. - -The fact that the symbol is an array may lead to warnings where the -variable is used. Insert type casts to avoid the warnings. Here is an -example; it takes advantage of the ISO C feature allowing macros that -expand to use the same name as the macro itself. - -@example -GLOBALVALUEREF (int, ss$_normal); -GLOBALVALUEDEF (int, xyzzy,123); -#ifdef __GNUC__ -#define ss$_normal ((int) ss$_normal) -#define xyzzy ((int) xyzzy) -#endif -@end example - -Don't use @code{globaldef} or @code{globalref} with a variable whose -type is an enumeration type; this is not implemented. Instead, make the -variable an integer, and use a @code{globalvaluedef} for each of the -enumeration values. An example of this would be: - -@example -#ifdef __GNUC__ -GLOBALDEF (int, color, 0); -GLOBALVALUEDEF (int, RED, 0); -GLOBALVALUEDEF (int, BLUE, 1); -GLOBALVALUEDEF (int, GREEN, 3); -#else -enum globaldef color @{RED, BLUE, GREEN = 3@}; -#endif -@end example - -@node VMS Misc -@section Other VMS Issues - -@cindex exit status and VMS -@cindex return value of @code{main} -@cindex @code{main} and the exit status -GCC automatically arranges for @code{main} to return 1 by default if -you fail to specify an explicit return value. This will be interpreted -by VMS as a status code indicating a normal successful completion. -Version 1 of GCC did not provide this default. - -GCC on VMS works only with the GNU assembler, GAS@. You need version -1.37 or later of GAS in order to produce value debugging information for -the VMS debugger. Use the ordinary VMS linker with the object files -produced by GAS@. - -@cindex shared VMS run time system -@cindex @file{VAXCRTL} -Under previous versions of GCC, the generated code would occasionally -give strange results when linked to the sharable @file{VAXCRTL} library. -Now this should work. - -A caveat for use of @code{const} global variables: the @code{const} -modifier must be specified in every external declaration of the variable -in all of the source files that use that variable. Otherwise the linker -will issue warnings about conflicting attributes for the variable. Your -program will still work despite the warnings, but the variable will be -placed in writable storage. - -@cindex name augmentation -@cindex case sensitivity and VMS -@cindex VMS and case sensitivity -Although the VMS linker does distinguish between upper and lower case -letters in global symbols, most VMS compilers convert all such symbols -into upper case and most run-time library routines also have upper case -names. To be able to reliably call such routines, GCC (by means of -the assembler GAS) converts global symbols into upper case like other -VMS compilers. However, since the usual practice in C is to distinguish -case, GCC (via GAS) tries to preserve usual C behavior by augmenting -each name that is not all lower case. This means truncating the name -to at most 23 characters and then adding more characters at the end -which encode the case pattern of those 23. Names which contain at -least one dollar sign are an exception; they are converted directly into -upper case without augmentation. - -Name augmentation yields bad results for programs that use precompiled -libraries (such as Xlib) which were generated by another compiler. You -can use the compiler option @samp{/NOCASE_HACK} to inhibit augmentation; -it makes external C functions and variables case-independent as is usual -on VMS@. Alternatively, you could write all references to the functions -and variables in such libraries using lower case; this will work on VMS, -but is not portable to other systems. The compiler option @samp{/NAMES} -also provides control over global name handling. - -Function and variable names are handled somewhat differently with G++. -The GNU C++ compiler performs @dfn{name mangling} on function -names, which means that it adds information to the function name to -describe the data types of the arguments that the function takes. One -result of this is that the name of a function can become very long. -Since the VMS linker only recognizes the first 31 characters in a name, -special action is taken to ensure that each function and variable has a -unique name that can be represented in 31 characters. - -If the name (plus a name augmentation, if required) is less than 32 -characters in length, then no special action is performed. If the name -is longer than 31 characters, the assembler (GAS) will generate a -hash string based upon the function name, truncate the function name to -23 characters, and append the hash string to the truncated name. If the -@samp{/VERBOSE} compiler option is used, the assembler will print both -the full and truncated names of each symbol that is truncated. - -The @samp{/NOCASE_HACK} compiler option should not be used when you are -compiling programs that use libg++. libg++ has several instances of -objects (i.e. @code{Filebuf} and @code{filebuf}) which become -indistinguishable in a case-insensitive environment. This leads to -cases where you need to inhibit augmentation selectively (if you were -using libg++ and Xlib in the same program, for example). There is no -special feature for doing this, but you can get the result by defining a -macro for each mixed case symbol for which you wish to inhibit -augmentation. The macro should expand into the lower case equivalent of -itself. For example: - -@example -#define StuDlyCapS studlycaps -@end example - -These macro definitions can be placed in a header file to minimize the -number of changes to your source code. |