This is doc/gcc.info, produced by makeinfo version 4.2 from ../../gcc/gcc/doc/gcc.texi. Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with the Invariant Sections being "GNU 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 section entitled "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. INFO-DIR-SECTION Programming START-INFO-DIR-ENTRY * gcc: (gcc). The GNU Compiler Collection. END-INFO-DIR-ENTRY This file documents the use of the GNU compilers. Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with the Invariant Sections being "GNU 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 section entitled "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.  File: gcc.info, Node: Top, Next: G++ and GCC, Up: (DIR) Introduction ************ This manual documents how to use the GNU compilers, as well as their features and incompatibilities, and how to report bugs. It corresponds to GCC version 3.4.2. The internals of the GNU compilers, including how to port them to new targets and some information about how to write front ends for new languages, are documented in a separate manual. *Note Introduction: (gccint)Top. * Menu: * G++ and GCC:: You can compile C or C++ programs. * Standards:: Language standards supported by GCC. * Invoking GCC:: Command options supported by `gcc'. * C Implementation:: How GCC implements the ISO C specification. * C Extensions:: GNU extensions to the C language family. * C++ Extensions:: GNU extensions to the C++ language. * Objective-C:: GNU Objective-C runtime features. * Compatibility:: Binary Compatibility * Gcov:: `gcov'---a test coverage program. * Trouble:: If you have trouble using GCC. * Bugs:: How, why and where to report bugs. * Service:: How to find suppliers of support for GCC. * Contributing:: How to contribute to testing and developing GCC. * Funding:: How to help assure funding for free software. * GNU Project:: The GNU Project and GNU/Linux. * Copying:: GNU General Public License says how you can copy and share GCC. * GNU Free Documentation License:: How you can copy and share this manual. * Contributors:: People who have contributed to GCC. * Option Index:: Index to command line options. * Keyword Index:: Index of concepts and symbol names.  File: gcc.info, Node: G++ and GCC, Next: Standards, Prev: Top, Up: Top Programming Languages Supported by GCC ************************************** GCC stands for "GNU Compiler Collection". GCC is an integrated distribution of compilers for several major programming languages. These languages currently include C, C++, Objective-C, Java, Fortran, and Ada. The abbreviation "GCC" has multiple meanings in common use. The current official meaning is "GNU Compiler Collection", which refers generically to the complete suite of tools. The name historically stood for "GNU C Compiler", and this usage is still common when the emphasis is on compiling C programs. Finally, the name is also used when speaking of the "language-independent" component of GCC: code shared among the compilers for all supported languages. The language-independent component of GCC includes the majority of the optimizers, as well as the "back ends" that generate machine code for various processors. The part of a compiler that is specific to a particular language is called the "front end". In addition to the front ends that are integrated components of GCC, there are several other front ends that are maintained separately. These support languages such as Pascal, Mercury, and COBOL. To use these, they must be built together with GCC proper. Most of the compilers for languages other than C have their own names. The C++ compiler is G++, the Ada compiler is GNAT, and so on. When we talk about compiling one of those languages, we might refer to that compiler by its own name, or as GCC. Either is correct. Historically, compilers for many languages, including C++ and Fortran, have been implemented as "preprocessors" which emit another high level language such as C. None of the compilers included in GCC are implemented this way; they all generate machine code directly. This sort of preprocessor should not be confused with the "C preprocessor", which is an integral feature of the C, C++, and Objective-C languages.  File: gcc.info, Node: Standards, Next: Invoking GCC, Prev: G++ and GCC, Up: Top Language Standards Supported by GCC *********************************** For each language compiled by GCC for which there is a standard, GCC attempts to follow one or more versions of that standard, possibly with some exceptions, and possibly with some extensions. GCC supports three versions of the C standard, although support for the most recent version is not yet complete. The original ANSI C standard (X3.159-1989) was ratified in 1989 and published in 1990. This standard was ratified as an ISO standard (ISO/IEC 9899:1990) later in 1990. There were no technical differences between these publications, although the sections of the ANSI standard were renumbered and became clauses in the ISO standard. This standard, in both its forms, is commonly known as "C89", or occasionally as "C90", from the dates of ratification. The ANSI standard, but not the ISO standard, also came with a Rationale document. To select this standard in GCC, use one of the options `-ansi', `-std=c89' or `-std=iso9899:1990'; to obtain all the diagnostics required by the standard, you should also specify `-pedantic' (or `-pedantic-errors' if you want them to be errors rather than warnings). *Note Options Controlling C Dialect: C Dialect Options. Errors in the 1990 ISO C standard were corrected in two Technical Corrigenda published in 1994 and 1996. GCC does not support the uncorrected version. An amendment to the 1990 standard was published in 1995. This amendment added digraphs and `__STDC_VERSION__' to the language, but otherwise concerned the library. This amendment is commonly known as "AMD1"; the amended standard is sometimes known as "C94" or "C95". To select this standard in GCC, use the option `-std=iso9899:199409' (with, as for other standard versions, `-pedantic' to receive all required diagnostics). A new edition of the ISO C standard was published in 1999 as ISO/IEC 9899:1999, and is commonly known as "C99". GCC has incomplete support for this standard version; see `http://gcc.gnu.org/gcc-3.4/c99status.html' for details. To select this standard, use `-std=c99' or `-std=iso9899:1999'. (While in development, drafts of this standard version were referred to as "C9X".) Errors in the 1999 ISO C standard were corrected in a Technical Corrigendum published in 2001. GCC does not support the uncorrected version. By default, GCC provides some extensions to the C language that on rare occasions conflict with the C standard. *Note Extensions to the C Language Family: C Extensions. Use of the `-std' options listed above will disable these extensions where they conflict with the C standard version selected. You may also select an extended version of the C language explicitly with `-std=gnu89' (for C89 with GNU extensions) or `-std=gnu99' (for C99 with GNU extensions). The default, if no C language dialect options are given, is `-std=gnu89'; this will change to `-std=gnu99' in some future release when the C99 support is complete. Some features that are part of the C99 standard are accepted as extensions in C89 mode. The ISO C standard defines (in clause 4) two classes of conforming implementation. A "conforming hosted implementation" supports the whole standard including all the library facilities; a "conforming freestanding implementation" is only required to provide certain library facilities: those in `', `', `', and `'; since AMD1, also those in `'; and in C99, also those in `' and `'. In addition, complex types, added in C99, are not required for freestanding implementations. The standard also defines two environments for programs, a "freestanding environment", required of all implementations and which may not have library facilities beyond those required of freestanding implementations, where the handling of program startup and termination are implementation-defined, and a "hosted environment", which is not required, in which all the library facilities are provided and startup is through a function `int main (void)' or `int main (int, char *[])'. An OS kernel would be a freestanding environment; a program using the facilities of an operating system would normally be in a hosted implementation. GCC aims towards being usable as a conforming freestanding implementation, or as the compiler for a conforming hosted implementation. By default, it will act as the compiler for a hosted implementation, defining `__STDC_HOSTED__' as `1' and presuming that when the names of ISO C functions are used, they have the semantics defined in the standard. To make it act as a conforming freestanding implementation for a freestanding environment, use the option `-ffreestanding'; it will then define `__STDC_HOSTED__' to `0' and not make assumptions about the meanings of function names from the standard library, with exceptions noted below. To build an OS kernel, you may well still need to make your own arrangements for linking and startup. *Note Options Controlling C Dialect: C Dialect Options. GCC does not provide the library facilities required only of hosted implementations, nor yet all the facilities required by C99 of freestanding implementations; to use the facilities of a hosted environment, you will need to find them elsewhere (for example, in the GNU C library). *Note Standard Libraries: Standard Libraries. Most of the compiler support routines used by GCC are present in `libgcc', but there are a few exceptions. GCC requires the freestanding environment provide `memcpy', `memmove', `memset' and `memcmp'. Some older ports of GCC are configured to use the BSD `bcopy', `bzero' and `bcmp' functions instead, but this is deprecated for new ports. Finally, if `__builtin_trap' is used, and the target does not implement the `trap' pattern, then GCC will emit a call to `abort'. For references to Technical Corrigenda, Rationale documents and information concerning the history of C that is available online, see `http://gcc.gnu.org/readings.html' There is no formal written standard for Objective-C. The most authoritative manual is "Object-Oriented Programming and the Objective-C Language", available at a number of web sites * `http://developer.apple.com/techpubs/macosx/Cocoa/ObjectiveC/' is a recent version * `http://www.toodarkpark.org/computers/objc/' is an older example * `http://www.gnustep.org' has additional useful information There is no standard for treelang, which is a sample language front end for GCC. Its only purpose is as a sample for people wishing to write a new language for GCC. The language is documented in `gcc/treelang/treelang.texi' which can be turned into info or HTML format. *Note GNAT Reference Manual: (gnat_rm)Top, for information on standard conformance and compatibility of the Ada compiler. *Note The GNU Fortran Language: (g77)Language, for details of the Fortran language supported by GCC. *Note Compatibility with the Java Platform: (gcj)Compatibility, for details of compatibility between `gcj' and the Java Platform.  File: gcc.info, Node: Invoking GCC, Next: C Implementation, Prev: Standards, Up: Top GCC Command Options ******************* When you invoke GCC, it normally does preprocessing, compilation, assembly and linking. The "overall options" allow you to stop this process at an intermediate stage. For example, the `-c' option says not to run the linker. Then the output consists of object files output by the assembler. 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. Most of the command line options that you can use with GCC 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. *Note Compiling C++ Programs: Invoking G++, for a summary of special options for compiling C++ programs. The `gcc' program accepts options and file names as operands. Many options have multi-letter names; therefore multiple single-letter options may _not_ be grouped: `-dr' is very different from `-d -r'. 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 `-L' more than once, the directories are searched in the order specified. Many options have long names starting with `-f' or with `-W'--for example, `-fforce-mem', `-fstrength-reduce', `-Wformat' and so on. Most of these have both positive and negative forms; the negative form of `-ffoo' would be `-fno-foo'. This manual documents only one of these two forms, whichever one is not the default. *Note Option Index::, for an index to GCC's options. * Menu: * Option Summary:: Brief list of all options, without explanations. * Overall Options:: Controlling the kind of output: an executable, object files, assembler files, or preprocessed source. * Invoking G++:: Compiling C++ programs. * C Dialect Options:: Controlling the variant of C language compiled. * C++ Dialect Options:: Variations on C++. * Objective-C Dialect Options:: Variations on Objective-C. * Language Independent Options:: Controlling how diagnostics should be formatted. * Warning Options:: How picky should the compiler be? * Debugging Options:: Symbol tables, measurements, and debugging dumps. * Optimize Options:: How much optimization? * Preprocessor Options:: Controlling header files and macro definitions. Also, getting dependency information for Make. * Assembler Options:: Passing options to the assembler. * Link Options:: Specifying libraries and so on. * Directory Options:: Where to find header files and libraries. Where to find the compiler executable files. * Spec Files:: How to pass switches to sub-processes. * Target Options:: Running a cross-compiler, or an old version of GCC. * Submodel Options:: Specifying minor hardware or convention variations, such as 68010 vs 68020. * Code Gen Options:: Specifying conventions for function calls, data layout and register usage. * Environment Variables:: Env vars that affect GCC. * Precompiled Headers:: Compiling a header once, and using it many times. * Running Protoize:: Automatically adding or removing function prototypes.  File: gcc.info, Node: Option Summary, Next: Overall Options, Up: Invoking GCC Option Summary ============== Here is a summary of all the options, grouped by type. Explanations are in the following sections. _Overall Options_ *Note Options Controlling the Kind of Output: Overall Options. -c -S -E -o FILE -pipe -pass-exit-codes -x LANGUAGE -v -### --help --target-help --version _C Language Options_ *Note Options Controlling C Dialect: C Dialect Options. -ansi -std=STANDARD -aux-info FILENAME -fno-asm -fno-builtin -fno-builtin-FUNCTION -fhosted -ffreestanding -fms-extensions -trigraphs -no-integrated-cpp -traditional -traditional-cpp -fallow-single-precision -fcond-mismatch -fsigned-bitfields -fsigned-char -funsigned-bitfields -funsigned-char -fwritable-strings _C++ Language Options_ *Note Options Controlling C++ Dialect: C++ Dialect Options. -fabi-version=N -fno-access-control -fcheck-new -fconserve-space -fno-const-strings -fno-elide-constructors -fno-enforce-eh-specs -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-N -fuse-cxa-atexit -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 _Objective-C Language Options_ *Note Options Controlling Objective-C Dialect: Objective-C Dialect Options. -fconstant-string-class=CLASS-NAME -fgnu-runtime -fnext-runtime -fno-nil-receivers -fobjc-exceptions -freplace-objc-classes -fzero-link -gen-decls -Wno-protocol -Wselector -Wundeclared-selector _Language Independent Options_ *Note Options to Control Diagnostic Messages Formatting: Language Independent Options. -fmessage-length=N -fdiagnostics-show-location=[once|every-line] _Warning Options_ *Note Options to Request or Suppress Warnings: Warning Options. -fsyntax-only -pedantic -pedantic-errors -w -Wextra -Wall -Waggregate-return -Wcast-align -Wcast-qual -Wchar-subscripts -Wcomment -Wconversion -Wno-deprecated-declarations -Wdisabled-optimization -Wno-div-by-zero -Wendif-labels -Werror -Werror-implicit-function-declaration -Wfloat-equal -Wformat -Wformat=2 -Wno-format-extra-args -Wformat-nonliteral -Wformat-security -Wformat-y2k -Wimplicit -Wimplicit-function-declaration -Wimplicit-int -Wimport -Wno-import -Winit-self -Winline -Wno-invalid-offsetof -Winvalid-pch -Wlarger-than-LEN -Wlong-long -Wmain -Wmissing-braces -Wmissing-format-attribute -Wmissing-noreturn -Wno-multichar -Wnonnull -Wpacked -Wpadded -Wparentheses -Wpointer-arith -Wredundant-decls -Wreturn-type -Wsequence-point -Wshadow -Wsign-compare -Wstrict-aliasing -Wswitch -Wswitch-default -Wswitch-enum -Wsystem-headers -Wtrigraphs -Wundef -Wuninitialized -Wunknown-pragmas -Wunreachable-code -Wunused -Wunused-function -Wunused-label -Wunused-parameter -Wunused-value -Wunused-variable -Wwrite-strings _C-only Warning Options_ -Wbad-function-cast -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Wtraditional -Wdeclaration-after-statement _Debugging Options_ *Note Options for Debugging Your Program or GCC: Debugging Options. -dLETTERS -dumpspecs -dumpmachine -dumpversion -fdump-unnumbered -fdump-translation-unit[-N] -fdump-class-hierarchy[-N] -fdump-tree-original[-N] -fdump-tree-optimized[-N] -fdump-tree-inlined[-N] -feliminate-dwarf2-dups -feliminate-unused-debug-types -feliminate-unused-debug-symbols -fmem-report -fprofile-arcs -frandom-seed=STRING -fsched-verbose=N -ftest-coverage -ftime-report -g -gLEVEL -gcoff -gdwarf-2 -ggdb -gstabs -gstabs+ -gvms -gxcoff -gxcoff+ -p -pg -print-file-name=LIBRARY -print-libgcc-file-name -print-multi-directory -print-multi-lib -print-prog-name=PROGRAM -print-search-dirs -Q -save-temps -time _Optimization Options_ *Note Options that Control Optimization: Optimize Options. -falign-functions=N -falign-jumps=N -falign-labels=N -falign-loops=N -fbranch-probabilities -fprofile-values -fvpt -fbranch-target-load-optimize -fbranch-target-load-optimize2 -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 -fgcse-las -floop-optimize -fcrossjumping -fif-conversion -fif-conversion2 -finline-functions -finline-limit=N -fkeep-inline-functions -fkeep-static-consts -fmerge-constants -fmerge-all-constants -fmove-all-movables -fnew-ra -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 -ffinite-math-only -fno-trapping-math -fno-zero-initialized-in-bss -fomit-frame-pointer -foptimize-register-move -foptimize-sibling-calls -fprefetch-loop-arrays -fprofile-generate -fprofile-use -freduce-all-givs -fregmove -frename-registers -freorder-blocks -freorder-functions -frerun-cse-after-loop -frerun-loop-opt -frounding-math -fschedule-insns -fschedule-insns2 -fno-sched-interblock -fno-sched-spec -fsched-spec-load -fsched-spec-load-dangerous -fsched-stalled-insns=N -sched-stalled-insns-dep=N -fsched2-use-superblocks -fsched2-use-traces -fsignaling-nans -fsingle-precision-constant -fstrength-reduce -fstrict-aliasing -ftracer -fthread-jumps -funroll-all-loops -funroll-loops -fpeel-loops -funswitch-loops -fold-unroll-loops -fold-unroll-all-loops --param NAME=VALUE -O -O0 -O1 -O2 -O3 -Os _Preprocessor Options_ *Note Options Controlling the Preprocessor: Preprocessor Options. -AQUESTION=ANSWER -A-QUESTION[=ANSWER] -C -dD -dI -dM -dN -DMACRO[=DEFN] -E -H -idirafter DIR -include FILE -imacros FILE -iprefix FILE -iwithprefix DIR -iwithprefixbefore DIR -isystem DIR -M -MM -MF -MG -MP -MQ -MT -nostdinc -P -fworking-directory -remap -trigraphs -undef -UMACRO -Wp,OPTION -Xpreprocessor OPTION _Assembler Option_ *Note Passing Options to the Assembler: Assembler Options. -Wa,OPTION -Xassembler OPTION _Linker Options_ *Note Options for Linking: Link Options. OBJECT-FILE-NAME -lLIBRARY -nostartfiles -nodefaultlibs -nostdlib -pie -s -static -static-libgcc -shared -shared-libgcc -symbolic -Wl,OPTION -Xlinker OPTION -u SYMBOL _Directory Options_ *Note Options for Directory Search: Directory Options. -BPREFIX -IDIR -I- -LDIR -specs=FILE _Target Options_ *Note Target Options::. -V VERSION -b MACHINE _Machine Dependent Options_ *Note Hardware Models and Configurations: Submodel Options. _M680x0 Options_ -m68000 -m68020 -m68020-40 -m68020-60 -m68030 -m68040 -m68060 -mcpu32 -m5200 -m68881 -mbitfield -mc68000 -mc68020 -mnobitfield -mrtd -mshort -msoft-float -mpcrel -malign-int -mstrict-align -msep-data -mno-sep-data -mshared-library-id=n -mid-shared-library -mno-id-shared-library _M68hc1x Options_ -m6811 -m6812 -m68hc11 -m68hc12 -m68hcs12 -mauto-incdec -minmax -mlong-calls -mshort -msoft-reg-count=COUNT _VAX Options_ -mg -mgnu -munix _SPARC Options_ -mcpu=CPU-TYPE -mtune=CPU-TYPE -mcmodel=CODE-MODEL -m32 -m64 -mapp-regs -mno-app-regs -mfaster-structs -mno-faster-structs -mflat -mno-flat -mfpu -mno-fpu -mhard-float -msoft-float -mhard-quad-float -msoft-quad-float -mimpure-text -mno-impure-text -mlittle-endian -mstack-bias -mno-stack-bias -munaligned-doubles -mno-unaligned-doubles -mv8plus -mno-v8plus -mvis -mno-vis -mcypress -mf930 -mf934 -msparclite -msupersparc -mv8 -threads -pthreads _ARM Options_ -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=NAME -march=NAME -mfpe=NAME -mstructure-size-boundary=N -mabort-on-noreturn -mlong-calls -mno-long-calls -msingle-pic-base -mno-single-pic-base -mpic-register=REG -mnop-fun-dllimport -mcirrus-fix-invalid-insns -mno-cirrus-fix-invalid-insns -mpoke-function-name -mthumb -marm -mtpcs-frame -mtpcs-leaf-frame -mcaller-super-interworking -mcallee-super-interworking _MN10300 Options_ -mmult-bug -mno-mult-bug -mam33 -mno-am33 -mam33-2 -mno-am33-2 -mno-crt0 -mrelax _M32R/D Options_ -m32r2 -m32rx -m32r -mdebug -malign-loops -mno-align-loops -missue-rate=NUMBER -mbranch-cost=NUMBER -mmodel=CODE-SIZE-MODEL-TYPE -msdata=SDATA-TYPE -mno-flush-func -mflush-func=NAME -mno-flush-trap -mflush-trap=NUMBER -G NUM _RS/6000 and PowerPC Options_ -mcpu=CPU-TYPE -mtune=CPU-TYPE -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 -malign-power -malign-natural -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 -mdynamic-no-pic -mprioritize-restricted-insns=PRIORITY -msched-costly-dep=DEPENDENCE_TYPE -minsert-sched-nops=SCHEME -mcall-sysv -mcall-netbsd -maix-struct-return -msvr4-struct-return -mabi=altivec -mabi=no-altivec -mabi=spe -mabi=no-spe -misel=yes -misel=no -mspe=yes -mspe=no -mfloat-gprs=yes -mfloat-gprs=no -mprototype -mno-prototype -msim -mmvme -mads -myellowknife -memb -msdata -msdata=OPT -mvxworks -mwindiss -G NUM -pthread _Darwin Options_ -all_load -allowable_client -arch -arch_errors_fatal -arch_only -bind_at_load -bundle -bundle_loader -client_name -compatibility_version -current_version -dependency-file -dylib_file -dylinker_install_name -dynamic -dynamiclib -exported_symbols_list -filelist -flat_namespace -force_cpusubtype_ALL -force_flat_namespace -headerpad_max_install_names -image_base -init -install_name -keep_private_externs -multi_module -multiply_defined -multiply_defined_unused -noall_load -nofixprebinding -nomultidefs -noprebind -noseglinkedit -pagezero_size -prebind -prebind_all_twolevel_modules -private_bundle -read_only_relocs -sectalign -sectobjectsymbols -whyload -seg1addr -sectcreate -sectobjectsymbols -sectorder -seg_addr_table -seg_addr_table_filename -seglinkedit -segprot -segs_read_only_addr -segs_read_write_addr -single_module -static -sub_library -sub_umbrella -twolevel_namespace -umbrella -undefined -unexported_symbols_list -weak_reference_mismatches -whatsloaded _MIPS Options_ -EL -EB -march=ARCH -mtune=ARCH -mips1 -mips2 -mips3 -mips4 -mips32 -mips32r2 -mips64 -mips16 -mno-mips16 -mabi=ABI -mabicalls -mno-abicalls -mxgot -mno-xgot -membedded-pic -mno-embedded-pic -mgp32 -mgp64 -mfp32 -mfp64 -mhard-float -msoft-float -msingle-float -mdouble-float -mint64 -mlong64 -mlong32 -GNUM -membedded-data -mno-embedded-data -muninit-const-in-rodata -mno-uninit-const-in-rodata -msplit-addresses -mno-split-addresses -mexplicit-relocs -mno-explicit-relocs -mrnames -mno-rnames -mcheck-zero-division -mno-check-zero-division -mmemcpy -mno-memcpy -mlong-calls -mno-long-calls -mmad -mno-mad -mfused-madd -mno-fused-madd -nocpp -mfix-sb1 -mno-fix-sb1 -mflush-func=FUNC -mno-flush-func -mbranch-likely -mno-branch-likely _i386 and x86-64 Options_ -mtune=CPU-TYPE -march=CPU-TYPE -mfpmath=UNIT -masm=DIALECT -mno-fancy-math-387 -mno-fp-ret-in-387 -msoft-float -msvr3-shlib -mno-wide-multiply -mrtd -malign-double -mpreferred-stack-boundary=NUM -mmmx -msse -msse2 -msse3 -m3dnow -mthreads -mno-align-stringops -minline-all-stringops -mpush-args -maccumulate-outgoing-args -m128bit-long-double -m96bit-long-double -mregparm=NUM -momit-leaf-frame-pointer -mno-red-zone -mno-tls-direct-seg-refs -mcmodel=CODE-MODEL -m32 -m64 -mstack-arg-probe _HPPA Options_ -march=ARCHITECTURE-TYPE -mbig-switch -mdisable-fpregs -mdisable-indexing -mfast-indirect-calls -mgas -mgnu-ld -mhp-ld -mjump-in-delay -mlinker-opt -mlong-calls -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=CPU-TYPE -mspace-regs -msio -mwsio -nolibdld -static -threads _Intel 960 Options_ -mCPU-TYPE -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 _DEC Alpha Options_ -mno-fp-regs -msoft-float -malpha-as -mgas -mieee -mieee-with-inexact -mieee-conformant -mfp-trap-mode=MODE -mfp-rounding-mode=MODE -mtrap-precision=MODE -mbuild-constants -mcpu=CPU-TYPE -mtune=CPU-TYPE -mbwx -mmax -mfix -mcix -mfloat-vax -mfloat-ieee -mexplicit-relocs -msmall-data -mlarge-data -msmall-text -mlarge-text -mmemory-latency=TIME _DEC Alpha/VMS Options_ -mvms-return-codes _H8/300 Options_ -mrelax -mh -ms -mn -mint32 -malign-300 _SH Options_ -m1 -m2 -m2e -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 _System V Options_ -Qy -Qn -YP,PATHS -Ym,DIR _ARC Options_ -EB -EL -mmangle-cpu -mcpu=CPU -mtext=TEXT-SECTION -mdata=DATA-SECTION -mrodata=READONLY-DATA-SECTION _TMS320C3x/C4x Options_ -mcpu=CPU -mbig -msmall -mregparm -mmemparm -mfast-fix -mmpyi -mbk -mti -mdp-isr-reload -mrpts=COUNT -mrptb -mdb -mloop-unsigned -mparallel-insns -mparallel-mpy -mpreserve-float _V850 Options_ -mlong-calls -mno-long-calls -mep -mno-ep -mprolog-function -mno-prolog-function -mspace -mtda=N -msda=N -mzda=N -mapp-regs -mno-app-regs -mdisable-callt -mno-disable-callt -mv850e1 -mv850e -mv850 -mbig-switch _NS32K Options_ -m32032 -m32332 -m32532 -m32081 -m32381 -mmult-add -mnomult-add -msoft-float -mrtd -mnortd -mregparam -mnoregparam -msb -mnosb -mbitfield -mnobitfield -mhimem -mnohimem _AVR Options_ -mmcu=MCU -msize -minit-stack=N -mno-interrupts -mcall-prologues -mno-tablejump -mtiny-stack _MCore Options_ -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 _MMIX Options_ -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 -msingle-exit -mno-single-exit _IA-64 Options_ -mbig-endian -mlittle-endian -mgnu-as -mgnu-ld -mno-pic -mvolatile-asm-stop -mb-step -mregister-names -mno-sdata -mconstant-gp -mauto-pic -minline-float-divide-min-latency -minline-float-divide-max-throughput -minline-int-divide-min-latency -minline-int-divide-max-throughput -mno-dwarf2-asm -mfixed-range=REGISTER-RANGE _D30V Options_ -mextmem -mextmemory -monchip -mno-asm-optimize -masm-optimize -mbranch-cost=N -mcond-exec=N _S/390 and zSeries Options_ -mtune=CPU-TYPE -march=CPU-TYPE -mhard-float -msoft-float -mbackchain -mno-backchain -msmall-exec -mno-small-exec -mmvcle -mno-mvcle -m64 -m31 -mdebug -mno-debug -mesa -mzarch -mfused-madd -mno-fused-madd _CRIS Options_ -mcpu=CPU -march=CPU -mtune=CPU -mmax-stack-frame=N -melinux-stacksize=N -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 -mmul-bug-workaround -mno-mul-bug-workaround _PDP-11 Options_ -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 _Xstormy16 Options_ -msim _Xtensa Options_ -mconst16 -mno-const16 -mfused-madd -mno-fused-madd -mtext-section-literals -mno-text-section-literals -mtarget-align -mno-target-align -mlongcalls -mno-longcalls _FRV Options_ -mgpr-32 -mgpr-64 -mfpr-32 -mfpr-64 -mhard-float -msoft-float -malloc-cc -mfixed-cc -mdword -mno-dword -mdouble -mno-double -mmedia -mno-media -mmuladd -mno-muladd -mlibrary-pic -macc-4 -macc-8 -mpack -mno-pack -mno-eflags -mcond-move -mno-cond-move -mscc -mno-scc -mcond-exec -mno-cond-exec -mvliw-branch -mno-vliw-branch -mmulti-cond-exec -mno-multi-cond-exec -mnested-cond-exec -mno-nested-cond-exec -mtomcat-stats -mcpu=CPU _Code Generation Options_ *Note Options for Code Generation Conventions: Code Gen Options. -fcall-saved-REG -fcall-used-REG -ffixed-REG -fexceptions -fnon-call-exceptions -funwind-tables -fasynchronous-unwind-tables -finhibit-size-directive -finstrument-functions -fno-common -fno-ident -fpcc-struct-return -fpic -fPIC -fpie -fPIE -freg-struct-return -fshared-data -fshort-enums -fshort-double -fshort-wchar -fverbose-asm -fpack-struct -fstack-check -fstack-limit-register=REG -fstack-limit-symbol=SYM -fargument-alias -fargument-noalias -fargument-noalias-global -fleading-underscore -ftls-model=MODEL -ftrapv -fwrapv -fbounds-check * Menu: * Overall Options:: Controlling the kind of output: an executable, object files, assembler files, or preprocessed source. * C Dialect Options:: Controlling the variant of C language compiled. * C++ Dialect Options:: Variations on C++. * Objective-C Dialect Options:: Variations on Objective-C. * Language Independent Options:: Controlling how diagnostics should be formatted. * Warning Options:: How picky should the compiler be? * Debugging Options:: Symbol tables, measurements, and debugging dumps. * Optimize Options:: How much optimization? * Preprocessor Options:: Controlling header files and macro definitions. Also, getting dependency information for Make. * Assembler Options:: Passing options to the assembler. * Link Options:: Specifying libraries and so on. * Directory Options:: Where to find header files and libraries. Where to find the compiler executable files. * Spec Files:: How to pass switches to sub-processes. * Target Options:: Running a cross-compiler, or an old version of GCC.  File: gcc.info, Node: Overall Options, Next: Invoking G++, Prev: Option Summary, Up: Invoking GCC Options Controlling the Kind of Output ====================================== Compilation can involve up to four stages: preprocessing, compilation proper, assembly and linking, always in that order. GCC is capable of preprocessing and compiling several files either into several assembler input files, or into one assembler input file; then each assembler input file produces an object file, and linking combines all the object files (those newly compiled, and those specified as input) into an executable file. For any given input file, the file name suffix determines what kind of compilation is done: `FILE.c' C source code which must be preprocessed. `FILE.i' C source code which should not be preprocessed. `FILE.ii' C++ source code which should not be preprocessed. `FILE.m' Objective-C source code. Note that you must link with the library `libobjc.a' to make an Objective-C program work. `FILE.mi' Objective-C source code which should not be preprocessed. `FILE.h' C or C++ header file to be turned into a precompiled header. `FILE.cc' `FILE.cp' `FILE.cxx' `FILE.cpp' `FILE.CPP' `FILE.c++' `FILE.C' C++ source code which must be preprocessed. Note that in `.cxx', the last two letters must both be literally `x'. Likewise, `.C' refers to a literal capital C. `FILE.hh' `FILE.H' C++ header file to be turned into a precompiled header. `FILE.f' `FILE.for' `FILE.FOR' Fortran source code which should not be preprocessed. `FILE.F' `FILE.fpp' `FILE.FPP' Fortran source code which must be preprocessed (with the traditional preprocessor). `FILE.r' Fortran source code which must be preprocessed with a RATFOR preprocessor (not included with GCC). *Note Options Controlling the Kind of Output: (g77)Overall Options, for more details of the handling of Fortran input files. `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 "specs". `FILE.adb' Ada source code file containing a library unit body (a subprogram or package body). Such files are also called "bodies". `FILE.s' Assembler code. `FILE.S' Assembler code which must be preprocessed. `OTHER' An object file to be fed straight into linking. Any file name with no recognized suffix is treated this way. You can specify the input language explicitly with the `-x' option: `-x LANGUAGE' Specify explicitly the LANGUAGE 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 `-x' option. Possible values for LANGUAGE are: c c-header cpp-output c++ c++-header c++-cpp-output objective-c objective-c-header objc-cpp-output assembler assembler-with-cpp ada f77 f77-cpp-input ratfor java treelang `-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 `-x' has not been used at all). `-pass-exit-codes' Normally the `gcc' program will exit with the code of 1 if any phase of the compiler returns a non-success return code. If you specify `-pass-exit-codes', the `gcc' program will instead return with numerically highest error produced by any phase that returned an error indication. If you only want some of the stages of compilation, you can use `-x' (or filename suffixes) to tell `gcc' where to start, and one of the options `-c', `-S', or `-E' to say where `gcc' is to stop. Note that some combinations (for example, `-x cpp-output -E') instruct `gcc' to do nothing at all. `-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. By default, the object file name for a source file is made by replacing the suffix `.c', `.i', `.s', etc., with `.o'. Unrecognized input files, not requiring compilation or assembly, are ignored. `-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. By default, the assembler file name for a source file is made by replacing the suffix `.c', `.i', etc., with `.s'. Input files that don't require compilation are ignored. `-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. Input files which don't require preprocessing are ignored. `-o FILE' Place output in file FILE. 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. If you specify `-o' when compiling more than one input file, or you are producing an executable file as output, all the source files on the command line will be compiled at once. If `-o' is not specified, the default is to put an executable file in `a.out', the object file for `SOURCE.SUFFIX' in `SOURCE.o', its assembler file in `SOURCE.s', and all preprocessed C source on standard output. `-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. `-###' Like `-v' 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. `-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 GNU assembler has no trouble. `--help' Print (on the standard output) a description of the command line options understood by `gcc'. If the `-v' option is also specified then `--help' will also be passed on to the various processes invoked by `gcc', so that they can display the command line options they accept. If the `-Wextra' option is also specified then command line options which have no documentation associated with them will also be displayed. `--target-help' Print (on the standard output) a description of target specific command line options for each tool. `--version' Display the version number and copyrights of the invoked GCC.  File: gcc.info, Node: Invoking G++, Next: C Dialect Options, Prev: Overall Options, Up: Invoking GCC Compiling C++ Programs ====================== C++ source files conventionally use one of the suffixes `.C', `.cc', `.cpp', `.CPP', `.c++', `.cp', or `.cxx'; C++ header files often use `.hh' or `.H'; and preprocessed C++ files use the suffix `.ii'. GCC 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 `gcc'). 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 or header files from standard input, or otherwise without a suffix that flags them as C++ programs. You might also like to precompile a C header file with a `.h' extension to be used in C++ compilations. `g++' is a program that calls GCC with the default language set to C++, and automatically specifies linking against the C++ library. On many systems, `g++' is also installed with the name `c++'. 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. *Note Options Controlling C Dialect: C Dialect Options, for explanations of options for languages related to C. *Note Options Controlling C++ Dialect: C++ Dialect Options, for explanations of options that are meaningful only for C++ programs.  File: gcc.info, Node: C Dialect Options, Next: C++ Dialect Options, Prev: Invoking G++, Up: Invoking GCC 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: `-ansi' In C mode, support all ISO C90 programs. In C++ mode, remove GNU extensions that conflict with ISO C++. This turns off certain features of GCC that are incompatible with ISO C90 (when compiling C code), or of standard C++ (when compiling C++ code), such as the `asm' and `typeof' keywords, and predefined macros such as `unix' and `vax' that identify the type of system you are using. It also enables the undesirable and rarely used ISO trigraph feature. For the C compiler, it disables recognition of C++ style `//' comments as well as the `inline' keyword. The alternate keywords `__asm__', `__extension__', `__inline__' and `__typeof__' continue to work despite `-ansi'. You would not want to use them in an ISO C program, of course, but it is useful to put them in header files that might be included in compilations done with `-ansi'. Alternate predefined macros such as `__unix__' and `__vax__' are also available, with or without `-ansi'. The `-ansi' option does not cause non-ISO programs to be rejected gratuitously. For that, `-pedantic' is required in addition to `-ansi'. *Note Warning Options::. The macro `__STRICT_ANSI__' is predefined when the `-ansi' option is used. Some header files may notice this macro and refrain from declaring certain functions or defining certain macros that the ISO standard doesn't call for; this is to avoid interfering with any programs that might use these names for other things. Functions which would normally be built in but do not have semantics defined by ISO C (such as `alloca' and `ffs') are not built-in functions with `-ansi' is used. *Note Other built-in functions provided by GCC: Other Builtins, for details of the functions affected. `-std=' Determine the language standard. This option is currently only supported when compiling C or C++. A value for this option must be provided; possible values are `c89' `iso9899:1990' ISO C90 (same as `-ansi'). `iso9899:199409' ISO C90 as modified in amendment 1. `c99' `c9x' `iso9899:1999' `iso9899:199x' ISO C99. Note that this standard is not yet fully supported; see `http://gcc.gnu.org/gcc-3.4/c99status.html' for more information. The names `c9x' and `iso9899:199x' are deprecated. `gnu89' Default, ISO C90 plus GNU extensions (including some C99 features). `gnu99' `gnu9x' ISO C99 plus GNU extensions. When ISO C99 is fully implemented in GCC, this will become the default. The name `gnu9x' is deprecated. `c++98' The 1998 ISO C++ standard plus amendments. `gnu++98' The same as `-std=c++98' plus GNU extensions. This is the default for C++ code. 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 `__restrict__' even when `-std=c99' is not specified. The `-std' options specifying some version of ISO C have the same effects as `-ansi', except that features that were not in ISO C90 but are in the specified version (for example, `//' comments and the `inline' keyword in ISO C99) are not disabled. *Note Language Standards Supported by GCC: Standards, for details of these standard versions. `-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. Besides declarations, the file indicates, in comments, the origin of each declaration (source file and line), whether the declaration was implicit, prototyped or unprototyped (`I', `N' for new or `O' for old, respectively, in the first character after the line number and the colon), and whether it came from a declaration or a definition (`C' or `F', 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. `-fno-asm' Do not recognize `asm', `inline' or `typeof' as a keyword, so that code can use these words as identifiers. You can use the keywords `__asm__', `__inline__' and `__typeof__' instead. `-ansi' implies `-fno-asm'. In C++, this switch only affects the `typeof' keyword, since `asm' and `inline' are standard keywords. You may want to use the `-fno-gnu-keywords' flag instead, which has the same effect. In C99 mode (`-std=c99' or `-std=gnu99'), this switch only affects the `asm' and `typeof' keywords, since `inline' is a standard keyword in ISO C99. `-fno-builtin' `-fno-builtin-FUNCTION' Don't recognize built-in functions that do not begin with `__builtin_' as prefix. *Note Other built-in functions provided by GCC: Other Builtins, for details of the functions affected, including those which are not built-in functions when `-ansi' or `-std' options for strict ISO C conformance are used because they do not have an ISO standard meaning. GCC normally generates special code to handle certain built-in functions more efficiently; for instance, calls to `alloca' may become single instructions that adjust the stack directly, and calls to `memcpy' 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. With the `-fno-builtin-FUNCTION' option only the built-in function FUNCTION is disabled. FUNCTION must not begin with `__builtin_'. If a function is named this is not built-in in this version of GCC, this option is ignored. There is no corresponding `-fbuiltin-FUNCTION' option; if you wish to enable built-in functions selectively when using `-fno-builtin' or `-ffreestanding', you may define macros such as: #define abs(n) __builtin_abs ((n)) #define strcpy(d, s) __builtin_strcpy ((d), (s)) `-fhosted' Assert that compilation takes place in a hosted environment. This implies `-fbuiltin'. A hosted environment is one in which the entire standard library is available, and in which `main' has a return type of `int'. Examples are nearly everything except a kernel. This is equivalent to `-fno-freestanding'. `-ffreestanding' Assert that compilation takes place in a freestanding environment. This implies `-fno-builtin'. A freestanding environment is one in which the standard library may not exist, and program startup may not necessarily be at `main'. The most obvious example is an OS kernel. This is equivalent to `-fno-hosted'. *Note Language Standards Supported by GCC: Standards, for details of freestanding and hosted environments. `-fms-extensions' Accept some non-standard constructs used in Microsoft header files. `-trigraphs' Support ISO C trigraphs. The `-ansi' option (and `-std' options for strict ISO C conformance) implies `-trigraphs'. `-no-integrated-cpp' Performs a compilation in two passes: preprocessing and compiling. This option allows a user supplied "cc1", "cc1plus", or "cc1obj" via the `-B' option. The user supplied compilation step can then add in an additional preprocessing step after normal preprocessing but before compiling. The default is to use the integrated cpp (internal cpp) The semantics of this option will change if "cc1", "cc1plus", and "cc1obj" are merged. `-traditional' `-traditional-cpp' Formerly, these options caused GCC to attempt to emulate a pre-standard C compiler. They are now only supported with the `-E' switch. The preprocessor continues to support a pre-standard mode. See the GNU CPP manual for details. `-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++. `-funsigned-char' Let the type `char' be unsigned, like `unsigned char'. Each kind of machine has a default for what `char' should be. It is either like `unsigned char' by default or like `signed char' by default. Ideally, a portable program should always use `signed char' or `unsigned char' when it depends on the signedness of an object. But many programs have been written to use plain `char' 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. The type `char' is always a distinct type from each of `signed char' or `unsigned char', even though its behavior is always just like one of those two. `-fsigned-char' Let the type `char' be signed, like `signed char'. Note that this is equivalent to `-fno-unsigned-char', which is the negative form of `-funsigned-char'. Likewise, the option `-fno-signed-char' is equivalent to `-funsigned-char'. `-fsigned-bitfields' `-funsigned-bitfields' `-fno-signed-bitfields' `-fno-unsigned-bitfields' These options control whether a bit-field is signed or unsigned, when the declaration does not use either `signed' or `unsigned'. By default, such a bit-field is signed, because this is consistent: the basic integer types such as `int' are signed types. `-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. Writing into string constants is a very bad idea; "constants" should be constant. This option is deprecated.  File: gcc.info, Node: C++ Dialect Options, Next: Objective-C Dialect Options, Prev: C Dialect Options, Up: Invoking GCC Options Controlling C++ Dialect =============================== This section describes the command-line options that are only meaningful for C++ programs; but you can also use most of the GNU compiler options regardless of what language your program is in. For example, you might compile a file `firstClass.C' like this: g++ -g -frepo -O -c firstClass.C In this example, only `-frepo' is an option meant only for C++ programs; you can use the other options with any language supported by GCC. Here is a list of options that are _only_ for compiling C++ programs: `-fabi-version=N' Use version N of the C++ ABI. Version 2 is the version of the C++ ABI that first appeared in G++ 3.4. Version 1 is the version of the C++ ABI that first appeared in G++ 3.2. Version 0 will always be the version that conforms most closely to the C++ ABI specification. Therefore, the ABI obtained using version 0 will change as ABI bugs are fixed. The default is version 2. `-fno-access-control' Turn off all access checking. This switch is mainly useful for working around bugs in the access control code. `-fcheck-new' Check that the pointer returned by `operator new' is non-null before attempting to modify the storage allocated. This check is normally unnecessary because the C++ standard specifies that `operator new' will only return `0' if it is declared `throw()', in which case the compiler will always check the return value even without this option. In all other cases, when `operator new' has a non-empty exception specification, memory exhaustion is signalled by throwing `std::bad_alloc'. See also `new (nothrow)'. `-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 `main()' has completed, you may have an object that is being destroyed twice because two definitions were merged. This option is no longer useful on most targets, now that support has been added for putting variables into BSS without making them common. `-fno-const-strings' Give string constants type `char *' instead of type `const char *'. By default, G++ uses type `const char *' as required by the standard. Even if you use `-fno-const-strings', you cannot actually modify the value of a string constant, unless you also use `-fwritable-strings'. 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 `const char *'. `-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. `-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 `NDEBUG'. The compiler will still optimize based on the exception specifications. `-ffor-scope' `-fno-for-scope' If `-ffor-scope' is specified, the scope of variables declared in a for-init-statement is limited to the `for' loop itself, as specified by the C++ standard. If `-fno-for-scope' is specified, the scope of variables declared in a for-init-statement extends to the end of the enclosing scope, as was the case in old versions of G++, and other (traditional) implementations of C++. 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. `-fno-gnu-keywords' Do not recognize `typeof' as a keyword, so that code can use this word as an identifier. You can use the keyword `__typeof__' instead. `-ansi' implies `-fno-gnu-keywords'. `-fno-implicit-templates' Never emit code for non-inline templates which are instantiated implicitly (i.e. by use); only emit code for explicit instantiations. *Note Template Instantiation::, for more information. `-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. `-fno-implement-inlines' To save space, do not emit out-of-line copies of inline functions controlled by `#pragma implementation'. This will cause linker errors if these functions are not inlined everywhere they are called. `-fms-extensions' Disable pedantic warnings about constructs used in MFC, such as implicit int and getting a pointer to member function via non-standard syntax. `-fno-nonansi-builtins' Disable built-in declarations of functions that are not mandated by ANSI/ISO C. These include `ffs', `alloca', `_exit', `index', `bzero', `conjf', and other related functions. `-fno-operator-names' Do not treat the operator name keywords `and', `bitand', `bitor', `compl', `not', `or' and `xor' as synonyms as keywords. `-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. `-fpermissive' Downgrade some diagnostics about nonconformant code from errors to warnings. Thus, using `-fpermissive' will allow some nonconforming code to compile. `-frepo' Enable automatic template instantiation at link time. This option also implies `-fno-implicit-templates'. *Note Template Instantiation::, for more information. `-fno-rtti' Disable generation of information about every class with virtual functions for use by the C++ runtime type identification features (`dynamic_cast' and `typeid'). 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. `-fstats' Emit statistics about front-end processing at the end of the compilation. This information is generally only useful to the G++ development team. `-ftemplate-depth-N' Set the maximum instantiation depth for template classes to N. A limit on the template instantiation depth is needed to detect endless recursions during template class instantiation. ANSI/ISO C++ conforming programs must not rely on a maximum depth greater than 17. `-fuse-cxa-atexit' Register destructors for objects with static storage duration with the `__cxa_atexit' function rather than the `atexit' function. This option is required for fully standards-compliant handling of static destructors, but will only work if your C library supports `__cxa_atexit'. `-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++. `-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.) In addition, these optimization, warning, and code generation options have meanings only for C++ programs: `-fno-default-inline' Do not assume `inline' for functions defined inside a class scope. *Note Options That Control Optimization: Optimize Options. Note that these functions will have linkage like inline functions; they just won't be inlined by default. `-Wabi (C++ only)' Warn when G++ generates code that is probably not compatible with the vendor-neutral C++ ABI. 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. 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. The known incompatibilities at this point include: * Incorrect handling of tail-padding for bit-fields. G++ may attempt to pack data into the same byte as a base class. For example: struct A { virtual void f(); int f1 : 1; }; struct B : public A { int f2 : 1; }; In this case, G++ will place `B::f2' into the same byte as`A::f1'; other compilers will not. You can avoid this problem by explicitly padding `A' so that its size is a multiple of the byte size on your platform; that will cause G++ and other compilers to layout `B' identically. * Incorrect handling of tail-padding for virtual bases. G++ does not use tail padding when laying out virtual bases. For example: struct A { virtual void f(); char c1; }; struct B { B(); char c2; }; struct C : public A, public virtual B {}; In this case, G++ will not place `B' into the tail-padding for `A'; other compilers will. You can avoid this problem by explicitly padding `A' so that its size is a multiple of its alignment (ignoring virtual base classes); that will cause G++ and other compilers to layout `C' identically. * Incorrect handling of bit-fields with declared widths greater than that of their underlying types, when the bit-fields appear in a union. For example: union U { int i : 4096; }; Assuming that an `int' does not have 4096 bits, G++ will make the union too small by the number of bits in an `int'. * Empty classes can be placed at incorrect offsets. For example: struct A {}; struct B { A a; virtual void f (); }; struct C : public B, public A {}; G++ will place the `A' base class of `C' at a nonzero offset; it should be placed at offset zero. G++ mistakenly believes that the `A' data member of `B' is already at offset zero. * Names of template functions whose types involve `typename' or template template parameters can be mangled incorrectly. template void f(typename Q::X) {} template