FreeBSD Manual Pages
GCC(1) GNU GCC(1) NAME gcc - GNU project C and C++ compiler SYNOPSIS gcc [-c|-S|-E] [-std=standard] [-g] [-pg] [-Olevel] [-Wwarn...] [-Wpedantic] [-Idir...] [-Ldir...] [-Dmacro[=defn]...] [-Umacro] [-foption...] [-mmachine-option...] [-o outfile] [@file] infile... Only the most useful options are listed here; see below for the remainder. g++ accepts mostly the same options as gcc. DESCRIPTION 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 or more stages of processing. Some op- tions 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 partic- ular option does not mention a source language, you can use that option with all supported languages. The usual way to run GCC is to run the executable called gcc, or ma- chine-gcc when cross-compiling, or machine-gcc-version to run a specific version of GCC. When you compile C++ programs, you should invoke GCC as g++ instead. 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: -dv is very different from -d -v. 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. Also, the placement of the -l option is significant. Many options have long names starting with -f or with -W---for example, -fmove-loop-invariants, -Wformat and so on. Most of these have both posi- tive and negative forms; the negative form of -ffoo is -fno-foo. This man- ual documents only one of these two forms, whichever one is not the de- fault. Some options take one or more arguments typically separated either by a space or by the equals sign (=) from the option name. Unless documented otherwise, an argument can be either numeric or a string. Numeric argu- ments must typically be small unsigned decimal or hexadecimal integers. Hexadecimal arguments must begin with the 0x prefix. Arguments to options that specify a size threshold of some sort may be arbitrarily large decimal or hexadecimal integers followed by a byte size suffix designating a multi- ple of bytes such as "kB" and "KiB" for kilobyte and kibibyte, respec- tively, "MB" and "MiB" for megabyte and mebibyte, "GB" and "GiB" for giga- byte and gigibyte, and so on. Such arguments are designated by byte-size in the following text. Refer to the NIST, IEC, and other relevant national and international standards for the full listing and explanation of the bi- nary and decimal byte size prefixes. OPTIONS Option Summary Here is a summary of all the options, grouped by type. Explanations are in the following sections. Overall Options -c -S -E -o file -dumpbase dumpbase -dumpbase-ext auxdropsuf -dumpdir dumppfx -x language -v -### --help[=class[,...]] --tar- get-help --version -pass-exit-codes -pipe -wrapper @file -ffile-prefix-map=old=new -fcanon-prefix-map -fplugin=file -fplu- gin-arg-name=arg -fdump-ada-spec[-slim] -fada-spec-parent=unit -fdump-go-spec=file --assemble --compile --dumpbase dumpbase --dump- base-ext auxdropsuf --dumpdir dumppfx --language=language --out- put=file --pass-exit-codes --pipe --preprocess --verbose C Language Options -ansi -std=standard -aux-info filename -fno-asm -fno-builtin -fno-builtin-function -fcond-mismatch -ffreestanding -fgimple -fgnu-tm -fgnu89-inline -fhosted -flax-vector-conversions -fms-ex- tensions -fpermitted-flt-eval-methods=standard -fplan9-extensions -fsigned-bitfields -funsigned-bitfields -fsigned-char -funsigned-char -fstrict-flex-arrays[=n] -fsso-struct=endianness --ansi C++ Language Options --compile-std-module -fabi-compat-version=n -fabi-version=n -fno-ac- cess-control -faligned-new=[n] -fno-assume-sane-operators-new-delete -fchar8_t -fcheck-new -fconcepts -fconcepts-diagnostics-depth=n -fconstexpr-depth=n -fconstexpr-cache-depth=n -fconstexpr-loop-limit=n -fconstexpr-ops-limit=n -fcontracts -fcontract-evaluation-semantic=[ig- nore|observe|enforce|quick_enforce] -fcontracts-conservative-ipa -fcontract-checks-outlined -fcontract-disable-optimized-checks -fcon- tracts-client-check=[none|pre|all] -fcontracts-defini- tion-check=[on|off] -fcoroutines -fdiagnostics-all-candidates -fno-elide-constructors -fno-enforce-eh-specs -fext-numeric-literals -fno-gnu-keywords -fno-immediate-escalation -fno-implement-inlines -fimplicit-constexpr -fno-implicit-inline-templates -fno-implicit-tem- plates -fmodule-header[=kind] -fmodule-implicit-inline -fno-module-lazy -fmodule-mapper=specification -fmodule-only -fmodules -fms-extensions -fnew-inheriting-ctors -fnew-ttp-matching -fno-nonansi-builtins -fnothrow-opt -fno-operator-names -fno-optional-diags -fno-pretty-tem- plates -frange-for-ext-temps -freflection -fno-rtti -fsized-deallo- cation -fstrict-enums -fstrong-eval-order[=kind] -ftemplate-back- trace-limit=n -ftemplate-depth=n -fno-threadsafe-statics -fuse-cxa-atexit -fno-use-cxa-get-exception-ptr -fno-weak -nostdinc++ -fvisibility-inlines-hidden -fvisibility-ms-compat -flang-info-in- clude-translate[=header] -flang-info-include-translate-not -flang-info-module-cmi[=module] -stdlib=libstdc++,libc++ -Wabbrevi- ated-auto-in-template-arg -Wabi-tag -Waligned-new[=kind] -Wcatch-value -Wcatch-value=n -Wno-class-conversion -Wclass-memaccess -Wcomma-sub- script -Wconditionally-supported -Wno-conversion-null -Wc- tad-maybe-unsupported -Wctor-dtor-privacy -Wdangling-reference -Wno-defaulted-function-deleted -Wno-delete-incomplete -Wdelete-non-virtual-dtor -Wno-deprecated-array-compare -Wdepre- cated-copy -Wdeprecated-copy-dtor -Wno-deprecated-enum-enum-conversion -Wno-deprecated-enum-float-conversion -Wno-deprecated-literal-operator -Wdeprecated-variadic-comma-omission -Weffc++ -Wno-elabo- rated-enum-base -Wno-exceptions -Wno-expose-global-module-tu-local -Wno-external-tu-local -Wextra-semi -Wno-global-module -Wno-inacces- sible-base -Wno-inherited-variadic-ctor -Wno-init-list-lifetime -Win- valid-constexpr -Winvalid-imported-macros -Wno-invalid-offsetof -Wno-literal-suffix -Wmismatched-new-delete -Wmismatched-tags -Wmulti- ple-inheritance -Wnamespaces -Wnarrowing -Wnoexcept -Wnoexcept-type -Wnon-virtual-dtor -Wpessimizing-move -Wno-placement-new -Wplace- ment-new=n -Wrange-loop-construct -Wredundant-move -Wredundant-tags -Wreorder -Wregister -Wno-sfinae-incomplete -Wstrict-null-sentinel -Wno-subobject-linkage -Wtemplates -Wno-non-c-typedef-for-linkage -Wno-non-template-friend -Wold-style-cast -Woverloaded-virtual -Wno-pmf-conversions -Wself-move -Wsign-promo -Wsized-deallocation -Wsuggest-final-methods -Wsuggest-final-types -Wsuggest-override -Wno-template-body -Wno-template-id-cdtor -Wtemplate-names-tu-local -Wno-terminate -Wno-vexing-parse -Wvirtual-inheritance -Wno-vir- tual-move-assign -Wvolatile Objective-C and Objective-C++ Language Options -fconstant-string-class=class-name -fgnu-runtime -fnext-runtime -fno-nil-receivers -fobjc-abi-version=n -fobjc-call-cxx-cdtors -fobjc-direct-dispatch -fobjc-exceptions -fobjc-gc -fobjc-nilcheck -fobjc-std=objc1 -fno-local-ivars -fivar-visibility=[public|pro- tected|private|package] -freplace-objc-classes -fzero-link -gen-decls -Wassign-intercept -Wno-property-assign-default -Wno-protocol -Wobjc-root-class -Wselector -Wstrict-selector-match -Wundeclared-se- lector OpenMP and OpenACC Options -foffload=arg -foffload-options=arg -fopenacc -fopenacc-dim=geom -fopenmp -fopenmp-simd -fopenmp-target-simd-clone[=device-type] Diagnostic Message Formatting Options -fmessage-length=n -fdiagnostics-plain-output -fdiagnostics-show-loca- tion=[once|every-line] -fdiagnostics-color=[auto|never|always] -fdiag- nostics-urls=[auto|never|always] -fdiagnostics-for- mat=[text|sarif-stderr|sarif-file] -fdiagnostics-add-output=DIAGNOS- TICS-OUTPUT-SPEC -fdiagnostics-set-output=DIAGNOSTICS-OUTPUT-SPEC -fno-diagnostics-json-formatting -fno-diagnostics-show-option -fno-di- agnostics-show-caret -fno-diagnostics-show-event-links -fno-diagnos- tics-show-labels -fno-diagnostics-show-line-numbers -fno-diagnos- tics-show-cwe -fno-diagnostics-show-rules -fno-diagnostics-show-high- light-colors -fno-diagnostics-show-nesting -fno-diagnostics-show-nest- ing-locations -fdiagnostics-show-nesting-levels -fdiagnostics-mini- mum-margin-width=width -fdiagnostics-parseable-fixits -fdiagnos- tics-generate-patch -fdiagnostics-show-template-tree -fno-elide-type -fdiagnostics-path-format=[none|separate-events|inline-events] -fdiag- nostics-show-path-depths -fno-show-column -fdiagnostics-col- umn-unit=[display|byte] -fdiagnostics-column-origin=origin -fdiagnos- tics-escape-format=[unicode|bytes] -fdiagnos- tics-text-art-charset=[none|ascii|unicode|emoji] -fdiagnos- tics-show-context[=depth] Warning Options -fsyntax-only -fmax-errors=n -Wpedantic -pedantic-errors -fpermis- sive -w -Wextra -Wall -Wabi=n -Waddress -Wno-address-of-packed-mem- ber -Waggregate-return -Walloc-size -Wal- loc-size-larger-than=byte-size -Walloc-zero -Walloca -Wal- loca-larger-than=byte-size -Wauto-profile -Wno-aggressive-loop-opti- mizations -Warith-conversion -Warray-bounds -Warray-bounds=n -War- ray-compare -Warray-parameter -Warray-parameter=n -Wno-attributes -Wattribute-alias=n -Wno-attribute-alias -Wno-attribute-warning -Wbidi-chars=[none|unpaired|any|ucn] -Wbool-compare -Wbool-operation -Wno-builtin-declaration-mismatch -Wno-builtin-macro-redefined -Wc90-c99-compat -Wc99-c11-compat -Wc11-c23-compat -Wc23-c2y-compat -Wc++-compat -Wc++11-compat -Wc++14-compat -Wc++17-compat -Wc++20-compat -Wc++26-compat -Wno-c++11-extensions -Wno-c++14-exten- sions -Wno-c++17-extensions -Wno-c++20-extensions -Wno-c++23-exten- sions -Wcalloc-transposed-args -Wcannot-profile -Wcast-align -Wcast-align=strict -Wcast-function-type -Wcast-qual -Wchar-sub- scripts -Wclobbered -Wcomment -Wcompare-distinct-pointer-types -Wno-complain-wrong-lang -Wconstant-logical-operand -Wconversion -Wno-coverage-mismatch -Wno-cpp -Wdangling-else -Wdangling-pointer -Wdangling-pointer=n -Wdate-time -Wno-deprecated -Wno-deprecated-dec- larations -Wno-designated-init -Wno-deprecated-openmp -Wdisabled-opti- mization -Wno-discarded-array-qualifiers -Wno-discarded-qualifiers -Wno-div-by-zero -Wdouble-promotion -Wduplicated-branches -Wdupli- cated-cond -Wempty-body -Wno-endif-labels -Wenum-compare -Wenum-con- version -Wenum-int-mismatch -Werror -Werror=* -Wexpansion-to-defined -Wfatal-errors -Wflex-array-member-not-at-end -Wfloat-conversion -Wfloat-equal -Wformat -Wformat=2 -Wno-format-contains-nul -Wno-for- mat-diag -Wno-format-extra-args -Wformat-nonliteral -Wformat-over- flow=n -Wformat-security -Wformat-signedness -Wformat-truncation=n -Wformat-y2k -Wframe-address -Wframe-larger-than=byte-size -Wno-free-nonheap-object -Wheader-guard -Wno-if-not-aligned -Wno-ig- nored-attributes -Wignored-qualifiers -Wno-incompatible-pointer-types -Whardened -Wimplicit -Wimplicit-fallthrough -Wimplicit-fallthrough=n -Wno-implicit-function-declaration -Wno-implicit-int -Winfinite-recur- sion -Winit-self -Winline -Wno-int-conversion -Wint-in-bool-context -Wno-int-to-pointer-cast -Wno-invalid-memory-model -Winvalid-pch -Winvalid-utf8 -Wno-unicode -Wjump-misses-init -Wkeyword-macro -Wlarger-than=byte-size -Wleading-whitespace=kind -Wlogical-not-paren- theses -Wlogical-op -Wlong-long -Wno-lto-type-mismatch -Wmain -Wmaybe-uninitialized -Wmemset-elt-size -Wmemset-transposed-args -Wmisleading-indentation -Wmissing-attributes -Wmissing-braces -Wmissing-field-initializers -Wmissing-format-attribute -Wmissing-in- clude-dirs -Wmissing-noreturn -Wmusttail-local-addr -Wmaybe-must- tail-local-addr -Wno-missing-profile -Wno-multichar -Wmultistate- ment-macros -Wnonnull -Wnonnull-compare -Wnormal- ized=[none|id|nfc|nfkc] -Wnull-dereference -Wno-odr -Wopenacc-paral- lelism -Wopenmp -Wopenmp-simd -Wno-overflow -Woverlength-strings -Wno-override-init-side-effects -Wpacked -Wno-packed-bitfield-compat -Wpacked-not-aligned -Wpadded -Wparentheses -Wno-pedantic-ms-format -Wpointer-arith -Wno-pointer-compare -Wno-pointer-to-int-cast -Wno-pragmas -Wno-pragma-once-outside-header -Wno-prio-ctor-dtor -Wno-psabi -Wredundant-decls -Wrestrict -Wno-return-local-addr -Wre- turn-type -Wno-scalar-storage-order -Wsequence-point -Wshadow -Wshadow=global -Wshadow=local -Wshadow=compatible-local -Wno-shadow-ivar -Wno-shift-count-negative -Wno-shift-count-overflow -Wshift-negative-value -Wno-shift-overflow -Wshift-overflow=n -Wsign-compare -Wsign-conversion -Wno-sizeof-array-argument -Wsizeof-array-div -Wsizeof-pointer-div -Wsizeof-pointer-memaccess -Wstack-protector -Wstack-usage=byte-size -Wstrict-aliasing -Wstrict-aliasing=n -Wstring-compare -Wno-stringop-overflow -Wno-stringop-overread -Wno-stringop-truncation -Wstrict-flex-arrays -Wsuggest-attribute=attribute-name -Wswitch -Wno-switch-bool -Wswitch-default -Wswitch-enum -Wno-switch-outside-range -Wno-switch-unreachable -Wsync-nand -Wsystem-headers -Wtautologi- cal-compare -Wtrailing-whitespace -Wtrailing-whitespace=kind -Wtram- polines -Wtrigraphs -Wtrivial-auto-var-init -Wno-tsan -Wtype-limits -Wundef -Wuninitialized -Wunknown-pragmas -Wunsuffixed-float-constants -Wunterminated-string-initialization -Wunused -Wunused-but-set-parame- ter -Wunused-but-set-parameter=n -Wunused-but-set-variable -Wunused-but-set-variable=n -Wunused-const-variable -Wunused-const-variable=n -Wunused-function -Wunused-label -Wunused-local-typedefs -Wunused-macros -Wunused-parameter -Wno-un- used-result -Wunused-value -Wunused-variable -Wuse-after-free -Wuse-after-free=n -Wuseless-cast -Wno-varargs -Wvariadic-macros -Wvector-operation-performance -Wvla -Wvla-larger-than=byte-size -Wno-vla-larger-than -Wvolatile-register-var -Wwrite-strings -Wno-xor-used-as-pow -Wzero-as-null-pointer-constant -Wzero-length-bounds -Wzero-init-padding-bits=value --all-warnings --extra-warnings --no-warnings --pedantic --pedantic-errors Static Analyzer Options -fanalyzer -fanalyzer-assume-nothrow -fanalyzer-call-summaries -fana- lyzer-checker=name -fno-analyzer-feasibility -fana- lyzer-show-events-in-system-headers -fno-analyzer-state-merge -fno-ana- lyzer-state-purge -fno-analyzer-suppress-followups -fanalyzer-transi- tivity -fno-analyzer-undo-inlining -fanalyzer-verbose-edges -fana- lyzer-verbose-state-changes -fanalyzer-verbosity=level -fdump-analyzer -fdump-analyzer-callgraph -fdump-analyzer-exploded-graph -fdump-ana- lyzer-exploded-nodes -fdump-analyzer-exploded-nodes-2 -fdump-ana- lyzer-exploded-nodes-3 -fdump-analyzer-exploded-paths -fdump-ana- lyzer-feasibility -fdump-analyzer-infinite-loop -fdump-analyzer-json -fdump-analyzer-state-purge -fdump-analyzer-stderr -fdump-analyzer-su- pergraph -fdump-analyzer-untracked -Wno-analyzer-double-fclose -Wno-an- alyzer-double-free -Wno-analyzer-exposure-through-output-file -Wno-ana- lyzer-exposure-through-uninit-copy -Wno-analyzer-fd-access-mode-mis- match -Wno-analyzer-fd-double-close -Wno-analyzer-fd-leak -Wno-ana- lyzer-fd-phase-mismatch -Wno-analyzer-fd-type-mismatch -Wno-ana- lyzer-fd-use-after-close -Wno-analyzer-fd-use-without-check -Wno-ana- lyzer-file-leak -Wno-analyzer-free-of-non-heap -Wno-analyzer-impre- cise-fp-arithmetic -Wno-analyzer-infinite-loop -Wno-analyzer-infi- nite-recursion -Wno-analyzer-jump-through-null -Wno-analyzer-mal- loc-leak -Wno-analyzer-mismatching-deallocation -Wno-ana- lyzer-mkostemp-redundant-flags -Wno-analyzer-mktemp-missing-placeholder -Wno-analyzer-mktemp-of-string-literal -Wno-analyzer-null-argument -Wno-analyzer-null-dereference -Wno-analyzer-out-of-bounds -Wno-ana- lyzer-overlapping-buffers -Wno-analyzer-possible-null-argument -Wno-an- alyzer-possible-null-dereference -Wno-analyzer-putenv-of-auto-var -Wno-analyzer-shift-count-negative -Wno-analyzer-shift-count-overflow -Wno-analyzer-stale-setjmp-buffer -Wno-analyzer-tainted-allocation-size -Wno-analyzer-tainted-assertion -Wno-analyzer-tainted-array-index -Wno-analyzer-tainted-divisor -Wno-analyzer-tainted-offset -Wno-ana- lyzer-tainted-size -Wno-analyzer-throw-of-unexpected-type -Wana- lyzer-symbol-too-complex -Wanalyzer-too-complex -Wno-analyzer-unde- fined-behavior-ptrdiff -Wno-analyzer-undefined-behavior-strtok -Wno-an- alyzer-unsafe-call-within-signal-handler -Wno-analyzer-use-after-free -Wno-analyzer-use-of-pointer-in-stale-stack-frame -Wno-ana- lyzer-use-of-uninitialized-value -Wno-analyzer-va-arg-type-mismatch -Wno-analyzer-va-list-exhausted -Wno-analyzer-va-list-leak -Wno-ana- lyzer-va-list-use-after-va-end -Wno-analyzer-write-to-const -Wno-ana- lyzer-write-to-string-literal C and Objective-C-only Warning Options -Wbad-function-cast -Wdeprecated-non-prototype -Wfree-labels -Wmiss- ing-declarations -Wmissing-parameter-name -Wmissing-parameter-type -Wdeclaration-missing-parameter-type -Wmissing-prototypes -Wmiss- ing-variable-declarations -Wmultiple-parameter-fwd-decl-lists -Wnested-externs -Wold-style-declaration -Wold-style-definition -Wstrict-prototypes -Wtraditional -Wtraditional-conversion -Wdeclara- tion-after-statement -Wpointer-sign Debugging Options -g -glevel -gdwarf -gdwarf-version -gbtf -gctf -gctflevel -gno-prune-btf -ggdb -gno-record-gcc-switches -gstrict-dwarf -gas-loc-support -gas-locview-support -gcodeview -gcolumn-info -gdwarf32 -gdwarf64 -gno-statement-frontiers -gno-variable-loca- tion-views -gvariable-location-views=incompat5 -ginternal-reset-loca- tion-views -ginline-points -gvms -gz[=type] -gsplit-dwarf -gde- scribe-dies -fdebug-prefix-map=old=new -fdebug-types-section -fno-eliminate-unused-debug-types -femit-struct-debug-baseonly -femit-struct-debug-reduced -femit-struct-debug-detailed[=spec-list] -fno-eliminate-unused-debug-symbols -femit-class-debug-always -fno-merge-debug-strings -fno-dwarf2-cfi-asm -fvar-tracking -fvar-tracking-assignments -fvar-tracking-uninit --debug Optimization Options -faggressive-loop-optimizations -falign-functions[=n[:m:[n2[:m2]]]] -falign-jumps[=n[:m:[n2[:m2]]]] -falign-labels[=n[:m:[n2[:m2]]]] -falign-loops[=n[:m:[n2[:m2]]]] -fmin-function-alignment=[n] -fno-allo- cation-dce -fallow-store-data-races -fassociative-math -fauto-profile -fauto-profile[=path] -fauto-profile-inlining -fauto-inc-dec -fbranch-probabilities -fcaller-saves -fcombine-stack-adjustments -fconserve-stack -ffold-mem-offsets -fcompare-elim -fcprop-registers -fcrossjumping -fcse-follow-jumps -fcse-skip-blocks -fcx-for- tran-rules -fcx-limited-range -fcx-method -fdata-sections -fdce -fde- layed-branch -fdelete-null-pointer-checks -fdep-fusion -fdevirtualize -fdevirtualize-speculatively -fdevirtualize-at-ltrans -fdse -fearly-inlining -fexcess-precision=style -fexpensive-optimizations -fext-dce -ffast-math -ffat-lto-objects -ffinite-loops -ffi- nite-math-only -ffloat-store -fforward-propagate -ffp-contract=style -ffp-int-builtin-inexact -ffunction-sections -ffuse-ops-with-volatile-access -fgcse -fgcse-after-reload -fgcse-las -fgcse-lm -fgraphite-identity -fgcse-sm -fhoist-adjacent-loads -fif-conversion -fif-conversion2 -findirect-inlining -finline-atomics -finline-functions -finline-functions-called-once -finline-limit=n -finline-small-functions -finline-stringops[=fn] -fipa-modref -fipa-cp -fipa-cp-clone -fipa-bit-cp -fipa-vrp -fipa-pta -fipa-profile -fipa-pure-const -fipa-reference -fipa-reference-addressable -fipa-reorder-for-locality -fipa-sra -fipa-stack-alignment -fipa-icf -fipa-icf-functions -fipa-icf-variables -fira-algorithm=algorithm -flate-combine-instructions -flifetime-dse -flive-patching=level -fira-region=region -fira-hoist-pressure -fira-loop-pressure -fno-ira-share-save-slots -fno-ira-share-spill-slots -fisolate-erro- neous-paths-dereference -fisolate-erroneous-paths-attribute -fivopts -fkeep-inline-functions -fkeep-static-functions -fkeep-static-consts -flimit-function-alignment -flive-range-shrinkage -floop-block -floop-interchange -floop-strip-mine -floop-unroll-and-jam -floop-nest-optimize -floop-parallelize-all -flra-remat -flto -flto-compression-level=n -flto-toplevel-asm-heuristics -flto-parti- tion=alg -flto-incremental=path -flto-incremental-cache-size=n -fmal- loc-dce -fmerge-all-constants -fmerge-constants -fmodulo-sched -fmodulo-sched-allow-regmoves -fmove-loop-invariants -fmove-loop-stores -fno-branch-count-reg -fno-defer-pop -fno-func- tion-cse -fno-guess-branch-probability -fno-inline -fno-math-errno -fno-peephole -fno-peephole2 -fno-printf-return-value -fno-sched-in- terblock -fno-sched-spec -fno-signed-zeros -fno-toplevel-reorder -fno-trapping-math -fno-zero-initialized-in-bss -fomit-frame-pointer -foptimize-crc -foptimize-sibling-calls -fpartial-inlining -fpeel-loops -fpredictive-commoning -fprefetch-loop-arrays -fpro- file-correction -fprofile-use -fprofile-use=path -fprofile-par- tial-training -fprofile-values -fprofile-reorder-functions -frecipro- cal-math -free -frename-registers -freorder-blocks -fre- order-blocks-algorithm=algorithm -freorder-blocks-and-partition -fre- order-functions -frerun-cse-after-loop -freschedule-modulo-sched- uled-loops -frounding-math -fsave-optimization-record -fsched2-use-su- perblocks -fsched-pressure -fsched-spec-load -fsched-spec-load-dan- gerous -fsched-stalled-insns-dep[=n] -fsched-stalled-insns[=n] -fsched-group-heuristic -fsched-critical-path-heuristic -fsched-spec-insn-heuristic -fsched-rank-heuristic -fsched-last-insn-heuristic -fsched-dep-count-heuristic -fschedule-fu- sion -fschedule-insns -fschedule-insns2 -fsection-anchors -fselec- tive-scheduling -fselective-scheduling2 -fsel-sched-pipelining -fsel-sched-pipelining-outer-loops -fsemantic-interposition -fshrink-wrap -fshrink-wrap-separate -fsignaling-nans -fsingle-preci- sion-constant -fsplit-ivs-in-unroller -fsplit-loops -fspecula- tively-call-stored-functions -fsplit-paths -fsplit-wide-types -fs- plit-wide-types-early -fssa-backprop -fssa-phiopt -fstdarg-opt -fs- tore-merging -fstrict-aliasing -fipa-strict-aliasing -fthread-jumps -ftracer -ftree-bit-ccp -ftree-builtin-call-dce -ftree-ccp -ftree-ch -ftree-coalesce-vars -ftree-copy-prop -ftree-cselim -ftree-dce -ftree-dominator-opts -ftree-dse -ftree-forwprop -ftree-fre -fcode-hoisting -ftree-loop-if-convert -ftree-loop-im -ftree-phiprop -ftree-loop-distribution -ftree-loop-distribute-patterns -ftree-loop-ivcanon -ftree-loop-linear -ftree-loop-optimize -ftree-loop-vectorize -ftree-parallelize-loops[=n] -ftree-pre -ftree-partial-pre -ftree-pta -ftree-reassoc -ftree-scev-cprop -ftree-sink -ftree-slsr -ftree-sra -ftree-switch-conversion -ftree-tail-merge -ftree-ter -ftree-vectorize -ftree-vrp -ftriv- ial-auto-var-init -funconstrained-commons -funit-at-a-time -fun- roll-all-loops -funroll-loops -funsafe-math-optimizations -funswitch-loops -fipa-ra -fvariable-expansion-in-unroller -fvect-cost-model -fvpt -fweb -fwhole-program -fwpa -fuse-linker-plugin -fzero-call-used-regs -O -O0 -O1 -O2 -O3 -Os -Ofast -Og -Oz --optimize Program Instrumentation Options -p -pg -fprofile-arcs -coverage -ftest-coverage -fcondition-cover- age -fpath-coverage -fprofile -fprofile-abs-path -fprofile-dir=path -fprofile-generate -fprofile-generate=path -fprofile-info-section -fprofile-info-section=name -fprofile-note=path -fprofile-pre- fix-path=path -fprofile-update=method -fprofile-filter-files=regex -fprofile-exclude-files=regex -fprofile-reproducible=[multi- threaded|parallel-runs|serial] -fsanitize=style -fsanitize-recover -fsanitize-recover=style -fsanitize-trap -fsanitize-trap=style -fasan-shadow-offset=number -fsanitize-sections=s1,s2,... -fsani- tize-undefined-trap-on-error -fcf-protection -fcf-protec- tion=[full|branch|return|none|check] -fharden-compares -fharden-condi- tional-branches -fhardened -fharden-control-flow-redundancy -fhard- cfr-skip-leaf -fhardcfr-check-exceptions -fhardcfr-check-return- ing-calls -fhardcfr-check-noreturn-calls=[al- ways|no-xthrow|nothrow|never] -fstack-protector -fstack-protector-all -fstack-protector-strong -fstack-protector-explicit -fstack-check -fs- tack-limit-register=reg -fstack-limit-symbol=sym -fno-stack-limit -fsplit-stack -fstrub=disable -fstrub=strict -fstrub=relaxed -fstrub=all -fstrub=at-calls -fstrub=internal -fvtable-ver- ify=[std|preinit|none] -fvtv-counts -fvtv-debug -finstrument-functions -finstrument-functions-once -finstrument-functions-exclude-func- tion-list=sym,sym,... -finstrument-functions-ex- clude-file-list=file,file,... -fprofile-prefix-map=old=new -fpatch- able-function-entry=N[,M] --coverage --profile Preprocessor Options -C -CC -Dmacro[=defn] -dD -dI -dM -dN -dU -fdebug-cpp -fdirec- tives-only -fdollars-in-identifiers -fexec-charset=charset -fex- tended-identifiers -finput-charset=charset -fmacro-prefix-map=old=new -fmax-include-depth=depth -fno-canonical-system-headers -fpch-deps -fpch-preprocess -fpreprocessed -ftabstop=width -ftrack-macro-expan- sion -fwide-exec-charset=charset -fworking-directory -H -imacros file -include file -M -MD -MF -MG -MM -MMD -MP -MQ -MT -Mno-modules -no-integrated-cpp -P -pthread -remap -traditional -traditional-cpp -trigraphs -Umacro -undef -Wp,option -Xpreprocessor option --comments --comments-in-macros --define-macro=macro[=defn] --dependencies --dump=letters --imacros=file --include=file --no-integrated-cpp --no-line-commands --print-missing-file-dependencies --traditional --traditional-cpp --trigraphs --trace-includes --undefine-macro=macro --user-dependencies --write-dependencies --write-user-dependencies Assembler Options -Wa,option -Xassembler option --for-assembler=option Linker Options object-file-name -flink-libatomic -fuse-ld=linker -llibrary -nos- tartfiles -nodefaultlibs -nolibc -nostdlib -nostdlib++ -e entry -pie -pthread -r -rdynamic -s -static -static-pie -static-libgcc -static-libstdc++ -static-libasan -static-libhwasan -static-liblsan -static-libtsan -static-libubsan -shared -shared-libgcc -symbolic -T script -Wl,option -Xlinker option -u symbol -Tbss=addr -Tdata=addr -Ttext=addr -N -n -t -Z -z keyword --entry=entry --for-linker=op- tion --force-link=symbol --no-standard-library --pie --static --sta- tic-pie --symbolic Directory Options -Bprefix -Idir -I- -idirafter dir -imacros file -imultilib dir -imultiarch dir -iplugindir=dir -iprefix file -iquote dir -isysroot dir -isystem dir -iwithprefix dir -iwithprefixbefore dir -Ldir -no-canonical-prefixes --no-sysroot-suffix -nostdinc -nostdinc++ --embed-dir=dir --embed-directory=dir --include-barrier --include-di- rectory=dir --include-directory-after=dir --include-prefix=prefix --include-with-prefix=prefix --include-with-prefix-after=prefix --in- clude-with-prefix-before=prefix --no-canonical-prefixes --no-stan- dard-includes --prefix=prefix --sysroot=dir Code Generation Options -fcall-saved-reg -fcall-used-reg -ffixed-reg -fexceptions -fnon-call-exceptions -fdelete-dead-exceptions -funwind-tables -fa- synchronous-unwind-tables -fno-gnu-unique -finhibit-size-directive -fcommon -fno-ident -fpcc-struct-return -fpic -fPIC -fpie -fPIE -fno-plt -fno-jump-tables -fno-bit-tests -frecord-gcc-switches -freg-struct-return -fshort-enums -fshort-wchar -fverbose-asm -fpack-struct[=n] -fleading-underscore -ftls-model=model -fs- tack-reuse=reuse_level -ftrampolines -ftrampoline-impl=[stack|heap] -ftrapv -fwrapv -fwrapv-pointer -fvisibility=[default|internal|hid- den|protected] -fstrict-volatile-bitfields -fsync-libcalls -fzero-init-padding-bits=value -Qy -Qn Developer Options -dletters -dumpspecs -dumpmachine -dumpversion -dumpfullversion -fcallgraph-info[=su,da] -fchecking -fchecking=n -fdbg-cnt-list -fdbg-cnt=counter-value-list -fdisable-ipa-pass_name -fdis- able-rtl-pass_name -fdisable-rtl-pass-name=range-list -fdis- able-tree-pass_name -fdisable-tree-pass-name=range-list -fdump-debug -fdump-earlydebug -fdump-noaddr -fdump-unnumbered -fdump-unnum- bered-links -fdump-final-insns[=file] -fdump-internal-locations -fdump-ipa-all -fdump-ipa-cgraph -fdump-ipa-inline -fdump-lang-all -fdump-lang-switch -fdump-lang-switch-options -fdump-lang-switch-op- tions=filename -fdump-passes -fdump-rtl-pass -fdump-rtl-pass=filename -fdump-statistics -fdump-tree-all -fdump-tree-switch -fdump-tree-switch-options -fdump-tree-switch-options=filename -fcom- pare-debug[=opts] -fcompare-debug-second -fenable-kind-pass -fen- able-kind-pass=range-list -fira-verbose=n -flto-report -flto-re- port-wpa -fmem-report-wpa -fmem-report -fpre-ipa-mem-report -fpost-ipa-mem-report -fopt-info -fopt-info-options[=file] -fmulti- flags -fprofile-report -frandom-seed=string -fsched-verbose=n -fsel-sched-verbose -fsel-sched-dump-cfg -fsel-sched-pipelining-ver- bose -fstats -fstack-usage -ftime-report -ftime-report-details -fvar-tracking-assignments-toggle -gtoggle -print-autofdo-gcov-version -print-file-name=library -print-libgcc-file-name -print-multi-direc- tory -print-multi-lib -print-multi-os-directory -print-multiarch -print-prog-name=program -print-search-dirs -Q -print-sysroot -print-sysroot-headers-suffix -save-temps -save-temps=cwd -save-temps=obj -specs=file -time[=file] --dump=letters --print-aut- ofdo-gcov-version --print-file-name=library --print-libgcc-file-file-name --print-multi-directory --print-multi-lib --print-multi-os-directory --print-multiarch --print-prog-name=program --print-search-dirs --print-sysroot --print-sysroot-headers-suffix --save-temps --specs=file --param name=value Target-Specific Options AArch64 Options (AArch64 Options) -mabi=name -mbig-endian -mlit- tle-endian -menable-sysreg-checking -mgeneral-regs-only -mcmodel=tiny -mcmodel=small -mcmodel=large -mstrict-align -momit-leaf-frame-pointer -mtls-dialect=desc -mtls-dialect=traditional -mtls-size=size -mtp=name -mfix-cortex-a53-835769 -mfix-cor- tex-a53-843419 -mlow-precision-recip-sqrt -mlow-precision-sqrt -mlow-precision-div -mmax-vectorization -mautovec-preference=name -mpc-relative-literal-loads -msign-return-address=scope -mbranch-pro- tection=features -mharden-sls=opts -march=name -mcpu=name -mtune=name -moverride=string -mstack-protector-guard=guard -mstack-protec- tor-guard-reg=sysreg -mstack-protector-guard-offset=offset -mtrack-speculation -moutline-atomics -mearly-ra -mearly-ldp-fusion -mlate-ldp-fusion -mnarrow-gp-writes -msve-vector-bits=bits Adapteva Epiphany Options (Adapteva Epiphany Options) -mhalf-reg-file -mprefer-short-insn-regs -mbranch-cost=num -mcmove -mnops=num -msoft-cmpsf -msplit-lohi -mpost-inc -mpost-modify -mstack-off- set=num -mround-nearest -mlong-calls -mshort-calls -msmall16 -mfp-mode=mode -mmay-round-for-trunc -mfp-iarith -mvect-double -max-vect-align=num -msplit-vecmove-early -m1reg-reg AMD GCN Options (AMD GCN Options) -march=gpu -mtune=gpu -mgang-pri- vate-size=bytes -msram-ecc=[on|off|any] -mxnack=[on|off|any] -Wope- nacc-dims ARC Options (ARC Options) -mbarrel-shifter -mjli-always -mcpu=cpu -mA6 -mARC600 -mA7 -mARC700 -mdpfp -mdpfp-compact -mdpfp-fast -mno-dpfp-lrsr -mea -mmul32x16 -mmul64 -matomic -mnorm -mspfp -mspfp-compact -mspfp-fast -msimd -msoft-float -mswap -mlock -mswape -mxy -misize -marclinux -marclinux_prof -mlong-calls -mmedium-calls -msdata -mirq-ctrl-saved -mrgf-banked-regs -mlpc-width=width -G num -mvolatile-cache -mtp-regno=regno -mbitops -mcmem -munaligned-access -mauto-modify-reg -mno-brcc -mcase-vec- tor-pcrel -mno-cond-exec -mearly-cbranchsi -mindexed-loads -mlra-priority-none -mlra-priority-compact -mlra-priority-noncompact -mmillicode -msize-level=level -mtune=cpu -mmultcost=num -mcode-den- sity-frame -mmpy-option=multo -mdiv-rem -mcode-density -mll64 -mfpu=fpu -mrf16 -mbranch-index ARM Options (ARM Options) -mapcs-frame -mapcs -mabi=name -mgen- eral-regs-only -mno-sched-prolog -mlittle-endian -mbig-endian -mbe8 -mbe32 -mfloat-abi=name -mfp16-format=name -mthumb-interwork -mcpu=name -march=name -mfpu=name -mtune=name -mstructure-size-boundary=n -mabort-on-noreturn -mlong-calls -msingle-pic-base -mpic-register=reg -mpic-data-is-text-relative -mnop-fun-dllimport -mpoke-function-name -mthumb -marm -mtpcs-frame -mtpcs-leaf-frame -mcaller-super-inter- working -mcallee-super-interworking -mtp=name -mtls-dialect=dialect -mword-relocations -mfix-cortex-m3-ldrd -mfix-cortex-a57-aes-1742098 -mfix-cortex-a72-aes-1655431 -munaligned-access -mslow-flash-data -masm-syntax-unified -mrestrict-it -mpure-code -mcmse -mfix-cmse-cve-2021-35465 -mstack-protector-guard=guard -mstack-protec- tor-guard-offset=offset -mfdpic -mbranch-protection=features -mvector- ize-with-neon-quad -mvectorize-with-neon-double AVR Options (AVR Options) -mmcu=mcu -mabsdata -maccumulate-args -masm-len-notes -mcvt -mbranch-cost=cost -mfuse-add=level -mfuse-move=level -mfuse-move2 -mcall-prologues -mgas-isr-prologues -mint8 -mflmap -mdouble=bits -mlong-double=bits -mno-call-main -mn_flash=size -mfract-convert-truncate -mno-interrupts -mmain-is-OS_task -mrelax -mpmem-wrap-around -mrmw -mstrict-X -mtiny-stack -mrodata-in-ram -msplit-bit-shift -msplit-ldst -mshort-calls -mskip-bug -muse-nonzero-bits -nodevicelib -nodevice- specs -Wasm-len-notes -Waddr-space-convert -Wmisspelled-isr Blackfin Options (Blackfin Options) -mcpu=cpu[-sirevision] -msim -momit-leaf-frame-pointer -mspecld-anomaly -mcsync-anomaly -mlow-64k -mstack-check-l1 -mid-shared-library -mleaf-id-shared-library -mshared-library-id=n -msep-data -mlong-calls -mfast-fp -minline-plt -mmulticore -mcorea -mcoreb -msdram -micplb C6X Options (C6X Options) -mbig-endian -mlittle-endian -march=cpu -msim -msdata=sdata-type -mdsbt -mlong-calls CRIS Options (CRIS Options) -mcpu=cpu -march=cpu -mtune=cpu -mmax-stackframe=n -metrax4 -metrax100 -mpdebug -mcc-init -mno-side-effects -mstack-align -mdata-align -mconst-align -m32-bit -m16-bit -m8-bit -mno-prologue-epilogue -mbest-lib-options -mover- ride-best-lib-options -mtrap-using-break8 -mtrap-unaligned-atomic -mu- naligned-atomic-may-use-library -sim -sim2 -mmul-bug-workaround C-SKY Options (C-SKY Options) -march=arch -mcpu=cpu -mbig-endian -mlittle-endian -mfpu=fpu -mdouble-float -mfdivdu -mfloat-abi=name -melrw -mistack -mmp -mcp -mcache -msecurity -mtrust -mdsp -medsp -mvdsp -mdiv -msmart -mhigh-registers -manchor -mpushpop -mmultiple-stld -mconstpool -mstack-size -mccrt -mbranch-cost=n -msched-prolog -msim Cygwin and MinGW Options (Cygwin and MinGW Options) -mconsole -mcrt- dll=library -mdll -mnop-fun-dllimport -mthreads -municode -mwin32 -mwindows -fno-set-stack-executable -fwritable-relocated-rdata -mpe-aligned-commons -muse-libstdc-wrappers Darwin Options (Darwin Options) -all_load -allowable_client -arch name -arch_errors_fatal -asm_macosx_version_min=version -bind_at_load -bundle -bundle_loader -client_name -compatibility_version -cur- rent_version -dead_strip -dependency-file -dylib_file -dylinker -dylinker_install_name -dynamic -dynamiclib -exported_symbols_list -fapple-kext -fconstant-cfstrings -ffix-and-continue -filelist -findirect-data -flat_namespace -force_cpusubtype_ALL -force_flat_namespace -framework name -gfull -gused -header- pad_max_install_names -iframework -image_base -init symbol-name -in- stall_name -keep_private_externs -matt-stubs -mconstant-cfstrings -mdynamic-no-pic -mfix-and-continue -mkernel -mmacosx-ver- sion-min=version -mone-byte-bool -msymbol-stubs -mtar- get-linker[=]version -nodefaultexport -nodefaultrpaths -pagezero_size -preload -read_only_relocs -sectalign -sectcreate -seg_addr_table -seg1addr -segaddr -segprot -segs_read_only_addr -segs_read_write_addr -sub_library -sub_umbrella -twolevel_namespace -twolevel_namespace_hints -umbrella -undefined -unexported_sym- bols_list -weak_framework name -weak_reference_mismatches -whatsloaded -whyload -F -ObjC -ObjC++ -Wnonportable-cfstrings DEC Alpha Options (DEC Alpha Options) -mno-fp-regs -msoft-float -mieee -mieee-with-inexact -mieee-conformant -mfp-trap-mode=mode -mfp-round- ing-mode=mode -mtrap-precision=mode -mbuild-constants -mcpu=cpu-type -mtune=cpu-type -mbwx -mmax -mfix -mcix -msafe-bwa -msafe-partial -mfloat-vax -mfloat-ieee -mexplicit-relocs -msmall-data -mlarge-data -msmall-text -mlarge-text -mmemory-latency=time -mtls-kernel -mtls-size=bitsize -mlong-double-128 -mlong-double-64 eBPF Options (eBPF Options) -mbig-endian -mlittle-endian -mframe-limit=bytes -mxbpf -mco-re -mjmpext -mjmp32 -malu32 -mv3-atomics -mbswap -msdiv -msmov -mcpu=version -masm=dialect -minline-memops-threshold=bytes -Wco-re FR30 Options (FR30 Options) -msmall-model -mno-lsim FRV Options (FRV Options) -mgpr-32 -mgpr-64 -mfpr-32 -mfpr-64 -mhard-float -msoft-float -malloc-cc -mfixed-cc -mdword -mdouble -mmedia -mmuladd -mfdpic -minline-plt -mgprel-ro -multilib-li- brary-pic -mlinked-fp -mlong-calls -malign-labels -mlibrary-pic -macc-4 -macc-8 -mpack -mno-eflags -mno-cond-move -mno-optimize-mem- bar -mno-scc -mno-cond-exec -mno-vliw-branch -mno-multi-cond-exec -mno-nested-cond-exec -mtomcat-stats -mTLS -mtls -mcpu=cpu FT32 Options (FT32 Options) -msim -mnodiv -mft32b -mcompress -mnopm GNU/Linux Options (GNU/Linux Options) -mglibc -muclibc -mmusl -mbionic -mandroid -tno-android-cc -tno-android-ld H8/300 Options (H8/300 Options) -mrelax -mh -ms -mn -msx -ms2600 -mquickcall -mslowbyte -mexr -mint32 -malign-300 HPPA Options (HPPA Options) -march=architecture-type -mno-atomic-lib- calls -mcaller-copies -mdisable-fpregs -mdisable-indexing -mordered -mfast-indirect-calls -mgas -mgnu-ld -mhp-ld -mfixed-range=regis- ter-range -mcoherent-ldcw -mlinker-opt -mlong-calls -mlong-load-store -mno-space-regs -msoft-float -mpa-risc-1-0 -mpa-risc-1-1 -mpa-risc-2-0 -mportable-runtime -mschedule=cpu-type -msoft-mult -msio -mwsio -munix=unix-std -nolibdld -static -threads IA-64 Options (IA-64 Options) -mbig-endian -mlittle-endian -mgnu-as -mgnu-ld -mno-pic -mvolatile-asm-stop -mregister-names -msdata -mconstant-gp -mauto-pic -minline-float-divide-min-latency -min- line-float-divide-max-throughput -mno-inline-float-divide -min- line-int-divide-min-latency -minline-int-divide-max-throughput -mno-in- line-int-divide -minline-sqrt-min-latency -minline-sqrt-max-throughput -mno-inline-sqrt -mdwarf2-asm -mearly-stop-bits -mfixed-range=regis- ter-range -mtls-size=tls-size -mtune=cpu-type -milp32 -mlp64 -msched-br-data-spec -msched-ar-data-spec -msched-control-spec -msched-br-in-data-spec -msched-ar-in-data-spec -msched-in-con- trol-spec -msched-spec-ldc -msched-spec-control-ldc -msched-stop-bits-after-every-cycle -msched-count-spec-in-criti- cal-path -msel-sched-dont-check-control-spec -msched-fp-mem-deps-zero-cost -msched-max-memory-insns-hard-limit -msched-max-memory-insns=max-insns LM32 Options (LM32 Options) -mbarrel-shift-enabled -mdivide-enabled -mmultiply-enabled -msign-extend-enabled -muser-enabled LoongArch Options (LoongArch Options) -march=arch-type -mtune=tune-type -mabi=base-abi-type -mfpu=fpu-type -msimd=simd-type -msoft-float -msingle-float -mdouble-float -mlsx -mlasx -mbranch-cost=n -maddr-reg-reg-cost=n -mcheck-zero-division -mbreak-code=code -mcond-move-int -mcond-move-float -memcpy -mstrict-align -G num -mmax-inline-memcpy-size=n -mexplicit-re- locs=style -mexplicit-relocs -mno-explicit-relocs -mdirect-extern-ac- cess -mcmodel=code-model -mrelax -mpass-mrelax-to-as -mrecip -mre- cip=opt -mfrecipe -mdiv32 -mlam-bh -mlamcas -mld-seq-sa -mscq -mtls-dialect=opt -mannotate-tablejump LynxOS Options (LynxOS Options) -mshared -mthreads -mlegacy-threads M32R/D Options (M32R/D Options) -m32r2 -m32rx -m32r -mdebug -ma- lign-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 M680x0 Options (M680x0 Options) -march=arch -mcpu=cpu -mtune=tune -m68000 -m68020 -m68020-40 -m68020-60 -m68030 -m68040 -m68060 -m68302 -m68332 -m68851 -mcpu32 -mfidoa -m5200 -m5206e -m528x -m5307 -m5407 -mcfv4e -mbitfield -mc68000 -mc68020 -mrtd -mdiv -mshort -mhard-float -m68881 -msoft-float -mpcrel -malign-int -mstrict-align -msep-data -mshared-library-id=n -mid-shared-library -mxgot -mxtls -mlong-jump-table-offsets MCore Options (MCore Options) -mhardlit -mdiv -mrelax-immediates -mwide-bitfields -m4byte-functions -mcallgraph-data -mslow-bytes -mno-lsim -mlittle-endian -mbig-endian -m210 -m340 -mstack-incre- ment MicroBlaze Options (MicroBlaze Options) -msoft-float -mhard-float -msmall-divides -mcpu=cpu -mmemcpy -mxl-soft-mul -mxl-soft-div -mxl-barrel-shift -mxl-pattern-compare -mxl-gp-opt -mxl-multiply-high -mxl-float-convert -mxl-float-sqrt -mbig-endian -mlittle-endian -mxl-reorder -mxl-mode-app-model -mxl-prefetch -mpic-data-is-text-relative MIPS Options (MIPS Options) -EL -EB -mel -meb -march=arch -mtune=arch -mips1 -mips2 -mips3 -mips4 -mips32 -mips32r2 -mips32r3 -mips32r5 -mips32r6 -mips64 -mips64r2 -mips64r3 -mips64r5 -mips64r6 -mips16 -mmips16e2 -mflip-mips16 -minter- link-compressed -minterlink-mips16 -mabi=abi -mabicalls -mshared -mplt -mxgot -mgp32 -mgp64 -mfp32 -mfpxx -mfp64 -mhard-float -msoft-float -mno-float -msingle-float -mdouble-float -modd-spreg -mabs=mode -mnan=encoding -mdsp -mdspr2 -mmcu -meva -mvirt -mxpa -mcrc -mginv -mmicromips -mmsa -mloongson-mmi -mloongson-ext -mloongson-ext2 -mfpu=fpu-type -msmartmips -mpaired-single -mdmx -mips3d -mmt -mllsc -mlong64 -mlong32 -msym32 -Gnum -mno-lo- cal-sdata -mno-extern-sdata -mno-gopt -membedded-data -muninit-const-in-rodata -mcode-readable=setting -mno-data-in-code -mcode-xonly -msplit-addresses -mexplicit-relocs -mexplicit-re- locs=release -mno-check-zero-division -mdivide-traps -mdivide-breaks -mno-load-store-pairs -mstrict-align -mno-unaligned-access -mmemcpy -mlong-calls -mmad -mimadd -mno-fused-madd -nocpp -mfix-24k -mfix-r4000 -mfix-r4400 -mfix-r5900 -mfix-r10000 -mfix-rm7000 -mfix-vr4120 -mfix-vr4130 -mfix-sb1 -mfix4300 -mr10k-cache-bar- rier=setting -mflush-func=func -mno-flush-func -mbranch-cost=num -mbranch-likely -mcompact-branches=policy -mno-fp-exceptions -mvr4130-align -msynci -mno-lxc1-sxc1 -mno-madd4 -mno-re- lax-pic-calls -mmcount-ra-address -mframe-header-opt MMIX Options (MMIX Options) -mlibfuncs -mepsilon -mabi=gnu -mabi=mmixware -mzero-extend -mknuthdiv -mtoplevel-symbols -melf -mbranch-predict -mbase-addresses -msingle-exit -mset-data-start=ad- dress -mset-program-start=address -mno-set-program-start MN10300 Options (MN10300 Options) -mmult-bug -mno-mult-bug -mam33 -mam33-2 -mam34 -mtune=cpu-type -mno-return-pointer-on-d0 -mno-crt0 -mrelax -mno-liw -mno-setlb Moxie Options (Moxie Options) -meb -mel -mmul.x -mno-crt0 MSP430 Options (MSP430 Options) -msim -masm-hex -mmcu=name -mlarge -msmall -mrelax -mwarn-mcu -mwarn-devices-csv -mcode-region=where -mdata-region=where -muse-lower-region-prefix -msilicon-er- rata=name[,name...] -msilicon-errata-warn=name[,name...] -mhw- mult=type -minrt -mtiny-printf -mmax-inline-shift=n NDS32 Options (NDS32 Options) -mbig-endian -mlittle-endian -EB -EL -mabi=name -mfloat-abi=name -mreduced-regs -mfull-regs -malways-align -malign-functions -mfp-as-gp -mcmov -mhw-abs -mext-perf -mext-perf2 -mext-string -mext-dsp -mext-fpu-fma -mext-fpu-sp -mext-fpu-dp -mv3push -m16-bit -mvh -misr-vector-size=num -misr-secure=num -mcache-block-size=num -march=arch -mcpu=cpu -mconfig-fpu=num -mcon- fig-mul=type -mconfig-register-ports=kind -mcmodel=code-model -mc- tor-dtor -mrelax -mrelax-hint -msched-prolog-epilog -mno-ret-in-naked-func -malways-save-lp -munaligned-access -min- line-asm-r15 Nvidia PTX Options (Nvidia PTX Options) -m64 -march=arch -misa=arch -march-map=arch -mptx=version -mmainkernel -moptimize -msoft-stack -msoft-stack-reserve-local=size -muniform-simt -mgomp OpenRISC Options (OpenRISC Options) -mboard=name -mhard-mul -mhard-div -msoft-mul -msoft-div -msoft-float -mhard-float -mdou- ble-float -munordered-float -mcmov -mror -mrori -msext -msfimm -mshftimm -mcmodel=code-model PDP-11 Options (PDP-11 Options) -mfpu -msoft-float -mac0 -m40 -m45 -m10 -mint32 -mint16 -msplit -munix-asm -mdec-asm -mgnu-asm -mlra Picolibc Options (Picolibc Options) --oslib=library --crt0=[none|mini- mal|hosted|semihost] --printf=[d|f|l|i|m] --scanf=[d|f|l|i|m] PowerPC Options See RS/6000 and PowerPC Options. PRU Options (PRU Options) -mmcu=mcu -minrt -mno-relax -mloop -mmul -mfillzero -mabi=variant RISC-V Options (RISC-V Options) -mbranch-cost=N-instruction -mabi=ABI-string -mfdiv -mdiv -mno-fence-tso -misa-spec=ISA-spec-string -march=[ISA|Profile|Profile_ISA|proces- sor-string] -mcpu=processor-string -mtune=processor-string -mpre- ferred-stack-boundary=num -msmall-data-limit=N-bytes -msave-restore -mno-shorten-memrefs -mstrict-align -mscalar-strict-align -mno-vec- tor-strict-align -mzilsd-word-align -mzilsd-strict-align -mcmodel=med- low -mcmodel=medany -mcmodel=large -mexplicit-relocs -mrelax -mriscv-attribute -malign-data=type -mbig-endian -mlittle-endian -mstack-protector-guard=guard -mstack-protector-guard-reg=reg -mstack-protector-guard-offset=offset -mcsr-check -momit-leaf-frame-pointer -mmovcc -mno-inline-atomics -mno-in- line-strlen -mno-inline-strcmp -mno-inline-strncmp -mstringop-strat- egy=strategy -mtls-dialect=desc -mtls-dialect=trad -mrvv-vec- tor-bits=value -mrvv-max-lmul=value -madjust-lmul-cost -mmax-vector- ization -mno-autovec-segment RL78 Options (RL78 Options) -msim -mallregs -mrelax -mes0 -mmul=none -mmul=g13 -mmul=g14 -mmul=rl78 -mcpu=g10 -mcpu=g13 -mcpu=g14 -mcpu=rl78 -mg10 -mg13 -mg14 -mrl78 -msave-mduc-in-interrupts RS/6000 and PowerPC Options (RS/6000 and PowerPC Options) -mcpu=cpu-type -mtune=cpu-type -mcmodel=code-model -mprofile-kernel -mpowerpc64 -maltivec -mpowerpc-gpopt -mpowerpc-gfxopt -mmfcrf -mpopcntb -mpopcntd -mfprnd -mcmpb -mhard-dfp -mfull-toc -mmini- mal-toc -mno-fp-in-toc -mno-sum-in-toc -maix64 -maix32 -m64 -m32 -mxl-compat -mpe -malign-power -malign-natural -msoft-float -mhard-float -mmultiple -mupdate -mavoid-indexed-addresses -mfused-madd -mbit-align -mbit-word -mstrict-align -mrelocatable -mrelocatable-lib -mlittle -mlittle-endian -mbig -mbig-endian -mdy- namic-no-pic -msingle-pic-base -mprioritize-restricted-insns=priority -msched-costly-dep=dependence_type -minsert-sched-nops=scheme -mcall-aixdesc -mcall-eabi -mcall-freebsd -mcall-linux -mcall-netbsd -mcall-openbsd -mcall-sysv -mcall-sysv-eabi -mcall-sysv-noeabi -mtraceback=traceback_type -maix-struct-return -msvr4-struct-return -mabi=abi-type -msecure-plt -mbss-plt -msplit-patch-nops -mregnames -mlongcall -mpltseq -mtls-markers -mblock-move-inline-limit=num -mblock-compare-inline-limit=num -mblock-compare-inline-loop-limit=num -mblock-ops-unaligned-vsx -mstring-compare-inline-limit=num -misel -mvsx -mvrsave -mmulhw -mdlmzb -mprototype -msim -mmvme -mads -myellowknife -memb -meabi -msdata -msdata=opt -mreadonly-in-sdata -mvxworks -G num -mrecip -mrecip=opt -mno-recip -mrecip-precision -mveclibabi=type -mfriz -mpointers-to-nested-functions -msave-toc-in- direct -mpower8-fusion -mcrypto -mhtm -mquad-memory -mquad-mem- ory-atomic -mcompat-align-parm -mfloat128 -mfloat128-hardware -mgnu-attribute -mstack-protector-guard=guard -mstack-protec- tor-guard-reg=reg -mstack-protector-guard-offset=offset -mprefixed -mpcrel -mmma -mrop-protect -mprivileged -mno-splat-word-constant -mno-splat-float-constant -mno-ieee128-constant -mno-warn-altivec-long RX Options (RX Options) -m64bit-doubles -m32bit-doubles -fpu -nofpu -mcpu=name -mbig-endian-data -mlittle-endian-data -msmall-data-limit=N -msim -mas100-syntax -mrelax -mmax-constant-size=N -mint-register=N -mpid -mno-allow-string-insns -mjsr -mno-warn-multiple-fast-inter- rupts -msave-acc-in-interrupts -mlra S/390 and zSeries Options (S/390 and zSeries Options) -mtune=cpu-type -march=cpu-type -mhard-float -msoft-float -mhard-dfp -mlong-double-64 -mlong-double-128 -mbackchain -mpacked-stack -msmall-exec -mmvcle -m64 -m31 -mdebug -mesa -mzarch -mhtm -mvx -mzvector -mtpf-trace -mtpf-trace-skip -mmain -mfused-madd -mno-fused-madd -mwarn-frame- size=framesize -mwarn-dynamicstack -mstack-size=stack-size -mno-stack-size -mstack-guard=stack-guard -mno-stack-guard -mstack-protector-guard=guard -mstack-protector-guard-record -mhot- patch=pre-halfwords,post-halfwords -mno-pic-data-is-text-relative -mindirect-branch=choice -mindirect-branch-jump=choice -mindi- rect-branch-call=choice -mfunction-return=choice -mfunction-re- turn-mem=choice -mfunction-return-reg=choice -mindirect-branch-table -mfentry -mrecord-mcount -mnop-mcount -mpreserve-args -mu- naliged-symbols SH Options (SH Options) -m1 -m2 -m2e -m2a -m2a-nofpu -m2a-single -m2a-single-only -m3 -m3e -m4 -m4-nofpu -m4-single -m4-single-only -m4-100 -m4-100-nofpu -m4-100-single -m4-100-single-only -m4-200 -m4-200-nofpu -m4-200-single -m4-200-single-only -m4-300 -m4-300-nofpu -m4-300-single -m4-300-single-only -m4-340 -m4-400 -m4-500 -m4a -m4al -m4a-nofpu -m4a-single -m4a-single-only -mb -ml -mdalign -mrelax -mbigtable -mbitops -mfmovd -mrenesas -mnomacsave -mieee -misize -minline-ic_invalidate -mprefergot -musermode -mult- cost=number -mdiv=strategy -mdivsi3_libfunc=name -mfixed-range=regis- ter-range -maccumulate-outgoing-args -matomic-model=atomic-model -mbranch-cost=num -mzdcbranch -mcbranch-force-delay-slot -mfsca -mfs- rra -mpretend-cmove -mfdpic -mtas -mlra Solaris 2 Options (Solaris 2 Options) -mclear-hwcap -mno-clear-hwcap -mimpure-text -mno-impure-text -gsctf SPARC Options (SPARC Options) -mcpu=cpu-type -mtune=cpu-type -mc- model=code-model -mmemory-model=mem-model -m32 -m64 -mptr32 -mptr64 -mapp-regs -mfaster-structs -mflat -mfpu -mhard-float -msoft-float -mhard-quad-float -msoft-quad-float -mstack-bias -mstd-struct-return -munaligned-doubles -muser-mode -mv8plus -mvis -mvis2 -mvis3 -mvis3b -mvis4 -mvis4b -mcbcond -mfmaf -mfsmuld -mpopc -msubxc -mfix-at697f -mfix-ut699 -mfix-ut700 -mfix-gr712rc System V Options (System V Options) -YP,paths -Ym,dir V850 Options (V850 Options) -mlong-calls -mep -mprolog-function -mspace -mtda=n -msda=n -mzda=n -mv850 -mv850e3v5 -m850e2v4 -mv850e2v3 -mv850e2 -mv850e1 -mv850es -mv850e -mdisable-callt -mre- lax -mlong-jumps -msoft-float -mhard-float -mloop -mrh850-abi -mghs -mgcc-abi -m8byte-align -mbig-switch -mapp-regs -msmall-sld -mno-strict-align -mjump-tables-in-data-section VAX Options (VAX Options) -munix -mgnu -md -md-float -mg -mg-float -mlra -mvaxc-alignment -mqmath Visium Options (Visium Options) -mdebug -msim -mfpu -mhard-float -msoft-float -mcpu=cpu-type -mtune=cpu-type -msv-mode -muser-mode VMS Options (VMS Options) -mvms-return-codes -mdebug-main=prefix -mmalloc64 -mpointer-size=size VxWorks Options (VxWorks Options) -mrtp -msmp -mvthreads -non-static -Bstatic -Bdynamic -Xbind-lazy -Xbind-now x86 Options (x86 Options) -mtune=cpu-type -march=cpu-type -mtune-ctrl=feature-list -mdump-tune-features -mno-default -mfp- math=unit -masm=dialect -mno-fancy-math-387 -mno-fp-ret-in-387 -m80387 -mhard-float -msoft-float -mieee-fp -mrtd -malign-double -mpreferred-stack-boundary=num -mincoming-stack-boundary=num -mcld -mcx16 -msahf -mmovbe -mcrc32 -mmwait -mrecip -mrecip=opt -mvzer- oupper -mstv -mprefer-avx128 -mprefer-vector-width=opt -mpar- tial-vector-fp-math -mmove-max=bits -mstore-max=bits -mnore- turn-no-callee-saved-registers -mmmx -msse -msse2 -msse3 -mssse3 -msse4.1 -msse4.2 -msse4 -mavx -mavx2 -mavx512f -mavx512cd -mavx512vl -mavx512bw -mavx512dq -mavx512ifma -mavx512vbmi -msha -maes -mpclmul -mfsgsbase -mrdrnd -mf16c -mfma -mpconfig -mwb- noinvd -mptwrite -mclflushopt -mclwb -mxsavec -mxsaves -msse4a -m3dnow -m3dnowa -mpopcnt -mabm -mbmi -mtbm -mfma4 -mxop -madx -mlzcnt -mbmi2 -mfxsr -mxsave -mxsaveopt -mrtm -mhle -mlwp -mmwaitx -mclzero -mpku -mgfni -mvaes -mwaitpkg -mshstk -mman- ual-endbr -mcet-switch -mforce-indirect-call -mavx512vbmi2 -mavx512bf16 -menqcmd -mvpclmulqdq -mavx512bitalg -mmovdiri -mmovdir64b -mavx512vpopcntdq -mavx512vnni -mprfchw -mrdpid -mrdseed -msgx -mavx512vp2intersect -mserialize -mtsxldtrk -mamx-tile -mamx-int8 -mamx-bf16 -muintr -mhreset -mavxvnni -mamx-fp8 -mavx512fp16 -mavxifma -mavxvnniint8 -mavxneconvert -mcmpccxadd -mamx-fp16 -mprefetchi -mraoint -mamx-complex -mavxvnniint16 -msm3 -msha512 -msm4 -mapxf -musermsr -mavx10.1 -mavx10.2 -mamx-avx512 -mamx-tf32 -mmovrs -mamx-movrs -mavx512bmm -mcldemote -mms-bit- fields -mno-align-stringops -minline-all-stringops -min- line-stringops-dynamically -mstringop-strategy=alg -mkl -mwidekl -mmemcpy-strategy=strategy -mmemset-strategy=strategy -mpush-args -maccumulate-outgoing-args -m128bit-long-double -m96bit-long-double -mlong-double-64 -mlong-double-80 -mlong-double-128 -mregparm=num -msseregparm -mveclibabi=type -mvect8-ret-in-mem -mpc32 -mpc64 -mpc80 -mdaz-ftz -mstackrealign -mstack-arg-probe -momit-leaf-frame-pointer -mno-red-zone -mno-tls-direct-seg-refs -mc- model=code-model -mabi=name -maddress-mode=mode -m32 -m64 -mx32 -m16 -miamcu -mlarge-data-threshold=num -msse2avx -mfentry -mrecord-mcount -mnop-mcount -m8bit-idiv -minstrument-return=type -mrecord-return -mfentry-name=name -mfentry-section=name -mskip-rax-setup -mavx256-split-unaligned-load -mavx256-split-un- aligned-store -malign-data=type -mstack-protector-guard=guard -mstack-protector-guard-reg=reg -mstack-protector-guard-offset=offset -mstack-protector-guard-symbol=symbol -mgeneral-regs-only -mcall-ms2sysv-xlogues -mtls-dialect=type -mrelax-cmpxchg-loop -mindi- rect-branch=choice -mfunction-return=choice -mindirect-branch-register -mharden-sls=choice -mindirect-branch-cs-prefix -mapx-in- line-asm-use-gpr32 -mgather -mscatter -mneeded -mno-direct-extern-ac- cess -munroll-only-small-loops -mdispatch-scheduler -mlam=choice x86 Windows Options See Cygwin and MinGW Options. Xstormy16 Options (Xstormy16 Options) -msim Xtensa Options (Xtensa Options) -mconst16 -mforce-no-pic -mno-serial- ize-volatile -mtext-section-literals -mauto-litpools -mno-tar- get-align -mlongcalls -mabi=abi-type -mextra-l32r-costs=cycles -mstrict-align -mforce-l32 zSeries Options See S/390 and zSeries Options. 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 pre- processing 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 com- pilation is done: file.c C source code that must be preprocessed. file.i C source code that should not be preprocessed. file.ii C++ source code that should not be preprocessed. file.m Objective-C source code. Note that you must link with the libobjc li- brary to make an Objective-C program work. file.mi Objective-C source code that should not be preprocessed. file.mm file.M Objective-C++ source code. Note that you must link with the libobjc library to make an Objective-C++ program work. Note that .M refers to a literal capital M. file.mii Objective-C++ source code that should not be preprocessed. file.h C, C++, Objective-C or Objective-C++ header file to be turned into a precompiled header (default), or C, C++ header file to be turned into an Ada spec (via the -fdump-ada-spec switch). file.cc file.cp file.cxx file.cpp file.CPP file.c++ file.C C++ source code that 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.mm file.M Objective-C++ source code that must be preprocessed. file.mii Objective-C++ source code that should not be preprocessed. file.hh file.H file.hp file.hxx file.hpp file.HPP file.h++ file.tcc C++ header file to be turned into a precompiled header or Ada spec. file.f file.for file.ftn file.fi Fixed form Fortran source code that should not be preprocessed. file.F file.FOR file.fpp file.FPP file.FTN Fixed form Fortran source code that must be preprocessed (with the tra- ditional preprocessor). file.f90 file.f95 file.f03 file.f08 file.fii Free form Fortran source code that should not be preprocessed. file.F90 file.F95 file.F03 file.F08 Free form Fortran source code that must be preprocessed (with the tra- ditional preprocessor). file.cob file.COB file.cbl file.CBL COBOL source code. file.go Go source code. file.d D source code. file.di D interface file. file.dd D documentation code (Ddoc). file.ads Ada source code file that contains a library unit declaration (a decla- ration of a package, subprogram, or generic, or a generic instantia- tion), 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 file.sx Assembler code that 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 --language=language --language language Specify explicitly the language for the following input files (rather than letting the compiler choose a default based on the file name suf- fix). 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++-system-header c++-user-header c++-cpp-output c++-system-module objective-c objective-c-header objective-c-cpp-output objc-cpp-output objective-c++ objective-c++-header objective-c++-cpp-output objc++-cpp-output assembler assembler-with-cpp ada adascil adawhy cobol d f77 f77-cpp-input f95 f95-cpp-input go modula-2 modula-2-cpp-output rust algol68 lto Note that -x does not imply a particular language standard. For exam- ple -x f77 may also require -std=legacy for some older source codes. -x none Turn off any specification of a language, so that subsequent files are handled according to their file name suffixes (as if -x has not been used at all). 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 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 ob- ject 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 --assemble Stop after the stage of compilation proper; do not assemble. The out- put is in the form of an assembler code file for each non-assembler in- put file specified. By default, the assembler file name for a source file is made by re- placing the suffix .c, .i, etc., with .s. Input files that don't require compilation are ignored. -E --preprocess 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 that don't require preprocessing are ignored. -o file --output=file --output file Place the primary output in file file. This applies to whatever sort of output is being produced, whether it be an executable file, an ob- ject file, an assembler file or preprocessed C code. 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, a precompiled header file in source.suffix.gch, and all preprocessed C source on standard output. Though -o names only the primary output, it also affects the naming of auxiliary and dump outputs. See the examples below. Unless overrid- den, both auxiliary outputs and dump outputs are placed in the same di- rectory as the primary output. In auxiliary outputs, the suffix of the input file is replaced with that of the auxiliary output file type; in dump outputs, the suffix of the dump file is appended to the input file suffix. In compilation commands, the base name of both auxiliary and dump outputs is that of the primary output; in compile and link com- mands, the primary output name, minus the executable suffix, is com- bined with the input file name. If both share the same base name, dis- regarding the suffix, the result of the combination is that base name, otherwise, they are concatenated, separated by a dash. gcc -c foo.c ... will use foo.o as the primary output, and place aux outputs and dumps next to it, e.g., aux file foo.dwo for -gsplit-dwarf, and dump file foo.c.???r.final for -fdump-rtl-final. If a non-linker output file is explicitly specified, aux and dump files by default take the same base name: gcc -c foo.c -o dir/foobar.o ... will name aux outputs dir/foobar.* and dump outputs dir/foobar.c.*. A linker output will instead prefix aux and dump outputs: gcc foo.c bar.c -o dir/foobar ... will generally name aux outputs dir/foobar-foo.* and dir/foobar-bar.*, and dump outputs dir/foobar-foo.c.* and dir/foobar-bar.c.*. The one exception to the above is when the executable shares the base name with the single input: gcc foo.c -o dir/foo ... in which case aux outputs are named dir/foo.* and dump outputs named dir/foo.c.*. The location and the names of auxiliary and dump outputs can be ad- justed by the options -dumpbase, -dumpbase-ext, -dumpdir, -save-temps=cwd, and -save-temps=obj. -dumpbase dumpbase --dumpbase dumpbase This option sets the base name for auxiliary and dump output files. It does not affect the name of the primary output file. Intermediate out- puts, when preserved, are not regarded as primary outputs, but as aux- iliary outputs: gcc -save-temps -S foo.c saves the (no longer) temporary preprocessed file in foo.i, and then compiles to the (implied) output file foo.s, whereas: gcc -save-temps -dumpbase save-foo -c foo.c preprocesses to in save-foo.i, compiles to save-foo.s (now an interme- diate, thus auxiliary output), and then assembles to the (implied) out- put file foo.o. Absent this option, dump and aux files take their names from the input file, or from the (non-linker) output file, if one is explicitly speci- fied: dump output files (e.g. those requested by -fdump-* options) with the input name suffix, and aux output files (those requested by other non-dump options, e.g. "-save-temps", "-gsplit-dwarf", "-fcall- graph-info") without it. Similar suffix differentiation of dump and aux outputs can be attained for explicitly-given -dumpbase basename.suf by also specifying -dump- base-ext .suf. If dumpbase is explicitly specified with any directory component, any dumppfx specification (e.g. -dumpdir or -save-temps=*) is ignored, and instead of appending to it, dumpbase fully overrides it: gcc foo.c -c -o dir/foo.o -dumpbase alt/foo \ -dumpdir pfx- -save-temps=cwd ... creates auxiliary and dump outputs named alt/foo.*, disregarding dir/ in -o, the ./ prefix implied by -save-temps=cwd, and pfx- in -dumpdir. When -dumpbase is specified in a command that compiles multiple inputs, or that compiles and then links, it may be combined with dumppfx, as specified under -dumpdir. Then, each input file is compiled using the combined dumppfx, and default values for dumpbase and auxdropsuf are computed for each input file: gcc foo.c bar.c -c -dumpbase main ... creates foo.o and bar.o as primary outputs, and avoids overwriting the auxiliary and dump outputs by using the dumpbase as a prefix, creating auxiliary and dump outputs named main-foo.* and main-bar.*. An empty string specified as dumpbase avoids the influence of the out- put basename in the naming of auxiliary and dump outputs during compi- lation, computing default values : gcc -c foo.c -o dir/foobar.o -dumpbase " ... will name aux outputs dir/foo.* and dump outputs dir/foo.c.*. Note how their basenames are taken from the input name, but the directory still defaults to that of the output. The empty-string dumpbase does not prevent the use of the output base- name for outputs during linking: gcc foo.c bar.c -o dir/foobar -dumpbase " -flto ... The compilation of the source files will name auxiliary outputs dir/foo.* and dir/bar.*, and dump outputs dir/foo.c.* and dir/bar.c.*. LTO recompilation during linking will use dir/foobar. as the prefix for dumps and auxiliary files. -dumpbase-ext auxdropsuf --dumpbase-ext auxdropsuf When forming the name of an auxiliary (but not a dump) output file, drop trailing auxdropsuf from dumpbase before appending any suffixes. If not specified, this option defaults to the suffix of a default dump- base, i.e., the suffix of the input file when -dumpbase is not present in the command line, or dumpbase is combined with dumppfx. gcc foo.c -c -o dir/foo.o -dumpbase x-foo.c -dumpbase-ext .c ... creates dir/foo.o as the main output, and generates auxiliary outputs in dir/x-foo.*, taking the location of the primary output, and dropping the .c suffix from the dumpbase. Dump outputs retain the suffix: dir/x-foo.c.*. This option is disregarded if it does not match the suffix of a speci- fied dumpbase, except as an alternative to the executable suffix when appending the linker output base name to dumppfx, as specified below: gcc foo.c bar.c -o main.out -dumpbase-ext .out ... creates main.out as the primary output, and avoids overwriting the aux- iliary and dump outputs by using the executable name minus auxdropsuf as a prefix, creating auxiliary outputs named main-foo.* and main-bar.* and dump outputs named main-foo.c.* and main-bar.c.*. -dumpdir dumppfx --dumpdir dumppfx When forming the name of an auxiliary or dump output file, use dumppfx as a prefix: gcc -dumpdir pfx- -c foo.c ... creates foo.o as the primary output, and auxiliary outputs named pfx-foo.*, combining the given dumppfx with the default dumpbase de- rived from the default primary output, derived in turn from the input name. Dump outputs also take the input name suffix: pfx-foo.c.*. If dumppfx is to be used as a directory name, it must end with a direc- tory separator: gcc -dumpdir dir/ -c foo.c -o obj/bar.o ... creates obj/bar.o as the primary output, and auxiliary outputs named dir/bar.*, combining the given dumppfx with the default dumpbase de- rived from the primary output name. Dump outputs also take the input name suffix: dir/bar.c.*. It defaults to the location of the output file, unless the output file is a special file like "/dev/null". Options -save-temps=cwd and -save-temps=obj override this default, just like an explicit -dumpdir option. In case multiple such options are given, the last one pre- vails: gcc -dumpdir pfx- -c foo.c -save-temps=obj ... outputs foo.o, with auxiliary outputs named foo.* because -save-temps=* overrides the dumppfx given by the earlier -dumpdir option. It does not matter that =obj is the default for -save-temps, nor that the out- put directory is implicitly the current directory. Dump outputs are named foo.c.*. When compiling from multiple input files, if -dumpbase is specified, dumpbase, minus a auxdropsuf suffix, and a dash are appended to (or override, if containing any directory components) an explicit or de- faulted dumppfx, so that each of the multiple compilations gets differ- ently-named aux and dump outputs. gcc foo.c bar.c -c -dumpdir dir/pfx- -dumpbase main ... outputs auxiliary dumps to dir/pfx-main-foo.* and dir/pfx-main-bar.*, appending dumpbase- to dumppfx. Dump outputs retain the input file suffix: dir/pfx-main-foo.c.* and dir/pfx-main-bar.c.*, respectively. Contrast with the single-input compilation: gcc foo.c -c -dumpdir dir/pfx- -dumpbase main ... that, applying -dumpbase to a single source, does not compute and ap- pend a separate dumpbase per input file. Its auxiliary and dump out- puts go in dir/pfx-main.*. When compiling and then linking from multiple input files, a defaulted or explicitly specified dumppfx also undergoes the dumpbase- transfor- mation above (e.g. the compilation of foo.c and bar.c above, but with- out -c). If neither -dumpdir nor -dumpbase are given, the linker out- put base name, minus auxdropsuf, if specified, or the executable suffix otherwise, plus a dash is appended to the default dumppfx instead. Note, however, that unlike earlier cases of linking: gcc foo.c bar.c -dumpdir dir/pfx- -o main ... does not append the output name main to dumppfx, because -dumpdir is explicitly specified. The goal is that the explicitly-specified dumppfx may contain the specified output name as part of the prefix, if desired; only an explicitly-specified -dumpbase would be combined with it, in order to avoid simply discarding a meaningful option. When compiling and then linking from a single input file, the linker output base name will only be appended to the default dumppfx as above if it does not share the base name with the single input file name. This has been covered in single-input linking cases above, but not with an explicit -dumpdir that inhibits the combination, even if overridden by -save-temps=*: gcc foo.c -dumpdir alt/pfx- -o dir/main.exe -save-temps=cwd ... Auxiliary outputs are named foo.*, and dump outputs foo.c.*, in the current working directory as ultimately requested by -save-temps=cwd. Summing it all up for an intuitive though slightly imprecise data flow: the primary output name is broken into a directory part and a basename part; dumppfx is set to the former, unless overridden by -dumpdir or -save-temps=*, and dumpbase is set to the latter, unless overridden by -dumpbase. If there are multiple inputs or linking, this dumpbase may be combined with dumppfx and taken from each input file. Auxiliary output names for each input are formed by combining dumppfx, dumpbase minus suffix, and the auxiliary output suffix; dump output names are only different in that the suffix from dumpbase is retained. When it comes to auxiliary and dump outputs created during LTO recompi- lation, a combination of dumppfx and dumpbase, as given or as derived from the linker output name but not from inputs, even in cases in which this combination would not otherwise be used as such, is passed down with a trailing period replacing the compiler-added dash, if any, as a -dumpdir option to lto-wrapper; being involved in linking, this program does not normally get any -dumpbase and -dumpbase-ext, and it ignores them. When running sub-compilers, lto-wrapper appends LTO stage names to the received dumppfx, ensures it contains a directory component so that it overrides any -dumpdir, and passes that as -dumpbase to sub-compilers. -v --verbose 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 arguments are quoted unless they contain only alphanumeric characters or "./-_". This is useful for shell scripts to capture the driver-generated command lines. --help Print (on the standard output) a description of the command-line op- tions understood by gcc. If the -v option is also specified then --help is also passed on to the various processes invoked by gcc, so that they can display the command-line options they accept. If the -Wextra option has also been specified (prior to the --help option), then command-line options that have no documentation associated with them are also displayed. --target-help Print (on the standard output) a description of target-specific com- mand-line options for each tool. For some targets extra target-spe- cific information may also be printed. --help={class|[^]qualifier}[,...] Print (on the standard output) a description of the command-line op- tions understood by the compiler that fit into all specified classes and qualifiers. These are the supported classes: optimizers Display all of the optimization options supported by the compiler. warnings Display all of the options controlling warning messages produced by the compiler. target Display target-specific options. Unlike the --target-help option however, target-specific options of the linker and assembler are not displayed. This is because those tools do not currently sup- port the extended --help= syntax. params Display the values recognized by the --param option. language Display the options supported for language, where language is the name of one of the languages supported in this version of GCC. If an option is supported by all languages, one needs to select common class. common Display the options that are common to all languages. These are the supported qualifiers: undocumented Display only those options that are undocumented. joined Display options taking an argument that appears after an equal sign in the same continuous piece of text, such as: --help=target. separate Display options taking an argument that appears as a separate word following the original option, such as: -o output-file. Thus for example to display all the undocumented target-specific switches supported by the compiler, use: --help=target,undocumented The sense of a qualifier can be inverted by prefixing it with the ^ character, so for example to display all binary warning options (i.e., ones that are either on or off and that do not take an argument) that have a description, use: --help=warnings,^joined,^undocumented The argument to --help= should not consist solely of inverted quali- fiers. Combining several classes is possible, although this usually restricts the output so much that there is nothing to display. One case where it does work, however, is when one of the classes is target. For example, to display all the target-specific optimization options, use: --help=target,optimizers The --help= option can be repeated on the command line. Each succes- sive use displays its requested class of options, skipping those that have already been displayed. If --help is also specified anywhere on the command line then this takes precedence over any --help= option. If the -Q option appears on the command line before the --help= option, then the descriptive text displayed by --help= is changed. Instead of describing the displayed options, an indication is given as to whether the option is enabled, disabled or set to a specific value (assuming that the compiler knows this at the point where the --help= option is used). Here is a truncated example from the ARM port of gcc: % gcc -Q -mabi=2 --help=target -c The following options are target specific: -mabi= 2 -mabort-on-noreturn [disabled] -mapcs [disabled] The output is sensitive to the effects of previous command-line op- tions, so for example it is possible to find out which optimizations are enabled at -O2 by using: -Q -O2 --help=optimizers Alternatively you can discover which binary optimizations are enabled by -O3 by using: gcc -c -Q -O3 --help=optimizers > /tmp/O3-opts gcc -c -Q -O2 --help=optimizers > /tmp/O2-opts diff /tmp/O2-opts /tmp/O3-opts | grep enabled --version Display the version number and copyrights of the invoked GCC. -pass-exit-codes --pass-exit-codes Normally the gcc program exits 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 instead returns with the numerically highest error produced by any phase returning an error indication. The C, C++, and Fortran front ends return 4 if an internal compiler error is encountered. -pipe --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 assem- bler has no trouble. -wrapper Invoke all subcommands under a wrapper program. The name of the wrap- per program and its parameters are passed as a comma separated list. gcc -c t.c -wrapper gdb,--args This invokes all subprograms of gcc under gdb --args, thus the invoca- tion of cc1 is gdb --args cc1 .... -ffile-prefix-map=old=new When compiling files residing in directory old, record any references to them in the result of the compilation as if the files resided in di- rectory new instead. Specifying this option is equivalent to specify- ing all the individual -f*-prefix-map options. This can be used to make reproducible builds that are location independent. Directories referenced by directives are not affected by these options. See also -fmacro-prefix-map, -fdebug-prefix-map, -fprofile-prefix-map and -fcanon-prefix-map. -fcanon-prefix-map For the -f*-prefix-map options normally comparison of old prefix against the filename that would be normally referenced in the result of the compilation is done using textual comparison of the prefixes, or ignoring character case for case insensitive filesystems and consider- ing slashes and backslashes as equal on DOS based filesystems. The -fcanon-prefix-map causes such comparisons to be done on canonicalized paths of old and the referenced filename. -fplugin=name.so Load the plugin code in file name.so, assumed to be a shared object to be dlopen'd by the compiler. The base name of the shared object file is used to identify the plugin for the purposes of argument parsing (See -fplugin-arg-name-key=value below). Each plugin should define the callback functions specified in the Plugins API. -fplugin-arg-name-key=value Define an argument called key with a value of value for the plugin called name. -fdump-ada-spec[-slim] For C and C++ source and include files, generate corresponding Ada specs. -fada-spec-parent=unit In conjunction with -fdump-ada-spec[-slim] above, generate Ada specs as child units of parent unit. -fdump-go-spec=file For input files in any language, generate corresponding Go declarations in file. This generates Go "const", "type", "var", and "func" declara- tions which may be a useful way to start writing a Go interface to code written in some other language. @file Read command-line options from file. The options read are inserted in place of the original @file option. If file does not exist, or cannot be read, then the option will be treated literally, and not removed. Options in file are separated by whitespace. A whitespace character may be included in an option by surrounding the entire option in either single or double quotes. Any character (including a backslash) may be included by prefixing the character to be included with a backslash. The file may itself contain additional @file options; any such options will be processed recursively. 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, .hpp, .H, or (for shared template code) .tcc; preprocessed C++ files use the suffix .ii; and C++20 module interface units sometimes use .ixx, .cppm, .cxxm, .c++m, or .ccm. 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, the use of gcc does not add the C++ library. g++ is a program that calls GCC and automatically specifies linking against the C++ library. It treats .c, .h and .i files as C++ source files instead of C source files unless -x is used. This program is also useful when precompiling a C header file with a .h extension for use in C++ compilations. On many sys- tems, g++ is also installed with the name c++. When you compile C++ programs, you may specify many of the same com- mand-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. Options Controlling C Dialect The following options control the dialect of C (or languages derived from C, such as C++, Objective-C and Objective-C++) that the compiler accepts: -ansi --ansi In C mode, this is equivalent to -std=c90. In C++ mode, it is equiva- lent to -std=c++98. -std= Determine the language standard. This option is currently only sup- ported when compiling C or C++. The compiler can accept several base standards, such as c90 or c++98, and GNU dialects of those standards, such as gnu90 or gnu++98. When a base standard is specified, the compiler accepts all programs following that standard plus those using GNU extensions that do not contradict it. For example, -std=c90 turns off certain features of GCC that are incompatible with ISO C90, such as the "asm" and "typeof" keywords, but not other GNU extensions that do not have a meaning in ISO C90, such as omitting the middle term of a "?:" expression. On the other hand, when a GNU dialect of a standard is specified, all features supported by the compiler are enabled, even when those features change the meaning of the base standard. As a result, some strict-conforming programs may be rejected. The particular standard is used by -Wpedantic to identify which features are GNU extensions given that version of the standard. For example -std=gnu90 -Wpedantic warns about C++ style // comments, while -std=gnu99 -Wpedantic does not. A value for this option must be provided; possible values are c90 c89 iso9899:1990 Support all ISO C90 programs (certain GNU extensions that conflict with ISO C90 are disabled). Same as -ansi for C code. iso9899:199409 ISO C90 as modified in amendment 1. c99 c9x iso9899:1999 iso9899:199x ISO C99. This standard is substantially completely supported, mod- ulo bugs and floating-point issues (mainly but not entirely relat- ing to optional C99 features from Annexes F and G). See <https://gcc.gnu.org/projects/c-status.html> for more information. The names c9x and iso9899:199x are deprecated. c11 c1x iso9899:2011 ISO C11, the 2011 revision of the ISO C standard. This standard is substantially completely supported, modulo bugs, floating-point is- sues (mainly but not entirely relating to optional C11 features from Annexes F and G) and the optional Annexes K (Bounds-checking interfaces) and L (Analyzability). The name c1x is deprecated. c17 c18 iso9899:2017 iso9899:2018 ISO C17, the 2017 revision of the ISO C standard (published in 2018). This standard is same as C11 except for corrections of de- fects (all of which are also applied with -std=c11) and a new value of "__STDC_VERSION__", and so is supported to the same extent as C11. c23 c2x iso9899:2024 ISO C23, the 2023 revision of the ISO C standard (published in 2024). The name c2x is deprecated. c2y The next version of the ISO C standard, still under development. The support for this version is experimental and incomplete. gnu90 gnu89 GNU dialect of ISO C90 (including some C99 features). gnu99 gnu9x GNU dialect of ISO C99. The name gnu9x is deprecated. gnu11 gnu1x GNU dialect of ISO C11. The name gnu1x is deprecated. gnu17 gnu18 GNU dialect of ISO C17. gnu23 gnu2x GNU dialect of ISO C23. This is the default for C code. The name gnu2x is deprecated. gnu2y The next version of the ISO C standard, still under development, plus GNU extensions. The support for this version is experimental and incomplete. The name gnu2x is deprecated. c++98 c++03 The 1998 ISO C++ standard plus the 2003 technical corrigendum and some additional defect reports. Same as -ansi for C++ code. gnu++98 gnu++03 GNU dialect of -std=c++98. c++11 c++0x The 2011 ISO C++ standard plus amendments. The name c++0x is dep- recated. gnu++11 gnu++0x GNU dialect of -std=c++11. The name gnu++0x is deprecated. c++14 c++1y The 2014 ISO C++ standard plus amendments. The name c++1y is dep- recated. gnu++14 gnu++1y GNU dialect of -std=c++14. The name gnu++1y is deprecated. c++17 c++1z The 2017 ISO C++ standard plus amendments. The name c++1z is dep- recated. gnu++17 gnu++1z GNU dialect of -std=c++17. The name gnu++1z is deprecated. c++20 c++2a The 2020 ISO C++ standard plus amendments. C++20 modules support is still experimental and needs to be enabled with -fmodules op- tion. The name c++2a is deprecated. gnu++20 gnu++2a GNU dialect of -std=c++20. This is the default for C++ code. C++20 modules support is still experimental and needs to be enabled with -fmodules option. The name gnu++2a is deprecated. c++23 c++2b The 2023 ISO C++ standard plus amendments (published in 2024). Support is experimental, and could change in incompatible ways in future releases. The name c++2b is deprecated. gnu++23 gnu++2b GNU dialect of -std=c++23. Support is experimental, and could change in incompatible ways in future releases. The name gnu++2b is deprecated. c++26 c++2c The next revision of the ISO C++ standard, planned for 2026. Sup- port is highly experimental, and will almost certainly change in incompatible ways in future releases. gnu++26 gnu++2c GNU dialect of -std=c++26. Support is highly experimental, and will almost certainly change in incompatible ways in future re- leases. c++29 c++2d The upcoming revision of the ISO C++ standard, planned for 2029. Support is highly experimental, and will almost certainly change in incompatible ways in future releases. gnu++29 gnu++2d GNU dialect of -std=c++29. Support is highly experimental, and will almost certainly change in incompatible ways in future re- leases. -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, re- spectively, 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 de- finitions, 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. In C, -ansi implies -fno-asm. In C++, "inline" is a standard keyword and is not affected by this switch. You may want to use the -fno-gnu-keywords flag instead, which disables "typeof" but not "asm" and "inline". 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. In C23 mode (-std=c23 or -std=gnu23), this switch only affects the "asm" keyword, since "typeof" is a standard keyword in ISO C23. -fno-builtin -fno-builtin-function Don't recognize built-in functions that do not begin with __builtin_ as prefix. GCC normally generates special code to handle certain built-in func- tions more efficiently; for instance, calls to "alloca" may become sin- gle instructions which 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. In addition, when a function is recognized as a built-in function, GCC may use in- formation about that function to warn about problems with calls to that function, or to generate more efficient code, even if the resulting code still contains calls to that function. For example, warnings are given with -Wformat for bad calls to "printf" when "printf" is built in and "strlen" is known not to modify global memory. With the -fno-builtin-function option only the built-in function func- tion is disabled. function must not begin with __builtin_. If a func- tion is named that 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)) -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++. -ffreestanding Assert that compilation targets a freestanding environment. This im- plies -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. -fgimple Enable parsing of function definitions marked with "__GIMPLE". This is an experimental feature that allows unit testing of GIMPLE passes. -fgnu-tm When the option -fgnu-tm is specified, the compiler generates code for the Linux variant of Intel's current Transactional Memory ABI specifi- cation document (Revision 1.1, May 6 2009). This is an experimental feature whose interface may change in future versions of GCC, as the official specification changes. Please note that not all architectures are supported for this feature. For more information on GCC's support for transactional memory, Note that the transactional memory feature is not supported with non-call exceptions (-fnon-call-exceptions). -fgnu89-inline The option -fgnu89-inline tells GCC to use the traditional GNU seman- tics for "inline" functions when in C99 mode. Using this option is roughly equivalent to adding the "gnu_inline" function attribute to all inline functions. The option -fno-gnu89-inline explicitly tells GCC to use the C99 seman- tics for "inline" when in C99 or gnu99 mode (i.e., it specifies the de- fault behavior). This option is not supported in -std=c90 or -std=gnu90 mode. The preprocessor macros "__GNUC_GNU_INLINE__" and "__GNUC_STDC_IN- LINE__" may be used to check which semantics are in effect for "inline" functions. -fhosted Assert that compilation targets 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. -flax-vector-conversions Allow implicit conversions between vectors with differing numbers of elements and/or incompatible element types. This option should not be used for new code. -fms-extensions Accept some non-standard constructs used in Microsoft header files. In C++ code, this allows member names in structures to be similar to previous types declarations. typedef int UOW; struct ABC { UOW UOW; }; Some cases of unnamed fields in structures and unions are only accepted with this option. Note that this option is off for all targets except for x86 targets us- ing ms-abi. -fpermitted-flt-eval-methods=style ISO/IEC TS 18661-3 defines new permissible values for "FLT_EVAL_METHOD" that indicate that operations and constants with a semantic type that is an interchange or extended format should be evaluated to the preci- sion and range of that type. These new values are a superset of those permitted under C99/C11, which does not specify the meaning of other positive values of "FLT_EVAL_METHOD". As such, code conforming to C11 may not have been written expecting the possibility of the new values. -fpermitted-flt-eval-methods specifies whether the compiler should al- low only the values of "FLT_EVAL_METHOD" specified in C99/C11, or the extended set of values specified in ISO/IEC TS 18661-3. style is either "c11" or "ts-18661-3" as appropriate. The default when in a standards compliant mode (-std=c11 or similar) is -fpermitted-flt-eval-methods=c11. The default when in a GNU dialect (-std=gnu11 or similar) is -fpermitted-flt-eval-methods=ts-18661-3. The -fdeps-* options are used to extract structured dependency informa- tion for a source. This involves determining what resources provided by other source files will be required to compile the source as well as what resources are provided by the source. This information can be used to add required dependencies between compilation rules of depen- dent sources based on their contents rather than requiring such infor- mation be reflected within the build tools as well. -fdeps-file=file Where to write structured dependency information. -fdeps-format=format The format to use for structured dependency information. p1689r5 is the only supported format right now. Note that when this argument is spec- ified, the output of -MF is stripped of some information (namely C++ modules) so that it does not use extended makefile syntax not under- stood by most tools. -fdeps-target=file Analogous to -MT but for structured dependency information. This indi- cates the target which will ultimately need any required resources and provide any resources extracted from the source that may be required by other sources. -fplan9-extensions Accept some non-standard constructs used in Plan 9 code. This enables -fms-extensions, permits passing pointers to structures with anonymous fields to functions that expect pointers to elements of the type of the field, and permits referring to anonymous fields de- clared using a typedef. This is only supported for C, not C++. -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 de- fault, such a bit-field is signed, because this is consistent: the ba- sic integer types such as "int" are signed types. -fsigned-char -funsigned-char -fsigned-char lets the type "char" be signed, like "signed char", while -funsigned-char lets the type "char" be unsigned, like "unsigned char". Note that -fsigned-char 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. Each target supported by GCC has a default for what "char" should be, which is typically specified in the processor-specific ABI document for that target. It is either like "unsigned char" by default or like "signed char" by default. Ideally, a portable program should always use "signed char" or "un- signed 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. These options 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. -fstrict-flex-arrays (C and C++ only) -fstrict-flex-arrays=level (C and C++ only) Control when to treat the trailing array of a structure as a flexible array member for the purpose of accessing the elements of such an ar- ray. The value of level controls the level of strictness. -fstrict-flex-arrays is equivalent to -fstrict-flex-arrays=3, which is the strictest; a trailing array is treated as a flexible array member only when it is declared as a flexible array member per C99 standard onwards. The negative form -fno-strict-flex-arrays is equivalent to -fstrict-flex-arrays=0, which is the least strict. In this case all trailing arrays of structures are treated as flexible array members. There are two more levels in between 0 and 3, which are provided to support older code that uses the GCC zero-length array extension ([0]) or one-element array as flexible array members ([1]). When level is 1, the trailing array is treated as a flexible array member when it is de- clared as either [], [0], or [1]. When level is 2, the trailing array is treated as a flexible array member when it is declared as either [], or [0]. You can control this behavior for a specific trailing array field of a structure by using the variable attribute "strict_flex_array" at- tribute. The -fstrict_flex_arrays option interacts with the -Wstrict-flex-arrays option. -fsso-struct=endianness Set the default scalar storage order of structures and unions to the specified endianness. The accepted values are big-endian, little-en- dian and native for the native endianness of the target (the default). This option is not supported for C++. Warning: the -fsso-struct switch causes GCC to generate code that is not binary compatible with code generated without it if the specified endianness is not the native endianness of the target. Options Controlling C++ Dialect This section describes the command-line options that are only meaningful for C++ programs. You can also use most of the GNU compiler options re- gardless of what language your program is in. For example, you might com- pile a file firstClass.C like this: g++ -g -fstrict-enums -O -c firstClass.C In this example, only -fstrict-enums is an option meant only for C++ pro- grams; you can use the other options with any language supported by GCC. Some options for compiling C programs, such as -std, are also relevant for C++ programs. Here is a list of options that are only for compiling C++ programs: --compile-std-module Build the compiled module interfaces for the <bits/stdc++.h> header unit and the std and std.compat modules before compiling any source files explicitly specified on the command line. This is intended to be useful for building simple programs that use import std; with a single command. -fabi-version=n Use version n of the C++ ABI. The default is version 0. Version 0 refers to the version conforming most closely to the C++ ABI specification. Therefore, the ABI obtained using version 0 will change in different versions of G++ as ABI bugs are fixed. Version 1 is the version of the C++ ABI that first appeared in G++ 3.2. Version 2 is the version of the C++ ABI that first appeared in G++ 3.4, and was the default through G++ 4.9. Version 3 corrects an error in mangling a constant address as a tem- plate argument. Version 4, which first appeared in G++ 4.5, implements a standard man- gling for vector types. Version 5, which first appeared in G++ 4.6, corrects the mangling of attribute const/volatile on function pointer types, decltype of a plain decl, and use of a function parameter in the declaration of another pa- rameter. Version 6, which first appeared in G++ 4.7, corrects the promotion be- havior of C++11 scoped enums and the mangling of template argument packs, const/static_cast, prefix ++ and --, and a class scope function used as a template argument. Version 7, which first appeared in G++ 4.8, that treats nullptr_t as a builtin type and corrects the mangling of lambdas in default argument scope. Version 8, which first appeared in G++ 4.9, corrects the substitution behavior of function types with function-cv-qualifiers. Version 9, which first appeared in G++ 5.2, corrects the alignment of "nullptr_t". Version 10, which first appeared in G++ 6.1, adds mangling of attrib- utes that affect type identity, such as ia32 calling convention attrib- utes (e.g. stdcall). Version 11, which first appeared in G++ 7, corrects the mangling of sizeof... expressions and operator names. For multiple entities with the same name within a function, that are declared in different scopes, the mangling now changes starting with the twelfth occurrence. It also implies -fnew-inheriting-ctors. Version 12, which first appeared in G++ 8, corrects the calling conven- tions for empty classes on the x86_64 target and for classes with only deleted copy/move constructors. It accidentally changes the calling convention for classes with a deleted copy constructor and a trivial move constructor. Version 13, which first appeared in G++ 8.2, fixes the accidental change in version 12. Version 14, which first appeared in G++ 10, corrects the mangling of the nullptr expression. Version 15, which first appeared in G++ 10.3, corrects G++ 10 ABI tag regression. Version 16, which first appeared in G++ 11, changes the mangling of "__alignof__" to be distinct from that of "alignof", and dependent op- erator names. Version 17, which first appeared in G++ 12, fixes layout of classes that inherit from aggregate classes with default member initializers in C++14 and up. Version 18, which first appeared in G++ 13, fixes manglings of lambdas that have additional context. Version 19, which first appeared in G++ 14, fixes manglings of struc- tured bindings to include ABI tags, handling of cv-qualified [[no_unique_address]] members, and adds mangling of C++20 constraints on function templates. Version 20, which first appeared in G++ 15, fixes manglings of lambdas in static data member initializers. Version 21, which first appeared in G++ 16, fixes unnecessary captures in noexcept lambdas (c++/119764), layout of a base class with all ex- plicitly defaulted constructors (c++/120012), and mangling of class and array objects with implicitly zero-initialized non-trailing subobjects (c++/121231). See also -Wabi. -fabi-compat-version=n On targets that support strong aliases, G++ works around mangling changes by creating an alias with the correct mangled name when defin- ing a symbol with an incorrect mangled name. This switch specifies which ABI version to use for the alias. With -fabi-version=0 (the default), this defaults to 13 (GCC 8.2 com- patibility). If another ABI version is explicitly selected, this de- faults to 0. For compatibility with GCC versions 3.2 through 4.9, use -fabi-compat-version=2. If this option is not provided but -Wabi=n is, that version is used for compatibility aliases. If this option is provided along with -Wabi (without the version), the version from this option is used for the warning. -fno-access-control Turn off all access checking. This switch is mainly useful for working around bugs in the access control code. -faligned-new -faligned-new=alignment Enable support for C++17 "new" of types that require more alignment than "void* ::operator new(std::size_t)" provides. A numeric argument such as "-faligned-new=32" can be used to specify how much alignment (in bytes) is provided by that function, but few users will need to override the default of alignof(std::max_align_t). This flag is enabled by default for -std=c++17. -fno-assume-sane-operators-new The C++ standard allows replacing the global "new", "new[]", "delete" and "delete[]" operators, though a lot of C++ programs don't replace them and just use the implementation provided version. Furthermore, the C++ standard allows omitting those calls if they are made from new or delete expressions (and by extension the same is assumed if "__builtin_operator_new" or "__builtin_operator_delete" functions are used). This option allows control over some optimizations around calls to those operators. With "-fassume-sane-operators-new-delete" option GCC may assume that calls to the replaceable global operators from new or delete expressions or from "__builtin_operator_new" or "__builtin_operator_delete" calls don't read or modify any global vari- ables or variables whose address could escape to the operators (global state; except for "errno" for the "new" and "new[]" operators). This allows most optimizations across those calls and is something that the implementation provided operators satisfy unless "malloc" implementa- tion details are observable in the code or unless "malloc" hooks are used, but might not be satisfied if a program replaces those operators. This behavior is enabled by default. With "-fno-assume-sane-opera- tors-new-delete" option GCC must assume all these calls (whether from new or delete expressions or called directly) may read and write global state unless proven otherwise (e.g. when GCC compiles their implemen- tation). Use this option if those operators are or may be replaced and code needs to expect such behavior. -fchar8_t -fno-char8_t Enable support for "char8_t" as adopted for C++20. This includes the addition of a new "char8_t" fundamental type, changes to the types of UTF-8 string and character literals, new signatures for user-defined literals, associated standard library updates, and new "__cpp_char8_t" and "__cpp_lib_char8_t" feature test macros. This option enables functions to be overloaded for ordinary and UTF-8 strings: int f(const char *); // #1 int f(const char8_t *); // #2 int v1 = f("text"); // Calls #1 int v2 = f(u8"text"); // Calls #2 and introduces new signatures for user-defined literals: int operator""_udl1(char8_t); int v3 = u8'x'_udl1; int operator""_udl2(const char8_t*, std::size_t); int v4 = u8"text"_udl2; template<typename T, T...> int operator""_udl3(); int v5 = u8"text"_udl3; The change to the types of UTF-8 string and character literals intro- duces incompatibilities with ISO C++11 and later standards. For exam- ple, the following code is well-formed under ISO C++11, but is ill-formed when -fchar8_t is specified. const char *cp = u8"xx";// error: invalid conversion from // `const char8_t*' to `const char*' int f(const char*); auto v = f(u8"xx"); // error: invalid conversion from // `const char8_t*' to `const char*' std::string s{u8"xx"}; // error: no matching function for call to // `std::basic_string<char>::basic_string()' using namespace std::literals; s = u8"xx"s; // error: conversion from // `basic_string<char8_t>' to non-scalar // type `basic_string<char>' requested -fcheck-new Check that the pointer returned by "operator new" is non-null before attempting to modify the storage allocated. This check is normally un- necessary because the C++ standard specifies that "operator new" only returns 0 if it is declared throw(), in which case the compiler always checks the return value even without this option. In all other cases, when "operator new" has a non-empty exception specification, memory ex- haustion is signalled by throwing "std::bad_alloc". See also new (nothrow). -fconcepts Enable support for the C++ Concepts feature for constraining template arguments. With -std=c++20 and above, Concepts are part of the lan- guage standard, so -fconcepts defaults to on. Some constructs that were allowed by the earlier C++ Extensions for Concepts Technical Specification, ISO 19217 (2015), but didn't make it into the standard, could additionally be enabled by -fconcepts-ts. The option -fconcepts-ts was deprecated in GCC 14 and removed in GCC 15; users are expected to convert their code to C++20 concepts. -fconcepts-diagnostics-depth=n Specify maximum error replay depth during recursive diagnosis of a con- straint satisfaction failure. The default is 1. -fconstexpr-depth=n Set the maximum nested evaluation depth for C++11 constexpr functions to n. A limit is needed to detect endless recursion during constant expression evaluation. The minimum specified by the standard is 512. -fconstexpr-cache-depth=n Set the maximum level of nested evaluation depth for C++11 constexpr functions that will be cached to n. This is a heuristic that trades off compilation speed (when the cache avoids repeated calculations) against memory consumption (when the cache grows very large from highly recursive evaluations). The default is 8. Very few users are likely to want to adjust it, but if your code does heavy constexpr calcula- tions you might want to experiment to find which value works best for you. -fconstexpr-fp-except Annex F of the C standard specifies that IEC559 floating point excep- tions encountered at compile time should not stop compilation. C++ compilers have historically not followed this guidance, instead treat- ing floating point division by zero as non-constant even though it has a well defined value. This flag tells the compiler to give Annex F priority over other rules saying that a particular operation is unde- fined. constexpr float inf = 1./0.; // OK with -fconstexpr-fp-except -fconstexpr-loop-limit=n Set the maximum number of iterations for a loop in C++14 constexpr functions to n. A limit is needed to detect infinite loops during con- stant expression evaluation. The default is 262144 (1<<18). -fconstexpr-ops-limit=n Set the maximum number of operations during a single constexpr evalua- tion. Even when number of iterations of a single loop is limited with the above limit, if there are several nested loops and each of them has many iterations but still smaller than the above limit, or if in a body of some loop or even outside of a loop too many expressions need to be evaluated, the resulting constexpr evaluation might take too long. The default is 33554432 (1<<25). -fcontracts Enable support for the C++ Contracts feature, as specified in the C++26 working draft (N5003). On violation of an enforced or observed contract (see -fcontract-evalu- ation-semantic below), a violation handler is called; the standard li- brary provides a default handler that emits information about the con- tract that failed. Users can replace the default violation handler by defining void handle_contract_violation (const std::contracts::contract_violation&); -fcontract-evaluation-semantic=semantic Set the semantic with which contracts will be evaluated to semantic. Available values for the evaluation mode are: '"ignored"' The contract checks will be elided, with no checking added at either compile or runtime. '"observed"' The contract checks are performed (at runtime) and, if one fails, a handler is called that allows actions such as logging or emit- ting run-time warnings. When the handler returns, the execution of the code will continue. At compile-time the checks are performed for "con- stexpr" evaluations, in this case a diagnostic is emitted if the check fails. '"enforce"' The contract checks are performed and the handler is called if one fails. When the handler returns the execution of the code is terminated preventing it from continuing past the failed case. At com- pile-time the checks are applied to "constexpr" and, if one fails, the program is ill-formed; an error will be emitted. '"quick_enforce"' The contract checks are performed (at runtime) and, if one fails, the execution is terminated immediately (without calling any handler). At compile-time there is no difference in behaviour be- tween this option and the "enforce" case, since no handler is invoked at compile time. -fcontracts-conservative-ipa This prevents inter-procedural analysis from taking action when the body of an inline function is visible in a given TU. This allows for the case that contract evaluation conditions are permitted to differ between TUs which means that such actions would be potentially incor- rect. -fcontract-checks-outlined By default, contract checks for "pre" and "post" condition checks are expanded in-line into function bodies. This option causes a small function to be created instead (containing the checks) that is called in the relevant position. This permits different criteria to be ap- plied to the compilation of the checking and the remainder of the func- tion body. -fcontract-disable-optimized-checks When "pre" and "post" condition checks are outlined (using -fcon- tract-checks-outlined), this option disables the optimisation steps for those functions which can avoid unwanted elision of checking steps. -fcontracts-client-check=mode This option enables insertion of checks at call sites (caller-side checking). The value of mode determines which contract checks are made: '"none"' No caller/client side checking (default) '"pre"' Preconditions are checked at the caller/client side. '"all"' Both pre and post-conditions are checked at the caller/client side. -fcontracts-definition-check=mode This option introduces the ability to disable callee/definition-side checks, which are otherwise enabled by default when the contracts fea- ture is active. The variable mode has the values '"on"' and '"off"'. -fcoroutines Enable support for the C++ coroutines extension. With -std=c++20 and above, coroutines are part of the language standard, so -fcoroutines defaults to on. -fdiagnostics-all-candidates Permit the C++ front end to note all candidates during overload resolu- tion failure, including when a deleted function is selected. -fdump-lang- -fdump-lang-switch -fdump-lang-switch-options -fdump-lang-switch-options=filename Control the dumping of C++-specific information. The options and file- name portions behave as described in the -fdump-tree option. The fol- lowing switch values are accepted: all Enable all of the below. class Dump class hierarchy information. Virtual table information is emitted unless 'slim' is specified. module Dump module information. Options lineno (locations), graph (reach- ability), blocks (clusters), uid (serialization), alias (merge- able), asmname (Elrond), eh (mapper) & vops (macros) may provide additional information. raw Dump the raw internal tree data. tinst Dump the sequence of template instantiations, indented to show the depth of recursion. The lineno option adds the source location where the instantiation was triggered, and the details option also dumps pre-instantiation substitutions such as those performed dur- ing template argument deduction. Lines in the .tinst dump start with I for an instantiation, S for another substitution, and R[IS] for the reopened context of a de- ferred instantiation. -fno-elide-constructors The C++ standard allows an implementation to omit creating a temporary that is only used to initialize another object of the same type. Spec- ifying this option disables that optimization, and forces G++ to call the copy constructor in all cases. This option also causes G++ to call trivial member functions which otherwise would be expanded inline. In C++17, the compiler is required to omit these temporaries, but this option still affects trivial member functions. -fno-enforce-eh-specs Don't generate code to check for violation of exception specifications at run time. This option violates the C++ standard, but may be useful for reducing code size in production builds, much like defining "NDE- BUG". This does not give user code permission to throw exceptions in violation of the exception specifications; the compiler still optimizes based on the specifications, so throwing an unexpected exception re- sults in undefined behavior at run time. -fextern-tls-init -fno-extern-tls-init The C++11 and OpenMP standards allow "thread_local" and "threadprivate" variables to have dynamic (runtime) initialization. To support this, any use of such a variable goes through a wrapper function that per- forms any necessary initialization. When the use and definition of the variable are in the same translation unit, this overhead can be opti- mized away, but when the use is in a different translation unit there is significant overhead even if the variable doesn't actually need dy- namic initialization. If the programmer can be sure that no use of the variable in a non-defining TU needs to trigger dynamic initialization (either because the variable is statically initialized, or a use of the variable in the defining TU will be executed before any uses in another TU), they can avoid this overhead with the -fno-extern-tls-init option. On targets that support symbol aliases, the default is -fex- tern-tls-init. On targets that do not support symbol aliases, the de- fault is -fno-extern-tls-init. -ffold-simple-inlines -fno-fold-simple-inlines Permit the C++ frontend to fold calls to "std::move", "std::forward", "std::addressof", "std::to_underlying" and "std::as_const". In con- trast to inlining, this means no debug information will be generated for such calls. Since these functions are rarely interesting to debug, this flag is enabled by default unless -fno-inline is active. -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. This option is implied by the strict ISO C++ dialects: -ansi, -std=c++98, -std=c++11, etc. -fno-immediate-escalation Do not enable immediate function escalation whereby certain functions can be promoted to consteval, as specified in P2564R3. For example: consteval int id(int i) { return i; } constexpr int f(auto t) { return t + id(t); // id causes f<int> to be promoted to consteval } void g(int i) { f (3); } compiles in C++20: "f" is an immediate-escalating function (due to the "auto" it is a function template and is declared "constexpr") and id(t) is an immediate-escalating expression, so "f" is promoted to "conste- val". Consequently, the call to id(t) is in an immediate context, so doesn't have to produce a constant (that is the mechanism allowing con- steval function composition). However, with -fno-immediate-escalation, "f" is not promoted to "consteval", and since the call to consteval function id(t) is not a constant expression, the compiler rejects the code. This option is turned on by default; it is only effective in C++20 mode or later. -fimplicit-constexpr Make inline functions implicitly constexpr, if they satisfy the re- quirements for a constexpr function. This option can be used in C++14 mode or later. This can result in initialization changing from dynamic to static and other optimizations. -fno-implicit-templates Never emit code for non-inline templates that are instantiated implic- itly (i.e. by use); only emit code for explicit instantiations. If you use this option, you must take care to structure your code to include all the necessary explicit instantiations to avoid getting undefined symbols at link time. -fno-implicit-inline-templates Don't emit code for implicit instantiations of inline templates, ei- ther. The default is to handle inlines differently so that compiles with and without optimization need the same set of explicit instantia- tions. -fno-implement-inlines To save space, do not emit out-of-line copies of inline functions con- trolled by "#pragma implementation". This causes linker errors if these functions are not inlined everywhere they are called. -fmodules -fno-modules Enable support for C++20 modules. The -fno-modules is usually not needed, as that is the default. Even though this is a C++20 feature, it is not currently implicitly enabled by selecting that standard ver- sion. -fmodule-header -fmodule-header=user -fmodule-header=system Compile a header file to create an importable header unit. -fmodule-implicit-inline Member functions defined in their class definitions are not implicitly inline for modular code. This is different to traditional C++ behav- ior, for good reasons. However, it may result in a difficulty during code porting. This option makes such function definitions implicitly inline. It does however generate an ABI incompatibility, so you must use it everywhere or nowhere. (Such definitions outside of a named module remain implicitly inline, regardless.) -fno-module-lazy Disable lazy module importing and module mapper creation. -fmodule-mapper=[hostname]:port[?ident] -fmodule-mapper=|program[?ident] args... -fmodule-mapper==socket[?ident] -fmodule-mapper=<>[inout][?ident] -fmodule-mapper=<in>out[?ident] -fmodule-mapper=file[?ident] An oracle to query for module name to filename mappings. If unspeci- fied the CXX_MODULE_MAPPER environment variable is used, and if that is unset, an in-process default is provided. -fmodule-only Only emit the Compiled Module Interface, inhibiting any object file. -fms-extensions Disable Wpedantic warnings about constructs used in MFC, such as im- plicit int and getting a pointer to member function via non-standard syntax. -fnew-inheriting-ctors Enable the P0136 adjustment to the semantics of C++11 constructor in- heritance. This is part of C++17 but also considered to be a Defect Report against C++11 and C++14. This flag is enabled by default unless -fabi-version=10 or lower is specified. -fnew-ttp-matching Enable the P0522 resolution to Core issue 150, template template para- meters and default arguments: this allows a template with default tem- plate arguments as an argument for a template template parameter with fewer template parameters. This flag is enabled by default for -std=c++17. -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. -fnothrow-opt Treat a throw() exception specification as if it were a "noexcept" specification to reduce or eliminate the text size overhead relative to a function with no exception specification. If the function has local variables of types with non-trivial destructors, the exception specifi- cation actually makes the function smaller because the EH cleanups for those variables can be optimized away. The semantic effect is that an exception thrown out of a function with such an exception specification results in a call to "terminate" rather than "unexpected". -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. -fno-pretty-templates When an error message refers to a specialization of a function tem- plate, the compiler normally prints the signature of the template fol- lowed by the template arguments and any typedefs or typenames in the signature (e.g. "void f(T) [with T = int]" rather than "void f(int)") so that it's clear which template is involved. When an error message refers to a specialization of a class template, the compiler omits any template arguments that match the default template arguments for that template. If either of these behaviors make it harder to understand the error message rather than easier, you can use -fno-pretty-templates to disable them. -frange-for-ext-temps Enable lifetime extension of C++ range based for temporaries. With -std=c++23 and above this is part of the language standard, so lifetime of the temporaries is extended until the end of the loop by default. This option allows enabling that behavior also in earlier versions of the standard. -freflection Enable experimental C++26 Reflection. -fno-rtti Disable generation of information about every class with virtual func- tions for use by the C++ run-time type identification features ("dy- namic_cast" and "typeid"). If you don't use those parts of the lan- guage, you can save some space by using this flag. Note that exception handling uses the same information, but G++ generates it as needed. The "dynamic_cast" operator can still be used for casts that do not require run-time type information, i.e. casts to "void *" or to unambiguous base classes. Mixing code compiled with -frtti with that compiled with -fno-rtti may not work. For example, programs may fail to link if a class compiled with -fno-rtti is used as a base for a class compiled with -frtti. -fsized-deallocation Enable the built-in global declarations void operator delete (void *, std::size_t) noexcept; void operator delete[] (void *, std::size_t) noexcept; as introduced in C++14. This is useful for user-defined replacement deallocation functions that, for example, use the size of the object to make deallocation faster. Enabled by default under -std=c++14 and above. The flag -Wsized-deallocation warns about places that might want to add a definition. -fstrict-enums Allow the compiler to optimize using the assumption that a value of enumerated type can only be one of the values of the enumeration (as defined in the C++ standard; basically, a value that can be represented in the minimum number of bits needed to represent all the enumerators). This assumption may not be valid if the program uses a cast to convert an arbitrary integer value to the enumerated type. This option has no effect for an enumeration type with a fixed underlying type. -fstrong-eval-order -fstrong-eval-order=kind Evaluate member access, array subscripting, and shift expressions in left-to-right order, and evaluate assignment in right-to-left order, as adopted for C++17. -fstrong-eval-order is equivalent to -fstrong-eval-order=all, and is enabled by default with -std=c++17 or later. -fstrong-eval-order=some enables just the ordering of member access and shift expressions, and is the default for C++ dialects prior to C++17. -fstrong-eval-order=none is equivalent to -fno-strong-eval-order. -ftemplate-backtrace-limit=n Set the maximum number of template instantiation notes for a single warning or error to n. The default value is 10. -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 recur- sions during template class instantiation. ANSI/ISO C++ conforming programs must not rely on a maximum depth greater than 17 (changed to 1024 in C++11). The default value is 900, as the compiler can run out of stack space before hitting 1024 in some situations. -fno-threadsafe-statics Do not emit the extra code to use the routines specified in the C++ ABI for thread-safe initialization of local statics. You can use this op- tion to reduce code size slightly in code that doesn't need to be thread-safe. -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 destruc- tors, but only works if your C library supports "__cxa_atexit". -fno-use-cxa-get-exception-ptr Don't use the "__cxa_get_exception_ptr" runtime routine. This causes "std::uncaught_exception" to be incorrect, but is necessary if the run- time routine is not available. -fvisibility-inlines-hidden This switch declares that the user does not attempt to compare pointers to inline functions or methods where the addresses of the two functions are taken in different shared objects. The effect of this is that GCC may, effectively, mark inline methods with "__attribute__ ((visibility ("hidden")))" so that they do not ap- pear in the export table of a DSO and do not require a PLT indirection when used within the DSO. Enabling this option can have a dramatic ef- fect on load and link times of a DSO as it massively reduces the size of the dynamic export table when the library makes heavy use of tem- plates. The behavior of this switch is not quite the same as marking the meth- ods as hidden directly, because it does not affect static variables lo- cal to the function or cause the compiler to deduce that the function is defined in only one shared object. You may mark a method as having a visibility explicitly to negate the effect of the switch for that method. For example, if you do want to compare pointers to a particular inline method, you might mark it as having default visibility. Marking the enclosing class with explicit visibility has no effect. Explicitly instantiated inline methods are unaffected by this option as their linkage might otherwise cross a shared library boundary. -fvisibility-ms-compat This flag attempts to use visibility settings to make GCC's C++ linkage model compatible with that of Microsoft Visual Studio. The flag makes these changes to GCC's linkage model: 1. It sets the default visibility to "hidden", like -fvisibility=hid- den. 2. Types, but not their members, are not hidden by default. 3. The One Definition Rule is relaxed for types without explicit visi- bility specifications that are defined in more than one shared ob- ject: those declarations are permitted if they are permitted when this option is not used. In new code it is better to use -fvisibility=hidden and export those classes that are intended to be externally visible. Unfortunately it is possible for code to rely, perhaps accidentally, on the Visual Stu- dio behavior. Among the consequences of these changes are that static data members of the same type with the same name but defined in different shared ob- jects are different, so changing one does not change the other; and that pointers to function members defined in different shared objects may not compare equal. When this flag is given, it is a violation of the ODR to define types with the same name differently. -fno-weak Do not use weak symbol support, even if it is provided by the linker. By default, G++ uses weak symbols if they are available. This option exists only for testing, and should not be used by end-users; it re- sults in inferior code and has no benefits. This option may be removed in a future release of G++. -fext-numeric-literals (C++ and Objective-C++ only) Accept imaginary, fixed-point, or machine-defined literal number suf- fixes as GNU extensions. When this option is turned off these suffixes are treated as C++11 user-defined literal numeric suffixes. This is on by default for all pre-C++11 dialects and all GNU dialects: -std=c++98, -std=gnu++98, -std=gnu++11, -std=gnu++14. This option is off by de- fault for ISO C++11 onwards (-std=c++11, ...). -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.) -flang-info-include-translate -flang-info-include-translate-not -flang-info-include-translate=header Inform of include translation events. The first will note accepted in- clude translations, the second will note declined include translations. The header form will inform of include translations relating to that specific header. If header is of the form "user" or "<system>" it will be resolved to a specific user or system header using the include path. -flang-info-module-cmi -flang-info-module-cmi=module Inform of Compiled Module Interface pathnames. The first will note all read CMI pathnames. The module form will note reading a specific mod- ule's CMI. module may be a named module or a header-unit (the latter indicated by either being a pathname containing directory separators or enclosed in "<>" or ""). -stdlib=libstdc++,libc++ When G++ is configured to support this option, it allows specification of alternate C++ runtime libraries. Two options are available: lib- stdc++ (the default, native C++ runtime for G++) and libc++ which is the C++ runtime installed on some operating systems (e.g. Darwin ver- sions from Darwin11 onwards). The option switches G++ to use the head- ers from the specified library and to emit "-lstdc++" or "-lc++" re- spectively, when a C++ runtime is required for linking. In addition, these warning options have meanings only for C++ programs: -Wabi-tag (C++ and Objective-C++ only) Warn when a type with an ABI tag is used in a context that does not have that ABI tag. See C++ Attributes for more information about ABI tags. -Wno-abbreviated-auto-in-template-arg Disable the error for an "auto" placeholder type used within a template argument list to declare a C++20 abbreviated function template, e.g. void f(S<auto>); This feature was proposed in the Concepts TS, but was not adopted into C++20; in the standard, a placeholder in a parameter declaration must appear as a decl-specifier. The error can also be reduced to a warning by -fpermissive or -Wno-error=abbreviated-auto-in-template-arg. -Wcomma-subscript (C++ and Objective-C++ only) Warn about uses of a comma expression within a subscripting expression. This usage was deprecated in C++20 and is going to be removed in C++23. However, a comma expression wrapped in "( )" is not deprecated. Exam- ple: void f(int *a, int b, int c) { a[b,c]; // deprecated in C++20, invalid in C++23 a[(b,c)]; // OK } In C++23 it is valid to have comma separated expressions in a subscript when an overloaded subscript operator is found and supports the right number and types of arguments. G++ will accept the formerly valid syn- tax for code that is not valid in C++23 but used to be valid but depre- cated in C++20 with a pedantic warning that can be disabled with -Wno-comma-subscript. Enabled by default with -std=c++20 unless -Wno-deprecated, and after -std=c++23 regardless of -Wno-deprecated. Before -std=c++20, enabled with explicit -Wdeprecated. This warning is upgraded to an error by -pedantic-errors in C++23 mode or later. -Wctad-maybe-unsupported (C++ and Objective-C++ only) Warn when performing class template argument deduction (CTAD) on a type with no explicitly written deduction guides. This warning will point out cases where CTAD succeeded only because the compiler synthesized the implicit deduction guides, which might not be what the programmer intended. Certain style guides allow CTAD only on types that specifi- cally "opt-in"; i.e., on types that are designed to support CTAD. This warning can be suppressed with the following pattern: struct allow_ctad_t; // any name works template <typename T> struct S { S(T) { } }; // Guide with incomplete parameter type will never be considered. S(allow_ctad_t) -> S<void>; -Wctor-dtor-privacy (C++ and Objective-C++ only) Warn when a class seems unusable because all the constructors or de- structors in that class are private, and it has neither friends nor public static member functions. Also warn if there are no non-private methods, and there's at least one private member function that isn't a constructor or destructor. -Wdangling-reference (C++ and Objective-C++ only) Warn when a reference is bound to a temporary whose lifetime has ended. For example: int n = 1; const int& r = std::max(n - 1, n + 1); // r is dangling In the example above, two temporaries are created, one for each argu- ment, and a reference to one of the temporaries is returned. However, both temporaries are destroyed at the end of the full expression, so the reference "r" is dangling. This warning also detects dangling ref- erences in member initializer lists: const int& f(const int& i) { return i; } struct S { const int &r; // r is dangling S() : r(f(10)) { } }; Member functions are checked as well, but only their object argument: struct S { const S& self () { return *this; } }; const S& s = S().self(); // s is dangling Certain functions are safe in this respect, for example "std::use_facet": they take and return a reference, but they don't re- turn one of its arguments, which can fool the warning. Such functions can be excluded from the warning by wrapping them in a "#pragma": #pragma GCC diagnostic push #pragma GCC diagnostic ignored "-Wdangling-reference" const T& foo (const T&) { ... } #pragma GCC diagnostic pop The "#pragma" can also surround the class; in that case, the warning will be disabled for all the member functions. -Wdangling-reference also warns about code like auto p = std::minmax(1, 2); where "std::minmax" returns "std::pair<const int&, const int&>", and both references dangle after the end of the full expression that con- tains the call to "std::minmax". The warning does not warn for "std::span"-like classes. We consider classes of the form: template<typename T> struct Span { T* data_; std::size len_; }; as "std::span"-like; that is, the class is a non-union class that has a pointer data member and a trivial destructor. The warning can be disabled by using the "gnu::no_dangling" attribute. This warning is enabled by -Wextra. -Wdelete-non-virtual-dtor (C++ and Objective-C++ only) Warn when "delete" is used to destroy an instance of a class that has virtual functions and non-virtual destructor. It is unsafe to delete an instance of a derived class through a pointer to a base class if the base class does not have a virtual destructor. This warning is enabled by -Wall. -Wdeprecated-copy (C++ and Objective-C++ only) Warn that the implicit declaration of a copy constructor or copy as- signment operator is deprecated if the class has a user-provided copy constructor or copy assignment operator, in C++11 and up. This warning is enabled by -Wextra. -Wdeprecated-copy-dtor (C++ and Objective-C++ only) Similar to -Wdeprecated-copy, but also deprecate if the class has a user-provided destructor. -Wno-deprecated-enum-enum-conversion (C++ and Objective-C++ only) Disable the warning about the case when the usual arithmetic conver- sions are applied on operands where one is of enumeration type and the other is of a different enumeration type. This conversion was depre- cated in C++20. For example: enum E1 { e }; enum E2 { f }; int k = f - e; -Wdeprecated-enum-enum-conversion is enabled by default with -std=c++20. In pre-C++20 dialects, this warning can be enabled by -Wenum-conversion or -Wdeprecated. -Wno-deprecated-enum-float-conversion (C++ and Objective-C++ only) Disable the warning about the case when the usual arithmetic conver- sions are applied on operands where one is of enumeration type and the other is of a floating-point type. This conversion was deprecated in C++20. For example: enum E1 { e }; enum E2 { f }; bool b = e <= 3.7; -Wdeprecated-enum-float-conversion is enabled by default with -std=c++20. In pre-C++20 dialects, this warning can be enabled by -Wenum-conversion or -Wdeprecated. -Wdeprecated-literal-operator (C++ and Objective-C++ only) Warn that the declaration of a user-defined literal operator with a space before the suffix is deprecated. This warning is enabled by de- fault in C++23, or with explicit -Wdeprecated. string operator "" _i18n(const char*, std::size_t); // deprecated string operator ""_i18n(const char*, std::size_t); // preferred -Wdeprecated-variadic-comma-omission (C++ and Objective-C++ only) Warn that omitting a comma before the varargs "..." at the end of a function parameter list is deprecated. This warning is enabled by de- fault in C++26, or with explicit -Wdeprecated. void f1(int...); // deprecated void f1(int, ...); // preferred template <typename ...T> void f2(T...); // ok template <typename ...T> void f3(T......); // deprecated -Wno-elaborated-enum-base For C++11 and above, warn if an (invalid) additional enum-base is used in an elaborated-type-specifier. That is, if an enum with given under- lying type and no enumerator list is used in a declaration other than just a standalone declaration of the enum. Enabled by default. This warning is upgraded to an error with -pedantic-errors. -Wno-init-list-lifetime (C++ and Objective-C++ only) Do not warn about uses of "std::initializer_list" that are likely to result in dangling pointers. Since the underlying array for an "ini- tializer_list" is handled like a normal C++ temporary object, it is easy to inadvertently keep a pointer to the array past the end of the array's lifetime. For example: * If a function returns a temporary "initializer_list", or a local "initializer_list" variable, the array's lifetime ends at the end of the return statement, so the value returned has a dangling pointer. * If a new-expression creates an "initializer_list", the array only lives until the end of the enclosing full-expression, so the "ini- tializer_list" in the heap has a dangling pointer. * When an "initializer_list" variable is assigned from a brace-en- closed initializer list, the temporary array created for the right side of the assignment only lives until the end of the full-expres- sion, so at the next statement the "initializer_list" variable has a dangling pointer. // li's initial underlying array lives as long as li std::initializer_list<int> li = { 1,2,3 }; // assignment changes li to point to a temporary array li = { 4, 5 }; // now the temporary is gone and li has a dangling pointer int i = li.begin()[0] // undefined behavior * When a list constructor stores the "begin" pointer from the "ini- tializer_list" argument, this doesn't extend the lifetime of the array, so if a class variable is constructed from a temporary "ini- tializer_list", the pointer is left dangling by the end of the variable declaration statement. -Winvalid-constexpr Warn when a function never produces a constant expression. In C++20 and earlier, for every "constexpr" function and function template, there must be at least one set of function arguments in at least one instantiation such that an invocation of the function or constructor could be an evaluated subexpression of a core constant expression. C++23 removed this restriction, so it's possible to have a function or a function template marked "constexpr" for which no invocation satis- fies the requirements of a core constant expression. This warning is enabled as a pedantic warning by default in C++20 and earlier. In C++23, -Winvalid-constexpr can be turned on, in which case it will be an ordinary warning. For example: void f (int& i); constexpr void g (int& i) { // Warns by default in C++20, in C++23 only with -Winvalid-constexpr. f(i); } -Winvalid-imported-macros Verify all imported macro definitions are valid at the end of compila- tion. This is not enabled by default, as it requires additional pro- cessing to determine. It may be useful when preparing sets of header-units to ensure consistent macros. -Wno-literal-suffix (C++ and Objective-C++ only) Do not warn when a string or character literal is followed by a ud-suf- fix which does not begin with an underscore. As a conforming exten- sion, GCC treats such suffixes as separate preprocessing tokens in or- der to maintain backwards compatibility with code that uses formatting macros from "<inttypes.h>". For example: #define __STDC_FORMAT_MACROS #include <inttypes.h> #include <stdio.h> int main() { int64_t i64 = 123; printf("My int64: %" PRId64"\n", i64); } In this case, "PRId64" is treated as a separate preprocessing token. This option also controls warnings when a user-defined literal operator is declared with a literal suffix identifier that doesn't begin with an underscore. Literal suffix identifiers that don't begin with an under- score are reserved for future standardization. These warnings are enabled by default. -Wno-narrowing (C++ and Objective-C++ only) For C++11 and later standards, narrowing conversions are diagnosed by default, as required by the standard. A narrowing conversion from a constant produces an error, and a narrowing conversion from a non-con- stant produces a warning, but -Wno-narrowing suppresses the diagnostic. Note that this does not affect the meaning of well-formed code; narrow- ing conversions are still considered ill-formed in SFINAE contexts. With -Wnarrowing in C++98, warn when a narrowing conversion prohibited by C++11 occurs within { }, e.g. int i = { 2.2 }; // error: narrowing from double to int This flag is included in -Wall and -Wc++11-compat. -Wnoexcept (C++ and Objective-C++ only) Warn when a noexcept-expression evaluates to false because of a call to a function that does not have a non-throwing exception specification (i.e. throw() or "noexcept") but is known by the compiler to never throw an exception. -Wnoexcept-type (C++ and Objective-C++ only) Warn if the C++17 feature making "noexcept" part of a function type changes the mangled name of a symbol relative to C++14. Enabled by -Wabi and -Wc++17-compat. As an example: template <class T> void f(T t) { t(); }; void g() noexcept; void h() { f(g); } In C++14, "f" calls "f<void(*)()>", but in C++17 it calls "f<void(*)()noexcept>". -Wclass-memaccess (C++ and Objective-C++ only) Warn when the destination of a call to a raw memory function such as "memset" or "memcpy" is an object of class type, and when writing into such an object might bypass the class non-trivial or deleted construc- tor or copy assignment, violate const-correctness or encapsulation, or corrupt virtual table pointers. Modifying the representation of such objects may violate invariants maintained by member functions of the class. For example, the call to "memset" below is undefined because it modifies a non-trivial class object and is, therefore, diagnosed. The safe way to either initialize or clear the storage of objects of such types is by using the appropriate constructor or assignment operator, if one is available. std::string str = "abc"; memset (&str, 0, sizeof str); The -Wclass-memaccess option is enabled by -Wall. Explicitly casting the pointer to the class object to "void *" or to a type that can be safely accessed by the raw memory function suppresses the warning. -Wnon-virtual-dtor (C++ and Objective-C++ only) Warn when a class has virtual functions and an accessible non-virtual destructor itself or in an accessible polymorphic base class, in which case it is possible but unsafe to delete an instance of a derived class through a pointer to the class itself or base class. This warning is automatically enabled if -Weffc++ is specified. The -Wdelete-non-vir- tual-dtor option (enabled by -Wall) should be preferred because it warns about the unsafe cases without false positives. -Wregister (C++ and Objective-C++ only) Warn on uses of the "register" storage class specifier, except when it is part of the GNU Explicit Register Variables extension. The use of the "register" keyword as storage class specifier has been deprecated in C++11 and removed in C++17. Enabled by default with -std=c++17. -Wreorder (C++ and Objective-C++ 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: struct A { int i; int j; A(): j (0), i (1) { } }; The compiler rearranges the member initializers for "i" and "j" to match the declaration order of the members, emitting a warning to that effect. This warning is enabled by -Wall. -Wno-pessimizing-move (C++ and Objective-C++ only) This warning warns when a call to "std::move" prevents copy elision. A typical scenario when copy elision can occur is when returning in a function with a class return type, when the expression being returned is the name of a non-volatile automatic object, and is not a function parameter, and has the same type as the function return type. struct T { ... }; T fn() { T t; ... return std::move (t); } But in this example, the "std::move" call prevents copy elision. This warning is enabled by -Wall. -Wno-redundant-move (C++ and Objective-C++ only) This warning warns about redundant calls to "std::move"; that is, when a move operation would have been performed even without the "std::move" call. This happens because the compiler is forced to treat the object as if it were an rvalue in certain situations such as returning a local variable, where copy elision isn't applicable. Consider: struct T { ... }; T fn(T t) { ... return std::move (t); } Here, the "std::move" call is redundant. Because G++ implements Core Issue 1579, another example is: struct T { // convertible to U ... }; struct U { ... }; U fn() { T t; ... return std::move (t); } In this example, copy elision isn't applicable because the type of the expression being returned and the function return type differ, yet G++ treats the return value as if it were designated by an rvalue. This warning is enabled by -Wextra. -Wrange-loop-construct (C++ and Objective-C++ only) This warning warns when a C++ range-based for-loop is creating an un- necessary copy. This can happen when the range declaration is not a reference, but probably should be. For example: struct S { char arr[128]; }; void fn () { S arr[5]; for (const auto x : arr) { ... } } It does not warn when the type being copied is a trivially-copyable type whose size is less than 64 bytes. This warning also warns when a loop variable in a range-based for-loop is initialized with a value of a different type resulting in a copy. For example: void fn() { int arr[10]; for (const double &x : arr) { ... } } In the example above, in every iteration of the loop a temporary value of type "double" is created and destroyed, to which the reference "const double &" is bound. This warning is enabled by -Wall. -Wredundant-tags (C++ and Objective-C++ only) Warn about redundant class-key and enum-key in references to class types and enumerated types in contexts where the key can be eliminated without causing an ambiguity. For example: struct foo; struct foo *p; // warn that keyword struct can be eliminated On the other hand, in this example there is no warning: struct foo; void foo (); // "hides" struct foo void bar (struct foo&); // no warning, keyword struct is necessary -Wno-subobject-linkage (C++ and Objective-C++ only) Do not warn if a class type has a base or a field whose type uses the anonymous namespace or depends on a type with no linkage. If a type A depends on a type B with no or internal linkage, defining it in multi- ple translation units would be an ODR violation because the meaning of B is different in each translation unit. If A only appears in a single translation unit, the best way to silence the warning is to give it in- ternal linkage by putting it in an anonymous namespace as well. The compiler doesn't give this warning for types defined in the main .C file, as those are unlikely to have multiple definitions. -Wsubob- ject-linkage is enabled by default. -Weffc++ (C++ and Objective-C++ only) Warn about violations of the following style guidelines from Scott Mey- ers' Effective C++ series of books: * Define a copy constructor and an assignment operator for classes with dynamically-allocated memory. * Prefer initialization to assignment in constructors. * Have "operator=" return a reference to *this. * Don't try to return a reference when you must return an object. * Distinguish between prefix and postfix forms of increment and decrement operators. * Never overload "&&", "||", or ",". This option also enables -Wnon-virtual-dtor, which is also one of the effective C++ recommendations. However, the check is extended to warn about the lack of virtual destructor in accessible non-polymorphic bases classes too. When selecting this option, be aware that the standard library headers do not obey all of these guidelines; use grep -v to filter out those warnings. -Wno-exceptions (C++ and Objective-C++ only) Disable the warning about the case when an exception handler is shad- owed by another handler, which can point out a wrong ordering of excep- tion handlers. -Wsfinae-incomplete (C++ and Objective-C++ only) Warn about a class that is found to be incomplete, or a function with auto return type that has not yet been deduced, in a context where that causes substitution failure rather than an error, and then the class or function is defined later in the translation unit. This is problematic because template instantiations or concept checks could have different results if they first occur either before or after the definition. This warning is enabled by default. -Wsfinae-incomplete=2 adds a warn- ing at the point of substitution failure, to make it easier to track down problems flagged by the default mode. -Wstrict-null-sentinel (C++ and Objective-C++ only) Warn about the use of an uncasted "NULL" as sentinel. When compiling only with GCC this is a valid sentinel, as "NULL" is defined to "__null". Although it is a null pointer constant rather than a null pointer, it is guaranteed to be of the same size as a pointer. But this use is not portable across different compilers. -Wno-non-c-typedef-for-linkage (C++ and Objective-C++ only) Disable pedwarn for unnamed classes with a typedef name for linkage purposes containing C++ specific members, base classes, default member initializers or lambda expressions, including those on nested member classes. typedef struct { int a; // non-static data members are ok struct T { int b; }; // member classes too enum E { E1, E2, E3 }; // member enumerations as well int c = 42; // default member initializers are not ok struct U : A { int c; }; // classes with base classes are not ok typedef int V; // typedef is not ok using W = int; // using declaration is not ok decltype([](){}) x; // lambda expressions not ok } S; In all these cases, the tag name S should be added after the struct keyword. -Wno-non-template-friend (C++ and Objective-C++ only) Disable warnings when non-template friend functions are declared within a template. In very old versions of GCC that predate implementation of the ISO standard, declarations such as friend int foo(int), where the name of the friend is an unqualified-id, could be interpreted as a par- ticular specialization of a template function; the warning exists to diagnose compatibility problems, and is enabled by default. -Wold-style-cast (C++ and Objective-C++ only) Warn if an old-style (C-style) cast to a non-void type is used within a C++ program. The new-style casts ("dynamic_cast", "static_cast", "reinterpret_cast", and "const_cast") are less vulnerable to unintended effects and much easier to search for. -Woverloaded-virtual (C++ and Objective-C++ only) -Woverloaded-virtual=n Warn when a function declaration hides virtual functions from a base class. For example, in: struct A { virtual void f(); }; struct B: public A { void f(int); // does not override }; the "A" class version of "f" is hidden in "B", and code like: B* b; b->f(); fails to compile. In cases where the different signatures are not an accident, the sim- plest solution is to add a using-declaration to the derived class to un-hide the base function, e.g. add "using A::f;" to "B". The optional level suffix controls the behavior when all the declara- tions in the derived class override virtual functions in the base class, even if not all of the base functions are overridden: struct C { virtual void f(); virtual void f(int); }; struct D: public C { void f(int); // does override } This pattern is less likely to be a mistake; if D is only used virtu- ally, the user might have decided that the base class semantics for some of the overloads are fine. At level 1, this case does not warn; at level 2, it does. -Wover- loaded-virtual by itself selects level 2. Level 1 is included in -Wall. -Wno-pmf-conversions (C++ and Objective-C++ only) Disable the diagnostic for converting a bound pointer to member func- tion to a plain pointer. -Wsign-promo (C++ and Objective-C++ only) Warn when overload resolution chooses a promotion from unsigned or enu- merated type to a signed type, over a conversion to an unsigned type of the same size. Previous versions of G++ tried to preserve unsigned- ness, but the standard mandates the current behavior. -Wtemplates (C++ and Objective-C++ only) Warn when a primary template declaration is encountered. Some coding rules disallow templates, and this may be used to enforce that rule. The warning is inactive inside a system header file, such as the STL, so one can still use the STL. One may also instantiate or specialize templates. -Wmismatched-new-delete (C++ and Objective-C++ only) Warn for mismatches between calls to "operator new" or "operator delete" and the corresponding call to the allocation or deallocation function. This includes invocations of C++ "operator delete" with pointers returned from either mismatched forms of "operator new", or from other functions that allocate objects for which the "operator delete" isn't a suitable deallocator, as well as calls to other deallo- cation functions with pointers returned from "operator new" for which the deallocation function isn't suitable. For example, the "delete" expression in the function below is diagnosed because it doesn't match the array form of the "new" expression the pointer argument was returned from. Similarly, the call to "free" is also diagnosed. void f () { int *a = new int[n]; delete a; // warning: mismatch in array forms of expressions char *p = new char[n]; free (p); // warning: mismatch between new and free } The related option -Wmismatched-dealloc diagnoses mismatches involving allocation and deallocation functions other than "operator new" and "operator delete". -Wmismatched-new-delete is included in -Wall. -Wmismatched-tags (C++ and Objective-C++ only) Warn for declarations of structs, classes, and class templates and their specializations with a class-key that does not match either the definition or the first declaration if no definition is provided. For example, the declaration of "struct Object" in the argument list of "draw" triggers the warning. To avoid it, either remove the redundant class-key "struct" or replace it with "class" to match its definition. class Object { public: virtual ~Object () = 0; }; void draw (struct Object*); It is not wrong to declare a class with the class-key "struct" as the example above shows. The -Wmismatched-tags option is intended to help achieve a consistent style of class declarations. In code that is in- tended to be portable to Windows-based compilers the warning helps pre- vent unresolved references due to the difference in the mangling of symbols declared with different class-keys. The option can be used ei- ther on its own or in conjunction with -Wredundant-tags. -Wmultiple-inheritance (C++ and Objective-C++ only) Warn when a class is defined with multiple direct base classes. Some coding rules disallow multiple inheritance, and this may be used to en- force that rule. The warning is inactive inside a system header file, such as the STL, so one can still use the STL. One may also define classes that indirectly use multiple inheritance. -Wvirtual-inheritance Warn when a class is defined with a virtual direct base class. Some coding rules disallow multiple inheritance, and this may be used to en- force that rule. The warning is inactive inside a system header file, such as the STL, so one can still use the STL. One may also define classes that indirectly use virtual inheritance. -Wno-virtual-move-assign Suppress warnings about inheriting from a virtual base with a non-triv- ial C++11 move assignment operator. This is dangerous because if the virtual base is reachable along more than one path, it is moved multi- ple times, which can mean both objects end up in the moved-from state. If the move assignment operator is written to avoid moving from a moved-from object, this warning can be disabled. -Wnamespaces Warn when a namespace definition is opened. Some coding rules disallow namespaces, and this may be used to enforce that rule. The warning is inactive inside a system header file, such as the STL, so one can still use the STL. One may also use using directives and qualified names. -Wno-template-body (C++ and Objective-C++ only) Disable diagnosing errors when parsing a template, and instead issue an error only upon instantiation of the template. This flag can also be used to downgrade such errors into warnings with Wno-error= or -fper- missive. -Wno-template-id-cdtor (C++ and Objective-C++ only) Disable the warning about the use of simple-template-id as the declara- tor-id of a constructor or destructor, which became invalid in C++20 via DR 2237. For example: template<typename T> struct S { S<T>(); // should be S(); ~S<T>(); // should be ~S(); }; -Wtemplate-id-cdtor is enabled by default with -std=c++20; it is also enabled by -Wc++20-compat. -Wtemplate-names-tu-local Warn when a template body hides an exposure of a translation-unit-local entity. In most cases, referring to a translation-unit-local entity (such as an internal linkage declaration) within an entity that is emitted into a module's CMI is an error. However, within the initial- izer of a variable, or in the body of a non-inline function, this is not an exposure and no error is emitted. This can cause variable or function templates to accidentally become unusable if they reference such an entity, because other translation units that import the template will never be able to instantiate it. This warning attempts to detect cases where this might occur. The presence of an explicit instantiation silences the warning. This flag is enabled by -Wextra. -Wno-expose-global-module-tu-local An exposure of a translation-unit-local entity from a module interface is invalid, as this may cause ODR violations and manifest in link er- rors or other unexpected behaviour. However, many existing libraries declare TU-local entities in their interface, and avoiding exposures of these entities may be difficult in some cases. As an extension, GCC allows exposures of internal variables and func- tions that were declared in the global module fragment. This warning indicates when such an invalid exposure has occurred, and can be si- lenced using diagnostic pragmas either at the site of the exposure, or at the point of declaration of the internal declaration. This also ap- plies to "export using" declarations naming such entities. When combined with -Wtemplate-names-tu-local, GCC will also warn about non-exposure references to TU-local entities in template bodies. Such templates can still be instantiated in other TUs but the above risks regarding exposures of translation-unit-local entities apply. This warning is enabled by default, and is upgraded to an error by -pedantic-errors. -Wno-external-tu-local Warn when naming a TU-local entity outside of the translation unit it was declared in. Such declarations will be ignored during name lookup. This can occur when performing ADL from a template declared in the same TU as the internal function: export module M; template <typename T> void foo(T t) { bar(t); } struct S {} s; static void bar(S) {} // internal linkage // instantiating foo(s) from outside this TU can see ::bar, // but naming it there is ill-formed. This can be worked around by making "bar" attached to the global mod- ule, using "extern "C++"". This warning is enabled by default, and is upgraded to an error by -pedantic-errors. -Wno-terminate (C++ and Objective-C++ only) Disable the warning about a throw-expression that will immediately re- sult in a call to "terminate". -Wno-vexing-parse (C++ and Objective-C++ only) Warn about the most vexing parse syntactic ambiguity. This warns about the cases when a declaration looks like a variable definition, but the C++ language requires it to be interpreted as a function declaration. For instance: void f(double a) { int i(); // extern int i (void); int n(int(a)); // extern int n (int); } Another example: struct S { S(int); }; void f(double a) { S x(int(a)); // extern struct S x (int); S y(int()); // extern struct S y (int (*) (void)); S z(); // extern struct S z (void); } The warning will suggest options how to deal with such an ambiguity; e.g., it can suggest removing the parentheses or using braces instead. This warning is enabled by default. -Wno-class-conversion (C++ and Objective-C++ only) Do not warn when a conversion function converts an object to the same type, to a base class of that type, or to void; such a conversion func- tion will never be called. -Wvolatile (C++ and Objective-C++ only) Warn about deprecated uses of the "volatile" qualifier. This includes postfix and prefix "++" and "--" expressions of "volatile"-qualified types, using simple assignments where the left operand is a "volatile"-qualified non-class type for their value, compound assign- ments where the left operand is a "volatile"-qualified non-class type, "volatile"-qualified function return type, "volatile"-qualified parame- ter type, and structured bindings of a "volatile"-qualified type. This usage was deprecated in C++20. Enabled by default with -std=c++20. Before -std=c++20, enabled with explicit -Wdeprecated. -Waligned-new -Waligned-new=[none|global|all] Warn about a new-expression of a type that requires greater alignment than the alignof(std::max_align_t) but uses an allocation function without an explicit alignment parameter. This option is enabled by -Wall. Normally this only warns about global allocation functions, but -Waligned-new=all also warns about class member allocation functions. -Wno-placement-new -Wplacement-new=n Warn about placement new expressions with undefined behavior, such as constructing an object in a buffer that is smaller than the type of the object. For example, the placement new expression below is diagnosed because it attempts to construct an array of 64 integers in a buffer only 64 bytes large. char buf [64]; new (buf) int[64]; This warning is enabled by default. -Wplacement-new=1 This is the default warning level of -Wplacement-new. At this level the warning is not issued for some strictly undefined con- structs that GCC allows as extensions for compatibility with legacy code. For example, the following "new" expression is not diagnosed at this level even though it has undefined behavior according to the C++ standard because it writes past the end of the one-element array. struct S { int n, a[1]; }; S *s = (S *)malloc (sizeof *s + 31 * sizeof s->a[0]); new (s->a)int [32](); -Wplacement-new=2 At this level, in addition to diagnosing all the same constructs as at level 1, a diagnostic is also issued for placement new expres- sions that construct an object in the last member of structure whose type is an array of a single element and whose size is less than the size of the object being constructed. While the previous example would be diagnosed, the following construct makes use of the flexible member array extension to avoid the warning at level 2. struct S { int n, a[]; }; S *s = (S *)malloc (sizeof *s + 32 * sizeof s->a[0]); new (s->a)int [32](); -Wcatch-value -Wcatch-value=n (C++ and Objective-C++ only) Warn about catch handlers that do not catch via reference. With -Wcatch-value=1 (or -Wcatch-value for short) warn about polymorphic class types that are caught by value. With -Wcatch-value=2 warn about all class types that are caught by value. With -Wcatch-value=3 warn about all types that are not caught by reference. -Wcatch-value is en- abled by -Wall. -Wconditionally-supported (C++ and Objective-C++ only) Warn for conditionally-supported (C++11 [intro.defs]) constructs. -Wno-defaulted-function-deleted (C++ and Objective-C++ only) Warn when an explicitly defaulted function is deleted by the compiler. That can occur when the function's declared type does not match the type of the function that would have been implicitly declared. This warning is enabled by default. -Wno-delete-incomplete (C++ and Objective-C++ only) Do not warn when deleting a pointer to incomplete type, which may cause undefined behavior at runtime. This warning is enabled by default. -Wextra-semi (C++, Objective-C++ only) Warn about redundant semicolons. There are various contexts in which an extra semicolon can occur. One is a semicolon after in-class func- tion definitions, which is valid in all C++ dialects (and is never a pedwarn): struct S { void foo () {}; }; Another is an extra semicolon at namespace scope, which has been al- lowed since C++11 (therefore is a pedwarn in C++98): struct S { }; ; And yet another is an extra semicolon in class definitions, which has been allowed since C++11 (therefore is a pedwarn in C++98): struct S { int a; ; }; -Wno-global-module (C++ and Objective-C++ only) Disable the diagnostic for when the global module fragment of a module unit does not consist only of preprocessor directives. -Wno-inaccessible-base (C++, Objective-C++ only) This option controls warnings when a base class is inaccessible in a class derived from it due to ambiguity. The warning is enabled by de- fault. Note that the warning for ambiguous virtual bases is enabled by the -Wextra option. struct A { int a; }; struct B : A { }; struct C : B, A { }; -Wno-inherited-variadic-ctor Suppress warnings about use of C++11 inheriting constructors when the base class inherited from has a C variadic constructor; the warning is on by default because the ellipsis is not inherited. -Wno-invalid-offsetof (C++ and Objective-C++ only) Suppress warnings from applying the "offsetof" macro to a non-POD type. According to the 2014 ISO C++ standard, applying "offsetof" to a non-standard-layout type is undefined. In existing C++ implementa- tions, however, "offsetof" typically gives meaningful results. This flag is for users who are aware that they are writing nonportable code and who have deliberately chosen to ignore the warning about it. The restrictions on "offsetof" may be relaxed in a future version of the C++ standard. -Wsized-deallocation (C++ and Objective-C++ only) Warn about a definition of an unsized deallocation function void operator delete (void *) noexcept; void operator delete[] (void *) noexcept; without a definition of the corresponding sized deallocation function void operator delete (void *, std::size_t) noexcept; void operator delete[] (void *, std::size_t) noexcept; or vice versa. Enabled by -Wextra along with -fsized-deallocation. -Wsuggest-final-types Warn about types with virtual methods where code quality would be im- proved if the type were declared with the C++11 "final" specifier, or, if possible, declared in an anonymous namespace. This allows GCC to more aggressively devirtualize the polymorphic calls. This warning is more effective with link-time optimization, where the information about the class hierarchy graph is more complete. -Wsuggest-final-methods Warn about virtual methods where code quality would be improved if the method were declared with the C++11 "final" specifier, or, if possible, its type were declared in an anonymous namespace or with the "final" specifier. This warning is more effective with link-time optimization, where the information about the class hierarchy graph is more complete. It is recommended to first consider suggestions of -Wsuggest-fi- nal-types and then rebuild with new annotations. -Wsuggest-override Warn about overriding virtual functions that are not marked with the "override" keyword. -Wno-conversion-null (C++ and Objective-C++ only) Do not warn for conversions between "NULL" and non-pointer types. -Wconversion-null is enabled by default. Options Controlling Objective-C and Objective-C++ Dialects (NOTE: This manual does not describe the Objective-C and Objective-C++ lan- guages themselves. This section describes the command-line options that are only meaningful for Objective-C and Objective-C++ programs. You can also use most of the language-independent GNU compiler options. For example, you might compile a file some_class.m like this: gcc -g -fgnu-runtime -O -c some_class.m In this example, -fgnu-runtime is an option meant only for Objective-C and Objective-C++ programs; you can use the other options with any language supported by GCC. Note that since Objective-C is an extension of the C language, Objective-C compilations may also use options specific to the C front-end (e.g., -Wtra- ditional). Similarly, Objective-C++ compilations may use C++-specific op- tions (e.g., -Wabi). Here is a list of options that are only for compiling Objective-C and Ob- jective-C++ programs: -fconstant-string-class=class-name Use class-name as the name of the class to instantiate for each literal string specified with the syntax "@"..."". The default class name is "NXConstantString" if the GNU runtime is being used, and "NSCon- stantString" if the NeXT runtime is being used (see below). On Darwin / macOS platforms, the -fconstant-cfstrings option, if also present, overrides the -fconstant-string-class setting and cause "@"..."" liter- als to be laid out as constant CoreFoundation strings. Note that -fconstant-cfstrings is an alias for the target-specific -mconstant-cf- strings equivalent. -fgnu-runtime Generate object code compatible with the standard GNU Objective-C run- time. This is the default for most types of systems. -fnext-runtime Generate output compatible with the NeXT runtime. This is the default for NeXT-based systems, including Darwin / macOS. The macro "__NEXT_RUNTIME__" is predefined if (and only if) this option is used. -fno-nil-receivers Assume that all Objective-C message dispatches ("[receiver mes- sage:arg]") in this translation unit ensure that the receiver is not "nil". This allows for more efficient entry points in the runtime to be used. This option is only available in conjunction with the NeXT runtime and ABI version 0 or 1. -fobjc-abi-version=n Use version n of the Objective-C ABI for the selected runtime. This option is currently supported only for the NeXT runtime. In that case, Version 0 is the traditional (32-bit) ABI without support for proper- ties and other Objective-C 2.0 additions. Version 1 is the traditional (32-bit) ABI with support for properties and other Objective-C 2.0 ad- ditions. Version 2 is the modern (64-bit) ABI. If nothing is speci- fied, the default is Version 0 on 32-bit target machines, and Version 2 on 64-bit target machines. -fobjc-call-cxx-cdtors For each Objective-C class, check if any of its instance variables is a C++ object with a non-trivial default constructor. If so, synthesize a special "- (id) .cxx_construct" instance method which runs non-trivial default constructors on any such instance variables, in order, and then return "self". Similarly, check if any instance variable is a C++ ob- ject with a non-trivial destructor, and if so, synthesize a special "- (void) .cxx_destruct" method which runs all such default destructors, in reverse order. The "- (id) .cxx_construct" and "- (void) .cxx_destruct" methods thusly generated only operate on instance variables declared in the current Objective-C class, and not those inherited from superclasses. It is the responsibility of the Objective-C runtime to invoke all such meth- ods in an object's inheritance hierarchy. The "- (id) .cxx_construct" methods are invoked by the runtime immediately after a new object in- stance is allocated; the "- (void) .cxx_destruct" methods are invoked immediately before the runtime deallocates an object instance. As of this writing, only the NeXT runtime on Mac OS X 10.4 and later has support for invoking the "- (id) .cxx_construct" and "- (void) .cxx_destruct" methods. -fobjc-direct-dispatch Allow fast jumps to the message dispatcher. On Darwin this is accom- plished via the comm page. -fobjc-exceptions Enable syntactic support for structured exception handling in Objec- tive-C, similar to what is offered by C++. This option is required to use the Objective-C keywords @try, @throw, @catch, @finally and @syn- chronized. This option is available with both the GNU runtime and the NeXT runtime (but not available in conjunction with the NeXT runtime on Mac OS X 10.2 and earlier). -fobjc-gc Enable garbage collection (GC) in Objective-C and Objective-C++ pro- grams. This option is only available with the NeXT runtime; the GNU runtime has a different garbage collection implementation that does not require special compiler flags. -fobjc-nilcheck For the NeXT runtime with version 2 of the ABI, check for a nil re- ceiver in method invocations before doing the actual method call. This is the default and can be disabled using -fno-objc-nilcheck. Class methods and super calls are never checked for nil in this way no matter what this flag is set to. Currently this flag does nothing when the GNU runtime, or an older version of the NeXT runtime ABI, is used. -fobjc-std=objc1 Conform to the language syntax of Objective-C 1.0, the language recog- nized by GCC 4.0. This only affects the Objective-C additions to the C/C++ language; it does not affect conformance to C/C++ standards, which is controlled by the separate C/C++ dialect option flags. When this option is used with the Objective-C or Objective-C++ compiler, any Objective-C syntax that is not recognized by GCC 4.0 is rejected. This is useful if you need to make sure that your Objective-C code can be compiled with older versions of GCC. -freplace-objc-classes Emit a special marker instructing ld(1) not to statically link in the resulting object file, and allow dyld(1) to load it in at run time in- stead. This is used in conjunction with the Fix-and-Continue debugging mode, where the object file in question may be recompiled and dynami- cally reloaded in the course of program execution, without the need to restart the program itself. Currently, Fix-and-Continue functionality is only available in conjunction with the NeXT runtime on Mac OS X 10.3 and later. -fzero-link When compiling for the NeXT runtime, the compiler ordinarily replaces calls to objc_getClass("...") (when the name of the class is known at compile time) with static class references that get initialized at load time, which improves run-time performance. Specifying the -fzero-link flag suppresses this behavior and causes calls to objc_getClass("...") to be retained. This is useful in Zero-Link debugging mode, since it allows for individual class implementations to be modified during pro- gram execution. The GNU runtime currently always retains calls to objc_get_class("...") regardless of command-line options. -fno-local-ivars By default instance variables in Objective-C can be accessed as if they were local variables from within the methods of the class they're de- clared in. This can lead to shadowing between instance variables and other variables declared either locally inside a class method or glob- ally with the same name. Specifying the -fno-local-ivars flag disables this behavior thus avoiding variable shadowing issues. -fivar-visibility=[public|protected|private|package] Set the default instance variable visibility to the specified option so that instance variables declared outside the scope of any access modi- fier directives default to the specified visibility. -gen-decls Dump interface declarations for all classes seen in the source file to a file named sourcename.decl. -Wassign-intercept (Objective-C and Objective-C++ only) Warn whenever an Objective-C assignment is being intercepted by the garbage collector. -Wno-property-assign-default (Objective-C and Objective-C++ only) Do not warn if a property for an Objective-C object has no assign se- mantics specified. -Wno-protocol (Objective-C and Objective-C++ only) If a class is declared to implement a protocol, a warning is issued for every method in the protocol that is not implemented by the class. The default behavior is to issue a warning for every method not explicitly implemented in the class, even if a method implementation is inherited from the superclass. If you use the -Wno-protocol option, then methods inherited from the superclass are considered to be implemented, and no warning is issued for them. -Wobjc-root-class (Objective-C and Objective-C++ only) Warn if a class interface lacks a superclass. Most classes will inherit from "NSObject" (or "Object") for example. When declaring classes in- tended to be root classes, the warning can be suppressed by marking their interfaces with "__attribute__((objc_root_class))". -Wselector (Objective-C and Objective-C++ only) Warn if multiple methods of different types for the same selector are found during compilation. The check is performed on the list of meth- ods in the final stage of compilation. Additionally, a check is per- formed for each selector appearing in a @selector(...) expression, and a corresponding method for that selector has been found during compila- tion. Because these checks scan the method table only at the end of compilation, these warnings are not produced if the final stage of com- pilation is not reached, for example because an error is found during compilation, or because the -fsyntax-only option is being used. -Wstrict-selector-match (Objective-C and Objective-C++ only) Warn if multiple methods with differing argument and/or return types are found for a given selector when attempting to send a message using this selector to a receiver of type "id" or "Class". When this flag is off (which is the default behavior), the compiler omits such warnings if any differences found are confined to types that share the same size and alignment. -Wundeclared-selector (Objective-C and Objective-C++ only) Warn if a @selector(...) expression referring to an undeclared selector is found. A selector is considered undeclared if no method with that name has been declared before the @selector(...) expression, either ex- plicitly in an @interface or @protocol declaration, or implicitly in an @implementation section. This option always performs its checks as soon as a @selector(...) expression is found, while -Wselector only performs its checks in the final stage of compilation. This also en- forces the coding style convention that methods and selectors must be declared before being used. -print-objc-runtime-info Generate C header describing the largest structure that is passed by value, if any. Options Controlling OpenMP and OpenACC GCC supports OpenMP extensions to the C, C++, and Fortran languages with the -fopenmp option. Similarly, OpenACC extensions are supported in all three languages with -fopenacc. -foffload=disable -foffload=default -foffload=target-list Specify for which OpenMP and OpenACC offload targets code should be generated. The default behavior, equivalent to -foffload=default, is to generate code for all supported offload targets. The -foffload=dis- able form generates code only for the host fallback, while -fof- fload=target-list generates code only for the specified comma-separated list of offload targets. Offload targets are specified in GCC's internal target-triplet format. You can run the compiler with -v to show the list of configured offload targets under "OFFLOAD_TARGET_NAMES". -foffload-options=options -foffload-options=target-triplet-list=options With -foffload-options=options, GCC passes the specified options to the compilers for all enabled offloading targets. You can specify options that apply only to a specific target or targets by using the -fof- fload-options=target-list=options form. The target-list is a comma-separated list in the same format as for the -foffload= option. Typical command lines are -foffload-options='-fno-math-errno -ffinite-math-only' \ -foffload-options=nvptx-none=-latomic -foffload-options=amdgcn-amdhsa=-march=gfx906 -fopenacc Enable handling of OpenACC directives #pragma acc in C/C++ and !$acc in free-form Fortran and !$acc, c$acc and *$acc in fixed-form Fortran. This option implies -pthread, and thus is only supported on targets that have support for -pthread. -fopenacc-dim=geom Specify default compute dimensions for parallel offload regions that do not explicitly specify them. The geom value is a triple of :-separated sizes, in order gang, worker, and vector. A size can be omitted, to use a target-specific default value. -fopenmp Enable handling of OpenMP directives #pragma omp, [[omp::decl(...)]], [[omp::directive(...)]], and [[omp::sequence(...)]] in C/C++. In For- tran, it enables !$omp and the conditional compilation sentinel !$. In fixed source form Fortran, the sentinels can also start with c or *. This option implies -pthread, and thus is only supported on targets that have support for -pthread. -fopenmp implies -fopenmp-simd. -fopenmp-simd Enable handling of OpenMP's "simd", "declare simd", "declare reduc- tion", "assume", "ordered", "scan" and "loop" directive, and of com- bined or composite directives with "simd" as constituent with "#pragma omp", "[[omp::directive(...)]]", "[[omp::sequence(...)]]" and "[[omp::decl(...)]]" in C/C++ and "!$omp" in Fortran. It additionally enables the conditional compilation sentinel !$ in Fortran. In fixed source form Fortran, the sentinels can also start with c or *. Other OpenMP directives are ignored. Unless -fopenmp is additionally speci- fied, the "loop" region binds to the current task region, independent of the specified "bind" clause. -fopenmp-target-simd-clone -fopenmp-target-simd-clone=device-type In addition to generating SIMD clones for functions marked with the "declare simd" directive, GCC also generates clones for functions marked with the OpenMP "declare target" directive that are suitable for vectorization when this option is in effect. The device-type may be one of "none", "host", "nohost", and "any", which correspond to key- words for the "device_type" clause of the "declare target" directive; clones are generated for the intersection of devices specified. -fopenmp-target-simd-clone is equivalent to -fopenmp-tar- get-simd-clone=any and -fno-openmp-target-simd-clone is equivalent to -fopenmp-target-simd-clone=none. At -O2 and higher (but not -Os or -Og) this optimization defaults to -fopenmp-target-simd-clone=nohost; otherwise it is disabled by default. Options to Control Diagnostic Messages Formatting Traditionally, diagnostic messages have been formatted irrespective of the output device's aspect (e.g. its width, ...). You can use the options de- scribed below to control the formatting algorithm for diagnostic messages, e.g. how many characters per line, how often source location information should be reported. Note that some language front ends may not honor these options. -fmessage-length=n Try to format error messages so that they fit on lines of about n char- acters. If n is zero, then no line-wrapping is done; each error mes- sage appears on a single line. This is the default for all front ends. Note - this option also affects the display of the #error and #warning pre-processor directives, and the deprecated function/type/variable at- tribute. It does not however affect the pragma GCC warning and pragma GCC error pragmas. -fdiagnostics-plain-output This option requests that diagnostic output look as plain as possible, which may be useful when running dejagnu or other utilities that need to parse diagnostics output and prefer that it remain more stable over time. -fdiagnostics-plain-output is currently equivalent to the fol- lowing options: -fno-diagnostics-show-caret -fno-diagnos- tics-show-line-numbers -fdiagnostics-color=never -fdiagnos- tics-urls=never -fdiagnostics-path-format=separate-events -fdiagnos- tics-text-art-charset=none -fno-diagnostics-show-event-links -fno-diag- nostics-show-nesting In the future, if GCC changes the default appear- ance of its diagnostics, the corresponding option to disable the new behavior will be added to this list. -fdiagnostics-show-location=once Only meaningful in line-wrapping mode. Instructs the diagnostic mes- sages reporter to emit source location information once; 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. -fdiagnostics-show-location=every-line Only meaningful in line-wrapping mode. Instructs the diagnostic mes- sages 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. -fdiagnostics-color[=WHEN] -fno-diagnostics-color Use color in diagnostics. WHEN is never, always, or auto. The default depends on how the compiler has been configured, it can be any of the above WHEN options or also never if GCC_COLORS environment variable isn't present in the environment, and auto otherwise. auto makes GCC use color only when the standard error is a terminal, and when not exe- cuting in an emacs shell. The forms -fdiagnostics-color and -fno-diag- nostics-color are aliases for -fdiagnostics-color=always and -fdiagnos- tics-color=never, respectively. The colors are defined by the environment variable GCC_COLORS. Its value is a colon-separated list of capabilities and Select Graphic Ren- dition (SGR) substrings. SGR commands are interpreted by the terminal or terminal emulator. (See the section in the documentation of your text terminal for permitted values and their meanings as character at- tributes.) These substring values are integers in decimal representa- tion and can be concatenated with semicolons. Common values to con- catenate include 1 for bold, 4 for underline, 5 for blink, 7 for in- verse, 39 for default foreground color, 30 to 37 for foreground colors, 90 to 97 for 16-color mode foreground colors, 38;5;0 to 38;5;255 for 88-color and 256-color modes foreground colors, 49 for default back- ground color, 40 to 47 for background colors, 100 to 107 for 16-color mode background colors, and 48;5;0 to 48;5;255 for 88-color and 256-color modes background colors. The default GCC_COLORS is error=01;31:warning=01;35:note=01;36:range1=32:range2=34:locus=01:\ quote=01:path=01;36:fixit-insert=32:fixit-delete=31:\ diff-filename=01:diff-hunk=32:diff-delete=31:diff-insert=32:\ type-diff=01;32:fnname=01;32:targs=35:valid=01;31:invalid=01;32\ highlight-a=01;32:highlight-b=01;34 where 01;31 is bold red, 01;35 is bold magenta, 01;36 is bold cyan, 32 is green, 34 is blue, 01 is bold, and 31 is red. Setting GCC_COLORS to the empty string disables colors. Supported capabilities are as fol- lows. "error=" SGR substring for error: markers. "warning=" SGR substring for warning: markers. "note=" SGR substring for note: markers. "path=" SGR substring for colorizing paths of control-flow events as printed via -fdiagnostics-path-format=, such as the identifiers of individual events and lines indicating interprocedural calls and returns. "range1=" SGR substring for first additional range. "range2=" SGR substring for second additional range. "locus=" SGR substring for location information, file:line or file:line:col- umn etc. "quote=" SGR substring for information printed within quotes. "fnname=" SGR substring for names of C++ functions. "targs=" SGR substring for C++ function template parameter bindings. "fixit-insert=" SGR substring for fix-it hints suggesting text to be inserted or replaced. "fixit-delete=" SGR substring for fix-it hints suggesting text to be deleted. "diff-filename=" SGR substring for filename headers within generated patches. "diff-hunk=" SGR substring for the starts of hunks within generated patches. "diff-delete=" SGR substring for deleted lines within generated patches. "diff-insert=" SGR substring for inserted lines within generated patches. "type-diff=" SGR substring for highlighting mismatching types within template arguments in the C++ frontend. "valid=" SGR substring for highlighting valid elements within text art dia- grams. "invalid=" SGR substring for highlighting invalid elements within text art di- agrams. "highlight-a=" "highlight-b=" SGR substrings for contrasting two different things within diagnos- tics, such as a pair of mismatching types. See -fdiagnos- tics-show-highlight-colors. -fdiagnostics-urls[=WHEN] Use escape sequences to embed URLs in diagnostics. For example, when -fdiagnostics-show-option emits text showing the command-line option controlling a diagnostic, embed a URL for documentation of that option. WHEN is never, always, or auto. auto makes GCC use URL escape se- quences only when the standard error is a terminal, and when not exe- cuting in an emacs shell or any graphical terminal which is known to be incompatible with this feature, see below. The default depends on how the compiler has been configured. It can be any of the above WHEN options. GCC can also be configured (via the --with-diagnostics-urls=auto-if-env configure-time option) so that the default is affected by environment variables. Under such a configuration, GCC defaults to using auto if either GCC_URLS or TERM_URLS environment variables are present and non-empty in the environment of the compiler, or never if neither are. However, even with -fdiagnostics-urls=always the behavior is dependent on those environment variables: If GCC_URLS is set to empty or no, do not embed URLs in diagnostics. If set to st, URLs use ST escape se- quences. If set to bel, the default, URLs use BEL escape sequences. Any other non-empty value enables the feature. If GCC_URLS is not set, use TERM_URLS as a fallback. Note: ST is an ANSI escape sequence, string terminator ESC \, BEL is an ASCII character, CTRL-G that usually sounds like a beep. At this time GCC tries to detect also a few terminals that are known to not implement the URL feature, and have bugs or at least had bugs in some versions that are still in use, where the URL escapes are likely to misbehave, i.e. print garbage on the screen. That list is currently xfce4-terminal, certain known to be buggy gnome-terminal versions, the linux console, and mingw. This check can be skipped with the -fdiag- nostics-urls=always. -fno-diagnostics-show-option By default, each diagnostic emitted includes text indicating the com- mand-line option that directly controls the diagnostic (if such an op- tion is known to the diagnostic machinery). Specifying the -fno-diag- nostics-show-option flag suppresses that behavior. -fno-diagnostics-show-caret By default, each diagnostic emitted includes the original source line and a caret ^ indicating the column. This option suppresses this in- formation. The source line is truncated to n characters, if the -fmes- sage-length=n option is given. When the output is done to the termi- nal, the width is limited to the width given by the COLUMNS environment variable or, if not set, to the terminal width. -fno-diagnostics-show-labels By default, when printing source code (via -fdiagnostics-show-caret), diagnostics can label ranges of source code with pertinent information, such as the types of expressions: printf ("foo %s bar", long_i + long_j); ~^ ~~~~~~~~~~~~~~~ | | char * long int This option suppresses the printing of these labels (in the example above, the vertical bars and the "char *" and "long int" text). -fno-diagnostics-show-event-links By default, when printing execution paths (via -fdiagnostics-path-for- mat=inline-events), GCC will print lines connecting related events, such as the line connecting events 1 and 2 in: 3 | if (p) | ^ | | | (1) following `false' branch (when `p' is NULL)... ->-+ | | | | |+------------------------------------------------------------+ 4 || return 0; 5 || return *p; || ~ || | |+-------->(2) ...to here | (3) dereference of NULL `p' This option suppresses the printing of such connector lines. -fno-diagnostics-show-cwe Diagnostic messages can optionally have an associated CWE ("https://cwe.mitre.org/index.html") identifier. GCC itself only provides such metadata for some of the -fanalyzer diagnostics. GCC plugins may also provide diagnostics with such metadata. By default, if this information is present, it will be printed with the diagnostic. This option suppresses the printing of this metadata. -fno-diagnostics-show-rules Diagnostic messages can optionally have rules associated with them, such as from a coding standard, or a specification. GCC itself does not do this for any of its diagnostics, but plugins may do so. By de- fault, if this information is present, it will be printed with the di- agnostic. This option suppresses the printing of this metadata. -fno-diagnostics-show-highlight-colors GCC can use color for emphasis and contrast when printing diagnostic messages and quoting the user's source. For example, in demo.c: In function `test_bad_format_string_args': ../../src/demo.c:25:18: warning: format `%i' expects argument of type `int', but argument 2 has type `const char *' [-Wformat=] 25 | printf("hello %i", msg); | ~^ ~~~ | | | | int const char * | %s * the %i and "int" in the message and the "int" in the quoted source are colored using "highlight-a" (bold green by default), and * the "const char *" in the message and in the quoted source are both colored using "highlight-b" (bold blue by default). The intent is to draw the reader's eyes to the relationships between the various aspects of the diagnostic message and the source, using color to group related elements and distinguish between mismatching ones. This additional colorization is enabled by default if color printing is enabled (as per -fdiagnostics-color=), but it can be separately dis- abled via -fno-diagnostics-show-highlight-colors. -fno-diagnostics-show-line-numbers By default, when printing source code (via -fdiagnostics-show-caret), a left margin is printed, showing line numbers. This option suppresses this left margin. -fdiagnostics-minimum-margin-width=width This option controls the minimum width of the left margin printed by -fdiagnostics-show-line-numbers. It defaults to 6. -fdiagnostics-show-context[=depth] -fno-diagnostics-show-context With this option, the compiler might print the interesting control flow chain that guards the basic block of the statement which has the warn- ing. depth is the maximum depth of the control flow chain. Currently, The list of the impacted warning options includes: -Warray-bounds, -Wstringop-overflow, -Wstringop-overread, -Wstringop-truncation. and -Wrestrict. More warning options might be added to this list in future releases. The forms -fdiagnostics-show-context and -fno-diagnos- tics-show-context are aliases for -fdiagnostics-show-context=1 and -fdiagnostics-show-context=0, respectively. -fdiagnostics-parseable-fixits Emit fix-it hints in a machine-parseable format, suitable for consump- tion by IDEs. For each fix-it, a line will be printed after the rele- vant diagnostic, starting with the string "fix-it:". For example: fix-it:"test.c":{45:3-45:21}:"gtk_widget_show_all" The location is expressed as a half-open range, expressed as a count of bytes, starting at byte 1 for the initial column. In the above exam- ple, bytes 3 through 20 of line 45 of "test.c" are to be replaced with the given string: 00000000011111111112222222222 12345678901234567890123456789 gtk_widget_showall (dlg); ^^^^^^^^^^^^^^^^^^ gtk_widget_show_all The filename and replacement string escape backslash as "\\", tab as "\t", newline as "\n", double quotes as "\"", non-printable characters as octal (e.g. vertical tab as "\013"). An empty replacement string indicates that the given range is to be re- moved. An empty range (e.g. "45:3-45:3") indicates that the string is to be inserted at the given position. -fdiagnostics-generate-patch Print fix-it hints to stderr in unified diff format, after any diagnos- tics are printed. For example: --- test.c +++ test.c @ -42,5 +42,5 @ void show_cb(GtkDialog *dlg) { - gtk_widget_showall(dlg); + gtk_widget_show_all(dlg); } The diff may or may not be colorized, following the same rules as for diagnostics (see -fdiagnostics-color). -fdiagnostics-show-template-tree In the C++ frontend, when printing diagnostics showing mismatching tem- plate types, such as: could not convert 'std::map<int, std::vector<double> >()' from 'map<[...],vector<double>>' to 'map<[...],vector<float>> the -fdiagnostics-show-template-tree flag enables printing a tree-like structure showing the common and differing parts of the types, such as: map< [...], vector< [double != float]>> The parts that differ are highlighted with color ("double" and "float" in this case). -fno-elide-type By default when the C++ frontend prints diagnostics showing mismatching template types, common parts of the types are printed as "[...]" to simplify the error message. For example: could not convert 'std::map<int, std::vector<double> >()' from 'map<[...],vector<double>>' to 'map<[...],vector<float>> Specifying the -fno-elide-type flag suppresses that behavior. This flag also affects the output of the -fdiagnostics-show-template-tree flag. -fdiagnostics-path-format=KIND Specify how to print paths of control-flow events for diagnostics that have such a path associated with them. KIND is none, separate-events, or inline-events, the default. none means to not print diagnostic paths. separate-events means to print a separate "note" diagnostic for each event within the diagnostic. For example: test.c:29:5: error: passing NULL as argument 1 to 'PyList_Append' which requires a non-NULL parameter test.c:25:10: note: (1) when 'PyList_New' fails, returning NULL test.c:27:3: note: (2) when 'i < count' test.c:29:5: note: (3) when calling 'PyList_Append', passing NULL from (1) as argument 1 inline-events means to print the events "inline" within the source code. This view attempts to consolidate the events into runs of suffi- ciently-close events, printing them as labelled ranges within the source. For example, the same events as above might be printed as: 'test': events 1-3 25 | list = PyList_New(0); | ^~~~~~~~~~~~~ | | | (1) when 'PyList_New' fails, returning NULL 26 | 27 | for (i = 0; i < count; i++) { | ~~~ | | | (2) when 'i < count' 28 | item = PyLong_FromLong(random()); 29 | PyList_Append(list, item); | ~~~~~~~~~~~~~~~~~~~~~~~~~ | | | (3) when calling 'PyList_Append', passing NULL from (1) as argument 1 Interprocedural control flow is shown by grouping the events by stack frame, and using indentation to show how stack frames are nested, pushed, and popped. For example: 'test': events 1-2 | | 133 | { | | ^ | | | | | (1) entering 'test' | 134 | boxed_int *obj = make_boxed_int (i); | | ~~~~~~~~~~~~~~~~~~ | | | | | (2) calling 'make_boxed_int' | +--> 'make_boxed_int': events 3-4 | | 120 | { | | ^ | | | | | (3) entering 'make_boxed_int' | 121 | boxed_int *result = (boxed_int *)wrapped_malloc (sizeof (boxed_int)); | | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | | | | | (4) calling 'wrapped_malloc' | +--> 'wrapped_malloc': events 5-6 | | 7 | { | | ^ | | | | | (5) entering 'wrapped_malloc' | 8 | return malloc (size); | | ~~~~~~~~~~~~~ | | | | | (6) calling 'malloc' | <-------------+ | 'test': event 7 | | 138 | free_boxed_int (obj); | | ^~~~~~~~~~~~~~~~~~~~ | | | | | (7) calling 'free_boxed_int' | (etc) -fdiagnostics-show-path-depths This option provides additional information when printing control-flow paths associated with a diagnostic. If this is option is provided then the stack depth will be printed for each run of events within -fdiagnostics-path-format=inline-events. If provided with -fdiagnostics-path-format=separate-events, then the stack depth and function declaration will be appended when printing each event. This is intended for use by GCC developers and plugin developers when debugging diagnostics that report interprocedural control flow. -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 dejagnu. -fdiagnostics-column-unit=UNIT Select the units for the column number. This affects traditional diag- nostics (in the absence of -fno-show-column). The default UNIT, display, considers the number of display columns oc- cupied by each character. This may be larger than the number of bytes required to encode the character, in the case of tab characters, or it may be smaller, in the case of multibyte characters. For example, the character "GREEK SMALL LETTER PI (U+03C0)" occupies one display column, and its UTF-8 encoding requires two bytes; the character "SLIGHTLY SMILING FACE (U+1F642)" occupies two display columns, and its UTF-8 en- coding requires four bytes. Setting UNIT to byte changes the column number to the raw byte count in all cases, as was traditionally output by GCC prior to version 11.1.0. -fdiagnostics-column-origin=ORIGIN Select the origin for column numbers, i.e. the column number assigned to the first column. The default value of 1 corresponds to traditional GCC behavior and to the GNU style guide. Some utilities may perform better with an origin of 0; any non-negative value may be specified. -fdiagnostics-escape-format=FORMAT When GCC prints pertinent source lines for a diagnostic it normally at- tempts to print the source bytes directly. However, some diagnostics relate to encoding issues in the source file, such as malformed UTF-8, or issues with Unicode normalization. These diagnostics are flagged so that GCC will escape bytes that are not printable ASCII when printing their pertinent source lines. This option controls how such bytes should be escaped. The default FORMAT, unicode displays Unicode characters that are not printable ASCII in the form <U+XXXX>, and bytes that do not correspond to a Unicode character validly-encoded in UTF-8-encoded will be dis- played as hexadecimal in the form <XX>. For example, a source line containing the string before followed by the Unicode character U+03C0 ("GREEK SMALL LETTER PI", with UTF-8 encoding 0xCF 0x80) followed by the byte 0xBF (a stray UTF-8 trailing byte), followed by the string after will be printed for such a diagnostic as: before<U+03C0><BF>after Setting FORMAT to bytes will display all non-printable-ASCII bytes in the form <XX>, thus showing the underlying encoding of non-ASCII Uni- code characters. For the example above, the following will be printed: before<CF><80><BF>after -fdiagnostics-text-art-charset=CHARSET Some diagnostics can contain "text art" diagrams: visualizations cre- ated from text, intended to be viewed in a monospaced font. This option selects which characters should be used for printing such diagrams, if any. CHARSET is none, ascii, unicode, or emoji. The none value suppresses the printing of such diagrams. The ascii value will ensure that such diagrams are pure ASCII ("ASCII art"). The unicode value will allow for conservative use of unicode drawing char- acters (such as box-drawing characters). The emoji value further adds the possibility of emoji in the output (such as emitting U+26A0 WARNING SIGN followed by U+FE0F VARIATION SELECTOR-16 to select the emoji vari- ant of the character). The default is emoji, except when the environment variable LANG is set to C, in which case the default is ascii. -fno-diagnostics-show-nesting Some GCC diagnostics have an internal tree-like structure of nested sub-diagnostics, such as for problems when instantiating C++ templates. By default GCC uses indentation and bullet points in its text output to show the nesting structure of these diagnostics, moves location infor- mation to separate lines to make the structure clearer, and eliminates redundant repeated information. Selecting -fno-diagnostics-show-nesting suppresses this indentation, reformatting, and elision, restoring an older `look" for the diagnos- tics. -fno-diagnostics-show-nesting-locations When fdiagnostics-show-nesting is enabled, file names and line- and column- numbers are displayed on separate lines from the messages. This location information can be disabled altogether with -fno-diagnos- tics-show-nesting-locations. This option exists for use by GCC devel- opers, for writing DejaGnu test cases. -fdiagnostics-show-nesting-levels When fdiagnostics-show-nesting is enabled, use fdiagnostics-show-nest- ing-levels to also display numbers showing the depth of the nesting. This option exists for use by GCC developers for debugging nested diag- nostics, but may be of use to plugin authors. -fdiagnostics-format=FORMAT Select a different format for printing diagnostics. FORMAT is text, sarif-stderr or sarif-file. Using this option replaces any additional "output sinks" added by -fdi- agnostics-add-output=, or that set by -fdiagnostics-set-output=. The default is text. The sarif-stderr and sarif-file formats both emit diagnostics in SARIF Version 2.1.0 format, either to stderr, or to a file named source.sarif, respectively. -fdiagnostics-add-output=DIAGNOSTICS-OUTPUT-SPEC Add an additional "output sink" for emitting diagnostics. DIAGNOSTICS-OUTPUT-SPEC should specify a scheme, optionally followed by ":" and one or more KEY=VALUE pairs, in this form: <SCHEME> <SCHEME>:<KEY>=<VALUE> <SCHEME>:<KEY>=<VALUE>,<KEY2>=<VALUE2> etc. Schemes, keys, or values with a name prefixed "experimental" may change or be removed without notice. Keys can be per-scheme, or related to GCC as a whole. SCHEME can be textEmit diagnostics to stderr using GCC's classic text output format. Supported keys for the "text" scheme are: color=[yes|no] Override colorization settings from -fdiagnostics-color for this text output. show-nesting=[yes|no] Enable a mode that emphasizes hierarchical relationships within diagnostics messages, as per -fdiagnostics-show-nesting. De- faults to "yes". show-nesting-locations=[yes|no] If "show-nesting=yes", then by default locations are shown; set this key to "no" to disable printing such locations. This ex- ists for use by GCC developers, for writing DejaGnu test cases. show-nesting-levels=[yes|no] This is a debugging option for use with "show-nesting=yes". Set this key to "yes" to print explicit nesting levels in the output. This exists for use by GCC developers. sarif Emit diagnostics to a file in SARIF format. Supported keys for the "sarif" scheme are: file=FILENAME Specify the filename to write the SARIF output to, potentially with a leading absolute or relative path. If not specified, it defaults to source.sarif. serialization=[json] Specify the serialization format to use when writing out the SARIF. Currently this can only be "json", but is present as an extension point for experimenting with other serializations. version=[2.1|2.2-prerelease] Specify the version of SARIF to use for the output. If not specified, defaults to 2.1. "2.2-prerelease" uses an unoffi- cial draft of the future SARIF 2.2 specification and should only be used for experimentation in this release. There is also this key intended for use by GCC developers, rather than end-users, and subject to change or removal without notice: state-graphs=[yes|no] This is a debugging feature and defaults to "no". If "state-graphs=yes", then attempt to capture detailed state in- formation from -fanalyzer in the generated SARIF. experimental-html Emit diagnostics to a file in HTML format. This scheme is experi- mental, and may go away in future GCC releases. The keys and de- tails of the output are also subject to change. Supported keys for the "experimental-html" scheme are: css=[yes|no] Add an embedded <style> to the generated HTML. Defaults to yes. file=FILENAME Specify the filename to write the HTML output to, potentially with a leading absolute or relative path. If not specified, it defaults to source.html. javascript=[yes|no] Add an embedded <script> to the generated HTML providing a barebones UI for viewing results. Defaults to yes. There are also these keys intended for use by GCC developers, rather than end-users, and subject to change or removal without no- tice: show-state-diagrams=[yes|no] This is a debugging feature and defaults to "no". If "show-state-diagrams=yes", then attempt to use dot to generate SVG diagrams in the generated HTML, visualizing the state at each event in a diagnostic path. These are visible by pressing "j" and "k" to single-step forward and backward through events. Enabling this option will slow down HTML generation. show-graph-dot-src=[yes|no] This is a debugging feature and defaults to "no". If "show-graph-dot-src=yes" then if "show-state-diagrams=yes", the generated state diagrams will also show the .dot source input to GraphViz used for the diagram. show-graph-sarif=[yes|no] This is a debugging feature and defaults to "no". If "show-graph-sarif=yes" then if "show-state-diagrams=yes", the generated state diagrams will also show a SARIF representation of the state. As well as scheme-specific keys, the following GCC-related key is us- able on sinks of any scheme: cfgs=[yes|no] If "cfgs=yes" for a sink, then GCC will attempt to send information to that sink about the control flow graphs for the functions it is compiling. Text sinks ignore the information. SARIF sinks will add the graphs within "theRun.graphs". HTML sinks will generate SVG displaying the graphs. The precise form of the information is subject to change without notice. For example, -fdiagnostics-add-output=sarif:version=2.1,file=foo.2.1.sarif -fdiagnostics-add-output=sarif:version=2.2-prerelease,file=foo.2.2.sarif would add a pair of outputs, each writing to a different file, using versions 2.1 and 2.2 of the SARIF standard respectively. In EBNF: <diagnostics-output-specifier> = <diagnostics-output-name> | <diagnostics-output-name>, ":", <key-value-pairs>; <diagnostics-output-name> = "text" | "sarif" | "experimental-html"; <key-value-pairs> = <key-value-pair> | <key-value-pair> "," <key-value-pairs>; <key-value-pair> = <key> "=" <value>; <key> = ? string without a '=' ? ; <value> = ? string without a ',' ? ; -fdiagnostics-set-output=DIAGNOSTICS-OUTPUT-SPEC This works in a similar way to -fdiagnostics-add-output= except that instead of adding an additional "output sink" for diagnostics, it re- places all existing output sinks, such as from -fdiagnostics-format=, -fdiagnostics-add-output=, or a prior call to -fdiagnostics-set-out- put=. -fno-diagnostics-json-formatting By default, when JSON is emitted for diagnostics (via -fdiagnos- tics-format=sarif-stderr or -fdiagnostics-format=sarif-file), GCC will add newlines and indentation to visually emphasize the hierarchical structure of the JSON. Use -fno-diagnostics-json-formatting to suppress this whitespace. It must be passed before the option it is to affect. This is intended for compatibility with tools that do not expect the output to contain newlines, such as that emitted by older GCC releases. Options to Request or Suppress Warnings Warnings are diagnostic messages that report constructions that are not in- herently erroneous but that are risky or suggest there may have been an er- ror. The following language-independent options do not enable specific warnings but control the kinds of diagnostics produced by GCC. -fsyntax-only Check the code for syntax errors, but don't do anything beyond that. -fmax-errors=n Limits the maximum number of error messages to n, at which point GCC bails out rather than attempting to continue processing the source code. If n is 0 (the default), there is no limit on the number of er- ror messages produced. If -Wfatal-errors is also specified, then -Wfa- tal-errors takes precedence over this option. -w --no-warnings Inhibit all warning messages. -Werror Turn all warnings into errors. -Werror= Turn the specified warning into an error. The specifier for a warning is appended; for example -Werror=switch turns the warnings controlled by -Wswitch into errors. This switch takes a negative form, to be used to negate -Werror for specific warnings; for example -Wno-error=switch makes -Wswitch warnings not be errors, even when -Werror is in effect. The warning message for each controllable warning includes the option that controls the warning. That option can then be used with -Werror= and -Wno-error= as described above. (Printing of the option in the warning message can be disabled using the -fno-diagnostics-show-option flag.) Note that specifying -Werror=foo automatically implies -Wfoo. However, -Wno-error=foo does not imply anything. -Wfatal-errors This option causes the compiler to abort compilation on the first error occurred rather than trying to keep going and printing further error messages. You can request many specific warnings with options beginning with -W, for example -Wunused-variable to request warnings on declarations of variables that are never used. Each of these specific warning options also has a negative form beginning with -Wno- to turn off warnings; for example, -Wno-unused-variable. This manual lists only one of the two forms, whichever is not the default. For further language-specific options also refer to C++ Dialect Options and Objective-C and Objective-C++ Dialect Op- tions. Additional warnings can be produced by enabling the static ana- lyzer; Some options, such as -Wall and -Wextra, turn on other options, such as -Wunused, which may turn on further options, such as -Wunused-variable. The combined effect of positive and negative forms is that more specific op- tions have priority over less specific ones, independently of their posi- tion in the command line. For options of the same specificity, the last one takes effect. Options enabled or disabled via pragmas take effect as if they appeared at the end of the command line. When an unrecognized warning option is requested (e.g., -Wunknown-warning), GCC gives an error stating that the option is not recognized. However, if the -Wno- form is used, the behavior is slightly different: no diagnostic is produced for -Wno-unknown-warning unless other diagnostics are being produced. This allows the use of new -Wno- options with old compilers, but if something goes wrong, the compiler warns that an unrecognized option is present. The effectiveness of some warnings depends on optimizations also being en- abled. For example, -Wsuggest-final-types is more effective with link-time optimization. Some other warnings may not be issued at all unless opti- mization is enabled. While optimization in general improves the efficacy of warnings about control and data-flow problems, in some cases it may also cause false positives. -Wpedantic -pedantic --pedantic Issue all the warnings demanded by strict ISO C and ISO C++; diagnose all programs that use forbidden extensions, and some other programs that do not follow ISO C and ISO C++. This follows the version of the ISO C or C++ standard specified by any -std option used. Valid ISO C and ISO C++ programs should compile properly with or with- out this option (though a rare few require -ansi or a -std option spec- ifying the version of the standard). However, without this option, certain GNU extensions and traditional C and C++ features are supported as well. With this option, they are diagnosed (or rejected with -pedantic-errors). -Wpedantic does not cause warning messages for use of the alternate keywords whose names begin and end with __. This alternate format can also be used to disable warnings for non-ISO __intN types, i.e. __intN__. Pedantic warnings are also disabled in the expression that follows "__extension__". However, only system header files should use these escape routes; application programs should avoid them. Some warnings about non-conforming programs are controlled by options other than -Wpedantic; in many cases they are implied by -Wpedantic but can be disabled separately by their specific option, e.g. -Wpedantic -Wno-pointer-sign. Where the standard specified with -std represents a GNU extended di- alect of C, such as gnu90 or gnu99, there is a corresponding base stan- dard, the version of ISO C on which the GNU extended dialect is based. Warnings from -Wpedantic are given where they are required by the base standard. (It does not make sense for such warnings to be given only for features not in the specified GNU C dialect, since by definition the GNU dialects of C include all features the compiler supports with the given option, and there would be nothing to warn about.) -pedantic-errors --pedantic-errors Give an error whenever the base standard (see -Wpedantic) requires a diagnostic, in some cases where there is undefined behavior at com- pile-time and in some other cases that do not prevent compilation of programs that are valid according to the standard. This is not equiva- lent to -Werror=pedantic: the latter option is unlikely to be useful, as it only makes errors of the diagnostics that are controlled by -Wpedantic, whereas this option also affects required diagnostics that are always enabled or controlled by options other than -Wpedantic. If you want the required diagnostics that are warnings by default to be errors instead, but don't also want to enable the -Wpedantic diagnos- tics, you can specify -pedantic-errors -Wno-pedantic (or -pedantic-er- rors -Wno-error=pedantic to enable them but only as warnings). Some required diagnostics are errors by default, but can be reduced to warnings using -fpermissive or their specific warning option, e.g. -Wno-error=narrowing. Some diagnostics for non-ISO practices are controlled by specific warn- ing options other than -Wpedantic, but are also made errors by -pedan- tic-errors. For instance: -Wattributes (for standard attributes) -Wchanges-meaning (C++) -Wcomma-subscript (C++23 or later) -Wdeclaration-after-statement (C90 or earlier) -Welaborated-enum-base (C++11 or later) -Wimplicit-int (C99 or later) -Wimplicit-function-declaration (C99 or later) -Wincompati- ble-pointer-types -Wint-conversion -Wlong-long (C90 or earlier) -Wmain -Wnarrowing (C++11 or later) -Wpointer-arith -Wpointer-sign -Wincompat- ible-pointer-types -Wregister (C++17 or later) -Wvla (C90 or earlier) -Wwrite-strings (C++11 or later) -fpermissive Downgrade some required diagnostics about nonconformant code from er- rors to warnings. Thus, using -fpermissive allows some nonconforming code to compile. Some C++ diagnostics are controlled only by this flag, but it also downgrades some C and C++ diagnostics that have their own flag: -Wabbreviated-auto-in-template-arg (C++ and Objective-C++ only) -Wdec- laration-missing-parameter-type (C and Objective-C only) -Wim- plicit-function-declaration (C and Objective-C only) -Wimplicit-int (C and Objective-C only) -Wincompatible-pointer-types (C and Objective-C only) -Wint-conversion (C and Objective-C only) -Wnarrowing (C++ and Objective-C++ only) -Wreturn-mismatch (C and Objective-C only) -Wtem- plate-body (C++ and Objective-C++ only) The -fpermissive option is the default for historic C language modes (-std=c89, -std=gnu89, -std=c90, -std=gnu90). -Wall --all-warnings This enables all the warnings about constructions that some users con- sider questionable, and that are easy to avoid (or modify to prevent the warning), even in conjunction with macros. This also enables some language-specific warnings described in C++ Dialect Options and Objec- tive-C and Objective-C++ Dialect Options. -Wall turns on the following warning flags: -Waddress -Waligned-new (C++ and Objective-C++ only) -Warray-bounds=1 (only with -O2) -Warray-compare -Warray-parameter=2 -Wbool-compare -Wbool-operation -Wc++11-compat -Wc++14-compat -Wc++17compat -Wc++20compat -Wcatch-value (C++ and Objective-C++ only) -Wchar-sub- scripts -Wclass-memaccess (C++ and Objective-C++ only) -Wcomment -Wdan- gling-else -Wdangling-pointer=2 -Wdelete-non-virtual-dtor (C++ and Ob- jective-C++ only) -Wduplicate-decl-specifier (C and Objective-C only) -Wenum-compare (in C/ObjC; this is on by default in C++) -Wenum-int-mismatch (C and Objective-C only) -Wformat=1 -Wformat-con- tains-nul -Wformat-diag -Wformat-extra-args -Wformat-overflow=1 -Wfor- mat-truncation=1 -Wformat-zero-length -Wframe-address -Wimplicit (C and Objective-C only) -Wimplicit-function-declaration (C and Objective-C only) -Wimplicit-int (C and Objective-C only) -Winfinite-recursion -Winit-self (C++ and Objective-C++ only) -Wint-in-bool-context -Wlogi- cal-not-parentheses -Wmain (only for C/ObjC and unless -ffreestanding) -Wmaybe-uninitialized -Wmemset-elt-size -Wmemset-transposed-args -Wmis- leading-indentation (only for C/C++) -Wmismatched-dealloc -Wmis- matched-new-delete (C++ and Objective-C++ only) -Wmissing-attributes -Wmissing-braces (only for C/ObjC) -Wmultistatement-macros -Wnarrowing (C++ and Objective-C++ only) -Wnonnull -Wnonnull-compare -Wopenmp-simd (C and C++ only) -Woverloaded-virtual=1 (C++ and Objective-C++ only) -Wpacked-not-aligned -Wparentheses -Wpessimizing-move (C++ and Objec- tive-C++ only) -Wpointer-sign (only for C/ObjC) -Wrange-loop-construct (C++ and Objective-C++ only) -Wreorder (C++ and Objective-C++ only) -Wrestrict -Wreturn-type -Wself-move (C++ and Objective-C++ only) -Wse- quence-point -Wsign-compare (C++ and Objective-C++ only) -Wsizeof-ar- ray-div -Wsizeof-pointer-div -Wsizeof-pointer-memaccess -Wstrict-alias- ing -Wswitch -Wtautological-compare -Wtrigraphs -Wuninitialized -Wun- known-pragmas -Wunused -Wunused-but-set-variable -Wunused-const-vari- able=1 (only for C/ObjC) -Wunused-function -Wunused-label -Wunused-lo- cal-typedefs -Wunused-value -Wunused-variable -Wuse-after-free=2 -Wvla-parameter -Wvolatile-register-var -Wzero-length-bounds Note that some warning flags are not implied by -Wall. Some of them warn about constructions that users generally do not consider question- able, 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. Some of them are enabled by -Wextra but many of them must be enabled individually. -Wextra --extra-warnings This enables some extra warning flags that are not enabled by -Wall. (This option used to be called -W. The older name is still supported, but the newer name is more descriptive.) -Wabsolute-value (only for C/ObjC) -Walloc-size -Wcalloc-trans- posed-args -Wcast-function-type -Wclobbered -Wdangling-reference (C++ only) -Wdeprecated-copy (C++ and Objective-C++ only) -Wempty-body -Wenum-conversion (only for C/ObjC) -Wexpansion-to-defined -Wig- nored-qualifiers (only for C/C++) -Wimplicit-fallthrough=3 -Wmaybe-uninitialized -Wmissing-field-initializers -Wmissing-parame- ter-name (C/ObjC only) -Wmissing-parameter-type (C/ObjC only) -Wold-style-declaration (C/ObjC only) -Wmultiple-parame- ter-fwd-decl-lists (C/ObjC only) -Woverride-init (C/ObjC only) -Wredun- dant-move (C++ and Objective-C++ only) -Wshift-negative-value (in C++11 to C++17 and in C99 and newer) -Wsign-compare (C++ and Objective-C++ only) -Wsized-deallocation (C++ and Objective-C++ only) -Wstring-com- pare -Wtype-limits -Wuninitialized -Wunterminated-string-initialization (C/ObjC only) -Wunused-parameter (only with -Wunused or -Wall) -Wunused-but-set-parameter (only with -Wunused or -Wall) The option -Wextra also prints warning messages for the following cases: * A pointer is compared against integer zero with "<", "<=", ">", or ">=". * (C++ only) An enumerator and a non-enumerator both appear in a con- ditional expression. * (C++ only) Ambiguous virtual bases. * (C++ only) Subscripting an array that has been declared "register". * (C++ only) Taking the address of a variable that has been declared "register". * (C++ only) A base class is not initialized in the copy constructor of a derived class. -Wabi (C, Objective-C, C++ and Objective-C++ only) Warn about code affected by ABI changes. This includes code that may not be compatible with the vendor-neutral C++ ABI as well as the psABI for the particular target. The latter warnings are also controlled separately by -Wpsabi, which is implied by -Wabi. Since G++ now defaults to updating the ABI with each major release, normally -Wabi warns only about C++ ABI compatibility problems if there is a check added later in a release series for an ABI issue discovered since the initial release. -Wabi warns about more things if an older ABI version is selected (with -fabi-version=n). -Wabi can also be used with an explicit version number to warn about C++ ABI compatibility with a particular -fabi-version level, e.g. -Wabi=2 to warn about changes relative to -fabi-version=2. If an explicit version number is provided and -fabi-compat-version is not specified, the version number from this option is used for compati- bility aliases. If no explicit version number is provided with this option, but -fabi-compat-version is specified, that version number is used for C++ ABI warnings. 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 is compatible. You should rewrite your code to avoid these warnings if you are con- cerned about the fact that code generated by G++ may not be binary com- patible with code generated by other compilers. Known incompatibilities in -fabi-version=2 (which was the default from GCC 3.4 to 4.9) include: * A template with a non-type template parameter of reference type was mangled incorrectly: extern int N; template <int &> struct S {}; void n (S<N>) {2} This was fixed in -fabi-version=3. * SIMD vector types declared using "__attribute ((vector_size))" were mangled in a non-standard way that does not allow for overloading of functions taking vectors of different sizes. The mangling was changed in -fabi-version=4. * "__attribute ((const))" and "noreturn" were mangled as type quali- fiers, and "decltype" of a plain declaration was folded away. These mangling issues were fixed in -fabi-version=5. * Scoped enumerators passed as arguments to a variadic function are promoted like unscoped enumerators, causing "va_arg" to complain. On most targets this does not actually affect the parameter passing ABI, as there is no way to pass an argument smaller than "int". Also, the ABI changed the mangling of template argument packs, "const_cast", "static_cast", prefix increment/decrement, and a class scope function used as a template argument. These issues were corrected in -fabi-version=6. * Lambdas in default argument scope were mangled incorrectly, and the ABI changed the mangling of "nullptr_t". These issues were corrected in -fabi-version=7. * When mangling a function type with function-cv-qualifiers, the un-qualified function type was incorrectly treated as a substitu- tion candidate. This was fixed in -fabi-version=8, the default for GCC 5.1. * decltype(nullptr) incorrectly had an alignment of 1, leading to un- aligned accesses. Note that this did not affect the ABI of a func- tion with a "nullptr_t" parameter, as parameters have a minimum alignment. This was fixed in -fabi-version=9, the default for GCC 5.2. * Target-specific attributes that affect the identity of a type, such as ia32 calling conventions on a function type (stdcall, regparm, etc.), did not affect the mangled name, leading to name collisions when function pointers were used as template arguments. This was fixed in -fabi-version=10, the default for GCC 6.1. -Wpsabi (C, Objective-C, C++ and Objective-C++ only) -Wpsabi enables warnings about processor-specific ABI changes, such as changes in alignment requirements or how function arguments are passed. On several targets, including AArch64, ARM, x86, MIPS, RS6000/PowerPC, and S/390, these details have changed between different versions of GCC and/or different versions of the C or C++ language standards in ways that affect binary compatibility of compiled code. With -Wpsabi, GCC can detect potentially incompatible usages and warn you about them. -Wpsabi is enabled by default, and is also implied by -Wabi. -Wno-changes-meaning (C++ and Objective-C++ only) C++ requires that unqualified uses of a name within a class have the same meaning in the complete scope of the class, so declaring the name after using it is ill-formed: struct A; struct B1 { A a; typedef A A; }; // warning, 'A' changes meaning struct B2 { A a; struct A { }; }; // error, 'A' changes meaning By default, the B1 case is only a warning because the two declarations have the same type, while the B2 case is an error. Both diagnostics can be disabled with -Wno-changes-meaning. Alternately, the error case can be reduced to a warning with -Wno-error=changes-meaning or -fper- missive. Both diagnostics are also suppressed by -fms-extensions. -Wchar-subscripts Warn if an array subscript has type "char". This is a common cause of error, as programmers often forget that this type is signed on some ma- chines. @xref{Characters implementation}, and "char" type signedness. This warning is enabled by -Wall. When enabled, the warning is given regardless of whether "char" is unsigned by default on the target, and it is also not affected by the -fsigned-char or -funsigned-char op- tions. -Wno-coverage-mismatch Warn if feedback profiles do not match when using the -fprofile-use op- tion. If a source file is changed between compiling with -fpro- file-generate and with -fprofile-use, the files with the profile feed- back can fail to match the source file and GCC cannot use the profile feedback information. By default, this warning is enabled and is treated as an error. -Wno-coverage-mismatch can be used to disable the warning or -Wno-error=coverage-mismatch can be used to disable the er- ror. Disabling the error for this warning can result in poorly opti- mized code and is useful only in the case of very minor changes such as bug fixes to an existing code-base. Completely disabling the warning is not recommended. -Wno-coverage-too-many-conditions Warn if -fcondition-coverage is used and an expression have too many terms and GCC gives up coverage. Coverage is given up when there are more terms in the conditional than there are bits in a "gcov_type_un- signed". This warning is enabled by default. -Wno-coverage-too-many-paths Warn if -fpath-coverage is used and a function has too many paths and GCC gives up coverage. Giving up is controlled by -fpath-cover- age-limit. This warning is enabled by default. -Wno-coverage-invalid-line-number Warn in case a function ends earlier than it begins due to an invalid linenum macros. The warning is emitted only with --coverage enabled. By default, this warning is enabled and is treated as an error. -Wno-coverage-invalid-line-number can be used to disable the warning or -Wno-error=coverage-invalid-line-number can be used to disable the er- ror. -Wno-cpp (C, Objective-C, C++, Objective-C++ and Fortran only) Suppress warning messages emitted by "#warning" directives. -Wdouble-promotion (C, C++, Objective-C and Objective-C++ only) Give a warning when a value of type "float" is implicitly promoted to "double". CPUs with a 32-bit "single-precision" floating-point unit implement "float" in hardware, but emulate "double" in software. On such a machine, doing computations using "double" values is much more expensive because of the overhead required for software emulation. It is easy to accidentally do computations with "double" because float- ing-point literals are implicitly of type "double". For example, in: float area(float radius) { return 3.14159 * radius * radius; } the compiler performs the entire computation with "double" because the floating-point literal is a "double". -Wduplicate-decl-specifier (C and Objective-C only) Warn if a declaration has a duplicate "const", "volatile", "restrict" or "_Atomic" specifier. This warning is enabled by -Wall. -Wformat -Wformat=n Check calls to "printf" and "scanf", etc., to make sure that the argu- ments 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 at- tributes, in the "printf", "scanf", "strftime" and "strfmon" (an X/Open extension, not in the C standard) families (or other target-specific families). Which functions are checked without format attributes hav- ing been specified depends on the standard version selected, and such checks of functions without the attribute specified are disabled by -ffreestanding or -fno-builtin. The formats are checked against the format features supported by GNU libc version 2.2. These include all ISO C90 and C99 features, as well as features from the Single Unix Specification and some BSD and GNU ex- tensions. Other library implementations may not support all these fea- tures; GCC does not support warning about features that go beyond a particular library's limitations. However, if -Wpedantic is used with -Wformat, warnings are given about format features not in the selected standard version (but not for "strfmon" formats, since those are not in any version of the C standard). -Wformat=1 -Wformat Option -Wformat is equivalent to -Wformat=1, and -Wno-format is equivalent to -Wformat=0. Since -Wformat also checks for null for- mat arguments for several functions, -Wformat also implies -Wnon- null. Some aspects of this level of format checking can be dis- abled by the options: -Wno-format-contains-nul, -Wno-format-diag, -Wno-format-extra-args, and -Wno-format-zero-length. -Wformat is enabled by -Wall. -Wformat=2 Enable -Wformat plus additional format checks. Currently equiva- lent to -Wformat -Wformat-nonliteral -Wformat-security -Wfor- mat-y2k. -Wno-format-contains-nul If -Wformat is specified, do not warn about format strings that contain NUL bytes. -Wno-format-diag If -Wformat is specified, do not warn about format strings that are un- suitable for GCC diagnostics. -Wno-format-extra-args If -Wformat is specified, do not warn about excess arguments to a "printf" or "scanf" format function. The C standard specifies that such arguments are ignored. Where the unused arguments lie between used arguments that are speci- fied with $ operand number specifications, normally warnings are still given, since the implementation could not know what type to pass to "va_arg" to skip the unused arguments. However, in the case of "scanf" formats, this option suppresses the warning if the unused arguments are all pointers, since the Single Unix Specification says that such unused arguments are allowed. -Wformat-overflow -Wformat-overflow=level Warn about calls to formatted input/output functions such as "sprintf" and "vsprintf" that might overflow the destination buffer. When the exact number of bytes written by a format directive cannot be deter- mined at compile-time it is estimated based on heuristics that depend on the level argument and on optimization. While enabling optimization will in most cases improve the accuracy of the warning, it may also re- sult in false positives. -Wformat-overflow -Wformat-overflow=1 Level 1 of -Wformat-overflow enabled by -Wformat employs a conserv- ative approach that warns only about calls that most likely over- flow the buffer. At this level, numeric arguments to format direc- tives with unknown values are assumed to have the value of one, and strings of unknown length to be empty. Numeric arguments that are known to be bounded to a subrange of their type, or string argu- ments whose output is bounded either by their directive's precision or by a finite set of string literals, are assumed to take on the value within the range that results in the most bytes on output. For example, the call to "sprintf" below is diagnosed because even with both a and b equal to zero, the terminating NUL character ('\0') appended by the function to the destination buffer will be written past its end. Increasing the size of the buffer by a sin- gle byte is sufficient to avoid the warning, though it may not be sufficient to avoid the overflow. void f (int a, int b) { char buf [13]; sprintf (buf, "a = %i, b = %i\n", a, b); } -Wformat-overflow=2 Level 2 warns also about calls that might overflow the destination buffer given an argument of sufficient length or magnitude. At level 2, unknown numeric arguments are assumed to have the minimum representable value for signed types with a precision greater than 1, and the maximum representable value otherwise. Unknown string arguments whose length cannot be assumed to be bounded either by the directive's precision, or by a finite set of string literals they may evaluate to, or the character array they may point to, are assumed to be 1 character long. At level 2, the call in the example above is again diagnosed, but this time because with a equal to a 32-bit "INT_MIN" the first %i directive will write some of its digits beyond the end of the des- tination buffer. To make the call safe regardless of the values of the two variables, the size of the destination buffer must be in- creased to at least 34 bytes. GCC includes the minimum size of the buffer in an informational note following the warning. An alternative to increasing the size of the destination buffer is to constrain the range of formatted values. The maximum length of string arguments can be bounded by specifying the precision in the format directive. When numeric arguments of format directives can be assumed to be bounded by less than the precision of their type, choosing an appropriate length modifier to the format specifier will reduce the required buffer size. For example, if a and b in the example above can be assumed to be within the precision of the "short int" type then using either the %hi format directive or casting the argument to "short" reduces the maximum required size of the buffer to 24 bytes. void f (int a, int b) { char buf [23]; sprintf (buf, "a = %hi, b = %i\n", a, (short)b); } -Wno-format-zero-length If -Wformat is specified, do not warn about zero-length formats. The C standard specifies that zero-length formats are allowed. -Wformat-nonliteral If -Wformat 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 "va_list". -Wformat-security If -Wformat is specified, also warn about uses of format functions that represent possible security problems. At present, this warns about calls to "printf" and "scanf" functions where the format string is not a string literal and there are no format arguments, as in "printf (foo);". This may be a security hole if the format string came from untrusted input and contains %n. (This is currently a subset of what -Wformat-nonliteral warns about, but in future warnings may be added to -Wformat-security that are not included in -Wformat-nonliteral.) -Wformat-signedness If -Wformat is specified, also warn if the format string requires an unsigned argument and the argument is signed and vice versa. -Wformat-truncation -Wformat-truncation=level Warn about calls to formatted input/output functions such as "snprintf" and "vsnprintf" that might result in output truncation. When the exact number of bytes written by a format directive cannot be determined at compile time it is estimated based on heuristics that depend on the level argument and on optimization. While enabling optimization will in most cases improve the accuracy of the warning, it may also result in false positives. Except as noted otherwise, the option uses the same logic -Wformat-overflow. -Wformat-truncation -Wformat-truncation=1 Level 1 of -Wformat-truncation enabled by -Wformat employs a con- servative approach that warns only about calls to bounded functions whose return value is unused and that will most likely result in output truncation. -Wformat-truncation=2 Level 2 warns also about calls to bounded functions whose return value is used and that might result in truncation given an argument of sufficient length or magnitude. -Wformat-y2k If -Wformat is specified, also warn about "strftime" formats that may yield only a two-digit year. -Wnonnull Warn about passing a null pointer for arguments marked as requiring a non-null value by the "nonnull" function attribute. -Wnonnull is included in -Wall and -Wformat. It can be disabled with the -Wno-nonnull option. -Wnonnull-compare Warn when comparing an argument marked with the "nonnull" function at- tribute against null inside the function. -Wnonnull-compare is included in -Wall. It can be disabled with the -Wno-nonnull-compare option. -Wnull-dereference Warn if the compiler detects paths that trigger erroneous or undefined behavior due to dereferencing a null pointer. This option is only ac- tive when -fdelete-null-pointer-checks is active, which is enabled by optimizations in most targets. The precision of the warnings depends on the optimization options used. -Wno-musttail-local-addr Do not warn about passing a pointer (or in C++, a reference) to a local variable or label to argument of a "musttail" call. Those variables go out of scope before the tail call instruction. -Wmaybe-musttail-local-addr Warn when address of a local variable can escape to a "musttail" call, unless it goes out of scope already before the "musttail" call. int foo (int *); int bar (int *x) { if (x[0] == 1) { int a = 42; foo (&a); /* Without the C<musttail> attribute this call would not be tail called, because address of the C<a> variable escapes and the second foo call could dereference it. With the attribute the local variables are assumed to go out of scope immediately before the tail call instruction and the compiler warns about this. */ [[gnu::musttail]] return foo (nullptr); } else { { int a = 42; foo (&a); } /* The C<a> variable isn't already in scope, so even when it escaped, even without C<musttail> attribute it would be undefined behavior to dereference it and the compiler could turn this into a tail call. No warning is diagnosed here. */ [[gnu::musttail]] return foo (nullptr); } } This warning is enabled by -Wextra. -Wnrvo (C++ and Objective-C++ only) Warn if the compiler does not elide the copy from a local variable to the return value of a function in a context where it is allowed by [class.copy.elision]. This elision is commonly known as the Named Re- turn Value Optimization. For instance, in the example below the com- piler cannot elide copies from both v1 and v2, so it elides neither. std::vector<int> f() { std::vector<int> v1, v2; // ... if (cond) return v1; else return v2; // warning: not eliding copy } -Winfinite-recursion Warn about infinitely recursive calls. The warning is effective at all optimization levels but requires optimization in order to detect infi- nite recursion in calls between two or more functions. -Winfinite-re- cursion is included in -Wall. Compare with -Wanalyzer-infinite-recursion which provides a similar di- agnostic, but is implemented in a different way (as part of -fana- lyzer). -Winit-self (C, C++, Objective-C and Objective-C++ only) Warn about uninitialized variables that are initialized with them- selves. Note this option can only be used with the -Wuninitialized op- tion. For example, GCC warns about "i" being uninitialized in the following snippet only when -Winit-self has been specified: int f() { int i = i; return i; } This warning is enabled by -Wall in C++. -Wno-implicit-int (C and Objective-C only) This option controls warnings when a declaration does not specify a type. This warning is enabled by default, as an error, in C99 and later dialects of C, and also by -Wall. The error can be downgraded to a warning using -fpermissive (along with certain other errors), or for this error alone, with -Wno-error=implicit-int. This warning is upgraded to an error by -pedantic-errors. -Wno-implicit-function-declaration (C and Objective-C only) This option controls warnings when a function is used before being de- clared. This warning is enabled by default, as an error, in C99 and later dialects of C, and also by -Wall. The error can be downgraded to a warning using -fpermissive (along with certain other errors), or for this error alone, with -Wno-error=implicit-function-declaration. This warning is upgraded to an error by -pedantic-errors. -Wimplicit (C and Objective-C only) Same as -Wimplicit-int and -Wimplicit-function-declaration. This warn- ing is enabled by -Wall. -Whardened Warn when -fhardened did not enable an option from its set (for which see -fhardened). For instance, using -fhardened and -fstack-protector at the same time on the command line causes -Whardened to warn because -fstack-protector-strong will not be enabled by -fhardened. This warning is enabled by default and has effect only when -fhardened is enabled. -Wimplicit-fallthrough -Wimplicit-fallthrough is the same as -Wimplicit-fallthrough=3 and -Wno-implicit-fallthrough is the same as -Wimplicit-fallthrough=0. -Wimplicit-fallthrough=n Warn when a switch case falls through. For example: switch (cond) { case 1: a = 1; break; case 2: a = 2; case 3: a = 3; break; } This warning does not warn when the last statement of a case cannot fall through, e.g. when there is a return statement or a call to func- tion declared with the noreturn attribute. -Wimplicit-fallthrough= also takes into account control flow statements, such as ifs, and only warns when appropriate. E.g. switch (cond) { case 1: if (i > 3) { bar (5); break; } else if (i < 1) { bar (0); } else return; default: ... } Since there are occasions where a switch case fall through is desir- able, GCC provides an attribute, "__attribute__ ((fallthrough))", that is to be used along with a null statement to suppress this warning that would normally occur: switch (cond) { case 1: bar (0); __attribute__ ((fallthrough)); default: ... } C++17 and C23 provide a standard way to suppress the -Wim- plicit-fallthrough warning using "[[fallthrough]];" instead of the GNU attribute. In C++11 or C++14 users can use "[[gnu::fallthrough]];", which is a GNU extension. Instead of these attributes, it is also pos- sible to add a fallthrough comment to silence the warning. The whole body of the C or C++ style comment should match the given regular ex- pressions listed below. The option argument n specifies what kind of comments are accepted: *<-Wimplicit-fallthrough=0 disables the warning altogether.> *<-Wimplicit-fallthrough=1 matches ".*" regular> expression, any comment is used as fallthrough comment. *<-Wimplicit-fallthrough=2 case insensitively matches> ".*falls?[ \t-]*thr(ough|u).*" regular expression. *<-Wimplicit-fallthrough=3 case sensitively matches one of the> following regular expressions: *<"-fallthrough"> *<"@fallthrough@"> *<"lint -fallthrough[ \t]*"> *<"[ \t.!]*(ELSE,? |INTENTIONAL(LY)? )?FALL(S | |-)?THR(OUGH|U)[ \t.!]*(-[^\n\r]*)?"> *<"[ \t.!]*(Else,? |Intentional(ly)? )?Fall((s | |-)[Tt]|t)hr(ough|u)[ \t.!]*(-[^\n\r]*)?"> *<"[ \t.!]*([Ee]lse,? |[Ii]ntentional(ly)? )?fall(s | |-)?thr(ough|u)[ \t.!]*(-[^\n\r]*)?"> *<-Wimplicit-fallthrough=4 case sensitively matches one of the> following regular expressions: *<"-fallthrough"> *<"@fallthrough@"> *<"lint -fallthrough[ \t]*"> *<"[ \t]*FALLTHR(OUGH|U)[ \t]*"> *<-Wimplicit-fallthrough=5 doesn't recognize any comments as> fallthrough comments, only attributes disable the warning. The comment needs to be followed after optional whitespace and other comments by "case" or "default" keywords or by a user label that pre- cedes some "case" or "default" label. switch (cond) { case 1: bar (0); /* FALLTHRU */ default: ... } The -Wimplicit-fallthrough=3 warning is enabled by -Wextra. -Wno-if-not-aligned (C, C++, Objective-C and Objective-C++ only) Control if warnings triggered by the "warn_if_not_aligned" attribute should be issued. These warnings are enabled by default. -Wignored-qualifiers (C and C++ only) Warn if the return type of a function has a type qualifier such as "const". For ISO C such a type qualifier has no effect, since the value returned by a function is not an lvalue. For C++, the warning is only emitted for scalar types or "void". ISO C prohibits qualified "void" return types on function definitions, so such return types al- ways receive a warning even without this option. This warning is also enabled by -Wextra. -Wno-ignored-attributes (C and C++ only) This option controls warnings when an attribute is ignored. This is different from the -Wattributes option in that it warns whenever the compiler decides to drop an attribute, not that the attribute is either unknown, used in a wrong place, etc. This warning is enabled by de- fault. -Wmain Warn if the type of "main" is suspicious. "main" should be a function with external linkage, returning int, taking either zero arguments, two, or three arguments of appropriate types. This warning is enabled by default in C++ and is enabled by either -Wall or -Wpedantic. This warning is upgraded to an error by -pedantic-errors. -Wmisleading-indentation (C and C++ only) Warn when the indentation of the code does not reflect the block struc- ture. Specifically, a warning is issued for "if", "else", "while", and "for" clauses with a guarded statement that does not use braces, fol- lowed by an unguarded statement with the same indentation. In the following example, the call to "bar" is misleadingly indented as if it were guarded by the "if" conditional. if (some_condition ()) foo (); bar (); /* Gotcha: this is not guarded by the "if". */ In the case of mixed tabs and spaces, the warning uses the -ftabstop= option to determine if the statements line up (defaulting to 8). The warning is not issued for code involving multiline preprocessor logic such as the following example. if (flagA) foo (0); #if SOME_CONDITION_THAT_DOES_NOT_HOLD if (flagB) #endif foo (1); The warning is not issued after a "#line" directive, since this typi- cally indicates autogenerated code, and no assumptions can be made about the layout of the file that the directive references. This warning is enabled by -Wall in C and C++. -Wmissing-attributes Warn when a declaration of a function is missing one or more attributes that a related function is declared with and whose absence may ad- versely affect the correctness or efficiency of generated code. For example, the warning is issued for declarations of aliases that use at- tributes to specify less restrictive requirements than those of their targets. This typically represents a potential optimization opportu- nity. By contrast, the -Wattribute-alias=2 option controls warnings issued when the alias is more restrictive than the target, which could lead to incorrect code generation. Attributes considered include "al- loc_align", "alloc_size", "cold", "const", "hot", "leaf", "malloc", "nonnull", "noreturn", "nothrow", "pure", "returns_nonnull", and "re- turns_twice". In C++, the warning is issued when an explicit specialization of a pri- mary template declared with attribute "alloc_align", "alloc_size", "as- sume_aligned", "format", "format_arg", "malloc", or "nonnull" is de- clared without it. Attributes "deprecated", "error", and "warning" suppress the warning.. You can use the "copy" attribute to apply the same set of attributes to a declaration as that on another declaration without explicitly enumer- ating the attributes. This attribute can be applied to declarations of functions, variables, or types. Common Attributes. -Wmissing-attributes is enabled by -Wall. For example, since the declaration of the primary function template be- low makes use of both attribute "malloc" and "alloc_size" the declara- tion of the explicit specialization of the template is diagnosed be- cause it is missing one of the attributes. template <class T> T* __attribute__ ((malloc, alloc_size (1))) allocate (size_t); template <> void* __attribute__ ((malloc)) // missing alloc_size allocate<void> (size_t); -Wmissing-braces Warn if an aggregate or union initializer is not fully bracketed. In the following example, the initializer for "a" is not fully bracketed, but that for "b" is fully bracketed. int a[2][2] = { 0, 1, 2, 3 }; int b[2][2] = { { 0, 1 }, { 2, 3 } }; This warning is enabled by -Wall. -Wmissing-include-dirs (C, C++, Objective-C, Objective-C++ and Fortran only) Warn if a user-supplied include directory does not exist. This option is disabled by default for C, C++, Objective-C and Objective-C++. For Fortran, it is partially enabled by default by warning for -I and -J, only. -Wno-missing-profile This option controls warnings if feedback profiles are missing when us- ing the -fprofile-use option. This option diagnoses those cases where a new function or a new file is added between compiling with -fpro- file-generate and with -fprofile-use, without regenerating the pro- files. In these cases, the profile feedback data files do not contain any profile feedback information for the newly added function or file respectively. Also, in the case when profile count data (.gcda) files are removed, GCC cannot use any profile feedback information. In all these cases, warnings are issued to inform you that a profile genera- tion step is due. Ignoring the warning can result in poorly optimized code. -Wno-missing-profile can be used to disable the warning, but this is not recommended and should be done only when non-existent pro- file data is justified. -Wmismatched-dealloc Warn for calls to deallocation functions with pointer arguments re- turned from allocation functions for which the former isn't a suitable deallocator. A pair of functions can be associated as matching alloca- tors and deallocators by use of attribute "malloc". Unless disabled by the -fno-builtin option the standard functions "calloc", "malloc", "re- alloc", and "free", as well as the corresponding forms of C++ "operator new" and "operator delete" are implicitly associated as matching allo- cators and deallocators. In the following example "mydealloc" is the deallocator for pointers returned from "myalloc". void mydealloc (void*); __attribute__ ((malloc (mydealloc, 1))) void* myalloc (size_t); void f (void) { void *p = myalloc (32); // ...use p... free (p); // warning: not a matching deallocator for myalloc mydealloc (p); // ok } In C++, the related option -Wmismatched-new-delete diagnoses mismatches involving either "operator new" or "operator delete". Option -Wmismatched-dealloc is included in -Wall. -Wmultistatement-macros Warn about unsafe multiple statement macros that appear to be guarded by a clause such as "if", "else", "for", "switch", or "while", in which only the first statement is actually guarded after the macro is ex- panded. For example: #define DOIT x++; y++ if (c) DOIT; will increment "y" unconditionally, not just when "c" holds. The can usually be fixed by wrapping the macro in a do-while loop: #define DOIT do { x++; y++; } while (0) if (c) DOIT; This warning is enabled by -Wall in C and C++. -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. Also warn if a comparison like "x<=y<=z" appears; this is equivalent to "(x<=y ? 1 : 0) <= z", which is a different interpretation from that of ordinary mathematical notation. Also warn for dangerous uses of the GNU extension to "?:" with omitted middle operand. When the condition in the "?": operator is a boolean expression, the omitted value is always 1. Often programmers expect it to be a value computed inside the conditional expression instead. For C++ this also warns for some cases of unnecessary parentheses in declarations, which can indicate an attempt at a function call instead of a declaration: { // Declares a local variable called mymutex. std::unique_lock<std::mutex> (mymutex); // User meant std::unique_lock<std::mutex> lock (mymutex); } This warning is enabled by -Wall. -Wno-self-move (C++ and Objective-C++ only) This warning warns when a value is moved to itself with "std::move". Such a "std::move" typically has no effect. struct T { ... }; void fn() { T t; ... t = std::move (t); } This warning is enabled by -Wall. -Wsequence-point Warn about code that may have undefined semantics because of violations of sequence point rules in the C and C++ standards. The C and C++ standards define the order in which expressions in a C/C++ program are evaluated in terms of sequence points, which repre- sent 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 "&&", "||", "? :" or "," (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 de- scribe only a partial order rather than a total order, since, for exam- ple, 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. 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 and C++ standards specify 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. Fur- thermore, the prior value shall be read only to determine the value to be stored.". If a program breaks these rules, the results on any par- ticular implementation are entirely unpredictable. Examples of code with undefined behavior are "a = a++;", "a[n] = b[n++]" and "a[i++] = i;". Some more complicated cases are not diag- nosed by this option, and it may give an occasional false positive re- sult, but in general it has been found fairly effective at detecting this sort of problem in programs. The C++17 standard will define the order of evaluation of operands in more cases: in particular it requires that the right-hand side of an assignment be evaluated before the left-hand side, so the above exam- ples are no longer undefined. But this option will still warn about them, to help people avoid writing code that is undefined in C and ear- lier revisions of C++. The 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 the GCC readings page, at <https://gcc.gnu.org/read- ings.html>. This warning is enabled by -Wall for C and C++. -Wno-return-local-addr Do not warn about returning a pointer (or in C++, a reference) to a variable that goes out of scope after the function returns. -Wreturn-mismatch Warn about return statements without an expressions in functions which do not return "void". Also warn about a "return" statement with an ex- pression in a function whose return type is "void", unless the expres- sion type is also "void". As a GNU extension, the latter case is ac- cepted without a warning unless -Wpedantic is used. Attempting to use the return value of a non-"void" function other than "main" that flows off the end by reaching the closing curly brace that terminates the function is undefined. This warning is specific to C and enabled by default. In C99 and later language dialects, it is treated as an error. It can be downgraded to a warning using -fpermissive (along with other warnings), or for just this warning, with -Wno-error=return-mismatch. -Wreturn-type Warn whenever a function is defined with a return type that defaults to "int" (unless -Wimplicit-int is active, which takes precedence). Also warn if execution may reach the end of the function body, or if the function does not contain any return statement at all. Attempting to use the return value of a non-"void" function other than "main" that flows off the end by reaching the closing curly brace that terminates the function is undefined. Unlike in C, in C++, flowing off the end of a non-"void" function other than "main" results in undefined behavior even when the value of the function is not used. This warning is enabled by default in C++ and by -Wall otherwise. -Wno-shift-count-negative Controls warnings if a shift count is negative. This warning is en- abled by default. -Wno-shift-count-overflow Controls warnings if a shift count is greater than or equal to the bit width of the type. This warning is enabled by default. -Wshift-negative-value Warn if left shifting a negative value. This warning is enabled by -Wextra in C99 (and newer) and C++11 to C++17 modes. -Wno-shift-overflow -Wshift-overflow=n These options control warnings about left shift overflows. -Wshift-overflow=1 This is the warning level of -Wshift-overflow and is enabled by de- fault in C99 and C++11 modes (and newer). This warning level does not warn about left-shifting 1 into the sign bit. (However, in C, such an overflow is still rejected in contexts where an integer constant expression is required.) No warning is emitted in C++20 mode (and newer), as signed left shifts always wrap. -Wshift-overflow=2 This warning level also warns about left-shifting 1 into the sign bit, unless C++14 mode (or newer) is active. -Wswitch Warn whenever a "switch" statement has an index of enumerated type and lacks a "case" for one or more of the named codes of that enumeration. (The presence of a "default" label prevents this warning.) "case" la- bels that do not correspond to enumerators also provoke warnings when this option is used, unless the enumeration is marked with the "flag_enum" attribute. This warning is enabled by -Wall. -Wswitch-default Warn whenever a "switch" statement does not have a "default" case. -Wswitch-enum Warn whenever a "switch" statement has an index of enumerated type and lacks a "case" for one or more of the named codes of that enumeration. "case" labels that do not correspond to enumerators also provoke warn- ings when this option is used, unless the enumeration is marked with the "flag_enum" attribute. The only difference between -Wswitch and this option is that this option gives a warning about an omitted enu- meration code even if there is a "default" label. -Wno-switch-bool Do not warn when a "switch" statement has an index of boolean type and the case values are outside the range of a boolean type. It is possi- ble to suppress this warning by casting the controlling expression to a type other than "bool". For example: switch ((int) (a == 4)) { ... } This warning is enabled by default for C and C++ programs. -Wno-switch-outside-range This option controls warnings when a "switch" case has a value that is outside of its respective type range. This warning is enabled by de- fault for C and C++ programs. -Wno-switch-unreachable Do not warn when a "switch" statement contains statements between the controlling expression and the first case label, which will never be executed. For example: switch (cond) { i = 15; ... case 5: ... } -Wswitch-unreachable does not warn if the statement between the con- trolling expression and the first case label is just a declaration: switch (cond) { int i; ... case 5: i = 5; ... } This warning is enabled by default for C and C++ programs. -Wsync-nand (C and C++ only) Warn when "__sync_fetch_and_nand" and "__sync_nand_and_fetch" built-in functions are used. These functions changed semantics in GCC 4.4. -Wtrivial-auto-var-init Warn when "-ftrivial-auto-var-init" cannot initialize the automatic variable. A common situation is an automatic variable that is declared between the controlling expression and the first case label of a "switch" statement. -Wunused-but-set-parameter -Wunused-but-set-parameter is the same as -Wunused-but-set-parameter=3 and -Wno-unused-but-set-parameter is the same as -Wunused-but-set-para- meter=0. -Wunused-but-set-parameter=n Warn whenever a function parameter is assigned to, but otherwise unused (aside from its declaration). To suppress this warning use the "unused" attribute. -Wunused-but-set-parameter=0 disables the warning. With -Wunused-but-set-parameter=1 all uses except initialization and left hand side of assignment which is not further used disable the warning. With -Wunused-but-set-parameter=2 additionally uses of parameter in "++" and "--" operators don't count as uses. And finally with -Wunused-but-set-parameter=3 additionally uses in parm "@=" rhs outside of rhs don't count as uses. See -Wunused-but-set-variable=n option for examples. This -Wunused-but-set-parameter=3 warning is also enabled by -Wunused together with -Wextra. -Wunused-but-set-variable -Wunused-but-set-variable is the same as -Wunused-but-set-variable=3 and -Wno-unused-but-set-variable is the same as -Wunused-but-set-vari- able=0. -Wunused-but-set-variable=n Warn whenever a local variable is assigned to, but otherwise unused (aside from its declaration). This -Wunused-but-set-variable=3 warning is enabled by -Wall. To suppress this warning use the "unused" attribute. -Wunused-but-set-variable=0 disables the warning. With -Wunused-but-set-variable=1 all uses except initialization and left hand side of assignment which is not further used disable the warning. With -Wunused-but-set-variable=2 additionally uses of variable in "++" and "--" operators don't count as uses. And finally with -Wunused-but-set-variable=3 additionally uses in parm "@=" rhs outside of rhs don't count as uses. This -Wunused-but-set-variable=3 warning is also enabled by -Wunused, which is enabled by -Wall. void foo (void) { int a = 1; // B<-Wunused-variable> warning int b = 0; // Warning for <n> >= 1 b = 1; b = 2; int c = 0; // Warning for <n> >= 2 ++c; c--; --c; c++; int d = 0; // Warning for <n> >= 3 d += 4; int e = 0; // No warning, cast to void (void) e; int f = 0; // No warning, f used int g = f = 5; (void) g; int h = 0; // No warning, preincrement result used int i = ++h; (void) i; int j = 0; // No warning, postdecrement result used int k = j--; (void) k; int l = 0; // No warning, l used int m = l |= 2; (void) m; } -Wunused-function Warn whenever a static function is declared but not defined or a non-inline static function is unused. This warning is enabled by -Wall. -Wunused-label Warn whenever a label is declared but not used. This warning is en- abled by -Wall. To suppress this warning use the "unused" attribute. -Wunused-local-typedefs (C, Objective-C, C++ and Objective-C++ only) Warn when a typedef locally defined in a function is not used. This warning is enabled by -Wall. -Wunused-parameter Warn whenever a function parameter is unused aside from its declara- tion. This option is not enabled by "-Wunused" unless "-Wextra" is also specified. To suppress this warning use the "unused" attribute. -Wno-unused-result Do not warn if a caller of a function marked with attribute "warn_un- used_result" does not use its return value. The default is -Wunused-re- sult. -Wunused-variable Warn whenever a local or static variable is unused aside from its dec- laration. This option implies -Wunused-const-variable=1 for C, but not for C++. This warning is enabled by -Wall. To suppress this warning use the "unused" attribute. -Wunused-const-variable -Wunused-const-variable=n Warn whenever a constant static variable is unused aside from its dec- laration. To suppress this warning use the "unused" attribute. -Wunused-const-variable=1 Warn about unused static const variables defined in the main compi- lation unit, but not about static const variables declared in any header included. -Wunused-const-variable=1 is enabled by either -Wunused-variable or -Wunused for C, but not for C++. In C, this declares variable stor- age, but in C++, this is not an error since const variables take the place of "#define"s. -Wunused-const-variable=2 This warning level also warns for unused constant static variables in headers (excluding system headers). It is equivalent to the short form -Wunused-const-variable. This level must be explicitly requested in both C and C++ because it might be hard to clean up all headers included. -Wunused-value Warn whenever a statement computes a result that is explicitly not used. To suppress this warning cast the unused expression to "void". This includes an expression-statement or the left-hand side of a comma expression that contains no side effects. For example, an expression such as "x[i,j]" causes a warning, while "x[(void)i,j]" does not. This warning is enabled by -Wall. -Wunused All the above -Wunused options combined, except those documented as needing to be specified explicitly. In order to get a warning about an unused function parameter, you must either specify -Wextra -Wunused (note that -Wall implies -Wunused), or separately specify -Wunused-parameter and/or -Wunused-but-set-parame- ter. -Wunused enables only -Wunused-const-variable=1 rather than -Wunused-const-variable, and only for C, not C++. -Wuse-after-free (C, Objective-C, C++ and Objective-C++ only) -Wuse-after-free=n Warn about uses of pointers to dynamically allocated objects that have been rendered indeterminate by a call to a deallocation function. The warning is enabled at all optimization levels but may yield different results with optimization than without. -Wuse-after-free=1 At level 1 the warning attempts to diagnose only unconditional uses of pointers made indeterminate by a deallocation call or a success- ful call to "realloc", regardless of whether or not the call re- sulted in an actual reallocation of memory. This includes dou- ble-"free" calls as well as uses in arithmetic and relational ex- pressions. Although undefined, uses of indeterminate pointers in equality (or inequality) expressions are not diagnosed at this level. -Wuse-after-free=2 At level 2, in addition to unconditional uses, the warning also di- agnoses conditional uses of pointers made indeterminate by a deal- location call. As at level 2, uses in equality (or inequality) ex- pressions are not diagnosed. For example, the second call to "free" in the following function is diagnosed at this level: struct A { int refcount; void *data; }; void release (struct A *p) { int refcount = --p->refcount; free (p); if (refcount == 0) free (p->data); // warning: p may be used after free } -Wuse-after-free=3 At level 3, the warning also diagnoses uses of indeterminate point- ers in equality expressions. All uses of indeterminate pointers are undefined but equality tests sometimes appear after calls to "realloc" as an attempt to determine whether the call resulted in relocating the object to a different address. They are diagnosed at a separate level to aid gradually transitioning legacy code to safe alternatives. For example, the equality test in the function below is diagnosed at this level: void adjust_pointers (int**, int); void grow (int **p, int n) { int **q = (int**)realloc (p, n *= 2); if (q == p) return; adjust_pointers ((int**)q, n); } To avoid the warning at this level, store offsets into allocated memory instead of pointers. This approach obviates needing to ad- just the stored pointers after reallocation. -Wuse-after-free=2 is included in -Wall. -Wuseless-cast (C, Objective-C, C++ and Objective-C++ only) Warn when an expression is cast to its own type. This warning does not occur when a class object is converted to a non-reference type as that is a way to create a temporary: struct S { }; void g (S&&); void f (S&& arg) { g (S(arg)); // make arg prvalue so that it can bind to S&& } -Wuninitialized Warn if an object with automatic or allocated storage duration is used without having been initialized. In C++, also warn if a non-static reference or non-static "const" member appears in a class without con- structors. In addition, passing a pointer (or in C++, a reference) to an unini- tialized object to a "const"-qualified argument of a built-in function known to read the object is also diagnosed by this warning. (-Wmaybe-uninitialized is issued for ordinary functions.) If you want to warn about code that uses the uninitialized value of the variable in its own initializer, use the -Winit-self option. These warnings occur for individual uninitialized elements of struc- ture, union or array variables as well as for variables that are unini- tialized as a whole. They do not occur for variables or elements de- clared "volatile". Because these warnings depend on optimization, the exact variables or elements for which there are warnings depend on the precise optimization options and version of GCC used. 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. In C++, this warning also warns about using uninitialized objects in member-initializer-lists. For example, GCC warns about "b" being uninitialized in the following snippet: struct A { int a; int b; A() : a(b) { } }; -Wno-invalid-memory-model This option controls warnings for invocations of __atomic Builtins, __sync Builtins, and the C11 atomic generic functions with a memory consistency argument that is either invalid for the operation or out- side the range of values of the "memory_order" enumeration. For exam- ple, since the "__atomic_store" and "__atomic_store_n" built-ins are only defined for the relaxed, release, and sequentially consistent mem- ory orders the following code is diagnosed: void store (int *i) { __atomic_store_n (i, 0, memory_order_consume); } -Winvalid-memory-model is enabled by default. -Wmaybe-uninitialized For an object with automatic or allocated storage duration, if there exists a path from the function entry to a use of the object that is initialized, but there exist some other paths for which the object is not initialized, the compiler emits a warning if it cannot prove the uninitialized paths are not executed at run time. In addition, passing a pointer (or in C++, a reference) to an unini- tialized object to a "const"-qualified function argument is also diag- nosed by this warning. (-Wuninitialized is issued for built-in func- tions known to read the object.) Annotating the function with at- tribute "access (none)" indicates that the argument isn't used to ac- cess the object and avoids the warning. These warnings are only possible in optimizing compilation, because otherwise GCC does not keep track of the state of variables. On the other hand, -Wmaybe-uninitialized is known not to warn in many situa- tions (false negatives) due to optimizations taking advantage of unde- finedness of uninitialized uses like constant propagation. These warnings are made optional because GCC may not be able to deter- mine when the code is correct in spite of appearing to have an error. Here is one example of how this can happen: { int x; switch (y) { case 1: x = 1; break; case 2: x = 4; break; case 3: x = 5; } foo (x); } If the value of "y" is always 1, 2 or 3, then "x" is always initial- ized, but GCC doesn't know this. To suppress the warning, you need to provide a default case with assert(0) or similar code. This option also warns when a non-volatile automatic variable might be changed by a call to "longjmp". The compiler sees only the calls to "setjmp". It cannot know where "longjmp" 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 "longjmp" cannot in fact be called at the place that would cause a problem. Some spurious warnings can be avoided if you declare all the functions you use that never return as "noreturn". This warning is enabled by -Wall or -Wextra. -Wunknown-pragmas Warn when a "#pragma" directive is encountered that is not understood by GCC. If this command-line option is used, warnings are even issued for unknown pragmas in system header files. This is not the case if the warnings are only enabled by the -Wall command-line option. -Wno-pragmas Do not warn about misuses of pragmas, such as incorrect parameters, in- valid syntax, or conflicts between pragmas. See also -Wunknown-prag- mas. -Wno-pragma-once-outside-header Do not warn when "#pragma once" is used in a file that is not a header file, such as a main file. -Wno-prio-ctor-dtor Do not warn if a priority from 0 to 100 is used for constructor or de- structor. The use of constructor and destructor attributes allow you to assign a priority to the constructor/destructor to control its order of execution before "main" is called or after it returns. The priority values must be greater than 100 as the compiler reserves priority val- ues between 0--100 for the implementation. -Wstrict-aliasing This option is only active when -fstrict-aliasing is active. It warns about code that might break the strict aliasing rules that the compiler is using for optimization. The warning does not catch all cases, but does attempt to catch the more common pitfalls. It is included in -Wall. It is equivalent to -Wstrict-aliasing=3. -Wstrict-aliasing=n This option is only active when -fstrict-aliasing is active. It warns about code that might break the strict aliasing rules that the compiler is using for optimization. Higher levels correspond to higher accuracy (fewer false positives). Higher levels also correspond to more effort, similar to the way -O works. -Wstrict-aliasing is equivalent to -Wstrict-aliasing=3. Level 1: Most aggressive, quick, least accurate. Possibly useful when higher levels do not warn but -fstrict-aliasing still breaks the code, as it has very few false negatives. However, it has many false posi- tives. Warns for all pointer conversions between possibly incompatible types, even if never dereferenced. Runs in the front end only. Level 2: Aggressive, quick, not too precise. May still have many false positives (not as many as level 1 though), and few false negatives (but possibly more than level 1). Unlike level 1, it only warns when an ad- dress is taken. Warns about incomplete types. Runs in the front end only. Level 3 (default for -Wstrict-aliasing): Should have very few false positives and few false negatives. Slightly slower than levels 1 or 2 when optimization is enabled. Takes care of the common pun+dereference pattern in the front end: "*(int*)&some_float". If optimization is en- abled, it also runs in the back end, where it deals with multiple statement cases using flow-sensitive points-to information. Only warns when the converted pointer is dereferenced. Does not warn about incom- plete types. -Wstrict-overflow -Wstrict-overflow=n Does nothing. Preserved for backward compatibility. -Wstrict-overflow=1 Does nothing. Preserved for backward compatibility. -Wstrict-overflow=2 Does nothing. Preserved for backward compatibility. -Wstrict-overflow=3 Does nothing. Preserved for backward compatibility. -Wstrict-overflow=4 Does nothing. Preserved for backward compatibility. -Wstrict-overflow=5 Does nothing. Preserved for backward compatibility. -Wstring-compare Warn for calls to "strcmp" and "strncmp" whose result is determined to be either zero or non-zero in tests for such equality owing to the length of one argument being greater than the size of the array the other argument is stored in (or the bound in the case of "strncmp"). Such calls could be mistakes. For example, the call to "strcmp" below is diagnosed because its result is necessarily non-zero irrespective of the contents of the array "a". extern char a[4]; void f (char *d) { strcpy (d, "string"); ... if (0 == strcmp (a, d)) // cannot be true puts ("a and d are the same"); } -Wstring-compare is enabled by -Wextra. -Wno-stringop-overflow -Wstringop-overflow -Wstringop-overflow=type Warn for code that can be statically determined to cause buffer over- flows or memory overruns, such as calls to "memcpy" and "strcpy" that overflow the destination buffer. The optional argument is one greater than the type of Object Size Checking to perform to determine the size of the destination. The argument is meaningful only for string func- tions that operate on character arrays; raw memory functions like "mem- cpy" always use type-zero Object Size Checking. The option also warns for calls that specify a size in excess of the largest possible object or at most "SIZE_MAX / 2" bytes. The option produces the best results with optimization enabled but can detect a small subset of simple buffer overflows even without optimiza- tion in calls to the GCC built-in functions like "__builtin_memcpy" that correspond to the standard functions. In any case, the option warns about just a subset of buffer overflows detected by the corre- sponding overflow checking built-ins, such as "__builtin___memcpy_chk", which can perform run-time checking if the access cannot be identified as safe at compile time. For example, the option issues a warning for the "strcpy" call below because it copies at least 5 characters (the string "blue" including the terminating NUL) into the buffer of size 4. enum Color { blue, purple, yellow }; const char* f (enum Color clr) { static char buf [4]; const char *str; switch (clr) { case blue: str = "blue"; break; case purple: str = "purple"; break; case yellow: str = "yellow"; break; } return strcpy (buf, str); // warning here } The effect of this option is not limited to string or memory manipula- tion functions. In this example, a warning is diagnosed because a 1-element array is passed to a function requiring at least a 4-element array argument: void f (int[static 4]); void g (void) { int *p = (int *) malloc (1 * sizeof(int)); f (p); // warning here } Option -Wstringop-overflow=2 is enabled by default. -Wstringop-overflow -Wstringop-overflow=1 The -Wstringop-overflow=1 option uses type-zero Object Size Check- ing to determine the sizes of destination objects. At this setting the option does not warn for writes past the end of subobjects of larger objects accessed by pointers unless the size of the largest surrounding object is known. When the destination may be one of several objects it is assumed to be the largest one of them. On Linux systems, when optimization is enabled at this setting the op- tion warns for the same code as when the "_FORTIFY_SOURCE" macro is defined to a non-zero value. -Wstringop-overflow=2 The -Wstringop-overflow=2 option uses type-one Object Size Checking to determine the sizes of destination objects. At this setting the option warns about overflows when writing to members of the largest complete objects whose exact size is known. However, it does not warn for excessive writes to the same members of unknown objects referenced by pointers since they may point to arrays containing unknown numbers of elements. This is the default setting of the option. -Wstringop-overflow=3 The -Wstringop-overflow=3 option uses type-two Object Size Checking to determine the sizes of destination objects. At this setting the option warns about overflowing the smallest object or data member. This is the most restrictive setting of the option that may result in warnings for safe code. -Wstringop-overflow=4 The -Wstringop-overflow=4 option uses type-three Object Size Check- ing to determine the sizes of destination objects. At this setting the option warns about overflowing any data members, and when the destination is one of several objects it uses the size of the largest of them to decide whether to issue a warning. Similarly to -Wstringop-overflow=3 this setting of the option may result in warnings for benign code. -Wno-stringop-overread Warn for calls to string manipulation functions such as "memchr", or "strcpy" that are determined to read past the end of the source se- quence. Option -Wstringop-overread is enabled by default. -Wno-stringop-truncation Do not warn for calls to bounded string manipulation functions such as "strncat", "strncpy", and "stpncpy" that may either truncate the copied string or leave the destination unchanged. In the following example, the call to "strncat" specifies a bound that is less than the length of the source string. As a result, the copy of the source will be truncated and so the call is diagnosed. To avoid the warning use "bufsize - strlen (buf) - 1)" as the bound. void append (char *buf, size_t bufsize) { strncat (buf, ".txt", 3); } As another example, the following call to "strncpy" results in copying to "d" just the characters preceding the terminating NUL, without ap- pending the NUL to the end. Assuming the result of "strncpy" is neces- sarily a NUL-terminated string is a common mistake, and so the call is diagnosed. To avoid the warning when the result is not expected to be NUL-terminated, call "memcpy" instead. void copy (char *d, const char *s) { strncpy (d, s, strlen (s)); } In the following example, the call to "strncpy" specifies the size of the destination buffer as the bound. If the length of the source string is equal to or greater than this size the result of the copy will not be NUL-terminated. Therefore, the call is also diagnosed. To avoid the warning, specify "sizeof buf - 1" as the bound and set the last element of the buffer to "NUL". void copy (const char *s) { char buf[80]; strncpy (buf, s, sizeof buf); ... } In situations where a character array is intended to store a sequence of bytes with no terminating "NUL" such an array may be annotated with attribute "nonstring" to avoid this warning. Such arrays, however, are not suitable arguments to functions that expect "NUL"-terminated strings. To help detect accidental misuses of such arrays GCC issues warnings unless it can prove that the use is safe. -Wstrict-flex-arrays (C and C++ only) Warn about improper usages of flexible array members according to the level of the "strict_flex_array (level)" attribute attached to the trailing array field of a structure if it's available, otherwise ac- cording to the level of the option -fstrict-flex-arrays=level. "-Wstrict-flex-arrays" is effective only when level is greater than 0. When level=1, warnings are issued for a trailing array reference of a structure that have 2 or more elements if the trailing array is refer- enced as a flexible array member. When level=2, in addition to level=1, additional warnings are issued for a trailing one-element array reference of a structure if the array is referenced as a flexible array member. When level=3, in addition to level=2, additional warnings are issued for a trailing zero-length array reference of a structure if the array is referenced as a flexible array member. This option is more effective when -ftree-vrp is active (the default for -O2 and above) but some warnings may be diagnosed even without op- timization. -Wsuggest-attribute=attribute-name Warn for cases where adding an attribute may be beneficial. The at- tribute-names currently supported are listed below. -Wsuggest-attribute=pure -Wsuggest-attribute=const -Wsuggest-attribute=noreturn -Wmissing-noreturn -Wsuggest-attribute=malloc -Wsuggest-attribute=returns_nonnull Warn about functions that might be candidates for attributes "pure", "const", "noreturn", "malloc" or "returns_nonnull". The compiler only warns for functions visible in other compilation units or (in the case of "pure" and "const") if it cannot prove that the function returns normally. A function returns normally if it doesn't contain an infinite loop or return abnormally by throw- ing, calling "abort" or trapping. This analysis requires option -fipa-pure-const, which is enabled by default at -O and higher. Higher optimization levels improve the accuracy of the analysis. -Wsuggest-attribute=format -Wmissing-format-attribute Warn about function pointers that might be candidates for "format" attributes. Note these are only possible candidates, not absolute ones. GCC guesses that function pointers with "format" attributes that are used in assignment, initialization, parameter passing or return statements should have a corresponding "format" attribute in the resulting type. I.e. the left-hand side of the assignment or initialization, the type of the parameter variable, or the return type of the containing function respectively should also have a "format" attribute to avoid the warning. GCC also warns about function definitions that might be candidates for "format" attributes. Again, these are only possible candi- dates. GCC guesses that "format" attributes might be appropriate for any function that calls a function like "vprintf" or "vscanf", but this might not always be the case, and some functions for which "format" attributes are appropriate may not be detected. -Wsuggest-attribute=cold Warn about functions that might be candidates for "cold" attribute. This is based on static detection and generally only warns about functions which always leads to a call to another "cold" function such as wrappers of C++ "throw" or fatal error reporting functions leading to "abort". -Walloc-size Warn about calls to allocation functions decorated with attribute "al- loc_size" that specify insufficient size for the target type of the pointer the result is assigned to, including those to the built-in forms of the functions "aligned_alloc", "alloca", "calloc", "malloc", and "realloc". -Walloc-zero Warn about calls to allocation functions decorated with attribute "al- loc_size" that specify zero bytes, including those to the built-in forms of the functions "aligned_alloc", "alloca", "calloc", "malloc", and "realloc". Because the behavior of these functions when called with a zero size differs among implementations (and in the case of "re- alloc" has been deprecated) relying on it may result in subtle porta- bility bugs and should be avoided. -Wcalloc-transposed-args Warn about calls to allocation functions decorated with attribute "al- loc_size" with two arguments, which use "sizeof" operator as the ear- lier size argument and don't use it as the later size argument. This is a coding style warning. The first argument to "calloc" is docu- mented to be number of elements in array, while the second argument is size of each element, so "calloc (n, sizeof (int))" is preferred over "calloc (sizeof (int), n)". If "sizeof" in the earlier argument and not the latter is intentional, the warning can be suppressed by using "calloc (sizeof (struct S) + 0, n)" or "calloc (1 * sizeof (struct S), 4)" or using "sizeof" in the later argument as well. -Walloc-size-larger-than=byte-size Warn about calls to functions decorated with attribute "alloc_size" that attempt to allocate objects larger than the specified number of bytes, or where the result of the size computation in an integer type with infinite precision would exceed the value of PTRDIFF_MAX on the target. -Walloc-size-larger-than=PTRDIFF_MAX is enabled by default. Warnings controlled by the option can be disabled either by specifying byte-size of SIZE_MAX or more or by -Wno-alloc-size-larger-than. -Wno-alloc-size-larger-than Disable -Walloc-size-larger-than= warnings. The option is equivalent to -Walloc-size-larger-than=SIZE_MAX or larger. -Walloca Warn on all uses of "alloca" in the source. -Wauto-profile Output warnings about auto-profile inconsistencies. -Wcannot-profile Warn when profiling instrumentation was requested, but could not be ap- plied to a certain function. -Walloca-larger-than=byte-size Warns on calls to "alloca" with an integer argument whose value is ei- ther zero, or that is not bounded by a controlling predicate that lim- its its value to at most byte-size. It also warns for calls to "al- loca" where the bound value is unknown. Arguments of non-integer types are considered unbounded even if they appear to be constrained to the expected range. For example, a bounded case of "alloca" could be: void func (size_t n) { void *p; if (n <= 1000) p = alloca (n); else p = malloc (n); f (p); } In the above example, passing "-Walloca-larger-than=1000" would not is- sue a warning because the call to "alloca" is known to be at most 1000 bytes. However, if "-Walloca-larger-than=500" were passed, the com- piler would emit a warning. Unbounded uses, on the other hand, are uses of "alloca" with no con- trolling predicate constraining its integer argument. For example: void func () { void *p = alloca (n); f (p); } If "-Walloca-larger-than=500" were passed, the above would trigger a warning, but this time because of the lack of bounds checking. Note, that even seemingly correct code involving signed integers could cause a warning: void func (signed int n) { if (n < 500) { p = alloca (n); f (p); } } In the above example, n could be negative, causing a larger than ex- pected argument to be implicitly cast into the "alloca" call. This option also warns when "alloca" is used in a loop. -Walloca-larger-than=PTRDIFF_MAX is enabled by default but is usually only effective when -ftree-vrp is active (default for -O2 and above). See also -Wvla-larger-than=byte-size. -Wno-alloca-larger-than Disable -Walloca-larger-than= warnings. The option is equivalent to -Walloca-larger-than=SIZE_MAX or larger. -Warith-conversion Do warn about implicit conversions from arithmetic operations even when conversion of the operands to the same type cannot change their values. This affects warnings from -Wconversion, -Wfloat-conversion, and -Wsign-conversion. void f (char c, int i) { c = c + i; // warns with B<-Wconversion> c = c + 1; // only warns with B<-Warith-conversion> } -Warray-bounds -Warray-bounds=n Warn about out of bounds subscripts or offsets into arrays. This warn- ing is enabled by -Wall. It is more effective when -ftree-vrp is ac- tive (the default for -O2 and above) but a subset of instances are is- sued even without optimization. By default, the trailing array of a structure will be treated as a flexible array member by -Warray-bounds or -Warray-bounds=n if it is declared as either a flexible array member per C99 standard onwards ([]), a GCC zero-length array extension ([0]), or an one-element array ([1]). As a result, out of bounds subscripts or offsets into zero-length arrays or one-element arrays are not warned by default. You can add the option -fstrict-flex-arrays or -fstrict-flex-ar- rays=level to control how this option treat trailing array of a struc- ture as a flexible array member: when level<=1, no change to the default behavior. when level=2, additional warnings will be issued for out of bounds sub- scripts or offsets into one-element arrays; when level=3, in addition to level=2, additional warnings will be is- sued for out of bounds subscripts or offsets into zero-length arrays. -Warray-bounds=1 This is the default warning level of -Warray-bounds and is enabled by -Wall; higher levels are not, and must be explicitly requested. -Warray-bounds=2 This warning level also warns about the intermediate results of pointer arithmetic that may yield out of bounds values. This warn- ing level may give a larger number of false positives and is deac- tivated by default. -Wunterminated-string-initialization (C and Objective-C only) Warn about character arrays initialized as unterminated character se- quences with a string literal, unless the declaration being initialized has the "nonstring" attribute. For example: char arr[3] = "foo"; /* Warning. */ char arr2[3] __attribute__((nonstring)) = "bar"; /* No warning. */ This warning is enabled by -Wextra. If -Wc++-compat is enabled, the warning has slightly different wording and warns even if the declara- tion being initialized has the "nonstring" warning, as in C++ such ini- tializations are an error. -Warray-compare Warn about equality and relational comparisons between two operands of array type. This comparison was deprecated in C++20. For example: int arr1[5]; int arr2[5]; bool same = arr1 == arr2; -Warray-compare is enabled by -Wall. -Warray-parameter -Warray-parameter=n Warn about redeclarations of functions involving parameters of array or pointer types of inconsistent kinds or forms, and enable the detection of out-of-bounds accesses to such parameters by warnings such as -War- ray-bounds. If the first function declaration uses the array form for a parameter declaration, the bound specified in the array is assumed to be the min- imum number of elements expected to be provided in calls to the func- tion and the maximum number of elements accessed by it. Failing to provide arguments of sufficient size or accessing more than the maximum number of elements may be diagnosed by warnings such as -Warray-bounds or -Wstringop-overflow. At level 1, the warning diagnoses inconsisten- cies involving array parameters declared using the "T[static N]" form. For example, the warning triggers for the second declaration of "f" be- cause the first one with the keyword "static" specifies that the array argument must have at least four elements, while the second allows an array of any size to be passed to "f". void f (int[static 4]); void f (int[]); // warning (inconsistent array form) void g (void) { int *p = (int *)malloc (1 * sizeof (int)); f (p); // warning (array too small) ... } At level 2 the warning also triggers for redeclarations involving any other inconsistency in array or pointer argument forms denoting array sizes. Pointers and arrays of unspecified bound are considered equiva- lent and do not trigger a warning. void g (int*); void g (int[]); // no warning void g (int[8]); // warning (inconsistent array bound) -Warray-parameter=2 is included in -Wall. The -Wvla-parameter option triggers warnings for similar inconsistencies involving Variable Length Array arguments. The short form of the option -Warray-parameter is equivalent to -War- ray-parameter=2. The negative form -Wno-array-parameter is equivalent to -Warray-parameter=0. -Wattribute-alias=n -Wno-attribute-alias Warn about declarations using the "alias" and similar attributes whose target is incompatible with the type of the alias. -Wattribute-alias=1 The default warning level of the -Wattribute-alias option diagnoses incompatibilities between the type of the alias declaration and that of its target. Such incompatibilities are typically indica- tive of bugs. -Wattribute-alias=2 At this level -Wattribute-alias also diagnoses cases where the at- tributes of the alias declaration are more restrictive than the at- tributes applied to its target. These mismatches can potentially result in incorrect code generation. In other cases they may be benign and could be resolved simply by adding the missing attribute to the target. For comparison, see the -Wmissing-attributes op- tion, which controls diagnostics when the alias declaration is less restrictive than the target, rather than more restrictive. Attributes considered include "alloc_align", "alloc_size", "cold", "const", "hot", "leaf", "malloc", "nonnull", "noreturn", "nothrow", "pure", "returns_nonnull", and "returns_twice". -Wattribute-alias is equivalent to -Wattribute-alias=1. This is the default. You can disable these warnings with either -Wno-at- tribute-alias or -Wattribute-alias=0. -Wbidi-chars=[none|unpaired|any|ucn] Warn about possibly misleading UTF-8 bidirectional control characters in comments, string literals, character constants, and identifiers. Such characters can change left-to-right writing direction into right-to-left (and vice versa), which can cause confusion between the logical order and visual order. This may be dangerous; for instance, it may seem that a piece of code is not commented out, whereas it in fact is. There are three levels of warning supported by GCC. The default is -Wbidi-chars=unpaired, which warns about improperly terminated bidi contexts. -Wbidi-chars=none turns the warning off. -Wbidi-chars=any warns about any use of bidirectional control characters. By default, this warning does not warn about UCNs. It is, however, possible to turn on such checking by using -Wbidi-chars=unpaired,ucn or -Wbidi-chars=any,ucn. Using -Wbidi-chars=ucn is valid, and is equiva- lent to -Wbidi-chars=unpaired,ucn, if no previous -Wbidi-chars=any was specified. -Wbool-compare Warn about boolean expression compared with an integer value different from "true"/"false". For instance, the following comparison is always false: int n = 5; ... if ((n > 1) == 2) { ... } This warning is enabled by -Wall. -Wbool-operation Warn about suspicious operations on expressions of a boolean type. For instance, bitwise negation of a boolean is very likely a bug in the program. For C, this warning also warns about incrementing or decre- menting a boolean, which rarely makes sense. (In C++, decrementing a boolean is always invalid. Incrementing a boolean is invalid in C++17, and deprecated otherwise.) This warning is enabled by -Wall. -Wduplicated-branches Warn when an if-else has identical branches. This warning detects cases like if (p != NULL) return 0; else return 0; It doesn't warn when both branches contain just a null statement. This warning also warn for conditional operators: int i = x ? *p : *p; -Wduplicated-cond Warn about duplicated conditions in an if-else-if chain. For instance, warn for the following code: if (p->q != NULL) { ... } else if (p->q != NULL) { ... } -Wframe-address Warn when the __builtin_frame_address or __builtin_return_address is called with an argument greater than 0. Such calls may return indeter- minate values or crash the program. The warning is included in -Wall. -Wno-discarded-qualifiers (C and Objective-C only) Do not warn if type qualifiers on pointers are being discarded. Typi- cally, the compiler warns if a "const char *" variable is passed to a function that takes a "char *" parameter. This option can be used to suppress such a warning. -Wno-discarded-array-qualifiers (C and Objective-C only) Do not warn if type qualifiers on arrays which are pointer targets are being discarded. Typically, the compiler warns if a "const int (*)[]" variable is passed to a function that takes a "int (*)[]" parameter. This option can be used to suppress such a warning. -Wno-incompatible-pointer-types (C and Objective-C only) Do not warn when there is a conversion between pointers that have in- compatible types. This warning is for cases not covered by -Wno-pointer-sign, which warns for pointer argument passing or assign- ment with different signedness. By default, in C99 and later dialects of C, GCC treats this issue as an error. The error can be downgraded to a warning using -fpermissive (along with certain other errors), or for this error alone, with -Wno-error=incompatible-pointer-types. This warning is upgraded to an error by -pedantic-errors. -Wno-int-conversion (C and Objective-C only) Do not warn about incompatible integer to pointer and pointer to inte- ger conversions. This warning is about implicit conversions; for ex- plicit conversions the warnings -Wno-int-to-pointer-cast and -Wno-pointer-to-int-cast may be used. By default, in C99 and later dialects of C, GCC treats this issue as an error. The error can be downgraded to a warning using -fpermissive (along with certain other errors), or for this error alone, with -Wno-error=int-conversion. This warning is upgraded to an error by -pedantic-errors. -Wzero-as-null-pointer-constant Warn when a literal 0 is used as null pointer constant. -Wzero-length-bounds Warn about accesses to elements of zero-length array members that might overlap other members of the same object. Declaring interior zero-length arrays is discouraged because accesses to them are unde- fined. For example, the first two stores in function "bad" are diagnosed be- cause the array elements overlap the subsequent members "b" and "c". The third store is diagnosed by -Warray-bounds because it is beyond the bounds of the enclosing object. struct X { int a[0]; int b, c; }; struct X x; void bad (void) { x.a[0] = 0; // -Wzero-length-bounds x.a[1] = 1; // -Wzero-length-bounds x.a[2] = 2; // -Warray-bounds } Option -Wzero-length-bounds is enabled by -Warray-bounds. -Wno-div-by-zero Do not warn about compile-time integer division by zero. Float- ing-point division by zero is not warned about, as it can be a legiti- mate way of obtaining infinities and NaNs. -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 GCC to emit warnings from system headers as if they occurred in user code. However, note that using -Wall in conjunction with this option does not warn about unknown pragmas in system headers---for that, -Wun- known-pragmas must also be used. -Wtautological-compare Warn if a self-comparison always evaluates to true or false. This warning detects various mistakes such as: int i = 1; ... if (i > i) { ... } This warning also warns about bitwise comparisons that always evaluate to true or false, for instance: if ((a & 16) == 10) { ... } will always be false. This warning is enabled by -Wall. -Wtrailing-whitespace -Wtrailing-whitespace=kind Warn about trailing whitespace at the end of lines, including inside of comments, but excluding trailing whitespace in raw string literals. "-Wtrailing-whitespace" is equivalent to "-Wtrailing-whitespace=blanks" and warns just about trailing space and horizontal tab characters. "-Wtrailing-whitespace=any" warns about those or trailing form feed or vertical tab characters. "-Wno-trailing-whitespace" or "-Wtrail- ing-whitespace=none" disables the warning, which is the default. This is a coding style warning. -Wleading-whitespace=kind Warn about style issues in leading whitespace, but not about the amount of indentation. Some projects use coding styles where only spaces are used for indentation, others use only tabs, others use zero or more tabs (for multiples of "-ftabstop=n") followed by zero or fewer than n spaces. No warning is emitted on lines which contain solely whitespace (although "-Wtrailing-whitespace=" warning might be emitted), no warn- ings are emitted inside of raw string literals. Warnings are also emitted for leading whitespace inside of multi-line comments. "-Wlead- ing-whitespace=spaces" warns about leading whitespace other than spaces for projects which want to indent just by spaces. "-Wleading-white- space=tabs" warns about leading whitespace other than horizontal tabs for projects which want to indent just by horizontal tabs. "-Wlead- ing-whitespace=blanks" warns about leading whitespace other than spaces and horizontal tabs, or about horizontal tab after a space in the lead- ing whitespace, or about n or more consecutive spaces in leading white- space (where n is argument of "-ftabstop=n", 8 by default). "-Wlead- ing-whitespace=none" disables the warning, which is the default. This is a coding style warning. -Wtrampolines Warn about trampolines generated for pointers to nested functions. A trampoline is a small piece of data or code that is created at run time on the stack when the address of a nested function is taken, and is used to call the nested function indirectly. For some targets, it is made up of data only and thus requires no special treatment. But, for most targets, it is made up of code and thus requires the stack to be made executable in order for the program to work properly. -Wfloat-equal Warn if floating-point values are used in equality comparisons. The idea behind this is that sometimes it is convenient (for the pro- grammer) to consider floating-point values as approximations to infi- nitely precise real numbers. If you are doing this, then you need to compute (by analyzing 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 should check to see whether the two values have ranges that over- lap; and this is done with the relational operators, so equality com- parisons are probably mistaken. -Wtraditional (C and Objective-C only) Warn about certain constructs that behave differently in traditional and ISO C. Also warn about ISO C constructs that have no traditional C equivalent, and/or problematic constructs that should be avoided. * Macro parameters that appear within string literals in the macro body. In traditional C macro replacement takes place within string literals, but in ISO C it does not. * In traditional C, some preprocessor directives did not exist. Tra- ditional preprocessors only considered a line to be a directive if the # appeared in column 1 on the line. Therefore -Wtraditional warns about directives that traditional C understands but ignores because the # does not appear as the first character on the line. It also suggests you hide directives like "#pragma" not understood by traditional C by indenting them. Some traditional implementa- tions do not recognize "#elif", so this option suggests avoiding it altogether. * A function-like macro that appears without arguments. * The unary plus operator. * The U integer constant suffix, or the F or L floating-point con- stant suffixes. (Traditional C does support the L suffix on inte- ger constants.) Note, these suffixes appear in macros defined in the system headers of most modern systems, e.g. the _MIN/_MAX macros in "<limits.h>". Use of these macros in user code might normally lead to spurious warnings, however GCC's integrated pre- processor has enough context to avoid warning in these cases. * A function declared external in one block and then used after the end of the block. * A "switch" statement has an operand of type "long". * A non-"static" function declaration follows a "static" one. This construct is not accepted by some traditional C compilers. * The ISO 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 val- ues, which typically represent bit patterns, are not warned about. * Usage of ISO string concatenation is detected. * Initialization of automatic aggregates. * Identifier conflicts with labels. Traditional C lacks a separate namespace for labels. * Initialization of unions. If the initializer is zero, the warning is omitted. This is done under the assumption that the zero ini- tializer in user code appears conditioned on e.g. "__STDC__" to avoid missing initializer warnings and relies on default initial- ization to zero in the traditional C case. * Conversions by prototypes between fixed/floating-point values and vice versa. The absence of these prototypes when compiling with traditional C causes serious problems. This is a subset of the possible conversion warnings; for the full set use -Wtradi- tional-conversion. * Use of ISO C style function definitions. This warning intention- ally is not issued for prototype declarations or variadic functions because these ISO C features appear in your code when using libib- erty's traditional C compatibility macros, "PARAMS" and "VPARAMS". This warning is also bypassed for nested functions because that feature is already a GCC extension and thus not relevant to tradi- tional C compatibility. -Wtraditional-conversion (C and Objective-C only) 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 argu- ment except when the same as the default promotion. -Wdeclaration-after-statement (C and Objective-C only) Warn when a declaration is found after a statement in a block. This construct, known from C++, was introduced with ISO C99 and is by de- fault allowed in GCC. It is not supported by ISO C90. This warning is upgraded to an error by -pedantic-errors. -Wshadow Warn whenever a local variable or type declaration shadows another variable, parameter, type, class member (in C++), or instance variable (in Objective-C) or whenever a built-in function is shadowed. Note that in C++, the compiler warns if a local variable shadows an explicit typedef, but not if it shadows a struct/class/enum. If this warning is enabled, it includes also all instances of local shadowing. This means that -Wno-shadow=local and -Wno-shadow=compatible-local are ignored when -Wshadow is used. Same as -Wshadow=global. -Wno-shadow-ivar (Objective-C only) Do not warn whenever a local variable shadows an instance variable in an Objective-C method. -Wshadow=global Warn for any shadowing. Same as -Wshadow. -Wshadow=local Warn when a local variable shadows another local variable or parameter. -Wshadow=compatible-local Warn when a local variable shadows another local variable or parameter whose type is compatible with that of the shadowing variable. In C++, type compatibility here means the type of the shadowing variable can be converted to that of the shadowed variable. The creation of this flag (in addition to -Wshadow=local) is based on the idea that when a local variable shadows another one of incompatible type, it is most likely intentional, not a bug or typo, as shown in the following example: for (SomeIterator i = SomeObj.begin(); i != SomeObj.end(); ++i) { for (int i = 0; i < N; ++i) { ... } ... } Since the two variable "i" in the example above have incompatible types, enabling only -Wshadow=compatible-local does not emit a warning. Because their types are incompatible, if a programmer accidentally uses one in place of the other, type checking is expected to catch that and emit an error or warning. Use of this flag instead of -Wshadow=local can possibly reduce the number of warnings triggered by intentional shadowing. Note that this also means that shadowing "const char *i" by "char *i" does not emit a warning. This warning is also enabled by -Wshadow=local. -Wlarger-than=byte-size Warn whenever an object is defined whose size exceeds byte-size. -Wlarger-than=PTRDIFF_MAX is enabled by default. Warnings controlled by the option can be disabled either by specifying byte-size of SIZE_MAX or more or by -Wno-larger-than. Also warn for calls to bounded functions such as "memchr" or "strnlen" that specify a bound greater than the largest possible object, which is PTRDIFF_MAX bytes by default. These warnings can only be disabled by -Wno-larger-than. -Wno-larger-than Disable -Wlarger-than= warnings. The option is equivalent to -Wlarger-than=SIZE_MAX or larger. -Wframe-larger-than=byte-size Warn if the size of a function frame exceeds byte-size. The computa- tion done to determine the stack frame size is approximate and not con- servative. The actual requirements may be somewhat greater than byte-size even if you do not get a warning. In addition, any space al- located via "alloca", variable-length arrays, or related constructs is not included by the compiler when determining whether or not to issue a warning. -Wframe-larger-than=PTRDIFF_MAX is enabled by default. Warn- ings controlled by the option can be disabled either by specifying byte-size of SIZE_MAX or more or by -Wno-frame-larger-than. -Wno-frame-larger-than Disable -Wframe-larger-than= warnings. The option is equivalent to -Wframe-larger-than=SIZE_MAX or larger. -Wfree-nonheap-object Warn when attempting to deallocate an object that was either not allo- cated on the heap, or by using a pointer that was not returned from a prior call to the corresponding allocation function. For example, be- cause the call to "stpcpy" returns a pointer to the terminating nul character and not to the beginning of the object, the call to "free" below is diagnosed. void f (char *p) { p = stpcpy (p, "abc"); // ... free (p); // warning } -Wfree-nonheap-object is included in -Wall. -Wstack-usage=byte-size Warn if the stack usage of a function might exceed byte-size. The com- putation done to determine the stack usage is conservative. Any space allocated via "alloca", variable-length arrays, or related constructs is included by the compiler when determining whether or not to issue a warning. The message is in keeping with the output of -fstack-usage. * If the stack usage is fully static but exceeds the specified amount, it's: warning: stack usage is 1120 bytes * If the stack usage is (partly) dynamic but bounded, it's: warning: stack usage might be 1648 bytes * If the stack usage is (partly) dynamic and not bounded, it's: warning: stack usage might be unbounded -Wstack-usage=PTRDIFF_MAX is enabled by default. Warnings controlled by the option can be disabled either by specifying byte-size of SIZE_MAX or more or by -Wno-stack-usage. -Wno-stack-usage Disable -Wstack-usage= warnings. The option is equivalent to -Wstack-usage=SIZE_MAX or larger. -Wunsafe-loop-optimizations Warn if the loop cannot be optimized because the compiler cannot assume anything on the bounds of the loop indices. With -funsafe-loop-opti- mizations warn if the compiler makes such assumptions. -Wno-pedantic-ms-format (MinGW targets only) When used in combination with -Wformat and -pedantic without GNU exten- sions, this option disables the warnings about non-ISO "printf" / "scanf" format width specifiers "I32", "I64", and "I" used on Windows targets, which depend on the MS runtime. -Wpointer-arith Warn about anything that depends on the "size of" a function type or of "void". GNU C assigns these types a size of 1, for convenience in cal- culations with "void *" pointers and pointers to functions. In C++, warn also when an arithmetic operation involves "NULL". This warning is also enabled by -Wpedantic. This warning is upgraded to an error by -pedantic-errors. -Wno-pointer-compare Do not warn if a pointer is compared with a zero character constant. This usually means that the pointer was meant to be dereferenced. For example: const char *p = foo (); if (p == '\0') return 42; Note that the code above is invalid in C++11. This warning is enabled by default. -Wno-tsan Disable warnings about unsupported features in ThreadSanitizer. ThreadSanitizer does not support "std::atomic_thread_fence" and can re- port false positives. -Wtype-limits Warn if a comparison is always true or always false due to the limited range of the data type, but do not warn for constant expressions. For example, warn if an unsigned variable is compared against zero with "<" or ">=". This warning is also enabled by -Wextra. -Wabsolute-value (C and Objective-C only) Warn for calls to standard functions that compute the absolute value of an argument when a more appropriate standard function is available. For example, calling abs(3.14) triggers the warning because the appro- priate function to call to compute the absolute value of a double argu- ment is "fabs". The option also triggers warnings when the argument in a call to such a function has an unsigned type. This warning can be suppressed with an explicit type cast and it is also enabled by -Wex- tra. -Wcomment -Wcomments Warn whenever a comment-start sequence /* appears in a /* comment, or whenever a backslash-newline appears in a // comment. This warning is enabled by -Wall. -Wtrigraphs Warn if any trigraphs are encountered that might change the meaning of the program. Trigraphs within comments are not warned about, except those that would form escaped newlines. This option is implied by -Wall. If -Wall is not given, this option is still enabled unless trigraphs are enabled. To get trigraph conversion without warnings, but get the other -Wall warnings, use -trigraphs -Wall -Wno-trigraphs. -Wundef Warn if an undefined identifier is evaluated in an "#if" directive. Such identifiers are replaced with zero. -Wexpansion-to-defined Warn whenever defined is encountered in the expansion of a macro (in- cluding the case where the macro is expanded by an #if directive). Such usage is not portable. This warning is also enabled by -Wpedantic and -Wextra. -Wunused-macros Warn about macros defined in the main file that are unused. A macro is used if it is expanded or tested for existence at least once. The pre- processor also warns if the macro has not been used at the time it is redefined or undefined. Built-in macros, macros defined on the command line, and macros defined in include files are not warned about. Note: If a macro is actually used, but only used in skipped conditional blocks, then the preprocessor reports it as unused. To avoid the warn- ing in such a case, you might improve the scope of the macro's defini- tion by, for example, moving it into the first skipped block. Alterna- tively, you could provide a dummy use with something like: #if defined the_macro_causing_the_warning #endif -Wno-endif-labels Do not warn whenever an "#else" or an "#endif" are followed by text. This sometimes happens in older programs with code of the form #if FOO ... #else FOO ... #endif FOO The second and third "FOO" should be in comments. This warning is on by default. -Wbad-function-cast (C and Objective-C only) Warn when a function call is cast to a non-matching type. For example, warn if a call to a function returning an integer type is cast to a pointer type. -Wc90-c99-compat (C and Objective-C only) Warn about features not present in ISO C90, but present in ISO C99. For instance, warn about use of variable length arrays, "long long" type, "bool" type, compound literals, designated initializers, and so on. This option is independent of the standards mode. Warnings are disabled in the expression that follows "__extension__". -Wc99-c11-compat (C and Objective-C only) Warn about features not present in ISO C99, but present in ISO C11. For instance, warn about use of anonymous structures and unions, "_Atomic" type qualifier, "_Thread_local" storage-class specifier, "_Alignas" specifier, "Alignof" operator, "_Generic" keyword, and so on. This option is independent of the standards mode. Warnings are disabled in the expression that follows "__extension__". -Wc11-c23-compat (C and Objective-C only) -Wc11-c2x-compat (C and Objective-C only) Warn about features not present in ISO C11, but present in ISO C23. For instance, warn about omitting the string in "_Static_assert", use of [[]] syntax for attributes, use of decimal floating-point types, and so on. This option is independent of the standards mode. Warnings are disabled in the expression that follows "__extension__". The name -Wc11-c2x-compat is deprecated. When not compiling in C23 mode, these warnings are upgraded to errors by -pedantic-errors. -Wc23-c2y-compat (C and Objective-C only) -Wc23-c2y-compat (C and Objective-C only) Warn about features not present in ISO C23, but present in ISO C2Y. For instance, warn about "_Generic" selecting with a type name instead of an expression. This option is independent of the standards mode. Warnings are disabled in the expression that follows "__extension__". When not compiling in C2Y mode, these warnings are upgraded to errors by -pedantic-errors. -Wc++-compat (C and Objective-C only) Warn about ISO C constructs that are outside of the common subset of ISO C and ISO C++, e.g. request for implicit conversion from "void *" to a pointer to non-"void" type. -Wc++11-compat (C++ and Objective-C++ only) Warn about C++ constructs whose meaning differs between ISO C++ 1998 and ISO C++ 2011, e.g., identifiers in ISO C++ 1998 that are keywords in ISO C++ 2011. This warning turns on -Wnarrowing and is enabled by -Wall. -Wc++14-compat (C++ and Objective-C++ only) Warn about C++ constructs whose meaning differs between ISO C++ 2011 and ISO C++ 2014. This warning is enabled by -Wall. -Wc++17-compat (C++ and Objective-C++ only) Warn about C++ constructs whose meaning differs between ISO C++ 2014 and ISO C++ 2017. This warning is enabled by -Wall. -Wc++20-compat (C++ and Objective-C++ only) Warn about C++ constructs whose meaning differs between ISO C++ 2017 and ISO C++ 2020. This warning is enabled by -Wall. -Wc++26-compat (C++ and Objective-C++ only) Warn about C++ constructs whose meaning differs between ISO C++ 2023 and upcoming ISO C++ 2026. This warning is enabled by -Wall. -Wno-c++11-extensions (C++ and Objective-C++ only) Do not warn about C++11 constructs in code being compiled using an older C++ standard. Even without this option, some C++11 constructs will only be diagnosed if -Wpedantic is used. -Wno-c++14-extensions (C++ and Objective-C++ only) Do not warn about C++14 constructs in code being compiled using an older C++ standard. Even without this option, some C++14 constructs will only be diagnosed if -Wpedantic is used. -Wno-c++17-extensions (C++ and Objective-C++ only) Do not warn about C++17 constructs in code being compiled using an older C++ standard. Even without this option, some C++17 constructs will only be diagnosed if -Wpedantic is used. -Wno-c++20-extensions (C++ and Objective-C++ only) Do not warn about C++20 constructs in code being compiled using an older C++ standard. Even without this option, some C++20 constructs will only be diagnosed if -Wpedantic is used. -Wno-c++23-extensions (C++ and Objective-C++ only) Do not warn about C++23 constructs in code being compiled using an older C++ standard. Even without this option, some C++23 constructs will only be diagnosed if -Wpedantic is used. -Wno-c++26-extensions (C++ and Objective-C++ only) Do not warn about C++26 constructs in code being compiled using an older C++ standard. Even without this option, some C++26 constructs will only be diagnosed if -Wpedantic is used. -Wcast-qual Warn whenever a pointer is cast so as to remove a type qualifier from the target type. For example, warn if a "const char *" is cast to an ordinary "char *". Also warn when making a cast that introduces a type qualifier in an un- safe way. For example, casting "char **" to "const char **" is unsafe, as in this example: /* p is char ** value. */ const char **q = (const char **) p; /* Assignment of readonly string to const char * is OK. */ *q = "string"; /* Now char** pointer points to read-only memory. */ **p = 'b'; -Wcast-align Warn whenever a pointer is cast such that the required alignment of the target is increased. For example, warn if a "char *" is cast to an "int *" on machines where integers can only be accessed at two- or four-byte boundaries. Warn whenever a pointer is cast such that the required alignment of the target is increased. For example, warn if a "char *" is cast to an "int *" regardless of the target machine. -Wcast-function-type Warn when a function pointer is cast to an incompatible function pointer. In a cast involving function types with a variable argument list only the types of initial arguments that are provided are consid- ered. Any parameter of pointer-type matches any other pointer-type. Any benign differences in integral types are ignored, like "int" vs. "long" on ILP32 targets. Likewise type qualifiers are ignored. The function type "void (*) (void)" is special and matches everything, which can be used to suppress this warning. In a cast involving pointer to member types this warning warns whenever the type cast is changing the pointer to member type. This warning is enabled by -Wex- tra. -Wcast-user-defined Warn when a cast to reference type does not involve a user-defined con- version that the programmer might expect to be called. struct A { operator const int&(); } a; auto r = (int&)a; // warning This warning is enabled by default. -Wwrite-strings When compiling C, give string constants the type "const char[length]" so that copying the address of one into a non-"const" "char *" pointer produces a warning. These warnings 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 "const" in declarations and prototypes. Oth- erwise, it is just a nuisance. This is why we did not make -Wall re- quest these warnings. When compiling C++, warn about the deprecated conversion from string literals to "char *". This warning is enabled by default for C++ pro- grams. This warning is upgraded to an error by -pedantic-errors in C++11 mode or later. -Wclobbered Warn for variables that might be changed by "longjmp" or "vfork". This warning is also enabled by -Wextra. -Wno-complain-wrong-lang By default, language front ends complain when a command-line option is valid, but not applicable to that front end. This may be disabled with -Wno-complain-wrong-lang, which is mostly useful when invoking a single compiler driver for multiple source files written in different lan- guages, for example: $ g++ -fno-rtti a.cc b.f90 The driver g++ invokes the C++ front end to compile a.cc and the For- tran front end to compile b.f90. The latter front end diagnoses f951: Warning: command-line option '-fno-rtti' is valid for C++/D/ObjC++ but not for Fortran, which may be disabled with -Wno-complain-wrong-lang. This option can also be used to disable warnings like cc1plus: note: CTF debug info requested, but not supported for 'GNU C++20' frontend produced by -gctf or -gsctf for unsupported languages. -Wcompare-distinct-pointer-types (C and Objective-C only) Warn if pointers of distinct types are compared without a cast. This warning is enabled by default. -Wconversion Warn for implicit conversions that may alter a value. This includes conversions between real and integer, like "abs (x)" when "x" is "dou- ble"; conversions between signed and unsigned, like "unsigned ui = -1"; and conversions to smaller types, like "sqrtf (M_PI)". Do not warn for explicit casts like "abs ((int) x)" and "ui = (unsigned) -1", or if the value is not changed by the conversion like in "abs (2.0)". Warnings about conversions between signed and unsigned integers can be disabled by using -Wno-sign-conversion. For C++, also warn for confusing overload resolution for user-defined conversions; and conversions that never use a type conversion operator: conversions to "void", the same type, a base class or a reference to them. Warnings about conversions between signed and unsigned integers are disabled by default in C++ unless -Wsign-conversion is explicitly enabled. Warnings about conversion from arithmetic on a small type back to that type are only given with -Warith-conversion. -Wdangling-else Warn about constructions where there may be confusion to which "if" statement an "else" branch belongs. Here is an example of such a case: { if (a) if (b) foo (); else bar (); } In C/C++, every "else" branch belongs to the innermost possible "if" statement, which in this example is "if (b)". This is often not what the programmer expected, as illustrated in the above example by inden- tation the programmer chose. When there is the potential for this con- fusion, GCC issues a warning when this flag is specified. To eliminate the warning, add explicit braces around the innermost "if" statement so there is no way the "else" can belong to the enclosing "if". The re- sulting code looks like this: { if (a) { if (b) foo (); else bar (); } } This warning is enabled by -Wparentheses. -Wdangling-pointer -Wdangling-pointer=n Warn about uses of pointers (or C++ references) to objects with auto- matic storage duration after their lifetime has ended. This includes local variables declared in nested blocks, compound literals and other unnamed temporary objects. In addition, warn about storing the address of such objects in escaped pointers. The warning is enabled at all op- timization levels but may yield different results with optimization than without. -Wdangling-pointer=1 At level 1, the warning diagnoses only unconditional uses of dan- gling pointers. -Wdangling-pointer=2 At level 2, in addition to unconditional uses the warning also di- agnoses conditional uses of dangling pointers. The short form -Wdangling-pointer is equivalent to -Wdan- gling-pointer=2, while -Wno-dangling-pointer and -Wdangling-pointer=0 have the same effect of disabling the warnings. -Wdangling-pointer=2 is included in -Wall. This example triggers the warning at level 1; the address of the un- named temporary is unconditionally referenced outside of its scope. char f (char c1, char c2, char c3) { char *p; { p = (char[]) { c1, c2, c3 }; } // warning: using dangling pointer 'p' to an unnamed temporary return *p; } In the following function the store of the address of the local vari- able "x" in the escaped pointer *p triggers the warning at level 1. void g (int **p) { int x = 7; // warning: storing the address of local variable 'x' in '*p' *p = &x; } In this example, the array a is out of scope when the pointer s is used. Since the code that sets "s" is conditional, the warning trig- gers at level 2. extern void frob (const char *); void h (char *s) { if (!s) { char a[12] = "tmpname"; s = a; } // warning: dangling pointer 's' to 'a' may be used frob (s); } -Wdate-time Warn when macros "__TIME__", "__DATE__" or "__TIMESTAMP__" are encoun- tered as they might prevent bitwise-identical reproducible compila- tions. -Wempty-body Warn if an empty body occurs in an "if", "else" or "do while" state- ment. This warning is also enabled by -Wextra. -Wno-endif-labels Do not warn about stray tokens after "#else" and "#endif". -Wenum-compare Warn about a comparison between values of different enumerated types. In C++, enumerated type mismatches in conditional expressions are also diagnosed and the warning is enabled by default. In C, this warning is enabled by -Wall. -Wenum-conversion Warn when a value of enumerated type is implicitly converted to a dif- ferent enumerated type. This warning is enabled by -Wextra in C. -Wenum-int-mismatch (C and Objective-C only) Warn about mismatches between an enumerated type and an integer type in declarations. For example: enum E { l = -1, z = 0, g = 1 }; int foo(void); enum E foo(void); In C, an enumerated type is compatible with "char", a signed integer type, or an unsigned integer type. However, since the choice of the underlying type of an enumerated type is implementation-defined, such mismatches may cause portability issues. In C++, such mismatches are an error. In C, this warning is enabled by -Wall and -Wc++-compat. -Wjump-misses-init (C, Objective-C only) Warn if a "goto" statement or a "switch" statement jumps forward across the initialization of a variable, or jumps backward to a label after the variable has been initialized. This only warns about variables that are initialized when they are declared. This warning is only sup- ported for C and Objective-C; in C++ this sort of branch is an error in any case. -Wjump-misses-init is included in -Wc++-compat. It can be disabled with the -Wno-jump-misses-init option. -Wsign-compare Warn when a comparison between signed and unsigned values could produce an incorrect result when the signed value is converted to unsigned. In C++, this warning is also enabled by -Wall. In C, it is also enabled by -Wextra. -Wsign-conversion Warn for implicit conversions that may change the sign of an integer value, like assigning a signed integer expression to an unsigned inte- ger variable. An explicit cast silences the warning. In C, this option is enabled also by -Wconversion. -Wflex-array-member-not-at-end (C and C++ only) Warn when a structure containing a C99 flexible array member as the last field is not at the end of another structure. This warning warns e.g. about struct flex { int length; char data[]; }; struct mid_flex { int m; struct flex flex_data; int n; }; -Wfloat-conversion Warn for implicit conversions that reduce the precision of a real value. This includes conversions from real to integer, and from higher precision real to lower precision real values. This option is also en- abled by -Wconversion. -Wno-scalar-storage-order Do not warn on suspicious constructs involving reverse scalar storage order. -Wsizeof-array-div Warn about divisions of two sizeof operators when the first one is ap- plied to an array and the divisor does not equal the size of the array element. In such a case, the computation will not yield the number of elements in the array, which is likely what the user intended. This warning warns e.g. about int fn () { int arr[10]; return sizeof (arr) / sizeof (short); } This warning is enabled by -Wall. -Wsizeof-pointer-div Warn for suspicious divisions of two sizeof expressions that divide the pointer size by the element size, which is the usual way to compute the array size but won't work out correctly with pointers. This warning warns e.g. about "sizeof (ptr) / sizeof (ptr[0])" if "ptr" is not an array, but a pointer. This warning is enabled by -Wall. -Wsizeof-pointer-memaccess Warn for suspicious length parameters to certain string and memory built-in functions if the argument uses "sizeof". This warning trig- gers for example for "memset (ptr, 0, sizeof (ptr));" if "ptr" is not an array, but a pointer, and suggests a possible fix, or about "memcpy (&foo, ptr, sizeof (&foo));". -Wsizeof-pointer-memaccess also warns about calls to bounded string copy functions like "strncat" or "strncpy" that specify as the bound a "sizeof" expression of the source array. For example, in the following function the call to "strncat" specifies the size of the source string as the bound. That is almost certainly a mistake and so the call is diagnosed. void make_file (const char *name) { char path[PATH_MAX]; strncpy (path, name, sizeof path - 1); strncat (path, ".text", sizeof ".text"); ... } The -Wsizeof-pointer-memaccess option is enabled by -Wall. -Wno-sizeof-array-argument Do not warn when the "sizeof" operator is applied to a parameter that is declared as an array in a function definition. This warning is en- abled by default for C and C++ programs. -Wmemset-elt-size Warn for suspicious calls to the "memset" built-in function, if the first argument references an array, and the third argument is a number equal to the number of elements, but not equal to the size of the array in memory. This indicates that the user has omitted a multiplication by the element size. This warning is enabled by -Wall. -Wmemset-transposed-args Warn for suspicious calls to the "memset" built-in function where the second argument is not zero and the third argument is zero. For exam- ple, the call "memset (buf, sizeof buf, 0)" is diagnosed because "mem- set (buf, 0, sizeof buf)" was meant instead. The diagnostic is only emitted if the third argument is a literal zero. Otherwise, if it is an expression that is folded to zero, or a cast of zero to some type, it is far less likely that the arguments have been mistakenly trans- posed and no warning is emitted. This warning is enabled by -Wall. -Waddress Warn about suspicious uses of address expressions. These include com- paring the address of a function or a declared object to the null pointer constant such as in void f (void); void g (void) { if (!f) // warning: expression evaluates to false abort (); } comparisons of a pointer to a string literal, such as in void f (const char *x) { if (x == "abc") // warning: expression evaluates to false puts ("equal"); } and tests of the results of pointer addition or subtraction for equal- ity to null, such as in void f (const int *p, int i) { return p + i == NULL; } Such uses typically indicate a programmer error: the address of most functions and objects necessarily evaluates to true (the exception are weak symbols), so their use in a conditional might indicate missing parentheses in a function call or a missing dereference in an array ex- pression. The subset of the warning for object pointers can be sup- pressed by casting the pointer operand to an integer type such as "intptr_t" or "uintptr_t". Comparisons against string literals result in unspecified behavior and are not portable, and suggest the intent was to call "strcmp". The warning is suppressed if the suspicious ex- pression is the result of macro expansion. -Waddress is enabled by -Wall. -Wno-address-of-packed-member Do not warn when the address of packed member of struct or union is taken, which usually results in an unaligned pointer value. This is enabled by default. -Wlogical-op Warn about suspicious uses of logical operators in expressions. This includes using logical operators in contexts where a bitwise operator is likely to be expected. Also warns when the operands of a logical operator are the same: extern int a; if (a < 0 && a < 0) { ... } -Wconstant-logical-operand Warn about another case of suspicious uses of logical operators in ex- pressions, when neither operand of a logical operator is boolean and one of the operands is (or folds into) a constant other than 0 or 1, or enumerator with value 1 if the enumeral type contains enumerators with values other than 0 or 1. In such case the warning will suggest using corresponding bitwise operator. extern int a; if (a && 64) { ... } If the warning is a false positive, one can clarify the code by using e.g. "a && (64 != 0)" instead. -Wlogical-not-parentheses Warn about logical not used on the left hand side operand of a compari- son. This option does not warn if the right operand is considered to be a boolean expression. Its purpose is to detect suspicious code like the following: int a; ... if (!a > 1) { ... } It is possible to suppress the warning by wrapping the LHS into paren- theses: if ((!a) > 1) { ... } This warning is enabled by -Wall. -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.) -Wno-aggressive-loop-optimizations Do not warn if the compiler detects undefined behavior in a loop with a constant number of iterations. -Waggressive-loop-optimizations is en- abled by default. -Wno-attributes Do not warn if an unexpected "__attribute__" is used, such as unrecog- nized attributes, function attributes applied to variables, etc. This does not stop errors for incorrect use of supported attributes. Warnings about ill-formed uses of standard attributes are upgraded to errors by -pedantic-errors. Additionally, using -Wno-attributes=, it is possible to suppress warn- ings about unknown scoped attributes (in C++11 and C23). For example, -Wno-attributes=vendor::attr disables warning about the following dec- laration: [[vendor::attr]] void f(); It is also possible to disable warning about all attributes in a name- space using -Wno-attributes=vendor:: which prevents warning about both of these declarations: [[vendor::safe]] void f(); [[vendor::unsafe]] void f2(); Note that -Wno-attributes= does not imply -Wno-attributes. -Wno-builtin-declaration-mismatch Warn if a built-in function is declared with an incompatible signature or as a non-function, or when a built-in function declared with a type that does not include a prototype is called with arguments whose pro- moted types do not match those expected by the function. When -Wextra is specified, also warn when a built-in function that takes arguments is declared without a prototype. The -Wbuiltin-declaration-mismatch warning is enabled by default. To avoid the warning include the appro- priate header to bring the prototypes of built-in functions into scope. For example, the call to "memset" below is diagnosed by the warning be- cause the function expects a value of type "size_t" as its argument but the type of 32 is "int". With -Wextra, the declaration of the function is diagnosed as well. extern void* memset (); void f (void *d) { memset (d, '\0', 32); } -Wno-builtin-macro-redefined Do not warn if certain built-in macros are redefined. This suppresses warnings for redefinition of "__TIMESTAMP__", "__TIME__", "__DATE__", "__FILE__", and "__BASE_FILE__". -Wkeyword-macro Warn if a keyword is defined as a macro or undefined. For C++ identi- fiers with special meaning or standard attribute identifiers are diag- nosed as well. This warning is enabled by default for C++26 if "-Wpedantic" and emits a pedwarn in that case. -Wfree-labels (C and Objective-C only) Warn if a label is applied to a non-statement, or occurs at the end of a compound statement. Such labels are allowed by C23 and later di- alects of C, and are available as a GCC extension in all other di- alects. This warning is also enabled by -Wc11-c23-compat. It is turned into an error if building for a C version before C23 by -pedantic-errors. -Wheader-guard Warn if a valid preprocessor header multiple inclusion guard has a "#define" directive right after "#ifndef" or "#if !defined" directive for the multiple inclusion guard, which defines a different macro from the guard macro with a similar name, the actual multiple inclusion guard macro isn't defined at the corresponding "#ifndef" directive at the end of the header, and the "#define" directive defines an ob- ject-like macro with empty definition. In such case, it often is just a misspelled guard name, either in the "#ifndef" or "#if !defined" di- rective or in the subsequent "#define" directive. This warning is en- abled by -Wall. -Wstrict-prototypes (C and Objective-C only) Warn if a function is declared or defined without specifying the argu- ment types. (An old-style function definition is permitted without a warning if preceded by a declaration that specifies the argument types.) -Wold-style-declaration (C and Objective-C only) Warn for obsolescent usages, according to the C Standard, in a declara- tion. For example, warn if storage-class specifiers like "static" are not the first things in a declaration. This warning is also enabled by -Wextra. -Wold-style-definition (C and Objective-C only) Warn if an old-style function definition is used. A warning is given even if there is a previous prototype. A definition using () is not considered an old-style definition in C23 mode, because it is equiva- lent to (void) in that case, but is considered an old-style definition for older standards. -Wmultiple-parameter-fwd-decl-lists (C and Objective-C only) Warn if more than one list of forward declarations of parameters ap- pears in a function prototype. This warning is also enabled by -Wex- tra. -Wdeprecated-non-prototype (C and Objective-C only) Warn if a function declared with an empty parameter list () is called with one or more arguments, or if a function definition with one or more parameters is encountered after such a declaration. Both cases are errors in C23 and later dialects of C. This warning is also enabled by -Wc11-c23-compat. -Wmissing-parameter-name (C and Objective-C only) Warn if a function definition omits a parameter name, specifying only its type. This can be used to document that a parameter is unused in the definition. It is part of C23 and later dialects of C, and avail- able as a GCC extension in all other dialects. This warning is also enabled by -Wc11-c23-compat. It is turned into an error if building for a C version before C23 by -pedantic-errors. -Wmissing-parameter-type (C and Objective-C only) A function parameter is declared without a type specifier in K&R-style functions: void foo(bar) { } This warning is also enabled by -Wextra. -Wno-declaration-missing-parameter-type (C and Objective-C only) Do not warn if a function declaration contains a parameter name without a type. Such function declarations do not provide a function prototype and prevent most type checking in function calls. This warning is enabled by default. In C99 and later dialects of C, it is treated as an error. The error can be downgraded to a warning using -fpermissive (along with certain other errors), or for this error alone, with -Wno-error=declaration-missing-parameter-type. This warning is upgraded to an error by -pedantic-errors. -Wmissing-prototypes (C and Objective-C only) Warn if a global function is defined without a previous prototype dec- laration. This warning is issued even if the definition itself pro- vides a prototype. Use this option to detect global functions that do not have a matching prototype declaration in a header file. This op- tion is not valid for C++ because all function declarations provide prototypes and a non-matching declaration declares an overload rather than conflict with an earlier declaration. Use -Wmissing-declarations to detect missing declarations in C++. -Wmissing-variable-declarations (C and Objective-C only) Warn if a global variable is defined without a previous declaration. Use this option to detect global variables that do not have a matching extern declaration in a header file. -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 op- tion to detect global functions that are not declared in header files. In C, no warnings are issued for functions with previous non-prototype declarations; use -Wmissing-prototypes to detect missing prototypes. In C++, no warnings are issued for function templates, or for inline functions, or for functions in anonymous namespaces. -Wmissing-field-initializers Warn if a structure's initializer has some fields missing. For exam- ple, the following code causes such a warning, because "x.h" is implic- itly zero: struct s { int f, g, h; }; struct s x = { 3, 4 }; In C this option does not warn about designated initializers, so the following modification does not trigger a warning: struct s { int f, g, h; }; struct s x = { .f = 3, .g = 4 }; In C this option does not warn about the universal zero initializer { 0 }: struct s { int f, g, h; }; struct s x = { 0 }; Likewise, in C++ this option does not warn about the empty { } initial- izer, for example: struct s { int f, g, h; }; s x = { }; This warning is included in -Wextra. To get other -Wextra warnings without this one, use -Wextra -Wno-missing-field-initializers. -Wno-missing-requires By default, the compiler warns about a concept-id appearing as a C++20 simple-requirement: bool satisfied = requires { C<T> }; Here satisfied will be true if C<T> is a valid expression, which it is for all T. Presumably the user meant to write bool satisfied = requires { requires C<T> }; so satisfied is only true if concept C is satisfied for type T. This warning can be disabled with -Wno-missing-requires. -Wno-missing-template-keyword The member access tokens ., -> and :: must be followed by the "tem- plate" keyword if the parent object is dependent and the member being named is a template. template <class X> void DoStuff (X x) { x.template DoSomeOtherStuff<X>(); // Good. x.DoMoreStuff<X>(); // Warning, x is dependent. } In rare cases it is possible to get false positives. To silence this, wrap the expression in parentheses. For example, the following is treated as a template, even where m and N are integers: void NotATemplate (my_class t) { int N = 5; bool test = t.m < N > (0); // Treated as a template. test = (t.m < N) > (0); // Same meaning, but not treated as a template. } This warning can be disabled with -Wno-missing-template-keyword. -Wno-multichar Do not warn if a multicharacter constant ('FOOF') is used. Usually they indicate a typo in the user's code, as they have implementa- tion-defined values, and should not be used in portable code. -Wnormalized=[none|id|nfc|nfkc] In ISO C and ISO C++, two identifiers are different if they are differ- ent sequences of characters. However, sometimes when characters out- side the basic ASCII character set are used, you can have two different character sequences that look the same. To avoid confusion, the ISO 10646 standard sets out some normalization rules which when applied en- sure that two sequences that look the same are turned into the same se- quence. GCC can warn you if you are using identifiers that have not been normalized; this option controls that warning. There are four levels of warning supported by GCC. The default is -Wnormalized=nfc, which warns about any identifier that is not in the ISO 10646 "C" normalized form, NFC. NFC is the recommended form for most uses. It is equivalent to -Wnormalized. Unfortunately, there are some characters allowed in identifiers by ISO C and ISO C++ that, when turned into NFC, are not allowed in identi- fiers. That is, there's no way to use these symbols in portable ISO C or C++ and have all your identifiers in NFC. -Wnormalized=id sup- presses the warning for these characters. It is hoped that future ver- sions of the standards involved will correct this, which is why this option is not the default. You can switch the warning off for all characters by writing -Wnormal- ized=none or -Wno-normalized. You should only do this if you are using some other normalization scheme (like "D"), because otherwise you can easily create bugs that are literally impossible to see. Some characters in ISO 10646 have distinct meanings but look identical in some fonts or display methodologies, especially once formatting has been applied. For instance "\u207F", "SUPERSCRIPT LATIN SMALL LETTER N", displays just like a regular "n" that has been placed in a super- script. ISO 10646 defines the NFKC normalization scheme to convert all these into a standard form as well, and GCC warns if your code is not in NFKC if you use -Wnormalized=nfkc. This warning is comparable to warning about every identifier that contains the letter O because it might be confused with the digit 0, and so is not the default, but may be useful as a local coding convention if the programming environment cannot be fixed to display these characters distinctly. -Wno-attribute-warning Do not warn about usage of functions declared with "warning" attribute. By default, this warning is enabled. -Wno-attribute-warning can be used to disable the warning or -Wno-error=attribute-warning can be used to disable the error when compiled with -Werror flag. -Wno-deprecated Do not warn about usage of deprecated features. In C++, explicitly specifying -Wdeprecated also enables warnings about some features that are deprecated in later language standards, specifi- cally -Wcomma-subscript, -Wvolatile, -Wdeprecated-enum-float-conver- sion, -Wdeprecated-enum-enum-conversion, -Wdeprecated-literal-operator, and -Wdeprecated-variadic-comma-omission. -Wno-deprecated-declarations Do not warn about uses of functions, variables, or types marked as dep- recated by using the "deprecated" attribute. -Wno-deprecated-openmp Do not warn about deprecated OpenMP code. -Wno-overflow Do not warn about compile-time overflow in constant expressions. -Wno-odr Warn about One Definition Rule violations during link-time optimiza- tion. Enabled by default. -Wopenacc-parallelism Warn about potentially suboptimal choices related to OpenACC paral- lelism. -Wno-openmp Warn about suspicious OpenMP code. -Wopenmp-simd Warn if the vectorizer cost model overrides the OpenMP simd directive set by user. The -fsimd-cost-model=unlimited option can be used to re- lax the cost model. -Woverride-init (C and Objective-C only) Warn if an initialized field without side effects is overridden when using designated initializers. This warning is included in -Wextra. To get other -Wextra warnings without this one, use -Wextra -Wno-override-init. -Wno-override-init-side-effects (C and Objective-C only) Do not warn if an initialized field with side effects is overridden when using designated initializers. This warning is enabled by de- fault. -Wpacked Warn if a structure is given the packed attribute, but the packed at- tribute 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.x" in "struct bar" is misaligned even though "struct bar" does not itself have the packed attribute: struct foo { int x; char a, b, c, d; } __attribute__((packed)); struct bar { char z; struct foo f; }; -Wnopacked-bitfield-compat The 4.1, 4.2 and 4.3 series of GCC ignore the "packed" attribute on bit-fields of type "char". This was fixed in GCC 4.4 but the change can lead to differences in the structure layout. GCC informs you when the offset of such a field has changed in GCC 4.4. For example there is no longer a 4-bit padding between field "a" and "b" in this struc- ture: struct foo { char a:4; char b:8; } __attribute__ ((packed)); This warning is enabled by default. Use -Wno-packed-bitfield-compat to disable this warning. -Wpacked-not-aligned (C, C++, Objective-C and Objective-C++ only) Warn if a structure field with explicitly specified alignment in a packed struct or union is misaligned. For example, a warning will be issued on "struct S", like, "warning: alignment 1 of 'struct S' is less than 8", in this code: struct __attribute__ ((aligned (8))) S8 { char a[8]; }; struct __attribute__ ((packed)) S { struct S8 s8; }; This warning is enabled by -Wall. -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 re- duce the padding and so make the structure smaller. -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. -Wrestrict Warn when an object referenced by a "restrict"-qualified parameter (or, in C++, a "__restrict"-qualified parameter) is aliased by another argu- ment, or when copies between such objects overlap. For example, the call to the "strcpy" function below attempts to truncate the string by replacing its initial characters with the last four. However, because the call writes the terminating NUL into "a[4]", the copies overlap and the call is diagnosed. void foo (void) { char a[] = "abcd1234"; strcpy (a, a + 4); ... } The -Wrestrict option detects some instances of simple overlap even without optimization but works best at -O2 and above. It is included in -Wall. -Wnested-externs (C and Objective-C only) Warn if an "extern" declaration is encountered within a function. -Winline Warn if a function that is declared as inline cannot be inlined. Even with this option, the compiler does not warn about failures to inline functions declared in system headers. The compiler uses a variety of heuristics to determine whether or not to inline a function. For example, the compiler takes into account the size of the function being inlined and the amount of inlining that has already been done in the current function. Therefore, seemingly in- significant changes in the source program can cause the warnings pro- duced by -Winline to appear or disappear. -Winterference-size -Wno-interference-size Warn about questionable uses of the C++17 "constexpr" variables "std::hardware_destructive_interference_size" and "std::hardware_con- structive_interference_size". These variables are intended to be used for controlling class layout, to avoid false sharing in concurrent code: struct independent_fields { alignas(std::hardware_destructive_interference_size) std::atomic<int> one; alignas(std::hardware_destructive_interference_size) std::atomic<int> two; }; Here one and two are intended to be far enough apart that stores to one won't require accesses to the other to reload the cache line. By default, these variables are given values based on the current -mtune option, typically to the L1 cache line size for the particular target CPU, sometimes to a range if tuning for a generic target. So all translation units that depend on ABI compatibility for the use of these variables must be compiled with the same -mtune (or -mcpu). If ABI stability is important, such as if the use is in a header for a library, you should probably not use the hardware interference size variables at all. These warnings are enabled by default. If you are confident that your use of these variables does not affect ABI outside a single build of your project, you can turn off the warning with -Wno-interference-size. -Wint-in-bool-context Warn for suspicious use of integer values where boolean values are ex- pected, such as conditional expressions (?:) using non-boolean integer constants in boolean context, like "if (a <= b ? 2 : 3)". Or left shifting of signed integers in boolean context, like "for (a = 0; 1 << a; a++);". Likewise for all kinds of multiplications regardless of the data type. This warning is enabled by -Wall. -Wno-int-to-pointer-cast Suppress warnings from casts to pointer type of an integer of a differ- ent size. In C++, casting to a pointer type of smaller size is an er- ror. Wint-to-pointer-cast is enabled by default. -Wno-pointer-to-int-cast (C and Objective-C only) Suppress warnings from casts from a pointer to an integer type of a different size. -Winvalid-pch Warn if a precompiled header is found in the search path but cannot be used. -Winvalid-utf8 Warn if an invalid UTF-8 character is found. This warning is on by de- fault for C++23 if -finput-charset=UTF-8 is used and turned into error with -pedantic-errors. -Wno-unicode Don't diagnose invalid forms of delimited or named escape sequences which are treated as separate tokens. Wunicode is enabled by default. -Wlong-long Warn if "long long" type is used. This is enabled by either -Wpedantic or -Wtraditional in ISO C90 and C++98 modes. To inhibit the warning messages, use -Wno-long-long. This warning is upgraded to an error by -pedantic-errors. -Wvariadic-macros Warn if variadic macros are used in ISO C90 mode, or if the GNU alter- nate syntax is used in ISO C99 mode. This is enabled by either -Wpedantic or -Wtraditional. To inhibit the warning messages, use -Wno-variadic-macros. -Wno-varargs Do not warn upon questionable usage of the macros used to handle vari- able arguments like "va_start". These warnings are enabled by default. -Wvector-operation-performance Warn if vector operation is not implemented via SIMD capabilities of the architecture. Mainly useful for the performance tuning. Vector operation can be implemented "piecewise", which means that the scalar operation is performed on every vector element; "in parallel", which means that the vector operation is implemented using scalars of wider type, which normally is more performance efficient; and "as a single scalar", which means that vector fits into a scalar type. -Wvla Warn if a variable-length array is used in the code. -Wno-vla prevents the -Wpedantic warning of the variable-length array. This warning is upgraded to an error by -pedantic-errors. -Wvla-larger-than=byte-size If this option is used, the compiler warns for declarations of vari- able-length arrays whose size is either unbounded, or bounded by an ar- gument that allows the array size to exceed byte-size bytes. This is similar to how -Walloca-larger-than=byte-size works, but with vari- able-length arrays. Note that GCC may optimize small variable-length arrays of a known value into plain arrays, so this warning may not get triggered for such arrays. -Wvla-larger-than=PTRDIFF_MAX is enabled by default but is typically only effective when -ftree-vrp is active (default for -O2 and above). See also -Walloca-larger-than=byte-size. -Wno-vla-larger-than Disable -Wvla-larger-than= warnings. The option is equivalent to -Wvla-larger-than=SIZE_MAX or larger. -Wvla-parameter Warn about redeclarations of functions involving arguments of Variable Length Array types of inconsistent kinds or forms, and enable the de- tection of out-of-bounds accesses to such parameters by warnings such as -Warray-bounds. If the first function declaration uses the VLA form the bound specified in the array is assumed to be the minimum number of elements expected to be provided in calls to the function and the maximum number of ele- ments accessed by it. Failing to provide arguments of sufficient size or accessing more than the maximum number of elements may be diagnosed. For example, the warning triggers for the following redeclarations be- cause the first one allows an array of any size to be passed to "f" while the second one specifies that the array argument must have at least "n" elements. In addition, calling "f" with the associated VLA bound parameter in excess of the actual VLA bound triggers a warning as well. void f (int n, int[n]); // warning: argument 2 previously declared as a VLA void f (int, int[]); void g (int n) { if (n > 4) return; int a[n]; // warning: access to a by f may be out of bounds f (sizeof a, a); ... } -Wvla-parameter is included in -Wall. The -Warray-parameter option triggers warnings for similar problems involving ordinary array argu- ments. -Wvolatile-register-var Warn if a register variable is declared volatile. The volatile modi- fier does not inhibit all optimizations that may eliminate reads and/or writes to register variables. This warning is enabled by -Wall. -Wno-xor-used-as-pow (C, C++, Objective-C and Objective-C++ only) Disable warnings about uses of "^", the exclusive or operator, where it appears the code meant exponentiation. Specifically, the warning oc- curs when the left-hand side is the decimal constant 2 or 10 and the right-hand side is also a decimal constant. In C and C++, "^" means exclusive or, whereas in some other languages (e.g. TeX and some versions of BASIC) it means exponentiation. This warning can be silenced by converting one of the operands to hexa- decimal as well as by compiling with -Wno-xor-used-as-pow. -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 GCC's optimizers are unable to handle the code effectively. Often, the problem is that your code is too big or too complex; GCC refuses to optimize programs when the optimization itself is likely to take inordinate amounts of time. -Wpointer-sign (C and Objective-C only) Warn for pointer argument passing or assignment with different signed- ness. This option is only supported for C and Objective-C. It is im- plied by -Wall and by -Wpedantic, which can be disabled with -Wno-pointer-sign. This warning is upgraded to an error by -pedantic-errors. -Wstack-protector This option is only active when -fstack-protector is active. It warns about functions that are not protected against stack smashing. -Woverlength-strings Warn about string constants that are longer than the "minimum maximum" length specified in the C standard. Modern compilers generally allow string constants that are much longer than the standard's minimum limit, but very portable programs should avoid using longer strings. The limit applies after string constant concatenation, and does not count the trailing NUL. In C90, the limit was 509 characters; in C99, it was raised to 4095. C++98 does not specify a normative minimum max- imum, so we do not diagnose overlength strings in C++. This option is implied by -Wpedantic, and can be disabled with -Wno-overlength-strings. -Wunsuffixed-float-constants (C and Objective-C only) Issue a warning for any floating constant that does not have a suffix. When used together with -Wsystem-headers it warns about such constants in system header files. This can be useful when preparing code to use with the "FLOAT_CONST_DECIMAL64" pragma from the decimal floating-point extension to C99. -Wno-lto-type-mismatch During the link-time optimization, do not warn about type mismatches in global declarations from different compilation units. Requires -flto to be enabled. Enabled by default. -Wno-designated-init (C and Objective-C only) Suppress warnings when a positional initializer is used to initialize a structure that has been marked with the "designated_init" attribute. -Wzero-init-padding-bits=value Warn about automatic variable initializers that might not zero initial- ize padding bits. Certain languages guarantee zero initialization of padding bits in cer- tain cases. The "-fzero-init-padding-bits=unions" and "-fzero-init-padding-bits=all" options provide additional guarantees that padding bits will be zero initialized in other circumstances. This warning is mainly intended to find source code that might need to be modified or else recompiled with "-fzero-init-padding-bits=unions" or "-fzero-init-padding-bits=all" in order to retain the behavior that it had when compiled by versions of GCC older than 15.1. It can also be used to find code that might result in uninitialized struct padding unless GCC is invoked with "-fzero-init-padding-bits=all" (regardless of the fact that older versions of GCC would not have guaranteed ini- tialization of struct padding either). It does not follow that all source code which causes warnings about uninitialized padding bits has undefined behavior: usually, the values of padding bits have no effect on execution of a program. The two options interact as follows: : f:standard : f:unions : f:all W:standard : X : X : X W:unions : U : X : X W:all : A : S : X Letter : Meaning X : No warnings about padding bits. U : Warnings about padding bits of unions. S : Warnings about padding bits of structs. A : Warnings about padding bits of structs and unions. Examples of union initialization for ISO C23 with "-fzero-init-padding-bits=standard" and "-Wzero-init-padding-bits=unions": long long q; unsigned char r; union U { unsigned char a; long long b; }; struct F { long long a; union U b; }; // Padding bits are explicitly initialized union U h = {}; // Padding bits might not be initialized union U i = { r }; // Padding bits might not be initialized union U j = { .a = r }; // Union is expected to have no padding bits union U k = { .b = q }; // Padding bits (of union) are explicitly initialized struct F l = { q, {}, .b.a = r }; // Padding bits (of union) might not be initialized struct F m = { q, {}, .b = {.a = r} }; In the declaration of "m", an empty initializer that would otherwise guarantee zero initialization of the padding bits of the union (i.e., storage allocated for member "b" that is not part of member "a") is overridden by a subsequently listed initializer. This is an anti-pat- tern. Whether or not a given initializer causes a warning to be produced can be predicted for simple cases but in general it is target-dependent be- cause the layout of storage is target-dependent. The level of opti- mization, size, and initial value of the object being initialized also affect whether warnings are produced. Options That Control Static Analysis -fanalyzer This option enables an static analysis of program flow which looks for "interesting" interprocedural paths through the code, and issues warn- ings for problems found on them. This analysis is much more expensive than other GCC warnings. In technical terms, it performs coverage-guided symbolic execution of the code being compiled. It is neither sound nor complete: it can have false positives and false negatives. It is a bug-finding tool, rather than a tool for proving program correctness. The analyzer is only suitable for use on C code in this release. Enabling this option effectively enables the following warnings: -Wanalyzer-allocation-size -Wanalyzer-deref-before-check -Wana- lyzer-div-by-zero -Wanalyzer-double-fclose -Wanalyzer-double-free -Wan- alyzer-exposure-through-output-file -Wanalyzer-expo- sure-through-uninit-copy -Wanalyzer-fd-access-mode-mismatch -Wana- lyzer-fd-double-close -Wanalyzer-fd-leak -Wanalyzer-fd-phase-mismatch -Wanalyzer-fd-type-mismatch -Wanalyzer-fd-use-after-close -Wana- lyzer-fd-use-without-check -Wanalyzer-file-leak -Wana- lyzer-free-of-non-heap -Wanalyzer-imprecise-fp-arithmetic -Wana- lyzer-infinite-loop -Wanalyzer-infinite-recursion -Wana- lyzer-jump-through-null -Wanalyzer-malloc-leak -Wanalyzer-mismatch- ing-deallocation -Wanalyzer-mkostemp-redundant-flags -Wanalyzer-mk- temp-missing-placeholder -Wanalyzer-mktemp-of-string-literal -Wana- lyzer-null-argument -Wanalyzer-null-dereference -Wana- lyzer-out-of-bounds -Wanalyzer-overlapping-buffers -Wanalyzer-possi- ble-null-argument -Wanalyzer-possible-null-dereference -Wana- lyzer-putenv-of-auto-var -Wanalyzer-shift-count-negative -Wana- lyzer-shift-count-overflow -Wanalyzer-stale-setjmp-buffer -Wana- lyzer-tainted-allocation-size -Wanalyzer-tainted-array-index -Wana- lyzer-tainted-assertion -Wanalyzer-tainted-divisor -Wana- lyzer-tainted-offset -Wanalyzer-tainted-size -Wanalyzer-throw-of-unex- pected-type -Wanalyzer-undefined-behavior-ptrdiff -Wanalyzer-unde- fined-behavior-strtok -Wanalyzer-unsafe-call-within-signal-handler -Wanalyzer-use-after-free -Wana- lyzer-use-of-pointer-in-stale-stack-frame -Wanalyzer-use-of-uninitial- ized-value -Wanalyzer-va-arg-type-mismatch -Wanalyzer-va-list-exhausted -Wanalyzer-va-list-leak -Wanalyzer-va-list-use-after-va-end -Wana- lyzer-write-to-const -Wanalyzer-write-to-string-literal This option is only available if GCC was configured with analyzer sup- port enabled. -Wanalyzer-symbol-too-complex If -fanalyzer is enabled, the analyzer uses various heuristics to at- tempt to track the state of memory, but these can be defeated by suffi- ciently complicated code. By default, the analysis silently stops tracking values of expressions if they exceed an internal limit, and falls back to an imprecise repre- sentation for such expressions. The -Wanalyzer-symbol-too-complex op- tion warns if this occurs. -Wanalyzer-too-complex If -fanalyzer is enabled, the analyzer uses various heuristics to at- tempt to explore the control flow and data flow in the program, but these can be defeated by sufficiently complicated code. By default, the analysis silently stops if the code is too complicated for the analyzer to fully explore and it reaches an internal limit. The -Wanalyzer-too-complex option warns if this occurs. -Wno-analyzer-allocation-size This warning requires -fanalyzer, which enables it; to disable it, use -Wno-analyzer-allocation-size. This diagnostic warns for paths through the code in which a pointer to a buffer is assigned to point at a buffer with a size that is not a multiple of "sizeof (*pointer)". See CWE-131: Incorrect Calculation of Buffer Size ("https://cwe.mitre.org/data/definitions/131.html"). -Wno-analyzer-div-by-zero This warning requires -fanalyzer, which enables it; to disable it, use -Wno-analyzer-div-by-zero. This diagnostic warns for paths through the code which attempt integer division by zero. It is analogous to -Wdiv-by-zero, but implemented in a different way. See CWE-369: Divide By Zero ("https://cwe.mitre.org/data/defini- tions/369.html"). -Wno-analyzer-deref-before-check This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-deref-before-check to disable it. This diagnostic warns for paths through the code in which a pointer is checked for "NULL" *after* it has already been dereferenced, suggesting that the pointer could have been NULL. Such cases suggest that the check for NULL is either redundant, or that it needs to be moved to be- fore the pointer is dereferenced. This diagnostic also considers values passed to a function argument marked with "__attribute__((nonnull))" as requiring a non-NULL value, and thus will complain if such values are checked for "NULL" after re- turning from such a function call. This diagnostic is unlikely to be reported when any level of optimiza- tion is enabled, as GCC's optimization logic will typically consider such checks for NULL as being redundant, and optimize them away before the analyzer "sees" them. Hence optimization should be disabled when attempting to trigger this diagnostic. -Wno-analyzer-double-fclose This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-double-fclose to disable it. This diagnostic warns for paths through the code in which a "FILE *" can have "fclose" called on it more than once. See CWE-1341: Multiple Releases of Same Resource or Handle ("https://cwe.mitre.org/data/definitions/1341.html"). -Wno-analyzer-double-free This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-double-free to disable it. This diagnostic warns for paths through the code in which a pointer can have a deallocator called on it more than once, either "free", or a deallocator referenced by attribute "malloc". See CWE-415: Double Free ("https://cwe.mitre.org/data/defini- tions/415.html"). -Wno-analyzer-exposure-through-output-file This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-exposure-through-output-file to disable it. This diagnostic warns for paths through the code in which a secu- rity-sensitive value is written to an output file (such as writing a password to a log file). See CWE-532: Information Exposure Through Log Files ("https://cwe.mitre.org/data/definitions/532.html"). -Wanalyzer-exposure-through-uninit-copy This warning requires both -fanalyzer and the use of a plugin to spec- ify a function that copies across a "trust boundary". Use -Wno-ana- lyzer-exposure-through-uninit-copy to disable it. This diagnostic warns for "infoleaks" - paths through the code in which uninitialized values are copied across a security boundary (such as code within an OS kernel that copies a partially-initialized struct on the stack to user space). See CWE-200: Exposure of Sensitive Information to an Unauthorized Ac- tor ("https://cwe.mitre.org/data/definitions/200.html"). -Wno-analyzer-fd-access-mode-mismatch This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-fd-access-mode-mismatch to disable it. This diagnostic warns for paths through code in which a "read" on a write-only file descriptor is attempted, or vice versa. This diagnostic also warns for code paths in a which a function with attribute "fd_arg_read (N)" is called with a file descriptor opened with "O_WRONLY" at referenced argument "N" or a function with attribute "fd_arg_write (N)" is called with a file descriptor opened with "O_RDONLY" at referenced argument N. -Wno-analyzer-fd-double-close This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-fd-double-close to disable it. This diagnostic warns for paths through code in which a file descriptor can be closed more than once. See CWE-1341: Multiple Releases of Same Resource or Handle ("https://cwe.mitre.org/data/definitions/1341.html"). -Wno-analyzer-fd-leak This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-fd-leak to disable it. This diagnostic warns for paths through code in which an open file de- scriptor is leaked. See CWE-775: Missing Release of File Descriptor or Handle after Effec- tive Lifetime ("https://cwe.mitre.org/data/definitions/775.html"). -Wno-analyzer-fd-phase-mismatch This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-fd-phase-mismatch to disable it. This diagnostic warns for paths through code in which an operation is attempted in the wrong phase of a file descriptor's lifetime. For ex- ample, it will warn on attempts to call "accept" on a stream socket that has not yet had "listen" successfully called on it. See CWE-666: Operation on Resource in Wrong Phase of Lifetime ("https://cwe.mitre.org/data/definitions/666.html"). -Wno-analyzer-fd-type-mismatch This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-fd-type-mismatch to disable it. This diagnostic warns for paths through code in which an operation is attempted on the wrong type of file descriptor. For example, it will warn on attempts to use socket operations on a file descriptor obtained via "open", or when attempting to use a stream socket operation on a datagram socket. -Wno-analyzer-fd-use-after-close This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-fd-use-after-close to disable it. This diagnostic warns for paths through code in which a read or write is called on a closed file descriptor. This diagnostic also warns for paths through code in which a function with attribute "fd_arg (N)" or "fd_arg_read (N)" or "fd_arg_write (N)" is called with a closed file descriptor at referenced argument "N". -Wno-analyzer-fd-use-without-check This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-fd-use-without-check to disable it. This diagnostic warns for paths through code in which a file descriptor is used without being checked for validity. This diagnostic also warns for paths through code in which a function with attribute "fd_arg (N)" or "fd_arg_read (N)" or "fd_arg_write (N)" is called with a file descriptor, at referenced argument "N", without being checked for validity. -Wno-analyzer-file-leak This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-file-leak to disable it. This diagnostic warns for paths through the code in which a "<stdio.h>" "FILE *" stream object is leaked. See CWE-775: Missing Release of File Descriptor or Handle after Effec- tive Lifetime ("https://cwe.mitre.org/data/definitions/775.html"). -Wno-analyzer-free-of-non-heap This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-free-of-non-heap to disable it. This diagnostic warns for paths through the code in which "free" is called on a non-heap pointer (e.g. an on-stack buffer, or a global). See CWE-590: Free of Memory not on the Heap ("https://cwe.mitre.org/data/definitions/590.html"). -Wno-analyzer-imprecise-fp-arithmetic This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-imprecise-fp-arithmetic to disable it. This diagnostic warns for paths through the code in which float- ing-point arithmetic is used in locations where precise computation is needed. This diagnostic only warns on use of floating-point operands inside the calculation of an allocation size at the moment. -Wno-analyzer-infinite-loop This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-infinite-loop to disable it. This diagnostics warns for paths through the code which appear to lead to an infinite loop. Specifically, the analyzer will issue this warning when it "sees" a loop in which: * no externally-visible work could be being done within the loop * there is no way to escape from the loop * the analyzer is sufficiently confident about the program state throughout the loop to know that the above are true One way for this warning to be emitted is when there is an execution path through a loop for which taking the path on one iteration implies that the same path will be taken on all subsequent iterations. For example, consider: while (1) { char opcode = *cpu_state.pc; switch (opcode) { case OPCODE_FOO: handle_opcode_foo (&cpu_state); break; case OPCODE_BAR: handle_opcode_bar (&cpu_state); break; } } The analyzer will complain for the above case because if "opcode" ever matches none of the cases, the "switch" will follow the implicit "de- fault" case, making the body of the loop be a "no-op" with "cpu_state.pc" unchanged, and thus using the same value of "opcode" on all subsequent iterations, leading to an infinite loop. See CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop') ("https://cwe.mitre.org/data/definitions/835.html"). -Wno-analyzer-infinite-recursion This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-infinite-recursion to disable it. This diagnostics warns for paths through the code which appear to lead to infinite recursion. Specifically, when the analyzer "sees" a recursive call, it will com- pare the state of memory at the entry to the new frame with that at the entry to the previous frame of that function on the stack. The warning is issued if nothing in memory appears to be changing; any changes ob- served to parameters or globals are assumed to lead to termination of the recursion and thus suppress the warning. This diagnostic is likely to miss cases of infinite recursion that are converted to iteration by the optimizer before the analyzer "sees" them. Hence optimization should be disabled when attempting to trigger this diagnostic. Compare with -Winfinite-recursion, which provides a similar diagnostic, but is implemented in a different way. See CWE-674: Uncontrolled Recursion ("https://cwe.mitre.org/data/defi- nitions/674.html"). -Wno-analyzer-jump-through-null This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-jump-through-null to disable it. This diagnostic warns for paths through the code in which a "NULL" function pointer is called. -Wno-analyzer-malloc-leak This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-malloc-leak to disable it. This diagnostic warns for paths through the code in which a pointer al- located via an allocator is leaked: either "malloc", or a function marked with attribute "malloc". See CWE-401: Missing Release of Memory after Effective Lifetime ("https://cwe.mitre.org/data/definitions/401.html"). -Wno-analyzer-mismatching-deallocation This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-mismatching-deallocation to disable it. This diagnostic warns for paths through the code in which the wrong deallocation function is called on a pointer value, based on which function was used to allocate the pointer value. The diagnostic will warn about mismatches between "free", scalar "delete" and vector "delete[]", and those marked as allocator/deallocator pairs using at- tribute "malloc". See CWE-762: Mismatched Memory Management Routines ("https://cwe.mitre.org/data/definitions/762.html"). -Wno-analyzer-mkostemp-redundant-flags This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-mkostemp-redundant-flags to disable it. This diagnostic warns for paths through the code in which "mkostemp" or "mkostemps" is called with flags that include "O_RDWR", "O_CREAT", or "O_EXCL". These flags are already implied by the function and specify- ing them is unnecessary, and produces errors on some systems. -Wno-analyzer-mktemp-missing-placeholder This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-mktemp-missing-placeholder to disable it. This diagnostic warns for paths through the code in which a function in the "mktemp" family ("mkstemp", "mkostemp", "mkstemps", "mkostemps", "mkdtemp", "mktemp") is called with a template string that does not contain the placeholder XXXXXX at the expected position. -Wno-analyzer-mktemp-of-string-literal This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-mktemp-of-string-literal to disable it. This diagnostic warns for paths through the code in which a function in the "mktemp" family ("mkstemp", "mkostemp", "mkstemps", "mkostemps", "mkdtemp", "mktemp") is called on a string literal. Since these func- tions modify their argument in place, passing a string literal leads to undefined behavior. See STR30-C. Do not attempt to modify string literals ("https://wiki.sei.cmu.edu/confluence/x/VtYxBQ"). -Wno-analyzer-out-of-bounds This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-out-of-bounds to disable it. This diagnostic warns for paths through the code in which a buffer is definitely read or written out-of-bounds. The diagnostic applies for cases where the analyzer is able to determine a constant offset and for accesses past the end of a buffer, also a constant capacity. Further, the diagnostic does limited checking for accesses past the end when the offset as well as the capacity is symbolic. See CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer ("https://cwe.mitre.org/data/definitions/119.html"). For cases where the analyzer is able, it will emit a text art diagram visualizing the spatial relationship between the memory region that the analyzer predicts would be accessed, versus the range of memory that is valid to access: whether they overlap, are touching, are close or far apart; which one is before or after in memory, the relative sizes in- volved, the direction of the access (read vs write), and, in some cases, the values of data involved. This diagram can be suppressed us- ing -fdiagnostics-text-art-charset=none. -Wno-analyzer-overlapping-buffers This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-overlapping-buffers to disable it. This diagnostic warns for paths through the code in which overlapping buffers are passed to an API for which the behavior on such buffers is undefined. Specifically, the diagnostic occurs on calls to the following functions *<"memcpy"> *<"strcat"> *<"strcpy"> for cases where the buffers are known to overlap. -Wno-analyzer-possible-null-argument This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-possible-null-argument to disable it. This diagnostic warns for paths through the code in which a possi- bly-NULL value is passed to a function argument marked with "__at- tribute__((nonnull))" as requiring a non-NULL value. See CWE-690: Unchecked Return Value to NULL Pointer Dereference ("https://cwe.mitre.org/data/definitions/690.html"). -Wno-analyzer-possible-null-dereference This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-possible-null-dereference to disable it. This diagnostic warns for paths through the code in which a possi- bly-NULL value is dereferenced. See CWE-690: Unchecked Return Value to NULL Pointer Dereference ("https://cwe.mitre.org/data/definitions/690.html"). -Wno-analyzer-null-argument This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-null-argument to disable it. This diagnostic warns for paths through the code in which a value known to be NULL is passed to a function argument marked with "__at- tribute__((nonnull))" as requiring a non-NULL value. See CWE-476: NULL Pointer Dereference ("https://cwe.mitre.org/data/de- finitions/476.html"). -Wno-analyzer-null-dereference This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-null-dereference to disable it. This diagnostic warns for paths through the code in which a value known to be NULL is dereferenced. See CWE-476: NULL Pointer Dereference ("https://cwe.mitre.org/data/de- finitions/476.html"). -Wno-analyzer-putenv-of-auto-var This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-putenv-of-auto-var to disable it. This diagnostic warns for paths through the code in which a call to "putenv" is passed a pointer to an automatic variable or an on-stack buffer. See POS34-C. Do not call putenv() with a pointer to an automatic vari- able as the argument ("https://wiki.sei.cmu.edu/confluence/x/6NYxBQ"). -Wno-analyzer-shift-count-negative This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-shift-count-negative to disable it. This diagnostic warns for paths through the code in which a shift is attempted with a negative count. It is analogous to the -Wshift-count-negative diagnostic implemented in the C/C++ front ends, but is implemented based on analyzing interprocedural paths, rather than merely parsing the syntax tree. However, the analyzer does not prioritize detection of such paths, so false negatives are more likely relative to other warnings. -Wno-analyzer-shift-count-overflow This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-shift-count-overflow to disable it. This diagnostic warns for paths through the code in which a shift is attempted with a count greater than or equal to the precision of the operand's type. It is analogous to the -Wshift-count-overflow diagnos- tic implemented in the C/C++ front ends, but is implemented based on analyzing interprocedural paths, rather than merely parsing the syntax tree. However, the analyzer does not prioritize detection of such paths, so false negatives are more likely relative to other warnings. -Wno-analyzer-stale-setjmp-buffer This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-stale-setjmp-buffer to disable it. This diagnostic warns for paths through the code in which "longjmp" is called to rewind to a "jmp_buf" relating to a "setjmp" call in a func- tion that has returned. When "setjmp" is called on a "jmp_buf" to record a rewind location, it records the stack frame. The stack frame becomes invalid when the function containing the "setjmp" call returns. Attempting to rewind to it via "longjmp" would reference a stack frame that no longer exists, and likely lead to a crash (or worse). -Wno-analyzer-tainted-allocation-size This warning requires -fanalyzer which enables it; use -Wno-ana- lyzer-tainted-allocation-size to disable it. This diagnostic warns for paths through the code in which a value that could be under an attacker's control is used as the size of an alloca- tion without being sanitized, so that an attacker could inject an ex- cessively large allocation and potentially cause a denial of service attack. See CWE-789: Memory Allocation with Excessive Size Value ("https://cwe.mitre.org/data/definitions/789.html"). -Wno-analyzer-tainted-assertion This warning requires -fanalyzer which enables it; use -Wno-ana- lyzer-tainted-assertion to disable it. This diagnostic warns for paths through the code in which a value that could be under an attacker's control is used as part of a condition without being first sanitized, and that condition guards a call to a function marked with attribute "noreturn" (such as the function "__builtin_unreachable"). Such functions typically indicate abnormal termination of the program, such as for assertion failure handlers. For example: assert (some_tainted_value < SOME_LIMIT); In such cases: * when assertion-checking is enabled: an attacker could trigger a de- nial of service by injecting an assertion failure * when assertion-checking is disabled, such as by defining "NDEBUG", an attacker could inject data that subverts the process, since it presumably violates a precondition that is being assumed by the code. Note that when assertion-checking is disabled, the assertions are typi- cally removed by the preprocessor before the analyzer has a chance to "see" them, so this diagnostic can only generate warnings on builds in which assertion-checking is enabled. For the purpose of this warning, any function marked with attribute "noreturn" is considered as a possible assertion failure handler, in- cluding "__builtin_unreachable". Note that these functions are some- times removed by the optimizer before the analyzer "sees" them. Hence optimization should be disabled when attempting to trigger this diag- nostic. See CWE-617: Reachable Assertion ("https://cwe.mitre.org/data/defini- tions/617.html"). The warning can also report problematic constructions such as switch (some_tainted_value) { case 0: /* [...etc; various valid cases omitted...] */ break; default: __builtin_unreachable (); /* BUG: attacker can trigger this */ } despite the above not being an assertion failure, strictly speaking. -Wno-analyzer-tainted-array-index This warning requires -fanalyzer which enables it; use -Wno-ana- lyzer-tainted-array-index to disable it. This diagnostic warns for paths through the code in which a value that could be under an attacker's control is used as the index of an array access without being sanitized, so that an attacker could inject an out-of-bounds access. See CWE-129: Improper Validation of Array Index ("https://cwe.mitre.org/data/definitions/129.html"). -Wno-analyzer-tainted-divisor This warning requires -fanalyzer which enables it; use -Wno-ana- lyzer-tainted-divisor to disable it. This diagnostic warns for paths through the code in which a value that could be under an attacker's control is used as the divisor in a divi- sion or modulus operation without being sanitized, so that an attacker could inject a division-by-zero. See CWE-369: Divide By Zero ("https://cwe.mitre.org/data/defini- tions/369.html"). -Wno-analyzer-tainted-offset This warning requires -fanalyzer which enables it; use -Wno-ana- lyzer-tainted-offset to disable it. This diagnostic warns for paths through the code in which a value that could be under an attacker's control is used as a pointer offset with- out being sanitized, so that an attacker could inject an out-of-bounds access. See CWE-823: Use of Out-of-range Pointer Offset ("https://cwe.mitre.org/data/definitions/823.html"). -Wno-analyzer-tainted-size This warning requires -fanalyzer which enables it; use -Wno-ana- lyzer-tainted-size to disable it. This diagnostic warns for paths through the code in which a value that could be under an attacker's control is used as the size of an opera- tion such as "memset" without being sanitized, so that an attacker could inject an out-of-bounds access. See CWE-129: Improper Validation of Array Index ("https://cwe.mitre.org/data/definitions/129.html"). -Wno-analyzer-throw-of-unexpected-type This warning requires -fanalyzer which enables it; use -Wno-ana- lyzer-throw-of-unexpected-type to disable it. Dynamic exception speci- fications are only available in C++14 and earlier. This diagnostic warns for paths through the code in which a an excep- tion is thrown from a function with a dynamic exception specification where the exception does not comply with the specification. -Wno-analyzer-undefined-behavior-ptrdiff This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-undefined-behavior-ptrdiff to disable it. This diagnostic warns for paths through the code in which a pointer subtraction occurs where the pointers refer to different chunks of mem- ory. Such code relies on undefined behavior, as pointer subtraction is only defined for cases where both pointers point to within (or just af- ter) the same array. See CWE-469: Use of Pointer Subtraction to Determine Size ("https://cwe.mitre.org/data/definitions/469.html"). -Wno-analyzer-undefined-behavior-strtok This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-undefined-behavior-strtok to disable it. This diagnostic warns for paths through the code in which a call is made to "strtok" with undefined behavior. Specifically, passing NULL as the first parameter for the initial call to "strtok" within a process has undefined behavior. -Wno-analyzer-unsafe-call-within-signal-handler This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-unsafe-call-within-signal-handler to disable it. This diagnostic warns for paths through the code in which a function known to be async-signal-unsafe (such as "fprintf") is called from a signal handler. See CWE-479: Signal Handler Use of a Non-reentrant Function ("https://cwe.mitre.org/data/definitions/479.html"). -Wno-analyzer-use-after-free This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-use-after-free to disable it. This diagnostic warns for paths through the code in which a pointer is used after a deallocator is called on it: either "free", or a dealloca- tor referenced by attribute "malloc". See CWE-416: Use After Free ("https://cwe.mitre.org/data/defini- tions/416.html"). -Wno-analyzer-use-of-pointer-in-stale-stack-frame This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-use-of-pointer-in-stale-stack-frame to disable it. This diagnostic warns for paths through the code in which a pointer is dereferenced that points to a variable in a stale stack frame. -Wno-analyzer-va-arg-type-mismatch This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-va-arg-type-mismatch to disable it. This diagnostic warns for interprocedural paths through the code for which the analyzer detects an attempt to use "va_arg" to extract a value passed to a variadic call, but uses a type that does not match that of the expression passed to the call. See CWE-686: Function Call With Incorrect Argument Type ("https://cwe.mitre.org/data/definitions/686.html"). -Wno-analyzer-va-list-exhausted This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-va-list-exhausted to disable it. This diagnostic warns for interprocedural paths through the code for which the analyzer detects an attempt to use "va_arg" to access the next value passed to a variadic call, but all of the values in the "va_list" have already been consumed. See CWE-685: Function Call With Incorrect Number of Arguments ("https://cwe.mitre.org/data/definitions/685.html"). -Wno-analyzer-va-list-leak This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-va-list-leak to disable it. This diagnostic warns for interprocedural paths through the code for which the analyzer detects that "va_start" or "va_copy" has been called on a "va_list" without a corresponding call to "va_end". -Wno-analyzer-va-list-use-after-va-end This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-va-list-use-after-va-end to disable it. This diagnostic warns for interprocedural paths through the code for which the analyzer detects an attempt to use a "va_list" after "va_end" has been called on it. "va_list". -Wno-analyzer-write-to-const This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-write-to-const to disable it. This diagnostic warns for paths through the code in which the analyzer detects an attempt to write through a pointer to a "const" object. However, the analyzer does not prioritize detection of such paths, so false negatives are more likely relative to other warnings. -Wno-analyzer-write-to-string-literal This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-write-to-string-literal to disable it. This diagnostic warns for paths through the code in which the analyzer detects an attempt to write through a pointer to a string literal. However, the analyzer does not prioritize detection of such paths, so false negatives are more likely relative to other warnings. -Wno-analyzer-use-of-uninitialized-value This warning requires -fanalyzer, which enables it; use -Wno-ana- lyzer-use-of-uninitialized-value to disable it. This diagnostic warns for paths through the code in which an uninitial- ized value is used. See CWE-457: Use of Uninitialized Variable ("https://cwe.mitre.org/data/definitions/457.html"). The analyzer has hardcoded knowledge about the behavior of the following memory-management functions: *<"alloca"> *<The built-in functions "__builtin_alloc",> "__builtin_alloc_with_align", @item "__builtin_calloc", "__builtin_free", "__builtin_malloc", "__builtin_memcpy", "__builtin_memcpy_chk", "__builtin_memset", "__builtin_memset_chk", "__builtin_realloc", "__builtin_stack_restore", and "__builtin_stack_save" *<"calloc"> *<"free"> *<"malloc"> *<"memset"> *<"operator delete"> *<"operator delete []"> *<"operator new"> *<"operator new []"> *<"realloc"> *<"strdup"> *<"strndup"> of the following functions for working with file descriptors: *<"open"> *<"close"> *<"creat"> *<"dup", "dup2" and "dup3"> *<"isatty"> *<"pipe", and "pipe2"> *<"read"> *<"write"> *<"socket", "bind", "listen", "accept", and "connect"> of the following functions for working with "<stdio.h>" streams: *<The built-in functions "__builtin_fprintf",> "__builtin_fprintf_unlocked", "__builtin_fputc", "__builtin_fputc_un- locked", "__builtin_fputs", "__builtin_fputs_unlocked", "__builtin_fwrite", "__builtin_fwrite_unlocked", "__builtin_printf", "__builtin_printf_unlocked", "__builtin_putc", "__builtin_putchar", "__builtin_putchar_unlocked", "__builtin_putc_unlocked", "__builtin_puts", "__builtin_puts_unlocked", "__builtin_vfprintf", and "__builtin_vprintf" *<"fopen"> *<"fclose"> *<"ferror"> *<"fgets"> *<"fgets_unlocked"> *<"fileno"> *<"fread"> *<"getc"> *<"getchar"> *<"fprintf"> *<"printf"> *<"fwrite"> and of the following functions: *<The built-in functions "__builtin_expect",> "__builtin_expect_with_probability", "__builtin_strchr", "__builtin_strcpy", "__builtin_strcpy_chk", "__builtin_strlen", "__builtin_va_copy", and "__builtin_va_start" *<The GNU extensions "error" and "error_at_line"> *<"getpass"> *<"longjmp"> *<"putenv"> *<"setjmp"> *<"siglongjmp"> *<"signal"> *<"sigsetjmp"> *<"strcat"> *<"strchr"> *<"strlen"> In addition, various functions with an "__analyzer_" prefix have special meaning to the analyzer, described in the GCC Internals manual. Various internal parameters, settable via --param, are used to control the explo- ration; these are also documented in the GCC Internals manual. The following options control the analyzer. -fanalyzer-assume-nothrow By default, if -fexceptions is enabled, the analyzer will assume that a call to any function without attribute "nothrow" could throw an excep- tion. This can help detect execution paths that leak due to exceptions bypassing clean-up code, but could lead to false positives when using headers where the author has not added the "nothrow" attribute. If -fanalyzer-assume-nothrow is enabled, then the analyzer will assume that external functions do not throw exceptions. This may be useful for reducing "noise" from the analyzer when enabling -fexceptions on C code, but could hide true issues if an exception could be raised by something the C code calls. -fanalyzer-call-summaries Simplify interprocedural analysis by computing the effect of certain calls, rather than exploring all paths through the function from call- site to each possible return. If enabled, call summaries are only used for functions with more than one call site, and that are sufficiently complicated. -fanalyzer-checker=name Restrict the analyzer to run just the named checker, and enable it. -fanalyzer-debug-text-art-headings This option is intended for analyzer developers. If enabled, the ana- lyzer will add extra annotations to any diagrams it generates. -fno-analyzer-feasibility This option is intended for analyzer developers. By default the analyzer verifies that there is a feasible control flow path for each diagnostic it emits: that the conditions that hold are not mutually exclusive. Diagnostics for which no feasible path can be found are rejected. This filtering can be suppressed with -fno-ana- lyzer-feasibility, for debugging issues in this code. -fanalyzer-fine-grained Does nothing. Preserved for backward compatibility. -fanalyzer-show-duplicate-count This option is intended for analyzer developers: if multiple diagnos- tics have been detected as being duplicates of each other, it emits a note when reporting the best diagnostic, giving the number of addi- tional diagnostics that were suppressed by the deduplication logic. -fanalyzer-show-events-in-system-headers By default the analyzer emits simplified diagnostics paths by hiding events fully located within a system header. With -fana- lyzer-show-events-in-system-headers such events are no longer sup- pressed. -fno-analyzer-simplify-supergraph This option is intended for analyzer developers. By default, the analyzer performs various simplifications to the pro- gram supergraph before analyzing it. With -fno-analyzer-simplify-su- pergraph this simplification can be suppressed, for debugging issues with it. -fno-analyzer-state-merge This option is intended for analyzer developers. By default the analyzer attempts to simplify analysis by merging suffi- ciently similar states at each program point as it builds its "exploded graph". With -fno-analyzer-state-merge this merging can be suppressed, for debugging state-handling issues. -fno-analyzer-state-purge This option is intended for analyzer developers. By default the analyzer attempts to simplify analysis by purging as- pects of state at a program point that appear to no longer be relevant e.g. the values of locals that aren't accessed later in the function and which aren't relevant to leak analysis. With -fno-analyzer-state-purge this purging of state can be suppressed, for debugging state-handling issues. -fno-analyzer-suppress-followups This option is intended for analyzer developers. By default the analyzer will stop exploring an execution path after en- countering certain diagnostics, in order to avoid potentially issuing a cascade of follow-up diagnostics. The diagnostics that terminate analysis along a path are: *<-Wanalyzer-null-argument> *<-Wanalyzer-null-dereference> *<-Wanalyzer-use-after-free> *<-Wanalyzer-use-of-pointer-in-stale-stack-frame> *<-Wanalyzer-use-of-uninitialized-value> With -fno-analyzer-suppress-followups the analyzer will continue to ex- plore such paths even after such diagnostics, which may be helpful for debugging issues in the analyzer, or for microbenchmarks for detecting undefined behavior. -fanalyzer-transitivity This option enables transitivity of constraints within the analyzer. -fno-analyzer-undo-inlining This option is intended for analyzer developers. -fanalyzer runs relatively late compared to other code analysis tools, and some optimizations have already been applied to the code. In par- ticular function inlining may have occurred, leading to the interproce- dural execution paths emitted by the analyzer containing function frames that don't correspond to those in the original source code. By default the analyzer attempts to reconstruct the original function frames, and to emit events showing the inlined calls. With -fno-analyzer-undo-inlining this attempt to reconstruct the origi- nal frame information can be disabled, which may be of help when debug- ging issues in the analyzer. -fanalyzer-verbose-edges This option is intended for analyzer developers. It enables more ver- bose, lower-level detail in the descriptions of control flow within di- agnostic paths. -fanalyzer-verbose-state-changes This option is intended for analyzer developers. It enables more ver- bose, lower-level detail in the descriptions of events relating to state machines within diagnostic paths. -fanalyzer-verbosity=level This option controls the complexity of the control flow paths that are emitted for analyzer diagnostics. The level can be one of: 0 At this level, interprocedural call and return events are dis- played, along with the most pertinent state-change events relating to a diagnostic. For example, for a double-"free" diagnostic, both calls to "free" will be shown. 1 As per the previous level, but also show events for the entry to each function. 2 As per the previous level, but also show events relating to control flow that are significant to triggering the issue (e.g. "true path taken" at a conditional). This level is the default. 3 As per the previous level, but show all control flow events, not just significant ones. 4 This level is intended for analyzer developers; it adds various other events intended for debugging the analyzer. -fdump-analyzer Dump internal details about what the analyzer is doing to file.ana- lyzer.txt. -fdump-analyzer-stderr overrides this option. -fdump-analyzer-stderr Dump internal details about what the analyzer is doing to stderr. This option overrides -fdump-analyzer. -fdump-analyzer-callgraph Dump a representation of the call graph suitable for viewing with GraphViz to file.callgraph.dot. -fdump-analyzer-exploded-graph Dump a representation of the "exploded graph" suitable for viewing with GraphViz to file.eg.dot. Nodes are color-coded based on state-machine states to emphasize state changes. -fdump-analyzer-exploded-nodes Emit diagnostics showing where nodes in the "exploded graph" are in re- lation to the program source. -fdump-analyzer-exploded-nodes-2 Dump a textual representation of the "exploded graph" to file.eg.txt. -fdump-analyzer-exploded-nodes-3 Dump a textual representation of the "exploded graph" to one dump file per node, to file.eg-id.txt. This is typically a large number of dump files. -fdump-analyzer-exploded-paths Dump a textual representation of the "exploded path" for each diagnos- tic to file.idx.kind.epath.txt. -fdump-analyzer-feasibility Dump internal details about the analyzer's search for feasible paths. The details are written in a form suitable for viewing with GraphViz to filenames of the form file.*.fg.dot, file.*.tg.dot, and file.*.fpath.txt. -fdump-analyzer-infinite-loop Dump internal details about the analyzer's search for infinite loops. The details are written in a form suitable for viewing with GraphViz to filenames of the form file.*.infinite-loop.dot. -fdump-analyzer-json Dump a compressed JSON representation of analyzer internals to file.an- alyzer.json.gz. The precise format is subject to change. -fdump-analyzer-state-purge As per -fdump-analyzer-supergraph, dump a representation of the "super- graph" suitable for viewing with GraphViz, but annotate the graph with information on what state will be purged at each node. The graph is written to file.state-purge.dot. -fdump-analyzer-supergraph Dump representations of the "supergraph" suitable for viewing with GraphViz to file.supergraph.index.kind.dot. These show all of the con- trol flow graphs in the program, at various stages of the analysis. The precise set of dumps and what they show is subject to change. -fdump-analyzer-untracked Emit custom warnings with internal details intended for analyzer devel- opers. Options for Debugging Your Program To tell GCC to emit extra information for use by a debugger, in almost all cases you need only to add -g to your other options. Some debug formats can co-exist (like DWARF with CTF) when each of them is enabled explicitly by adding the respective command-line option to your other options. GCC allows you to use -g with -O. The shortcuts taken by optimized code may occasionally be surprising: 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 are already at hand; some statements may execute in different places because they have been moved out of loops. Nevertheless it is pos- sible to debug optimized output. This makes it reasonable to use the opti- mizer for programs that might have bugs. If you are not using some other optimization option, consider using -Og with -g. With no -O option at all, some compiler passes that collect in- formation useful for debugging do not run at all, so that -Og may result in a better debugging experience. -g --debug Produce debugging information in the operating system's native format (stabs, COFF, XCOFF, or DWARF). GDB can work with this debugging in- formation. On most systems that use stabs format, -g enables use of extra debug- ging information that only GDB can use; this extra information makes debugging work better in GDB but probably makes other debuggers crash or refuse to read the program. If you want to control for certain whether to generate the extra information, use -gvms (see below). -ggdb Produce debugging information for use by GDB. This means to use the most expressive format available (DWARF, stabs, or the native format if neither of those are supported), including GDB extensions if at all possible. -gdwarf -gdwarf-version Produce debugging information in DWARF format (if that is supported). The value of version may be either 2, 3, 4 or 5; the default version for most targets is 5 (with the exception of VxWorks, TPF and Darwin / macOS, which default to version 2, and AIX, which defaults to version 4). Note that with DWARF Version 2, some ports require and always use some non-conflicting DWARF 3 extensions in the unwind tables. Version 4 may require GDB 7.0 and -fvar-tracking-assignments for maxi- mum benefit. Version 5 requires GDB 8.0 or higher. GCC no longer supports DWARF Version 1, which is substantially differ- ent than Version 2 and later. For historical reasons, some other DWARF-related options such as -fno-dwarf2-cfi-asm) retain a reference to DWARF Version 2 in their names, but apply to all currently-supported versions of DWARF. -gbtf Request BTF debug information. BTF is the default debugging format for the eBPF target. On other targets, like x86, BTF debug information can be generated along with DWARF debug information when both of the debug formats are enabled explicitly via their respective command-line op- tions. -gprune-btf -gno-prune-btf Prune BTF information before emission. When pruning, only type infor- mation for types used by global variables and file-scope functions will be emitted. If compiling for the BPF target with BPF CO-RE enabled, type information will also be emitted for types used in BPF CO-RE relo- cations. In addition, struct and union types which are only referred to via pointers from members of other struct or union types shall be pruned and replaced with BTF_KIND_FWD, as though those types were only present in the input as forward declarations. This option substantially reduces the size of produced BTF information, but at significant loss in the amount of detailed type information. It is primarily useful when compiling for the BPF target, to minimize the size of the resulting object, and to eliminate BTF information which is not immediately relevant to the BPF program loading process. This option is enabled by default for the BPF target when generating BTF information. -gctf -gctflevel Request CTF debug information and use level to specify how much CTF de- bug information should be produced. If -gctf is specified without a value for level, the default level of CTF debug information is 2. CTF debug information can be generated along with DWARF debug informa- tion when both of the debug formats are enabled explicitly via their respective command line options. Level 0 produces no CTF debug information at all. Thus, -gctf0 negates -gctf. Level 1 produces CTF information for tracebacks only. This includes callsite information, but does not include type information. Level 2 produces type information for entities (functions, data objects etc.) at file-scope or global-scope only. -gvms Produce debugging information in Alpha/VMS debug format (if that is supported). This is the format used by DEBUG on Alpha/VMS systems. -gcodeview Produce debugging information in CodeView debug format (if that is sup- ported). This is the format used by Microsoft Visual C++ on Windows. -glevel -ggdblevel -gvmslevel Request debugging information and also use level to specify how much information. The default level is 2. Level 0 produces no debug information at all. Thus, -g0 negates -g. Level 1 produces minimal information, enough for making backtraces in parts of the program that you don't plan to debug. This includes de- scriptions of functions and external variables, and line number tables, but no information about local variables. Level 2 is the normal setting to produce debuggable code. The debug output includes all the information from level 1, plus information about local variables and typedefs to allow stepping through code and examining its state. For C++ code, additional information is also emitted to assist in debugging namespace, class, and template func- tions. Level 3 includes extra information, such as all the macro definitions present in the program. Some debuggers support macro expansion when you use -g3. If you use multiple -g options, with or without level numbers, the last such option is the one that is effective. -gdwarf does not accept a concatenated debug level, to avoid confusion with -gdwarf-level. Instead use an additional -glevel option to change the debug level for DWARF. -fno-eliminate-unused-debug-symbols By default, no debug information is produced for symbols that are not actually used. Use this option if you want debug information for all symbols. -femit-class-debug-always Instead of emitting debugging information for a C++ class in only one object file, emit it in all object files using the class. This option should be used only with debuggers that are unable to handle the way GCC normally emits debugging information for classes because using this option increases the size of debugging information by as much as a fac- tor of two. -fno-merge-debug-strings Direct the linker to not merge together strings in the debugging infor- mation that are identical in different object files. Merging is not supported by all assemblers or linkers. Merging decreases the size of the debug information in the output file at the cost of increasing link processing time. Merging is enabled by default. -fdebug-prefix-map=old=new When compiling files residing in directory old, record debugging infor- mation describing them as if the files resided in directory new in- stead. This can be used to replace a build-time path with an in- stall-time path in the debug info. It can also be used to change an absolute path to a relative path by using . for new. This can give more reproducible builds, which are location independent, but may re- quire an extra command to tell GDB where to find the source files. See also -ffile-prefix-map and -fcanon-prefix-map. -fvar-tracking Run variable tracking pass. It computes where variables are stored at each position in code. Better debugging information is then generated (if the debugging information format supports this information). It is enabled by default when compiling with optimization (-Os, -O, -O2, ...), debugging information (-g) and the debug info format sup- ports it. -fvar-tracking-assignments Annotate assignments to user variables early in the compilation and at- tempt to carry the annotations over throughout the compilation all the way to the end, in an attempt to improve debug information while opti- mizing. Use of -gdwarf-4 is recommended along with it. It can be enabled even if var-tracking is disabled, in which case anno- tations are created and maintained, but discarded at the end. By de- fault, this flag is enabled together with -fvar-tracking, except when selective scheduling is enabled. -fvar-tracking-uninit -fno-var-tracking-uninit Perform variable tracking and also mark uninitialized variables in the debug information. This flag is enabled by default by -fvar-tracking; it also implies -fvar-tracking. To do variable tracking without mark- ing uninitialized variables, use -fvar-tracking -fno-var-track- ing-uninit. -gsplit-dwarf If DWARF debugging information is enabled, separate as much debugging information as possible into a separate output file with the extension .dwo. This option allows the build system to avoid linking files with debug information. To be useful, this option requires a debugger capa- ble of reading .dwo files. -gdwarf32 -gdwarf64 If DWARF debugging information is enabled, the -gdwarf32 selects the 32-bit DWARF format and the -gdwarf64 selects the 64-bit DWARF format. The default is target specific, on most targets it is -gdwarf32 though. The 32-bit DWARF format is smaller, but can't support more than 2GiB of debug information in any of the DWARF debug information sections. The 64-bit DWARF format allows larger debug information and might not be well supported by all consumers yet. -gdescribe-dies Add description attributes to some DWARF DIEs that have no name at- tribute, such as artificial variables, external references and call site parameter DIEs. -gpubnames Generate DWARF ".debug_pubnames" and ".debug_pubtypes" sections. -ggnu-pubnames Generate ".debug_pubnames" and ".debug_pubtypes" sections in a format suitable for conversion into a GDB index. This option is only useful with a linker that can produce GDB index version 7. -gno-pubnames Don't generate DWARF ".debug_pubnames" and ".debug_pubtypes" sections. -fdebug-types-section When using DWARF Version 4 or higher, type DIEs can be put into their own ".debug_types" section instead of making them part of the ".de- bug_info" section. It is more efficient to put them in a separate com- dat section since the linker can then remove duplicates. But not all DWARF consumers support ".debug_types" sections yet and on some objects ".debug_types" produces larger instead of smaller debugging informa- tion. -grecord-gcc-switches -gno-record-gcc-switches This switch causes the command-line options used to invoke the compiler that may affect code generation to be appended to the DW_AT_producer attribute in DWARF debugging information. The options are concatenated with spaces separating them from each other and from the compiler ver- sion. It is enabled by default. See also -frecord-gcc-switches for another way of storing compiler options into the object file. -gstrict-dwarf Disallow using extensions of later DWARF standard version than selected with -gdwarf-version. On most targets using non-conflicting DWARF ex- tensions from later standard versions is allowed. -gno-strict-dwarf Allow using extensions of later DWARF standard version than selected with -gdwarf-version. -gas-loc-support Inform the compiler that the assembler supports ".loc" directives. It may then use them for the assembler to generate DWARF2+ line number ta- bles. This is generally desirable, because assembler-generated line-number tables are a lot more compact than those the compiler can generate it- self. This option is enabled by default if, at GCC configure time, the assem- bler is found to support such directives. -gno-as-loc-support Force GCC to generate DWARF2+ line number tables internally, if DWARF2+ line number tables are to be generated. -gas-locview-support Inform the compiler that the assembler supports "view" assignment and reset assertion checking in ".loc" directives. This option is enabled by default if, at GCC configure time, the assem- bler is found to support them. -gno-as-locview-support Force GCC to assign view numbers internally, if -gvariable-loca- tion-views are explicitly requested. -gcolumn-info -gno-column-info Emit location column information into DWARF debugging information, rather than just file and line. This option is enabled by default. -gstatement-frontiers -gno-statement-frontiers This option causes GCC to create markers in the internal representation at the beginning of statements, and to keep them roughly in place throughout compilation, using them to guide the output of "is_stmt" markers in the line number table. This is enabled by default when com- piling with optimization (-Os, -O1, -O2, ...), and outputting DWARF 2 debug information at the normal level. -gvariable-location-views -gvariable-location-views=incompat5 -gno-variable-location-views Augment variable location lists with progressive view numbers implied from the line number table. This enables debug information consumers to inspect state at certain points of the program, even if no instruc- tions associated with the corresponding source locations are present at that point. If the assembler lacks support for view numbers in line number tables, this causes the compiler to emit the line number table, which generally makes them somewhat less compact. The augmented line number tables and location lists are fully backward-compatible, so they can be consumed by debug information consumers that are not aware of these augmentations, but they won't derive any benefit from them ei- ther. This is enabled by default when outputting DWARF 2 debug information at the normal level, as long as there is assembler support, -fvar-track- ing-assignments is enabled and -gstrict-dwarf is not. When assembler support is not available, this may still be enabled, but it forces GCC to output internal line number tables, and if -ginternal-reset-loca- tion-views is not enabled, that most certainly leads to silently mis- matching location views. There is a proposed representation for view numbers that is not back- ward compatible with the location list format introduced in DWARF 5, that can be enabled with -gvariable-location-views=incompat5. This op- tion may be removed in the future, is only provided as a reference im- plementation of the proposed representation. Debug information con- sumers are not expected to support this extended format, and they would be rendered unable to decode location lists using it. -ginternal-reset-location-views -gno-internal-reset-location-views Attempt to determine location views that can be omitted from location view lists. This requires the compiler to have very accurate instruc- tion length estimates, which isn't always the case, and it may cause incorrect view lists to be generated silently when using an assembler that does not support location view lists. The GNU assembler flags any such error as a "view number mismatch". This is only enabled on ports that define a reliable estimation function. -ginline-points -gno-inline-points Generate extended debug information for inlined functions. Location view tracking markers are inserted at inlined entry points, so that ad- dress and view numbers can be computed and output in debug information. This can be enabled independently of location views, in which case the view numbers won't be output, but it can only be enabled along with statement frontiers, and it is only enabled by default if location views are enabled. -gz[=type] Produce compressed debug sections in DWARF format, if that is sup- ported. If type is not given, the default type depends on the capabil- ities of the assembler and linker used. type may be one of none (don't compress debug sections), zlib (use zlib compression in ELF gABI for- mat), or zstd (use zstd compression in ELF gABI format). If the linker doesn't support writing compressed debug sections, the option is rejected. Otherwise, if the assembler does not support them, -gz is silently ignored when producing object files. -femit-struct-debug-baseonly Emit debug information for struct-like types only when the base name of the compilation source file matches the base name of file in which the struct is defined. This option substantially reduces the size of debugging information, but at significant potential loss in type information to the debugger. See -femit-struct-debug-reduced for a less aggressive option. See -femit-struct-debug-detailed for more detailed control. This option works only with DWARF debug output. -femit-struct-debug-reduced Emit debug information for struct-like types only when the base name of the compilation source file matches the base name of file in which the type is defined, unless the struct is a template or defined in a system header. This option significantly reduces the size of debugging information, with some potential loss in type information to the debugger. See -femit-struct-debug-baseonly for a more aggressive option. See -femit-struct-debug-detailed for more detailed control. This option works only with DWARF debug output. -femit-struct-debug-detailed[=spec-list] Specify the struct-like types for which the compiler generates debug information. The intent is to reduce duplicate struct debug informa- tion between different object files within the same program. This option is a detailed version of -femit-struct-debug-reduced and -femit-struct-debug-baseonly, which serves for most needs. A specification has the syntax[dir:|ind:][ord:|gen:](any|sys|base|none) The optional first word limits the specification to structs that are used directly (dir:) or used indirectly (ind:). A struct type is used directly when it is the type of a variable, member. Indirect uses arise through pointers to structs. That is, when use of an incomplete struct is valid, the use is indirect. An example is struct one direct; struct two * indirect;. The optional second word limits the specification to ordinary structs (ord:) or generic structs (gen:). Generic structs are a bit compli- cated to explain. For C++, these are non-explicit specializations of template classes, or non-template classes within the above. Other pro- gramming languages have generics, but -femit-struct-debug-detailed does not yet implement them. The third word specifies the source files for those structs for which the compiler should emit debug information. The values none and any have the normal meaning. The value base means that the base of name of the file in which the type declaration appears must match the base of the name of the main compilation file. In practice, this means that when compiling foo.c, debug information is generated for types declared in that file and foo.h, but not other header files. The value sys means those types satisfying base or declared in system or compiler headers. You may need to experiment to determine the best settings for your ap- plication. The default is -femit-struct-debug-detailed=all. This option works only with DWARF debug output. -fno-dwarf2-cfi-asm Emit DWARF unwind info as compiler generated ".eh_frame" section in- stead of using GAS ".cfi_*" directives. -fno-eliminate-unused-debug-types Normally, when producing DWARF output, GCC avoids producing debug sym- bol output for types that are nowhere used in the source file being compiled. Sometimes it is useful to have GCC emit debugging informa- tion for all types declared in a compilation unit, regardless of whether or not they are actually used in that compilation unit, for ex- ample if, in the debugger, you want to cast a value to a type that is not actually used in your program (but is declared). More often, how- ever, this results in a significant amount of wasted space. Options That Control Optimization These options control various sorts of optimizations. Without any optimization option, the compiler's goal is to reduce the cost of compilation and to make debugging produce the expected results. State- ments 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 expect from the source code. Turning on optimization flags makes the compiler attempt to improve the performance and/or code size at the expense of compilation time and possi- bly the ability to debug the program. The compiler performs optimization based on the knowledge it has of the program. Compiling multiple files at once to a single output file mode al- lows the compiler to use information gained from all of the files when com- piling each of them. Not all optimizations are controlled directly by a flag. Only optimiza- tions that have a flag are listed in this section. Most optimizations are completely disabled at -O0 or if an -O level is not set on the command line, even if individual optimization flags are speci- fied. Similarly, -Og suppresses many optimization passes. Depending on the target and how GCC was configured, a slightly different set of optimizations may be enabled at each -O level than those listed here. You can invoke GCC with -Q --help=optimizers to find out the exact set of optimizations that are enabled at each level. -O -O1 --optimize Optimize. Optimizing compilation takes somewhat more time, and a lot more memory for a large function. With -O, the compiler tries to reduce code size and execution time, without performing any optimizations that take a great deal of compila- tion time. -O is the recommended optimization level for large machine-generated code as a sensible balance between time taken to compile and memory use: higher optimization levels perform optimizations with greater al- gorithmic complexity than at -O. -O turns on the following optimization flags: -fauto-inc-dec -fbranch-count-reg -fcombine-stack-adjustments -fcom- pare-elim -fcprop-registers -fdce -fdefer-pop -fdelayed-branch -fdse -fforward-propagate -fguess-branch-probability -fif-conversion -fif-conversion2 -finline-functions-called-once -fipa-modref -fipa-pro- file -fipa-pure-const -fipa-reference -fipa-reference-addressable -fivopts -fmerge-constants -fmove-loop-invariants -fmove-loop-stores -fomit-frame-pointer -freorder-blocks -fshrink-wrap -fshrink-wrap-sepa- rate -fsplit-wide-types -fssa-backprop -fssa-phiopt -ftree-bit-ccp -ftree-ccp -ftree-ch -ftree-coalesce-vars -ftree-copy-prop -ftree-dce -ftree-dominator-opts -ftree-dse -ftree-forwprop -ftree-fre -ftree-phiprop -ftree-pta -ftree-scev-cprop -ftree-sink -ftree-slsr -ftree-sra -ftree-ter -funit-at-a-time -O2 Optimize even more. GCC performs nearly all supported optimizations that do not involve a space-speed tradeoff. As compared to -O, this option increases both compilation time and the performance of the gen- erated code. -O2 turns on all optimization flags specified by -O1. It also turns on the following optimization flags: -falign-functions -falign-jumps -falign-labels -falign-loops -fcaller-saves -fcode-hoisting -fcrossjumping -fcse-follow-jumps -fcse-skip-blocks -fdelete-null-pointer-checks -fdep-fusion -fdevirtu- alize -fdevirtualize-speculatively -fexpensive-optimizations -ffi- nite-loops -fgcse -fgcse-lm -fhoist-adjacent-loads -finline-functions -finline-small-functions -findirect-inlining -fipa-bit-cp -fipa-cp -fipa-icf -fipa-ra -fipa-sra -fipa-vrp -fisolate-erro- neous-paths-dereference -flra-remat -foptimize-crc -foptimize-sib- ling-calls -foptimize-strlen -fpartial-inlining -fpeephole2 -fre- order-blocks-algorithm=stc -freorder-blocks-and-partition -fre- order-functions -frerun-cse-after-loop -fschedule-insns -fschedule-in- sns2 -fsched-interblock -fsched-spec -fspeculatively-call-stored-func- tions -fstore-merging -fstrict-aliasing -fthread-jumps -ftree-builtin-call-dce -ftree-loop-vectorize -ftree-pre -ftree-slp-vectorize -ftree-switch-conversion -ftree-tail-merge -ftree-vrp -fvect-cost-model=very-cheap Please note the warning under -fgcse about invoking -O2 on programs that use computed gotos. -O3 Optimize yet more. -O3 turns on all optimizations specified by -O2 and also turns on the following optimization flags: -fgcse-after-reload -fipa-cp-clone -floop-interchange -floop-un- roll-and-jam -fpeel-loops -fpredictive-commoning -fsplit-loops -fs- plit-paths -ftree-loop-distribution -ftree-partial-pre -funswitch-loops -fvect-cost-model=dynamic -fversion-loops-for-strides -O0 Reduce compilation time and make debugging produce the expected re- sults. This is the default. At -O0, GCC completely disables most optimization passes; they are not run even if you explicitly enable them on the command line, or are listed by -Q --help=optimizers as being enabled by default. Many opti- mizations performed by GCC depend on code analysis or canonicalization passes that are enabled by -O, and it would not be useful to run indi- vidual optimization passes in isolation. -Os Optimize for size. -Os enables all -O2 optimizations except those that often increase code size: -falign-functions -falign-jumps -falign-labels -falign-loops -fprefetch-loop-arrays -freorder-blocks-algorithm=stc It also enables -finline-functions, causes the compiler to tune for code size rather than execution speed, and performs further optimiza- tions designed to reduce code size. -Ofast Disregard strict standards compliance. -Ofast enables all -O3 opti- mizations. It also enables optimizations that are not valid for all standard-compliant programs. It turns on -ffast-math, -fal- low-store-data-races and the Fortran-specific -fstack-arrays, unless -fmax-stack-var-size is specified, and -fno-protect-parens. It turns off -fsemantic-interposition. -Og Optimize while keeping in mind debugging experience. -Og should be the optimization level of choice for the standard edit-compile-debug cycle, offering a reasonable blend of optimization, fast compilation and de- bugging experience especially for code with a high abstraction penalty. In contrast to -O0, this enables -fvar-tracking-assignments and -fvar-tracking which handle debug information in the prologue and epi- logue of functions better than -O0. Like -O0, -Og completely skips a number of optimization passes so that individual options controlling them have no effect. Otherwise -Og en- ables all -O1 optimization flags except for those known to greatly in- terfere with debugging: -fbranch-count-reg -fdelayed-branch -fdse -fif-conversion -fif-con- version2 -finline-functions-called-once -fmove-loop-invariants -fmove-loop-stores -fssa-phiopt -ftree-bit-ccp -ftree-dse -ftree-pta -ftree-sra -Oz Optimize aggressively for size rather than speed. This may increase the number of instructions executed if those instructions require fewer bytes to encode. -Oz behaves similarly to -Os including enabling most -O2 optimizations. If you use multiple -O options, with or without level numbers, the last such option is the one that is effective. Options of the form -fflag specify machine-independent flags. Most flags have both positive and negative forms; the negative form of -ffoo is -fno-foo. In the table below, only one of the forms is listed---the one you typically use. You can figure out the other form by either removing no- or adding it. The following options control specific optimizations. They are either ac- tivated by -O options or are related to ones that are. You can use the following flags in the rare cases when "fine-tuning" of optimizations to be performed is desired. -fno-defer-pop For machines that must pop arguments after a function call, always pop the arguments as soon as each function returns. At levels -O1 and higher, -fdefer-pop is the default; this allows the compiler to let ar- guments accumulate on the stack for several function calls and pop them all at once. -fforward-propagate Perform a forward propagation pass on RTL. The pass tries to combine two instructions and checks if the result can be simplified. If loop unrolling is active, two passes are performed and the second is sched- uled after loop unrolling. This option is enabled by default at optimization levels -O1, -O2, -O3, -Os. -favoid-store-forwarding -fno-avoid-store-forwarding Many CPUs will stall for many cycles when a load partially depends on previous smaller stores. This pass tries to detect such cases and avoid the penalty by changing the order of the load and store and then fixing up the loaded value. Disabled by default. -ffp-contract=style -ffp-contract=off disables floating-point expression contraction. -ffp-contract=fast enables floating-point expression contraction such as forming of fused multiply-add operations if the target has native support for them. -ffp-contract=on enables floating-point expression contraction if allowed by the language standard. This is implemented for C and C++, where it enables contraction within one expression, but not across different statements. The default is -ffp-contract=off for C in a standards compliant mode (-std=c11 or similar), -ffp-contract=fast otherwise. -ffp-int-builtin-inexact Allow the built-in functions "ceil", "floor", "round" and "trunc", and their "float" and "long double" variants, to generate code that raises the "inexact" floating-point exception for noninteger arguments. ISO C99 and C11 allow these functions to raise the "inexact" exception, but ISO/IEC TS 18661-1:2014, the C bindings to IEEE 754-2008, as integrated into ISO C23, does not allow these functions to do so. The default is -fno-fp-int-builtin-inexact, disallowing the exception to be raised, unless C17 or an earlier C standard is selected. This option does nothing unless -ftrapping-math is in effect. Even if -fno-fp-int-builtin-inexact is used, if the functions generate a call to a library function then the "inexact" exception may be raised if the library implementation does not follow TS 18661. -fomit-frame-pointer Omit the frame pointer in functions that don't need one. This avoids the instructions to save, set up and restore the frame pointer; on many targets it also makes an extra register available. On some targets this flag has no effect because the standard calling sequence always uses a frame pointer, so it cannot be omitted. Note that -fno-omit-frame-pointer doesn't guarantee the frame pointer is used in all functions. Several targets always omit the frame pointer in leaf functions. Enabled by default at -O1 and higher. -foptimize-crc Detect loops calculating CRC (performing polynomial long division) and replace them with a faster implementation. Detect 8, 16, 32, and 64 bit CRC, with a constant polynomial without the leading 1 bit, for both bit-forward and bit-reversed cases. If the target supports a CRC in- struction and the polynomial used in the source code matches the poly- nomial used in the CRC instruction, generate that CRC instruction. Otherwise, if the target supports a carry-less-multiplication instruc- tion, generate CRC using it; otherwise generate table-based CRC. Enabled by default at -O2 and higher. -foptimize-sibling-calls Optimize sibling and tail recursive calls. Enabled at levels -O2, -O3, -Os. -foptimize-strlen Optimize various standard C string functions (e.g. "strlen", "strchr" or "strcpy") and their "_FORTIFY_SOURCE" counterparts into faster al- ternatives. Enabled at levels -O2, -O3. -finline-atomics -fno-inline-atomics Inline __atomic operations when a lock-free instruction sequence is available. This optimization is enabled by default. -finline-stringops[=fn] Expand memory and string operations (for now, only "memset") inline, even when the length is variable or big enough as to require looping. This is most useful along with -ffreestanding and -fno-builtin. In some circumstances, it enables the compiler to generate code that takes advantage of known alignment and length multipliers, but even then it may be less efficient than optimized runtime implementations, and grow code size so much that even a less performant but shared im- plementation runs faster due to better use of code caches. This option is disabled by default. -fno-inline Do not expand any functions inline apart from those marked with the "always_inline" attribute. This is the default when not optimizing. Single functions can be exempted from inlining by marking them with the "noinline" attribute. -finline-small-functions Integrate functions into their callers when their body is smaller than expected function call code (so overall size of program gets smaller). The compiler heuristically decides which functions are simple enough to be worth integrating in this way. This inlining applies to all func- tions, even those not declared inline. Enabled at levels -O2, -O3, -Os. -findirect-inlining Inline also indirect calls that are discovered to be known at compile time thanks to previous inlining. This option has any effect only when inlining itself is turned on by the -finline-functions or -fin- line-small-functions options. Enabled at levels -O2, -O3, -Os. -finline-functions Consider all functions for inlining, even if they are not declared in- line. The compiler heuristically decides which functions are worth in- tegrating in this way. If all calls to a given function are integrated, and the function is declared "static", then the function is normally not output as assem- bler code in its own right. Enabled at levels -O2, -O3, -Os. Also enabled by -fprofile-use and -fauto-profile. -finline-functions-called-once Consider all "static" functions called once for inlining into their caller even if they are not marked "inline". If a call to a given function is integrated, then the function is not output as assembler code in its own right. Enabled at levels -O1, -O2, -O3 and -Os, but not -Og. -fearly-inlining Inline functions marked by "always_inline" and functions whose body seems smaller than the function call overhead early before doing -fpro- file-generate instrumentation and real inlining pass. Doing so makes profiling significantly cheaper and usually inlining faster on programs having large chains of nested wrapper functions. Enabled by default. -fipa-sra Perform interprocedural scalar replacement of aggregates, removal of unused parameters and replacement of parameters passed by reference by parameters passed by value. Enabled at levels -O2, -O3 and -Os. -finline-limit=n By default, GCC limits the size of functions that can be inlined. This flag allows coarse control of this limit. n is the size of functions that can be inlined in number of pseudo instructions. Inlining is actually controlled by a number of internal parameters, which are documented in the GCC Internals manual and should not nor- mally be set directly. Note: there may be no value to -finline-limit that results in default behavior. Note: pseudo instruction represents, in this particular context, an ab- stract measurement of function's size. In no way does it represent a count of assembly instructions and as such its exact meaning might change from one release to an another. -fno-keep-inline-dllexport This is a more fine-grained version of -fkeep-inline-functions, which applies only to functions that are declared using the "dllexport" at- tribute or declspec. -fkeep-inline-functions In C, emit "static" functions that are declared "inline" into the ob- ject file, even if the function has been inlined into all of its callers. This switch does not affect functions using the "extern in- line" extension in GNU C90. In C++, emit any and all inline functions into the object file. -fkeep-static-functions Emit "static" functions into the object file, even if the function is never used. -fkeep-static-consts Emit variables declared "static const" when optimization isn't turned on, even if the variables aren't referenced. GCC enables this option by default. If you want to force the compiler to check if a variable is referenced, regardless of whether or not op- timization is turned on, use the -fno-keep-static-consts option. -fmerge-constants Attempt to merge identical constants (string constants and float- ing-point constants) across compilation units. This option is the default for optimized compilation if the assembler and linker support it. Use -fno-merge-constants to inhibit this behav- ior. Enabled at levels -O1, -O2, -O3, -Os. -fmerge-all-constants Attempt to merge identical constants and identical variables. This option implies -fmerge-constants. In addition to -fmerge-con- stants this considers e.g. even constant initialized arrays or initial- ized constant variables with integral or floating-point types. Lan- guages like C or C++ require each variable, including multiple in- stances of the same variable in recursive calls, to have distinct loca- tions, so using this option results in non-conforming behavior. -fmodulo-sched Perform swing modulo scheduling immediately before the first scheduling pass. This pass looks at innermost loops and reorders their instruc- tions by overlapping different iterations. -fmodulo-sched-allow-regmoves Perform more aggressive SMS-based modulo scheduling with register moves allowed. By setting this flag certain anti-dependences edges are deleted, which triggers the generation of reg-moves based on the life-range analysis. This option is effective only with -fmodulo-sched enabled. -fno-branch-count-reg Disable the optimization pass that scans for opportunities to use "decrement and branch" instructions on a count register instead of in- struction sequences that decrement a register, compare it against zero, and then branch based upon the result. This option is only meaningful on architectures that support such instructions, which include x86, PowerPC, IA-64 and S/390. Note that the -fno-branch-count-reg option doesn't remove the decrement and branch instructions from the generated instruction stream introduced by other optimization passes. The default is -fbranch-count-reg at -O1 and higher, except for -Og. -fno-function-cse Do not put function addresses in registers; make each instruction that calls a constant function contain the function's address explicitly. This option results in less efficient code, but some strange hacks that alter the assembler output may be confused by the optimizations per- formed when this option is not used. The default is -ffunction-cse. -ffuse-ops-with-volatile-access Allow limited optimization of operations with volatile memory access when doing so does not change the semantics outlined in The default is -ffuse-ops-with-volatile-access -fno-zero-initialized-in-bss If the target supports a BSS section, GCC by default puts variables that are initialized to zero into BSS. This can save space in the re- sulting code. This option turns off this behavior because some programs explicitly rely on variables going to the data section---e.g., so that the result- ing executable can find the beginning of that section and/or make as- sumptions based on that. The default is -fzero-initialized-in-bss except in Ada. -fthread-jumps Perform optimizations that check to see if a jump branches to a loca- tion 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. Enabled at levels -O1, -O2, -O3, -Os. -fsplit-wide-types When using a type that occupies multiple registers, such as "long long" on a 32-bit system, split the registers apart and allocate them inde- pendently. This normally generates better code for those types, but may make debugging more difficult. Enabled at levels -O1, -O2, -O3, -Os. -fsplit-wide-types-early Fully split wide types early, instead of very late. This option has no effect unless -fsplit-wide-types is turned on. This is the default on some targets. -fcse-follow-jumps In common subexpression elimination (CSE), scan through jump instruc- tions when the target of the jump is not reached by any other path. For example, when CSE encounters an "if" statement with an "else" clause, CSE follows the jump when the condition tested is false. Enabled at levels -O2, -O3, -Os. -fcse-skip-blocks This is similar to -fcse-follow-jumps, but causes CSE to follow jumps that conditionally skip over blocks. When CSE encounters a simple "if" statement with no else clause, -fcse-skip-blocks causes CSE to follow the jump around the body of the "if". Enabled at levels -O2, -O3, -Os. -frerun-cse-after-loop Re-run common subexpression elimination after loop optimizations are performed. Enabled at levels -O2, -O3, -Os. -fgcse Perform a global common subexpression elimination pass. This pass also performs global constant and copy propagation. Note: When compiling a program using computed gotos, a GCC extension, you may get better run-time performance if you disable the global com- mon subexpression elimination pass by adding -fno-gcse to the command line. Enabled at levels -O2, -O3, -Os. -fgcse-lm When -fgcse-lm is enabled, global common subexpression elimination at- tempts to move loads that 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. Enabled by default when -fgcse is enabled. -fgcse-sm When -fgcse-sm is enabled, a store motion pass is run after global com- mon subexpression elimination. This pass attempts to move stores out of loops. When used in conjunction with -fgcse-lm, loops containing a load/store sequence can be changed to a load before the loop and a store after the loop. Not enabled at any optimization level. -fgcse-las When -fgcse-las is enabled, the global common subexpression elimination pass eliminates redundant loads that come after stores to the same mem- ory location (both partial and full redundancies). Not enabled at any optimization level. -fgcse-after-reload When -fgcse-after-reload is enabled, a redundant load elimination pass is performed after reload. The purpose of this pass is to clean up re- dundant spilling. Enabled by -O3, -fprofile-use and -fauto-profile. -faggressive-loop-optimizations This option tells the loop optimizer to use language constraints to de- rive bounds for the number of iterations of a loop. This assumes that loop code does not invoke undefined behavior by for example causing signed integer overflows or out-of-bound array accesses. The bounds for the number of iterations of a loop are used to guide loop unrolling and peeling and loop exit test optimizations. This option is enabled by default. -funconstrained-commons This option tells the compiler that variables declared in common blocks (e.g. Fortran) may later be overridden with longer trailing arrays. This prevents certain optimizations that depend on knowing the array bounds. -fcrossjumping Perform cross-jumping transformation. This transformation unifies equivalent code and saves code size. The resulting code may or may not perform better than without cross-jumping. Enabled at levels -O2, -O3, -Os. -fauto-inc-dec Combine increments or decrements of addresses with memory accesses. This pass is always skipped on architectures that do not have instruc- tions to support this. Enabled by default at -O1 and higher on archi- tectures that support this. -fdce Perform dead code elimination (DCE) on RTL. Enabled by default at -O1 and higher. -fdse Perform dead store elimination (DSE) on RTL. Enabled by default at -O1 and higher. -fif-conversion Attempt to transform conditional jumps into branch-less equivalents. This includes use of conditional moves, min, max, set flags and abs in- structions, and some tricks doable by standard arithmetics. The use of conditional execution on chips where it is available is controlled by -fif-conversion2. Enabled at levels -O1, -O2, -O3, -Os, but not with -Og. -fif-conversion2 Use conditional execution (where available) to transform conditional jumps into branch-less equivalents. Enabled at levels -O1, -O2, -O3, -Os, but not with -Og. -fdeclone-ctor-dtor The C++ ABI requires multiple entry points for constructors and de- structors: one for a base subobject, one for a complete object, and one for a virtual destructor that calls operator delete afterwards. For a hierarchy with virtual bases, the base and complete variants are clones, which means two copies of the function. With this option, the base and complete variants are changed to be thunks that call a common implementation. Enabled by -Os. -fdelete-null-pointer-checks Assume that programs cannot safely dereference null pointers, and that no code or data element resides at address zero. This option enables simple constant folding optimizations at all optimization levels. In addition, other optimization passes in GCC use this flag to control global dataflow analyses that eliminate useless checks for null point- ers; these assume that a memory access to address zero always results in a trap, so that if a pointer is checked after it has already been dereferenced, it cannot be null. Note however that in some environments this assumption is not true. Use -fno-delete-null-pointer-checks to disable this optimization for programs that depend on that behavior. This option is enabled by default on most targets. On AVR and MSP430, this option is completely disabled. Passes that use the dataflow information are enabled independently at different optimization levels. -fdevirtualize Attempt to convert calls to virtual functions to direct calls. This is done both within a procedure and interprocedurally as part of indirect inlining (-findirect-inlining) and interprocedural constant propagation (-fipa-cp). Enabled at levels -O2, -O3, -Os. -fdevirtualize-speculatively Attempt to convert calls to virtual functions to speculative direct calls. Based on the analysis of the type inheritance graph, determine for a given call the set of likely targets. If the set is small, preferably of size 1, change the call into a conditional deciding be- tween direct and indirect calls. The speculative calls enable more op- timizations, such as inlining. When they seem useless after further optimization, they are converted back into original form. -fdevirtualize-at-ltrans Stream extra information needed for aggressive devirtualization when running the link-time optimizer in local transformation mode. This op- tion enables more devirtualization but significantly increases the size of streamed data. For this reason it is disabled by default. -fexpensive-optimizations Perform a number of minor optimizations that are relatively expensive. Enabled at levels -O2, -O3, -Os. -fext-dce -fno-ext-dce Perform dead code elimination on zero and sign extensions, with special dataflow analysis. -free Attempt to remove redundant extension instructions. This is especially helpful for the x86-64 architecture, which implicitly zero-extends in 64-bit registers after writing to their lower 32-bit half. Enabled for Alpha, AArch64, LoongArch, PowerPC, RISC-V, SPARC, h83000 and x86 at levels -O2, -O3, -Os. -fno-lifetime-dse In C++ the value of an object is only affected by changes within its lifetime: when the constructor begins, the object has an indeterminate value, and any changes during the lifetime of the object are dead when the object is destroyed. Normally dead store elimination will take ad- vantage of this; if your code relies on the value of the object storage persisting beyond the lifetime of the object, you can use this flag to disable this optimization. To preserve stores before the constructor starts (e.g. because your operator new clears the object storage) but still treat the object as dead after the destructor, you can use -flifetime-dse=1. The default behavior can be explicitly selected with -flifetime-dse=2. -flifetime-dse=0 is equivalent to -fno-lifetime-dse. -flive-range-shrinkage Attempt to decrease register pressure through register live range shrinkage. This is helpful for fast processors with small or moderate size register sets. -fira-algorithm=algorithm Use the specified coloring algorithm for the integrated register allo- cator. The algorithm argument can be priority, which specifies Chow's priority coloring, or CB, which specifies Chaitin-Briggs coloring. Chaitin-Briggs coloring is not implemented for all architectures, but for those targets that do support it, it is the default because it gen- erates better code. -fira-region=region Use specified regions for the integrated register allocator. The re- gion argument should be one of the following: all Use all loops as register allocation regions. This can give the best results for machines with a small and/or irregular register set. mixed Use all loops except for loops with small register pressure as the regions. This value usually gives the best results in most cases and for most architectures, and is enabled by default when compil- ing with optimization for speed (-O, -O2, ...). one Use all functions as a single region. This typically results in the smallest code size, and is enabled by default for -Os or -O0. -fira-hoist-pressure Use IRA to evaluate register pressure in the code hoisting pass for de- cisions to hoist expressions. This option usually results in smaller code, but it can slow the compiler down. This option is enabled at level -Os for all targets. -fira-loop-pressure Use IRA to evaluate register pressure in loops for decisions to move loop invariants. This option usually results in generation of faster and smaller code on machines with large register files (>= 32 regis- ters), but it can slow the compiler down. This option is enabled at level -O3 for some targets. -fno-ira-share-save-slots Disable sharing of stack slots used for saving call-used hard registers living through a call. Each hard register gets a separate stack slot, and as a result function stack frames are larger. -fno-ira-share-spill-slots Disable sharing of stack slots allocated for pseudo-registers. Each pseudo-register that does not get a hard register gets a separate stack slot, and as a result function stack frames are larger. -flra-remat Enable CFG-sensitive rematerialization in LRA. Instead of loading val- ues of spilled pseudos, LRA tries to rematerialize (recalculate) values if it is profitable. Enabled at levels -O2, -O3, -Os. -fdelayed-branch If supported for the target machine, attempt to reorder instructions to exploit instruction slots available after delayed branch instructions. Enabled at levels -O1, -O2, -O3, -Os, but not at -Og. -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 in- structions by allowing other instructions to be issued until the result of the load or floating-point instruction is required. Conventionally enabled at optimization levels -O2 and -O3. However, many targets override this behavior. For example, on x86, it is dis- abled at all levels, while on AArch64, it is enabled only at -O3. -fschedule-insns2 Similar to -fschedule-insns, but requests an additional pass of in- struction scheduling after register allocation has been done. This is especially useful on machines with a relatively small number of regis- ters and where memory load instructions take more than one cycle. Enabled at levels -O2, -O3, -Os. -fno-sched-interblock Disable instruction scheduling across basic blocks, which is normally enabled when scheduling before register allocation, i.e. with -fsched- ule-insns or at -O2 or higher. -fno-sched-spec Disable speculative motion of non-load instructions, which is normally enabled when scheduling before register allocation, i.e. with -fsched- ule-insns or at -O2 or higher. -fsched-pressure Enable register pressure sensitive insn scheduling before register al- location. This only makes sense when scheduling before register allo- cation is enabled, i.e. with -fschedule-insns or at -O2 or higher. Us- age of this option can improve the generated code and decrease its size by preventing register pressure increase above the number of available hard registers and subsequent spills in register allocation. -fsched-spec-load Allow speculative motion of some load instructions. This only makes sense when scheduling before register allocation, i.e. with -fsched- ule-insns or at -O2 or higher. -fsched-spec-load-dangerous Allow speculative motion of more load instructions. This only makes sense when scheduling before register allocation, i.e. with -fsched- ule-insns or at -O2 or higher. -fsched-stalled-insns -fsched-stalled-insns=n Define how many insns (if any) can be moved prematurely from the queue of stalled insns into the ready list during the second scheduling pass. -fno-sched-stalled-insns means that no insns are moved prematurely, -fsched-stalled-insns=0 means there is no limit on how many queued in- sns can be moved prematurely. -fsched-stalled-insns without a value is equivalent to -fsched-stalled-insns=1. -fsched-stalled-insns-dep -fsched-stalled-insns-dep=n Define how many insn groups (cycles) are examined for a dependency on a stalled insn that is a candidate for premature removal from the queue of stalled insns. This has an effect only during the second scheduling pass, and only if -fsched-stalled-insns is used. -fno-sched-stalled-insns-dep is equivalent to -fsched-stalled-in- sns-dep=0. -fsched-stalled-insns-dep without a value is equivalent to -fsched-stalled-insns-dep=1. -fsched2-use-superblocks When scheduling after register allocation, use superblock scheduling. This allows motion across basic block boundaries, resulting in faster schedules. This option is experimental, as not all machine descrip- tions used by GCC model the CPU closely enough to avoid unreliable re- sults from the algorithm. This only makes sense when scheduling after register allocation, i.e. with -fschedule-insns2 or at -O2 or higher. -fsched-group-heuristic Enable the group heuristic in the scheduler. This heuristic favors the instruction that belongs to a schedule group. This is enabled by de- fault when scheduling is enabled, i.e. with -fschedule-insns or -fschedule-insns2 or at -O2 or higher. -fsched-critical-path-heuristic Enable the critical-path heuristic in the scheduler. This heuristic favors instructions on the critical path. This is enabled by default when scheduling is enabled, i.e. with -fschedule-insns or -fsched- ule-insns2 or at -O2 or higher. -fsched-spec-insn-heuristic Enable the speculative instruction heuristic in the scheduler. This heuristic favors speculative instructions with greater dependency weak- ness. This is enabled by default when scheduling is enabled, i.e. with -fschedule-insns or -fschedule-insns2 or at -O2 or higher. -fsched-rank-heuristic Enable the rank heuristic in the scheduler. This heuristic favors the instruction belonging to a basic block with greater size or frequency. This is enabled by default when scheduling is enabled, i.e. with -fschedule-insns or -fschedule-insns2 or at -O2 or higher. -fsched-last-insn-heuristic Enable the last-instruction heuristic in the scheduler. This heuristic favors the instruction that is less dependent on the last instruction scheduled. This is enabled by default when scheduling is enabled, i.e. with -fschedule-insns or -fschedule-insns2 or at -O2 or higher. -fsched-dep-count-heuristic Enable the dependent-count heuristic in the scheduler. This heuristic favors the instruction that has more instructions depending on it. This is enabled by default when scheduling is enabled, i.e. with -fschedule-insns or -fschedule-insns2 or at -O2 or higher. -fspeculatively-call-stored-functions Attempt to convert indirect calls of function pointers to pointers loaded from a structure field if all visible stores to that field store just a single candidate. When doing so, turn the call into a condi- tional deciding between the direct call and the original indirect one. These speculative calls often enable more optimizations, such as inlin- ing. When they seem useless after further optimization, they are con- verted back into original form. -freschedule-modulo-scheduled-loops Modulo scheduling is performed before traditional scheduling. If a loop is modulo scheduled, later scheduling passes may change its sched- ule. Use this option to control that behavior. -fselective-scheduling Schedule instructions using selective scheduling algorithm. Selective scheduling runs instead of the first scheduler pass. -fselective-scheduling2 Schedule instructions using selective scheduling algorithm. Selective scheduling runs instead of the second scheduler pass. -fsel-sched-pipelining Enable software pipelining of innermost loops during selective schedul- ing. This option has no effect unless one of -fselective-scheduling or -fselective-scheduling2 is turned on. -fsel-sched-pipelining-outer-loops When pipelining loops during selective scheduling, also pipeline outer loops. This option has no effect unless -fsel-sched-pipelining is turned on. -fsemantic-interposition Some object formats, like ELF, allow interposing of symbols by the dy- namic linker. This means that for symbols exported from the DSO, the compiler cannot perform interprocedural propagation, inlining and other optimizations in anticipation that the function or variable in question may change. While this feature is useful, for example, to rewrite mem- ory allocation functions by a debugging implementation, it is expensive in the terms of code quality. With -fno-semantic-interposition the compiler assumes that if interposition happens for functions the over- writing function will have precisely the same semantics (and side ef- fects). Similarly if interposition happens for variables, the con- structor of the variable will be the same. The flag has no effect for functions explicitly declared inline (where it is never allowed for in- terposition to change semantics) and for symbols explicitly declared weak. -fshrink-wrap Emit function prologues only before parts of the function that need it, rather than at the top of the function. This flag is enabled by de- fault at -O and higher. -fshrink-wrap-separate Shrink-wrap separate parts of the prologue and epilogue separately, so that those parts are only executed when needed. This option is on by default, but has no effect unless -fshrink-wrap is also turned on and the target supports this. -fcaller-saves Enable allocation of values to registers that are 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 re- sult in better code. This option is always enabled by default on certain machines, usually those which have no call-preserved registers to use instead. Enabled at levels -O2, -O3, -Os. -fcombine-stack-adjustments Tracks stack adjustments (pushes and pops) and stack memory references and then tries to find ways to combine them. Enabled by default at -O1 and higher. -fipa-ra Use caller save registers for allocation if those registers are not used by any called function. In that case it is not necessary to save and restore them around calls. This is only possible if called func- tions are part of same compilation unit as current function and they are compiled before it. Enabled at levels -O2, -O3, -Os, however the option is disabled if gen- erated code will be instrumented for profiling (-p, or -pg) or if callee's register usage cannot be known exactly (this happens on tar- gets that do not expose prologues and epilogues in RTL). -fconserve-stack Attempt to minimize stack usage. The compiler attempts to use less stack space, even if that makes the program slower. This option im- plies setting the large-stack-frame parameter to 100 and the large-stack-frame-growth parameter to 400. -ftree-reassoc Perform reassociation on trees. This flag is enabled by default at -O1 and higher. -fcode-hoisting Perform code hoisting. Code hoisting tries to move the evaluation of expressions executed on all paths to the function exit as early as pos- sible. This is especially useful as a code size optimization, but it often helps for code speed as well. This flag is enabled by default at -O2 and higher. -ftree-pre Perform partial redundancy elimination (PRE) on trees. This flag is enabled by default at -O2 and -O3. -ftree-partial-pre Make partial redundancy elimination (PRE) more aggressive. This flag is enabled by default at -O3. -ftree-forwprop Perform forward propagation on trees. This flag is enabled by default at -O1 and higher. -ftree-fre Perform full redundancy elimination (FRE) on trees. The difference be- tween FRE and PRE is that FRE only considers expressions that are com- puted on all paths leading to the redundant computation. This analysis is faster than PRE, though it exposes fewer redundancies. This flag is enabled by default at -O1 and higher. -ftree-phiprop Perform hoisting of loads from conditional pointers on trees. This pass is enabled by default at -O1 and higher. -fhoist-adjacent-loads Speculatively hoist loads from both branches of an if-then-else if the loads are from adjacent locations in the same structure and the target architecture has a conditional move instruction. This flag is enabled by default at -O2 and higher. -ftree-copy-prop Perform copy propagation on trees. This pass eliminates unnecessary copy operations. This flag is enabled by default at -O1 and higher. -fipa-pure-const Discover which functions are pure or constant. Enabled by default at -O1 and higher. -fipa-reference Discover which static variables do not escape the compilation unit. Enabled by default at -O1 and higher. -fipa-reference-addressable Discover read-only, write-only and non-addressable static variables. Enabled by default at -O1 and higher. -fipa-reorder-for-locality Group call chains close together in the binary layout to improve code locality and minimize jump distances between frequently called func- tions. Unlike -freorder-functions this pass considers the call chains between functions and groups them together, rather than grouping all hot/normal/cold/never-executed functions into separate sections. Un- like -fprofile-reorder-functions it aims to improve code locality throughout the runtime of the program rather than focusing on program startup. This option is incompatible with an explicit -flto-partition= option since it enforces a custom partitioning scheme. If using this option it is recommended to also use profile feedback, but this option is not enabled by default otherwise. -fipa-stack-alignment Reduce stack alignment on call sites if possible. Enabled by default. -fipa-pta Perform interprocedural pointer analysis and interprocedural modifica- tion and reference analysis. This option can cause excessive memory and compile-time usage on large compilation units. It is not enabled by default at any optimization level. -fipa-profile Perform interprocedural profile propagation. The functions called only from cold functions are marked as cold. Also functions executed once (such as "cold", "noreturn", static constructors or destructors) are identified. Cold functions and loop less parts of functions executed once are then optimized for size. Enabled by default at -O1 and higher. -fipa-modref Perform interprocedural mod/ref analysis. This optimization analyzes the side effects of functions (memory locations that are modified or referenced) and enables better optimization across the function call boundary. This flag is enabled by default at -O1 and higher. -fipa-cp Perform interprocedural constant propagation. This optimization ana- lyzes the program to determine when values passed to functions are con- stants and then optimizes accordingly. This optimization can substan- tially increase performance if the application has constants passed to functions. This flag is enabled by default at -O2, -Os and -O3. It is also enabled by -fprofile-use and -fauto-profile. -fipa-cp-clone Perform function cloning to make interprocedural constant propagation stronger. When enabled, interprocedural constant propagation performs function cloning when externally visible function can be called with constant arguments. Because this optimization can create multiple copies of functions, it may significantly increase code size. This flag is enabled by default at -O3. It is also enabled by -fprofile-use and -fauto-profile. -fipa-bit-cp When enabled, perform interprocedural bitwise constant propagation. This flag is enabled by default at -O2 and by -fprofile-use and -fauto-profile. It requires that -fipa-cp is enabled. -fipa-vrp When enabled, perform interprocedural propagation of value ranges. This flag is enabled by default at -O2. It requires that -fipa-cp is en- abled. -fipa-icf-functions -fipa-icf-variables -fipa-icf Perform Identical Code Folding for functions (-fipa-icf-functions), read-only variables (-fipa-icf-variables), or both (-fipa-icf). The optimization reduces code size and may disturb unwind stacks by replac- ing a function by an equivalent one with a different name. The opti- mization works more effectively with link-time optimization enabled. Although the behavior is similar to the Gold Linker's ICF optimization, GCC ICF works on different levels and thus the optimizations are not same - there are equivalences that are found only by GCC and equiva- lences found only by Gold. -fipa-icf is enabled by default at -O2 and -Os. -flate-combine-instructions Enable two instruction combination passes that run relatively late in the compilation process. One of the passes runs before register allo- cation and the other after register allocation. The main aim of the passes is to substitute definitions into all uses. Most targets enable this flag by default at -O2 and -Os. -flive-patching=level Control GCC's optimizations to produce output suitable for live-patch- ing. If the compiler's optimization uses a function's body or information extracted from its body to optimize/change another function, the latter is called an impacted function of the former. If a function is patched, its impacted functions should be patched too. The impacted functions are determined by the compiler's interprocedural optimizations. For example, a caller is impacted when inlining a func- tion into its caller, cloning a function and changing its caller to call this new clone, or extracting a function's pureness/constness in- formation to optimize its direct or indirect callers, etc. Usually, the more IPA optimizations enabled, the larger the number of impacted functions for each function. In order to control the number of impacted functions and more easily compute the list of impacted function, IPA optimizations can be partially enabled at two different levels. The level argument should be one of the following: inline-clone Only enable inlining and cloning optimizations, which includes in- lining, cloning, interprocedural scalar replacement of aggregates and partial inlining. As a result, when patching a function, all its callers and its clones' callers are impacted, therefore need to be patched as well. -flive-patching=inline-clone disables the following optimization flags: -fwhole-program -fipa-pta -fipa-reference -fipa-ra -fipa-icf -fipa-icf-functions -fipa-icf-variables -fipa-bit-cp -fipa-vrp -fipa-pure-const -fipa-reference-addressable -fipa-stack-alignment -fipa-modref inline-only-static Only enable inlining of static functions. As a result, when patch- ing a static function, all its callers are impacted and so need to be patched as well. In addition to all the flags that -flive-patching=inline-clone dis- ables, -flive-patching=inline-only-static disables the following additional optimization flags: -fipa-cp-clone -fipa-sra -fpar- tial-inlining -fipa-cp When -flive-patching is specified without any value, the default value is inline-clone. This flag is disabled by default. Note that -flive-patching is not supported with link-time optimization (-flto). -fisolate-erroneous-paths-dereference Detect paths that trigger erroneous or undefined behavior due to deref- erencing a null pointer (with -fdelete-null-pointer-checks enabled) or a division by zero. Isolate those paths from the main control flow and turn the statement with erroneous or undefined behavior into a trap. This flag is enabled by default at -O2 and higher. -fisolate-erroneous-paths-attribute Detect paths that trigger erroneous or undefined behavior due to a null value being used in a way forbidden by a "returns_nonnull" or "nonnull" attribute. Isolate those paths from the main control flow and turn the statement with erroneous or undefined behavior into a trap. This is not currently enabled, but may be enabled by -O2 in the future. -ftree-sink Perform forward store motion on trees. This flag is enabled by default at -O1 and higher. -ftree-bit-ccp Perform sparse conditional bit constant propagation on trees and propa- gate pointer alignment information. This pass only operates on local scalar variables and is enabled by default at -O1 and higher, except for -Og. It requires that -ftree-ccp is enabled. -ftree-ccp Perform sparse conditional constant propagation (CCP) on trees. This pass only operates on local scalar variables and is enabled by default at -O1 and higher. -fssa-backprop Propagate information about uses of a value up the definition chain in order to simplify the definitions. For example, this pass strips sign operations if the sign of a value never matters. The flag is enabled by default at -O1 and higher. -fssa-phiopt Perform pattern matching on SSA PHI nodes to optimize conditional code. This pass is enabled by default at -O1 and higher, except for -Og. -ftree-switch-conversion Perform conversion of simple initializations in a switch to initializa- tions from a scalar array. This flag is enabled by default at -O2 and higher. -ftree-tail-merge Look for identical code sequences. When found, replace one with a jump to the other. This optimization is known as tail merging or cross jumping. This flag is enabled by default at -O2 and higher. The com- pilation time in this pass can be limited using max-tail-merge-compar- isons parameter and max-tail-merge-iterations parameter. -ftree-cselim Perform conditional store elimination on trees. This flag is enabled by default at -O1 and higher on targets that have conditional move in- structions. -ftree-dce Perform dead code elimination (DCE) on trees. This flag is enabled by default at -O1 and higher. -ftree-builtin-call-dce Perform conditional dead code elimination (DCE) for calls to built-in functions that may set "errno" but are otherwise free of side effects. This flag is enabled by default at -O2 and higher if -Os is not also specified. -ffinite-loops Assume that a loop with an exit will eventually take the exit and not loop indefinitely. This allows the compiler to remove loops that oth- erwise have no side-effects, not considering eventual endless looping as such. This option is enabled by default at -O2 for C++ with -std=c++11 or higher. -ftree-dominator-opts Perform a variety of simple scalar cleanups (constant/copy propagation, redundancy elimination, range propagation and expression simplifica- tion) based on a dominator tree traversal. This also performs jump threading (to reduce jumps to jumps). This flag is enabled by default at -O1 and higher. -ftree-dse Perform dead store elimination (DSE) on trees. A dead store is a store into a memory location that is later overwritten by another store with- out any intervening loads. In this case the earlier store can be deleted. This flag is enabled by default at -O1 and higher. -ftree-ch Perform loop header copying on trees. This is beneficial since it in- creases effectiveness of code motion optimizations. It also saves one jump. This flag is enabled by default at -O1 and higher. It is not enabled for -Os, since it usually increases code size. -ftree-loop-optimize Perform loop optimizations on trees. This flag is enabled by default at -O1 and higher. -ftree-loop-linear -floop-strip-mine -floop-block Perform loop nest optimizations. Same as -floop-nest-optimize. To use this code transformation, GCC has to be configured with --with-isl to enable the Graphite loop transformation infrastructure. -fgraphite-identity Enable the identity transformation for graphite. For every SCoP we generate the polyhedral representation and transform it back to gimple. Using -fgraphite-identity we can check the costs or benefits of the GIMPLE -> GRAPHITE -> GIMPLE transformation. Some minimal optimiza- tions are also performed by the code generator isl, like index split- ting and dead code elimination in loops. -floop-nest-optimize Enable the isl based loop nest optimizer. This is a generic loop nest optimizer based on the Pluto optimization algorithms. It calculates a loop structure optimized for data-locality and parallelism. This op- tion is experimental. -floop-parallelize-all Use the Graphite data dependence analysis to identify loops that can be parallelized. Parallelize all the loops that can be analyzed to not contain loop carried dependences without checking that it is profitable to parallelize the loops. -ftree-coalesce-vars While transforming the program out of the SSA representation, attempt to reduce copying by coalescing versions of different user-defined variables, instead of just compiler temporaries. This may severely limit the ability to debug an optimized program compiled with -fno-var-tracking-assignments. In the negated form, this flag prevents SSA coalescing of user variables. This option is enabled by default if optimization is enabled, and it does very little otherwise. -ftree-loop-if-convert Attempt to transform conditional jumps in the innermost loops to branch-less equivalents. The intent is to remove control-flow from the innermost loops in order to improve the ability of the vectorization pass to handle these loops. This is enabled by default if vectoriza- tion is enabled. -ftree-loop-distribution Perform loop distribution. This flag can improve cache performance on big loop bodies and allow further loop optimizations, like paralleliza- tion or vectorization, to take place. For example, the loop DO I = 1, N A(I) = B(I) + C D(I) = E(I) * F ENDDO is transformed to DO I = 1, N A(I) = B(I) + C ENDDO DO I = 1, N D(I) = E(I) * F ENDDO This flag is enabled by default at -O3. It is also enabled by -fpro- file-use and -fauto-profile. -ftree-loop-distribute-patterns Perform loop distribution of patterns that can be code generated with calls to a library. This flag is enabled by default at -O2 and higher, and by -fprofile-use and -fauto-profile. This pass distributes the initialization loops and generates a call to memset zero. For example, the loop DO I = 1, N A(I) = 0 B(I) = A(I) + I ENDDO is transformed to DO I = 1, N A(I) = 0 ENDDO DO I = 1, N B(I) = A(I) + I ENDDO and the initialization loop is transformed into a call to memset zero. -floop-interchange Perform loop interchange outside of graphite. This flag can improve cache performance on loop nest and allow further loop optimizations, like vectorization, to take place. For example, the loop for (int i = 0; i < N; i++) for (int j = 0; j < N; j++) for (int k = 0; k < N; k++) c[i][j] = c[i][j] + a[i][k]*b[k][j]; is transformed to for (int i = 0; i < N; i++) for (int k = 0; k < N; k++) for (int j = 0; j < N; j++) c[i][j] = c[i][j] + a[i][k]*b[k][j]; This flag is enabled by default at -O3. It is also enabled by -fpro- file-use and -fauto-profile. -floop-unroll-and-jam Apply unroll and jam transformations on feasible loops. In a loop nest this unrolls the outer loop by some factor and fuses the resulting mul- tiple inner loops. This flag is enabled by default at -O3. It is also enabled by -fprofile-use and -fauto-profile. -ftree-loop-im Perform loop invariant motion on trees. This pass moves only invari- ants that are hard to handle at RTL level (function calls, operations that expand to nontrivial sequences of insns). With -funswitch-loops it also moves operands of conditions that are invariant out of the loop, so that we can use just trivial invariantness analysis in loop unswitching. The pass also includes store motion. -ftree-loop-ivcanon Create a canonical counter for number of iterations in loops for which determining number of iterations requires complicated analysis. Later optimizations then may determine the number easily. Useful especially in connection with unrolling. -ftree-scev-cprop Perform final value replacement. If a variable is modified in a loop in such a way that its value when exiting the loop can be determined using only its initial value and the number of loop iterations, replace uses of the final value by such a computation, provided it is suffi- ciently cheap. This reduces data dependencies and may allow further simplifications. Enabled by default at -O1 and higher. -fivopts Perform induction variable optimizations (strength reduction, induction variable merging and induction variable elimination) on trees. Enabled by default at -O1 and higher. -ftree-parallelize-loops -ftree-parallelize-loops=n Parallelize loops, i.e., split their iteration space to run in multiple threads. This is only possible for loops whose iterations are indepen- dent and can be arbitrarily reordered. The optimization is only prof- itable on multiprocessor machines, for loops that are CPU-intensive, rather than constrained e.g. by memory bandwidth. This option implies -pthread, and thus is only supported on targets that have support for -pthread. When a positive value n is specified, the number of threads is fixed at compile time and cannot be changed after compilation. The compiler gen- erates "#pragma omp parallel num_threads(n)". When used without "=n" (i.e., -ftree-parallelize-loops), the number of threads is determined at program execution time via the OMP_NUM_THREADS environment variable. If OMP_NUM_THREADS is not set, the OpenMP runtime automatically detects the number of available processors and uses that value. This enables creating binaries that adapt to different hardware configurations without recompilation. -ftree-pta Perform function-local points-to analysis on trees. This flag is en- abled by default at -O1 and higher, except for -Og. -ftree-sra Perform scalar replacement of aggregates. This pass replaces structure references with scalars to prevent committing structures to memory too early. This flag is enabled by default at -O1 and higher, except for -Og. -fstore-merging Perform merging of narrow stores to consecutive memory addresses. This pass merges contiguous stores of immediate values narrower than a word into fewer wider stores to reduce the number of instructions. This is enabled by default at -O2 and higher as well as -Os. -ftree-ter Perform temporary expression replacement during the SSA->normal phase. Single use/single def temporaries are replaced at their use location with their defining expression. This results in non-GIMPLE code, but gives the expanders much more complex trees to work on resulting in better RTL generation. This is enabled by default at -O1 and higher. -ftree-slsr Perform straight-line strength reduction on trees. This recognizes re- lated expressions involving multiplications and replaces them by less expensive calculations when possible. This is enabled by default at -O1 and higher. -ftree-vectorize Perform vectorization on trees. This flag enables -ftree-loop-vectorize and -ftree-slp-vectorize if not explicitly specified. -ftree-loop-vectorize Perform loop vectorization on trees. This flag is enabled by default at -O2 and by -ftree-vectorize, -fprofile-use, and -fauto-profile. -ftree-slp-vectorize Perform basic block vectorization on trees. This flag is enabled by de- fault at -O2 and by -ftree-vectorize, -fprofile-use, and -fauto-pro- file. -ftrivial-auto-var-init=choice Initialize automatic variables or temporary objects with either a pat- tern or with zeroes to increase the security and predictability of a program by preventing uninitialized memory disclosure and use. GCC still considers an automatic variable that doesn't have an explicit initializer as uninitialized, -Wuninitialized and -Wana- lyzer-use-of-uninitialized-value will still report warning messages on such automatic variables or temporary objects and the compiler will perform optimization as if the variable were uninitialized. With this option, GCC will also initialize any padding of automatic variables or temporary objects that have structure or union types to zeroes. How- ever, the current implementation cannot initialize automatic variables whose initialization is bypassed through "switch" or "goto" statement. Using -Wtrivial-auto-var-init to report all such cases. The three values of choice are: * uninitialized doesn't initialize any automatic variables. * pattern Initialize automatic variables with values which will likely transform logic bugs into crashes down the line, are easily recognized in a crash dump and without being values that program- mers can rely on for useful program semantics. The current value is byte-repeatable pattern with byte "0xFE". The values used for pattern initialization might be changed in the future. * zero Initialize automatic variables with zeroes. The default is uninitialized except for C++26, in which case if -ftriv- ial-auto-var-init= is not specified at all automatic variables or tem- porary objects are zero initialized, but zero initialization of padding bits does not happen. Note that the initializer values, whether zero or pattern, refer to data representation (in memory or machine registers), rather than to their interpretation as numerical values. This distinction may be im- portant in languages that support types with biases or implicit multi- pliers, and with such extensions as hardbool. For example, a variable that uses 8 bits to represent (biased) quantities in the "range 160..400" will be initialized with the bit patterns 0x00 or 0xFE, de- pending on choice, whether or not these representations stand for val- ues in that range, and even if they do, the interpretation of the value held by the variable will depend on the bias. A hardbool variable that uses say 0x5A and 0xA5 for "false" and "true", respectively, will trap with either choice of trivial initializer, i.e., zero initialization will not convert to the representation for "false", even if it would for a "static" variable of the same type. This means the initializer pattern doesn't generally depend on the type of the initialized vari- able. One notable exception is that (non-hardened) boolean variables that fit in registers are initialized with "false" (zero), even when pattern is requested. You can control this behavior for a specific variable by using the variable attribute "uninitialized" standard attribute or the C++26 "[[indeterminate]]". -fvect-cost-model=model Alter the cost model used for vectorization. The model argument should be one of unlimited, dynamic, cheap or very-cheap. With the unlimited model the vectorized code-path is assumed to be profitable while with the dynamic model a runtime check guards the vectorized code-path to enable it only for iteration counts that will likely execute faster than when executing the original scalar loop. The cheap model disables vectorization of loops where doing so would be cost prohibitive for ex- ample due to required runtime checks for data dependence or alignment but otherwise is equal to the dynamic model. The very-cheap model dis- ables vectorization of loops when any runtime check for data dependence or alignment is required, it also disables vectorization of epilogue loops but otherwise is equal to the cheap model. The default cost model depends on other optimization flags and is ei- ther dynamic or cheap. -fsimd-cost-model=model Alter the cost model used for vectorization of loops marked with the OpenMP simd directive. The model argument should be one of unlimited, dynamic, cheap. All values of model have the same meaning as described in -fvect-cost-model and by default a cost model defined with -fvect-cost-model is used. -ftree-vrp Perform Value Range Propagation on trees. This is similar to the con- stant propagation pass, but instead of values, ranges of values are propagated. This allows the optimizers to remove unnecessary range checks like array bound checks and null pointer checks. This is en- abled by default at -O2 and higher. Null pointer check elimination is only done if -fdelete-null-pointer-checks is enabled. -fsplit-paths Split paths leading to loop backedges. This can improve dead code elimination and common subexpression elimination. This is enabled by default at -O3 and above. -fsplit-ivs-in-unroller Enables expression of values of induction variables in later iterations of the unrolled loop using the value in the first iteration. This breaks long dependency chains, thus improving efficiency of the sched- uling passes. A combination of -fweb and CSE is often sufficient to obtain the same effect. However, that is not reliable in cases where the loop body is more complicated than a single basic block. It also does not work at all on some architectures due to restrictions in the CSE pass. This optimization is enabled by default. -fvariable-expansion-in-unroller With this option, the compiler creates multiple copies of some local variables when unrolling a loop, which can result in superior code. This optimization is enabled by default for PowerPC targets, but dis- abled by default otherwise. -fpartial-inlining Inline parts of functions. This option has any effect only when inlin- ing itself is turned on by the -finline-functions or -fin- line-small-functions options. Enabled at levels -O2, -O3, -Os. -fpredictive-commoning Perform predictive commoning optimization, i.e., reusing computations (especially memory loads and stores) performed in previous iterations of loops. This option is enabled at level -O3. It is also enabled by -fpro- file-use and -fauto-profile. -fprefetch-loop-arrays If supported by the target machine, generate instructions to prefetch memory to improve the performance of loops that access large arrays. This option may generate better or worse code; results are highly de- pendent on the structure of loops within the source code. Disabled at level -Os. -fno-printf-return-value Do not substitute constants for known return value of formatted output functions such as "sprintf", "snprintf", "vsprintf", and "vsnprintf" (but not "printf" of "fprintf"). This transformation allows GCC to op- timize or even eliminate branches based on the known return value of these functions called with arguments that are either constant, or whose values are known to be in a range that makes determining the ex- act return value possible. For example, when -fprintf-return-value is in effect, both the branch and the body of the "if" statement (but not the call to "snprint") can be optimized away when "i" is a 32-bit or smaller integer because the return value is guaranteed to be at most 8. char buf[9]; if (snprintf (buf, "%08x", i) >= sizeof buf) ... The -fprintf-return-value option relies on other optimizations and yields best results with -O2 and above. It works in tandem with the -Wformat-overflow and -Wformat-truncation options. The -fprintf-re- turn-value option is enabled by default. -fno-peephole -fno-peephole2 Disable any machine-specific peephole optimizations. The difference between -fno-peephole and -fno-peephole2 is in how they are implemented in the compiler; some targets use one, some use the other, a few use both. -fpeephole is enabled by default. -fpeephole2 enabled at levels -O2, -O3, -Os. -fno-guess-branch-probability Do not guess branch probabilities using heuristics. GCC uses heuristics to guess branch probabilities if they are not pro- vided by profiling feedback (-fprofile-arcs). These heuristics are based on the control flow graph. If some branch probabilities are specified by "__builtin_expect", then the heuristics are used to guess branch probabilities for the rest of the control flow graph, taking the "__builtin_expect" info into account. The interactions between the heuristics and "__builtin_expect" can be complex, and in some cases, it may be useful to disable the heuristics so that the effects of "__builtin_expect" are easier to understand. It is also possible to specify expected probability of the expression with "__builtin_expect_with_probability" built-in function. The default is -fguess-branch-probability at levels -O, -O2, -O3, -Os. -freorder-blocks Reorder basic blocks in the compiled function in order to reduce number of taken branches and improve code locality. Enabled at levels -O1, -O2, -O3, -Os. -freorder-blocks-algorithm=algorithm Use the specified algorithm for basic block reordering. The algorithm argument can be simple, which does not increase code size (except some- times due to secondary effects like alignment), or stc, the "software trace cache" algorithm, which tries to put all often executed code to- gether, minimizing the number of branches executed by making extra copies of code. The default is simple at levels -O1, -Os, and stc at levels -O2, -O3. -freorder-blocks-and-partition In addition to reordering basic blocks in the compiled function, in or- der to reduce number of taken branches, partitions hot and cold basic blocks into separate sections of the assembly and .o files, to improve paging and cache locality performance. This optimization is automatically turned off in the presence of excep- tion handling or unwind tables (on targets using setjump/longjump or target specific scheme), for linkonce sections, for functions with a user-defined section attribute and on any architecture that does not support named sections. When -fsplit-stack is used this option is not enabled by default (to avoid linker errors), but may be enabled explic- itly (if using a working linker). Enabled for x86 at levels -O2, -O3, -Os. -freorder-functions Reorder functions in the object file in order to improve code locality. Unlike -fipa-reorder-for-locality this option prioritises grouping all functions within a category (hot/normal/cold/never-executed) together. This is implemented by using special subsections ".text.hot" for most frequently executed functions and ".text.unlikely" for unlikely exe- cuted functions. Reordering is done by the linker so object file for- mat must support named sections and linker must place them in a reason- able way. This option isn't effective unless you either provide profile feedback (see -fprofile-arcs for details) or manually annotate functions with "hot" or "cold" attributes. Enabled at levels -O2, -O3, -Os. -fstrict-aliasing Allow the compiler to assume the strictest aliasing rules applicable to the language being compiled. For C (and C++), this activates optimiza- tions based on the type of expressions. In particular, accessing an object of one type via an expression of a different type is not al- lowed, unless the types are compatible types, differ only in signedness or qualifiers, or the expression has a character type. Accessing scalar objects via a corresponding vector type is also allowed. For example, an "unsigned int" can alias an "int", but not a "void*" or a "double". A character type may alias any other type. Pay special attention to code like this: union a_union { int i; double d; }; int f() { union a_union t; t.d = 3.0; return t.i; } The practice of reading from a different union member than the one most recently written to (called "type-punning") is common. Even with -fstrict-aliasing, type-punning is allowed in C, provided the memory is accessed through the union type. In ISO C++, type-punning through a union type is undefined behavior, but GCC supports it as an extension. So, the code above works as expected. However, this code might not: int f() { union a_union t; int* ip; t.d = 3.0; ip = &t.i; return *ip; } Similarly, access by taking the address, casting the resulting pointer and dereferencing the result has undefined behavior, even if the cast uses a union type, e.g.: int f() { double d = 3.0; return ((union a_union *) &d)->i; } The -fstrict-aliasing option is enabled at levels -O2, -O3, -Os. -fipa-strict-aliasing Controls whether rules of -fstrict-aliasing are applied across function boundaries. Note that if multiple functions gets inlined into a single function the memory accesses are no longer considered to be crossing a function boundary. The -fipa-strict-aliasing option is enabled by default and is effective only in combination with -fstrict-aliasing. -falign-functions -falign-functions=n -falign-functions=n:m -falign-functions=n:m:n2 -falign-functions=n:m:n2:m2 Align the start of functions to the next power-of-two greater than or equal to n, skipping up to m-1 bytes. This ensures that at least the first m bytes of the function can be fetched by the CPU without cross- ing an n-byte alignment boundary. This is an optimization of code per- formance and alignment is ignored for functions considered cold. If alignment is required for all functions, use -fmin-function-alignment. If m is not specified, it defaults to n. Examples: -falign-functions=32 aligns functions to the next 32-byte boundary, -falign-functions=24 aligns to the next 32-byte boundary only if this can be done by skipping 23 bytes or less, -falign-func- tions=32:7 aligns to the next 32-byte boundary only if this can be done by skipping 6 bytes or less. The second pair of n2:m2 values allows you to specify a secondary alignment: -falign-functions=64:7:32:3 aligns to the next 64-byte boundary if this can be done by skipping 6 bytes or less, otherwise aligns to the next 32-byte boundary if this can be done by skipping 2 bytes or less. If m2 is not specified, it defaults to n2. Some assemblers only support this flag when n is a power of two; in that case, it is rounded up. -fno-align-functions and -falign-functions=1 are equivalent and mean that functions are not aligned. If n is not specified or is zero, use a machine-dependent default. The maximum allowed n option value is 65536. Enabled at levels -O2, -O3. -flimit-function-alignment If this option is enabled, the compiler tries to avoid unnecessarily overaligning functions. It attempts to instruct the assembler to align by the amount specified by -falign-functions, but not to skip more bytes than the size of the function. -falign-labels -falign-labels=n -falign-labels=n:m -falign-labels=n:m:n2 -falign-labels=n:m:n2:m2 Align all branch targets to a power-of-two boundary. Parameters of this option are analogous to the -falign-functions op- tion. -fno-align-labels and -falign-labels=1 are equivalent and mean that labels are not aligned. If -falign-loops or -falign-jumps are applicable and are greater than this value, then their values are used instead. If n is not specified or is zero, use a machine-dependent default which is very likely to be 1, meaning no alignment. The maximum allowed n option value is 65536. Enabled at levels -O2, -O3. -falign-loops -falign-loops=n -falign-loops=n:m -falign-loops=n:m:n2 -falign-loops=n:m:n2:m2 Align loops to a power-of-two boundary. If the loops are executed many times, this makes up for any execution of the dummy padding instruc- tions. This is an optimization of code performance and alignment is ignored for loops considered cold. If -falign-labels is greater than this value, then its value is used instead. Parameters of this option are analogous to the -falign-functions op- tion. -fno-align-loops and -falign-loops=1 are equivalent and mean that loops are not aligned. The maximum allowed n option value is 65536. If n is not specified or is zero, use a machine-dependent default. Enabled at levels -O2, -O3. -falign-jumps -falign-jumps=n -falign-jumps=n:m -falign-jumps=n:m:n2 -falign-jumps=n:m:n2:m2 Align branch targets to a power-of-two boundary, for branch targets where the targets can only be reached by jumping. In this case, no dummy operations need be executed. This is an optimization of code performance and alignment is ignored for jumps considered cold. If -falign-labels is greater than this value, then its value is used instead. Parameters of this option are analogous to the -falign-functions op- tion. -fno-align-jumps and -falign-jumps=1 are equivalent and mean that loops are not aligned. If n is not specified or is zero, use a machine-dependent default. The maximum allowed n option value is 65536. Enabled at levels -O2, -O3. -fmin-function-alignment Specify minimal alignment of functions to the next power-of-two greater than or equal to n. Unlike -falign-functions this alignment is applied also to all functions (even those considered cold). The alignment is also not affected by -flimit-function-alignment -fno-allocation-dce Do not remove unused C++ allocations (using operator "new" and operator "delete") in dead code elimination. See also -fmalloc-dce. -fallow-store-data-races Allow the compiler to perform optimizations that may introduce new data races on stores, without proving that the variable cannot be concur- rently accessed by other threads. Does not affect optimization of lo- cal data. It is safe to use this option if it is known that global data will not be accessed by multiple threads. Examples of optimizations enabled by -fallow-store-data-races include hoisting or if-conversions that may cause a value that was already in memory to be re-written with that same value. Such re-writing is safe in a single threaded context but may be unsafe in a multi-threaded con- text. Note that on some processors, if-conversions may be required in order to enable vectorization. Enabled at level -Ofast. -funit-at-a-time This option is left for compatibility reasons. -funit-at-a-time has no effect, while -fno-unit-at-a-time implies -fno-toplevel-reorder and -fno-section-anchors. Enabled by default. -fno-toplevel-reorder Do not reorder top-level functions, variables, and "asm" statements. Output them in the same order that they appear in the input file. When this option is used, unreferenced static variables are not removed. This option is intended to support existing code that relies on a par- ticular ordering. For new code, it is better to use attributes when possible. -ftoplevel-reorder is the default at -O1 and higher, and also at -O0 if -fsection-anchors is explicitly requested. Additionally -fno-toplevel-reorder implies -fno-section-anchors. -funreachable-traps With this option, the compiler turns calls to "__builtin_unreachable" into traps, instead of using them for optimization. This also affects any such calls implicitly generated by the compiler. This option has the same effect as -fsanitize=unreachable -fsani- tize-trap=unreachable, but does not affect the values of those options. If -fsanitize=unreachable is enabled, that option takes priority over this one. This option is enabled by default at -O0 and -Og. -fweb Constructs webs as commonly used for register allocation purposes and assign each web individual pseudo register. This allows the register allocation pass to operate on pseudos directly, but also strengthens several other optimization passes, such as CSE, loop optimizer and trivial dead code remover. It can, however, make debugging impossible, since variables no longer stay in a "home register". Enabled by default with -funroll-loops. -fwhole-program Assume that the current compilation unit represents the whole program being compiled. All public functions and variables with the exception of "main" and those merged by attribute "externally_visible" become static functions and in effect are optimized more aggressively by in- terprocedural optimizers. With -flto this option has a limited use. In most cases the precise list of symbols used or exported from the binary is known the resolu- tion info passed to the link-time optimizer by the linker plugin. It is still useful if no linker plugin is used or during incremental link step when final code is produced (with -flto -flinker-out- put=nolto-rel). -flto[=n] This option runs the standard link-time optimizer. When invoked with source code, it generates GIMPLE (one of GCC's internal representa- tions) and writes it to special ELF sections in the object file. When the object files are linked together, all the function bodies are read from these ELF sections and instantiated as if they had been part of the same translation unit. To use the link-time optimizer, -flto and optimization options should be specified at compile time and during the final link. It is recom- mended that you compile all the files participating in the same link with the same options and also specify those options at link time. For example: gcc -c -O2 -flto foo.c gcc -c -O2 -flto bar.c gcc -o myprog -flto -O2 foo.o bar.o The first two invocations to GCC save a bytecode representation of GIM- PLE into special ELF sections inside foo.o and bar.o. The final invo- cation reads the GIMPLE bytecode from foo.o and bar.o, merges the two files into a single internal image, and compiles the result as usual. Since both foo.o and bar.o are merged into a single image, this causes all the interprocedural analyses and optimizations in GCC to work across the two files as if they were a single one. This means, for ex- ample, that the inliner is able to inline functions in bar.o into func- tions in foo.o and vice-versa. Another (simpler) way to enable link-time optimization is: gcc -o myprog -flto -O2 foo.c bar.c The above generates bytecode for foo.c and bar.c, merges them together into a single GIMPLE representation and optimizes them as usual to pro- duce myprog. The important thing to keep in mind is that to enable link-time opti- mizations you need to use the GCC driver to perform the link step. GCC automatically performs link-time optimization if any of the objects in- volved were compiled with the -flto command-line option. You can al- ways override the automatic decision to do link-time optimization by passing -fno-lto to the link command. To make whole-program optimization effective, it is necessary to make certain assumptions. The compiler needs to know what functions and variables can be accessed by libraries and runtime outside of the link-time optimized unit. When supported by the linker, the linker plugin (see -fuse-linker-plugin) passes information to the compiler about used and externally visible symbols. When the linker plugin is not available, -fwhole-program should be used to allow the compiler to make these assumptions, which leads to more aggressive optimization de- cisions. When a file is compiled with -flto without -fuse-linker-plugin, the generated object file is larger than a regular object file because it contains GIMPLE bytecodes and the usual final code (see -ffat-lto-ob- jects). This means that object files with LTO information can be linked as normal object files; if -fno-lto is passed to the linker, no interprocedural optimizations are applied. Note that when -fno-fat-lto-objects is enabled the compile stage is faster but you cannot perform a regular, non-LTO link on them. When producing the final binary, GCC only applies link-time optimiza- tions to those files that contain bytecode. Therefore, you can mix and match object files and libraries with GIMPLE bytecodes and final object code. GCC automatically selects which files to optimize in LTO mode and which files to link without further processing. Generally, options specified at link time override those specified at compile time, although in some cases GCC attempts to infer link-time options from the settings used to compile the input files. If you do not specify an optimization level option -O at link time, then GCC uses the highest optimization level used when compiling the object files. Note that it is generally ineffective to specify an op- timization level option only at link time and not at compile time, for two reasons. First, compiling without optimization suppresses compiler passes that gather information needed for effective optimization at link time. Second, some early optimization passes can be performed only at compile time and not at link time. There are some code generation flags preserved by GCC when generating bytecodes, as they need to be used during the final link. Currently, the following options and their settings are taken from the first ob- ject file that explicitly specifies them: -fcommon, -fexceptions, -fnon-call-exceptions, -fgnu-tm and all the -m target flags. The following options -fPIC, -fpic, -fpie and -fPIE are combined based on the following scheme: B<-fPIC> + B<-fpic> = B<-fpic> B<-fPIC> + B<-fno-pic> = B<-fno-pic> B<-fpic/-fPIC> + (no option) = (no option) B<-fPIC> + B<-fPIE> = B<-fPIE> B<-fpic> + B<-fPIE> = B<-fpie> B<-fPIC/-fpic> + B<-fpie> = B<-fpie> Certain ABI-changing flags are required to match in all compilation units, and trying to override this at link time with a conflicting value is ignored. This includes options such as -freg-struct-return and -fpcc-struct-return. Other options such as -ffp-contract, -fno-strict-overflow, -fwrapv, -fno-trapv or -fno-strict-aliasing are passed through to the link stage and merged conservatively for conflicting translation units. Specifi- cally -fno-strict-overflow, -fwrapv and -fno-trapv take precedence; and for example -ffp-contract=off takes precedence over -ffp-contract=fast. You can override them at link time. Diagnostic options such as -Wstringop-overflow are passed through to the link stage and their setting matches that of the compile-step at function granularity. Note that this matters only for diagnostics emitted during optimization. Note that code transforms such as inlin- ing can lead to warnings being enabled or disabled for regions if code not consistent with the setting at compile time. When you need to pass options to the assembler via -Wa or -Xassembler make sure to either compile such translation units with -fno-lto or consistently use the same assembler options on all translation units. You can alternatively also specify assembler options at LTO link time. To enable debug info generation you need to supply -g at compile time. If any of the input files at link time were built with debug info gen- eration enabled the link will enable debug info generation as well. Any elaborate debug info settings like the dwarf level -gdwarf-5 need to be explicitly repeated at the linker command line and mixing differ- ent settings in different translation units is discouraged. If LTO encounters objects with C linkage declared with incompatible types in separate translation units to be linked together (undefined behavior according to ISO C99 6.2.7), a non-fatal diagnostic may be is- sued. The behavior is still undefined at run time. Similar diagnos- tics may be raised for other languages. Another feature of LTO is that it is possible to apply interprocedural optimizations on files written in different languages: gcc -c -flto foo.c g++ -c -flto bar.cc gfortran -c -flto baz.f90 g++ -o myprog -flto -O3 foo.o bar.o baz.o -lgfortran Notice that the final link is done with g++ to get the C++ runtime li- braries and -lgfortran is added to get the Fortran runtime libraries. In general, when mixing languages in LTO mode, you should use the same link command options as when mixing languages in a regular (non-LTO) compilation. If object files containing GIMPLE bytecode are stored in a library archive, say libfoo.a, it is possible to extract and use them in an LTO link if you are using a linker with plugin support. To create static libraries suitable for LTO, use gcc-ar and gcc-ranlib instead of ar and ranlib; to show the symbols of object files with GIMPLE bytecode, use gcc-nm. Those commands require that ar, ranlib and nm have been com- piled with plugin support. At link time, use the flag -fuse-linker-plugin to ensure that the library participates in the LTO optimization process: gcc -o myprog -O2 -flto -fuse-linker-plugin a.o b.o -lfoo With the linker plugin enabled, the linker extracts the needed GIMPLE files from libfoo.a and passes them on to the running GCC to make them part of the aggregated GIMPLE image to be optimized. If you are not using a linker with plugin support and/or do not enable the linker plugin, then the objects inside libfoo.a are extracted and linked as usual, but they do not participate in the LTO optimization process. In order to make a static library suitable for both LTO opti- mization and usual linkage, compile its object files with -flto -ffat-lto-objects. Link-time optimizations do not require the presence of the whole pro- gram to operate. If the program does not require any symbols to be ex- ported, it is possible to combine -flto and -fwhole-program to allow the interprocedural optimizers to use more aggressive assumptions which may lead to improved optimization opportunities. Use of -fwhole-pro- gram is not needed when linker plugin is active (see -fuse-linker-plu- gin). The current implementation of LTO makes no attempt to generate bytecode that is portable between different types of hosts. The bytecode files are versioned and there is a strict version check, so bytecode files generated in one version of GCC do not work with an older or newer ver- sion of GCC. Link-time optimization does not work well with generation of debugging information on systems other than those using a combination of ELF and DWARF. If you specify the optional n, the optimization and code generation done at link time is executed in parallel using n parallel jobs by uti- lizing an installed make program. The environment variable MAKE may be used to override the program used. You can also specify -flto=jobserver to use GNU make's job server mode to determine the number of parallel jobs. This is useful when the Make- file calling GCC is already executing in parallel. You must prepend a + to the command recipe in the parent Makefile for this to work. This option likely only works if MAKE is GNU make. Even without the option value, GCC tries to automatically detect a running GNU make's job server. Use -flto=auto to use GNU make's job server, if available, or otherwise fall back to autodetection of the number of CPU threads present in your system. -flto-partition=alg Specify the partitioning algorithm used by the link-time optimizer. The value is either 1to1 to specify a partitioning mirroring the origi- nal source files or balanced to specify partitioning into equally sized chunks (whenever possible) or max to create new partition for every symbol where possible or cache to balance chunk sizes while keeping re- lated symbols together for better caching in incremental LTO. Specify- ing none as an algorithm disables partitioning and streaming com- pletely. The default value is balanced. While 1to1 can be used as an workaround for various code ordering issues, the max partitioning is intended for internal testing only. The value one specifies that ex- actly one partition should be used while the value none bypasses parti- tioning and executes the link-time optimization step directly from the WPA phase. -flto-incremental=path Enable incremental LTO, with its cache in given existing directory. Can significantly shorten edit-compile cycles with LTO. When used with LTO (-flto), the output of translation units inside LTO is cached. Cached translation units are likely to be encountered again when recompiling with small code changes, leading to recompile time re- duction. Multiple GCC instances can use the same cache in parallel. -flto-incremental-cache-size=n Specifies number of cache entries in incremental LTO after which to prune old entries. This is a soft limit, temporarily there may be more entries. -flto-compression-level=n This option specifies the level of compression used for intermediate language written to LTO object files, and is only meaningful in con- junction with LTO mode (-flto). GCC currently supports two LTO com- pression algorithms. For zstd, valid values are 0 (no compression) to 19 (maximum compression), while zlib supports values from 0 to 9. Val- ues outside this range are clamped to either minimum or maximum of the supported values. If the option is not given, a default balanced com- pression setting is used. -flto-toplevel-asm-heuristics Enables heuristics to find symbols used in top-level basic "asm". This will restrict link-time optimizations that could cause renaming or deletion of such symbols which would result in missing symbol errors by linker. This flag is intended for projects that have not converted to using top-level extended "asm", which specify the usage directly without any false positives. The heuristics are simple and do not parse the assembly. The heuris- tics scan through top-level assembly for all possible identifiers; if an identifier is found among declared symbols, the symbol will be marked to restrict link-time optimizations. Static symbols disable more optimizations. Identifiers followed by ':' disable more optimiza- tions as well, because they might be a locally defined symbol in assem- bly, even when the declaration is marked 'extern'. -fuse-linker-plugin Enables the use of a linker plugin during link-time optimization. This option relies on plugin support in the linker, which is available in gold or in GNU ld 2.21 or newer. This option enables the extraction of object files with GIMPLE bytecode out of library archives. This improves the quality of optimization by exposing more code to the link-time optimizer. This information speci- fies what symbols can be accessed externally (by non-LTO object or dur- ing dynamic linking). Resulting code quality improvements on binaries (and shared libraries that use hidden visibility) are similar to -fw- hole-program. See -flto for a description of the effect of this flag and how to use it. This option is enabled by default when LTO support in GCC is enabled and GCC was configured for use with a linker supporting plugins (GNU ld 2.21 or newer or gold). -ffat-lto-objects Fat LTO objects are object files that contain both the intermediate language and the object code. This makes them usable for both LTO link- ing and normal linking. This option is effective only when compiling with -flto and is ignored at link time. -fno-fat-lto-objects improves compilation time over plain LTO, but re- quires the complete toolchain to be aware of LTO. It requires a linker with linker plugin support for basic functionality. Additionally, nm, ar and ranlib need to support linker plugins to allow a full-featured build environment (capable of building static libraries etc). GCC pro- vides the gcc-ar, gcc-nm, gcc-ranlib wrappers to pass the right options to these tools. With non fat LTO makefiles need to be modified to use them. Note that modern binutils provide plugin auto-load mechanism. In- stalling the linker plugin into $libdir/bfd-plugins has the same effect as usage of the command wrappers (gcc-ar, gcc-nm and gcc-ranlib). The default is -fno-fat-lto-objects on targets with linker plugin sup- port. -fcompare-elim After register allocation and post-register allocation instruction splitting, identify arithmetic instructions that compute processor flags similar to a comparison operation based on that arithmetic. If possible, eliminate the explicit comparison operation. This pass only applies to certain targets that cannot explicitly repre- sent the comparison operation before register allocation is complete. Enabled at levels -O1, -O2, -O3, -Os. -ffold-mem-offsets -fno-fold-mem-offsets Try to eliminate add instructions by folding them in memory loads/stores. Enabled at levels -O2, -O3. -fcprop-registers After register allocation and post-register allocation instruction splitting, perform a copy-propagation pass to try to reduce scheduling dependencies and occasionally eliminate the copy. Enabled at levels -O1, -O2, -O3, -Os. -fprofile-correction Profiles collected using an instrumented binary for multi-threaded pro- grams may be inconsistent due to missed counter updates. When this op- tion is specified, GCC uses heuristics to correct or smooth out such inconsistencies. By default, GCC emits an error message when an incon- sistent profile is detected. This option is enabled by -fauto-profile. -fprofile-partial-training With "-fprofile-use" all portions of programs not executed during training runs are optimized aggressively for size rather than speed. In some cases it is not practical to train all possible hot paths in the program. (For example, it may contain functions specific to a given hardware and training may not cover all hardware configurations the program later runs on.) With "-fprofile-partial-training" profile feedback is ignored for all functions not executed during the training runs, causing them to be optimized as if they were compiled without profile feedback. This leads to better performance when the training is not representative at the cost of significantly bigger code. -fprofile-use -fprofile-use=path Enable profile feedback-directed optimizations, and the following opti- mizations, many of which are generally profitable only with profile feedback available: -fbranch-probabilities -fprofile-values -funroll-loops -fpeel-loops -ftracer -fvpt -finline-functions -fipa-cp -fipa-cp-clone -fipa-bit-cp -fpredictive-commoning -fsplit-loops -funswitch-loops -fgcse-after-reload -ftree-loop-vectorize -ftree-slp-vectorize -fvect-cost-model=dynamic -ftree-loop-distribute-patterns -fpro- file-reorder-functions Before you can use this option, you must first generate profiling in- formation. By default, GCC emits an error message if the feedback profiles do not match the source code. This error can be turned into a warning by us- ing -Wno-error=coverage-mismatch. Note this may result in poorly opti- mized code. Additionally, by default, GCC also emits a warning message if the feedback profiles do not exist (see -Wmissing-profile). If path is specified, GCC looks at the path to find the profile feed- back data files. See -fprofile-dir. -fauto-profile -fauto-profile=path Enable sampling-based feedback-directed optimizations, and the follow- ing optimizations, many of which are generally profitable only with profile feedback available: -fbranch-probabilities -fprofile-values -funroll-loops -fpeel-loops -ftracer -fvpt -finline-functions -fipa-cp -fipa-cp-clone -fipa-bit-cp -fpredictive-commoning -fsplit-loops -funswitch-loops -fgcse-after-reload -ftree-loop-vectorize -ftree-slp-vectorize -fvect-cost-model=dynamic -ftree-loop-distribute-patterns -fpro- file-correction path is the name of a file containing AutoFDO profile information. If omitted, it defaults to fbdata.afdo in the current directory. Producing an AutoFDO profile data file requires running your program with the perf utility on a supported GNU/Linux target system. For more information, see <https://perfwiki.github.io/main/>. E.g. perf record -e br_inst_retired:near_taken -b -o perf.data \ -- your_program Then use the create_gcov tool to convert the raw profile data to a for- mat that can be used by GCC. You must also supply the unstripped bi- nary for your program to this tool. See <https://github.com/google/autofdo>. E.g. create_gcov --binary=your_program.unstripped --profile=perf.data \ --gcov=profile.afdo -fauto-profile-inlining When auto-profile is available inline all relevant functions which was inlined in the tran run before reading the profile feedback. This im- proves context sensitivity of the profile. Enabled by default. The following options control compiler behavior regarding floating-point arithmetic. These options trade off between speed and correctness. All must be specifically enabled. -fexcess-precision=style This option allows control over excess precision on machines where floating-point operations occur in a format with more precision or range than the IEEE standard and interchange floating-point types. An example of such a target is x87 floating point on x86 processors, which uses an 80-bit representation internally instead of the 64-bit IEEE format. For most programs, the excess precision is harmless, but some programs may rely on the requirements of the C or C++ language stan- dards for handling IEEE values. By default, -fexcess-precision=fast is in effect; this means that oper- ations may be carried out in a wider precision than the types specified in the source if that would result in faster code, and it is unpre- dictable when rounding to the types specified in the source code takes place. When compiling C or C++, if -fexcess-precision=standard is specified then excess precision follows the rules specified in ISO C99 or C++; in particular, both casts and assignments cause values to be rounded to their semantic types (whereas -ffloat-store only affects as- signments). This option is enabled by default for C or C++ if a strict conformance option such as -std=c99 or -std=c++17 is used. -ffast-math enables -fexcess-precision=fast by default regardless of whether a strict conformance option is used. If -fexcess-precision=16 is speci- fied, constants and the results of expressions with types "_Float16" and "__bf16" are computed without excess precision. -fexcess-precision=standard is not implemented for languages other than C or C++. On the x86, it has no effect if -mfpmath=sse or -mfp- math=sse+387 is specified; in the former case, IEEE semantics apply without excess precision, and in the latter, rounding is unpredictable. -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. This option has generally been subsumed by -fex- cess-precision=standard, which is more general. If you do use -ffloat-store, you may need to modify your program to explicitly store intermediate computations in temporary variables since -ffloat-store handles rounding to IEEE format only on assignments and not casts as -fexcess-precision=standard does. -ffast-math Sets the options -fno-math-errno, -funsafe-math-optimizations, -ffi- nite-math-only, -fno-rounding-math, -fno-signaling-nans, -fcx-lim- ited-range and -fexcess-precision=fast. This option causes the preprocessor macro "__FAST_MATH__" to be de- fined. This option is not turned on by any -O option besides -Ofast since it can result in incorrect output for programs that depend on an exact im- plementation of IEEE or ISO rules/specifications for math functions. It may, however, yield faster code for programs that do not require the guarantees of these specifications. -fno-math-errno Do not set "errno" after calling math functions that are executed with a single instruction, e.g., "sqrt". A program that relies on IEEE ex- ceptions for math error handling may want to use this flag for speed while maintaining IEEE arithmetic compatibility. This option is not turned on by any -O option besides -Ofast since it can result in incorrect output for programs that depend on an exact im- plementation of IEEE or ISO rules/specifications for math functions. It may, however, yield faster code for programs that do not require the guarantees of these specifications. The default is -fmath-errno. On Darwin systems, the math library never sets "errno". There is therefore no reason for the compiler to consider the possibility that it might, and -fno-math-errno is the default. -funsafe-math-optimizations Allow optimizations for floating-point arithmetic that (a) assume that arguments and results are valid and (b) may violate IEEE or ANSI stan- dards. When used at link time, it may include libraries or startup files that change the default FPU control word or other similar opti- mizations. This option is not turned on by any -O option besides -Ofast since it can result in incorrect output for programs that depend on an exact im- plementation of IEEE or ISO rules/specifications for math functions. It may, however, yield faster code for programs that do not require the guarantees of these specifications. Enables -fno-signed-zeros, -fno-trapping-math, -fassociative-math and -freciprocal-math. The default is -fno-unsafe-math-optimizations. -fassociative-math Allow re-association of operands in series of floating-point opera- tions. This violates the ISO C and C++ language standard by possibly changing computation result. NOTE: re-ordering may change the sign of zero as well as ignore NaNs and inhibit or create underflow or overflow (and thus cannot be used on code that relies on rounding behavior like "(x + 2**52) - 2**52". May also reorder floating-point comparisons and thus may not be used when ordered comparisons are required. This op- tion requires that both -fno-signed-zeros and -fno-trapping-math be in effect. Moreover, it doesn't make much sense with -frounding-math. For Fortran the option is automatically enabled when both -fno-signed-zeros and -fno-trapping-math are in effect. The default is -fno-associative-math. -freciprocal-math Allow the reciprocal of a value to be used instead of dividing by the value if this enables optimizations. For example "x / y" can be re- placed with "x * (1/y)", which is useful if "(1/y)" is subject to com- mon subexpression elimination. Note that this loses precision and in- creases the number of flops operating on the value. The default is -fno-reciprocal-math. -ffinite-math-only Allow optimizations for floating-point arithmetic that assume that ar- guments and results are not NaNs or +-Infs. This option is not turned on by any -O option besides -Ofast since it can result in incorrect output for programs that depend on an exact im- plementation of IEEE or ISO rules/specifications for math functions. It may, however, yield faster code for programs that do not require the guarantees of these specifications. The default is -fno-finite-math-only. -fno-signed-zeros Allow optimizations for floating-point arithmetic that ignore the signedness of zero. IEEE arithmetic specifies the behavior of distinct +0.0 and -0.0 values, which then prohibits simplification of expres- sions such as x+0.0 or 0.0*x (even with -ffinite-math-only). This op- tion implies that the sign of a zero result isn't significant. The default is -fsigned-zeros. -fno-trapping-math Compile code assuming that floating-point operations cannot generate user-visible traps. These traps include division by zero, overflow, underflow, inexact result and invalid operation. This option requires that -fno-signaling-nans be in effect. Setting this option may allow faster code if one relies on "non-stop" IEEE arithmetic, for example. This option is not turned on by any -O option besides -Ofast since it can result in incorrect output for programs that depend on an exact im- plementation of IEEE or ISO rules/specifications for math functions. The default is -ftrapping-math. Future versions of GCC may provide finer control of this setting using C99's "FENV_ACCESS" pragma. This command-line option will be used along with -frounding-math to specify the default state for "FENV_AC- CESS". -frounding-math Disable transformations and optimizations that assume default float- ing-point rounding behavior (round-to-nearest). This option should be specified for programs that change the FP rounding mode dynamically, or that may be executed with a non-default rounding mode. This option disables constant folding of floating-point expressions at compile time (which may be affected by rounding mode) and arithmetic transformations that are unsafe in the presence of sign-dependent rounding modes. The default is -fno-rounding-math. This option is experimental and does not currently guarantee to disable all GCC optimizations that are affected by rounding mode. Future ver- sions of GCC may provide finer control of this setting using C99's "FENV_ACCESS" pragma. This command-line option will be used along with -ftrapping-math to specify the default state for "FENV_ACCESS". -fsignaling-nans Compile code assuming that IEEE signaling NaNs may generate user-visi- ble traps during floating-point operations. Setting this option dis- ables optimizations that may change the number of exceptions visible with signaling NaNs. This option implies -ftrapping-math. This option causes the preprocessor macro "__SUPPORT_SNAN__" to be de- fined. The default is -fno-signaling-nans. This option is experimental and does not currently guarantee to disable all GCC optimizations that affect signaling NaN behavior. -fsingle-precision-constant Treat floating-point constants as single precision instead of implic- itly converting them to double-precision constants. -fcx-limited-range When enabled, this option states that a range reduction step is not needed when performing complex division. Also, there is no checking whether the result of a complex multiplication or division is "NaN + I*NaN", with an attempt to rescue the situation in that case. The op- tion is enabled by -ffast-math. This option controls the default setting of the ISO C99 "CX_LIM- ITED_RANGE" pragma. Nevertheless, the option applies to all languages. -fcx-fortran-rules Complex multiplication and division follow Fortran rules. Range reduc- tion is done as part of complex division, but there is no checking whether the result of a complex multiplication or division is "NaN + I*NaN", with an attempt to rescue the situation in that case. -fcx-method=method Complex multiplication and division follow the stated method. The method argument should be one of limited-range, fortran or stdc. The default is to honor language specific constraints which means for- tran for Fortran and stdc otherwise. The following options control optimizations that may improve performance, but are not enabled by any -O options. This section includes experimental options that may produce broken code. -fbranch-probabilities After running a program compiled with -fprofile-arcs, you can compile it a second time using -fbranch-probabilities, to improve optimizations based on the number of times each branch was taken. When a program compiled with -fprofile-arcs exits, it saves arc execution counts to a file called sourcename.gcda 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. See details about the file naming in -fprofile-arcs. With -fbranch-probabilities, GCC puts a REG_BR_PROB note on each JUMP_INSN and CALL_INSN. These can be used to improve optimization. Currently, they are only used in one place: in reorg.cc, instead of guessing which path a branch is most likely to take, the REG_BR_PROB values are used to exactly determine which path is taken more often. Enabled by -fprofile-use and -fauto-profile. -fprofile-values If combined with -fprofile-arcs, it adds code so that some data about values of expressions in the program is gathered. With -fbranch-probabilities, it reads back the data gathered from pro- filing values of expressions for usage in optimizations. Enabled by -fprofile-generate, -fprofile-use, and -fauto-profile. -fprofile-reorder-functions Function reordering based on profile instrumentation collects first time of execution of a function and orders these functions in ascending order, aiming to optimize program startup through more efficient load- ing of text segments. Enabled with -fprofile-use. -fvpt If combined with -fprofile-arcs, this option instructs the compiler to add code to gather information about values of expressions. With -fbranch-probabilities, it reads back the data gathered and actu- ally performs the optimizations based on them. Currently the optimiza- tions include specialization of division operations using the knowledge about the value of the denominator. Enabled with -fprofile-use and -fauto-profile. -frename-registers Attempt to avoid false dependencies in scheduled code by making use of registers left over after register allocation. This optimization most benefits processors with lots of registers. Depending on the debug in- formation format adopted by the target, however, it can make debugging impossible, since variables no longer stay in a "home register". Enabled by default with -funroll-loops. -fschedule-fusion Performs a target dependent pass over the instruction stream to sched- ule instructions of same type together because target machine can exe- cute them more efficiently if they are adjacent to each other in the instruction flow. Enabled at levels -O2, -O3, -Os. -fdep-fusion Detect macro-op fusible pairs consisting of single-use instructions and their uses, and place such pairs together in the instruction stream to increase fusion opportunities in hardware. This pass is executed once before register allocation, and another time before register renaming. Enabled at levels -O2, -O3, -Os. -ftracer Perform tail duplication to enlarge superblock size. This transforma- tion simplifies the control flow of the function allowing other opti- mizations to do a better job. Enabled by -fprofile-use and -fauto-profile. -funroll-loops Unroll loops whose number of iterations can be determined at compile time or upon entry to the loop. -funroll-loops implies -frerun-cse-af- ter-loop, -fweb and -frename-registers. It also turns on complete loop peeling (i.e. complete removal of loops with a small constant number of iterations). This option makes code larger, and may or may not make it run faster. Enabled by -fprofile-use and -fauto-profile. -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. -funroll-all-loops implies the same options as -funroll-loops. -fpeel-loops Peels loops for which there is enough information that they do not roll much (from profile feedback or static analysis). It also turns on com- plete loop peeling (i.e. complete removal of loops with small constant number of iterations). Enabled by -O3, -fprofile-use, and -fauto-profile. -fmalloc-dce Control whether "malloc" (and its variants such as "calloc" or "strdup"), can be optimized away provided its return value is only used as a parameter of "free" call or compared with "NULL". If -fmal- loc-dce=1 is used, only calls to "free" are allowed while with -fmal- loc-dce=2 also comparisons with "NULL" pointer are considered safe to remove. The default is -fmalloc-dce=2. See also -fallocation-dce. -fmove-loop-invariants Enables the loop invariant motion pass in the RTL loop optimizer. En- abled at level -O1 and higher, except for -Og. -fmove-loop-stores Enables the loop store motion pass in the GIMPLE loop optimizer. This moves invariant stores to after the end of the loop in exchange for carrying the stored value in a register across the iteration. Note for this option to have an effect -ftree-loop-im has to be enabled as well. Enabled at level -O1 and higher, except for -Og. -fsplit-loops Split a loop into two if it contains a condition that's always true for one side of the iteration space and false for the other. Enabled by -fprofile-use and -fauto-profile. -funswitch-loops Move branches with loop invariant conditions out of the loop, with du- plicates of the loop on both branches (modified according to result of the condition). Enabled by -fprofile-use and -fauto-profile. -fversion-loops-for-strides If a loop iterates over an array with a variable stride, create another version of the loop that assumes the stride is always one. For exam- ple: for (int i = 0; i < n; ++i) x[i * stride] = ...; becomes: if (stride == 1) for (int i = 0; i < n; ++i) x[i] = ...; else for (int i = 0; i < n; ++i) x[i * stride] = ...; This is particularly useful for assumed-shape arrays in Fortran where (for example) it allows better vectorization assuming contiguous ac- cesses. This flag is enabled by default at -O3. It is also enabled by -fprofile-use and -fauto-profile. -ffunction-sections -fdata-sections Place each function or data item into its own section in the output file if the target supports arbitrary sections. The name of the func- tion or the name of the data item determines the section's name in the output file. Use these options on systems where the linker can perform optimizations to improve locality of reference in the instruction space. Most sys- tems using the ELF object format have linkers with such optimizations. On AIX, the linker rearranges sections (CSECTs) based on the call graph. The performance impact varies. Together with a linker garbage collection (linker --gc-sections option) these options may lead to smaller statically-linked executables (after stripping). On ELF/DWARF systems these options do not degenerate the quality of the debug information. There could be issues with other object files/debug info formats. Only use these options when there are significant benefits from doing so. When you specify these options, the assembler and linker create larger object and executable files and are also slower. These options affect code generation. They prevent optimizations by the compiler and assembler using relative locations inside a translation unit since the locations are unknown until link time. An example of such an optimiza- tion is relaxing calls to short call instructions. -fstdarg-opt Optimize the prologue of variadic argument functions with respect to usage of those arguments. -fsection-anchors Try to reduce the number of symbolic address calculations by using shared "anchor" symbols to address nearby objects. This transformation can help to reduce the number of GOT entries and GOT accesses on some targets. For example, the implementation of the following function "foo": static int a, b, c; int foo (void) { return a + b + c; } usually calculates the addresses of all three variables, but if you compile it with -fsection-anchors, it accesses the variables from a common anchor point instead. The effect is similar to the following pseudocode (which isn't valid C): int foo (void) { register int *xr = &x; return xr[&a - &x] + xr[&b - &x] + xr[&c - &x]; } Not all targets support this option. -fzero-call-used-regs=choice Zero call-used registers at function return to increase program secu- rity by either mitigating Return-Oriented Programming (ROP) attacks or preventing information leakage through registers. The possible values of choice are the same as for the "zero_call_used_regs" attribute. The default is skip. You can control this behavior for a specific function by using the function attribute "zero_call_used_regs". Program Instrumentation Options GCC supports a number of command-line options that control adding run-time instrumentation to the code it normally generates. For example, one pur- pose of instrumentation is collect profiling statistics for use in finding program hot spots, code coverage analysis, or profile-guided optimizations. Another class of program instrumentation is adding run-time checking to de- tect programming errors like invalid pointer dereferences or out-of-bounds array accesses, as well as deliberately hostile attacks such as stack smashing or C++ vtable hijacking. There is also a general hook which can be used to implement other forms of tracing or function-level instrumenta- tion for debug or program analysis purposes. -p --profile -fprofile -pg Generate extra code to write profile information suitable for the analysis program prof (for -p, --profile, and -fprofile) or gprof (for -pg). You must use this option when compiling the source files you want data about, and you must also use it when linking. You can use the function attribute "no_instrument_function" to suppress profiling of individual functions when compiling with these options. -fprofile-arcs Add code so that program flow arcs are instrumented. During execution the program records how many times each branch and call is executed and how many times it is taken or returns. On targets that support con- structors with priority support, profiling properly handles construc- tors, destructors and C++ constructors (and destructors) of classes which are used as a type of a global variable. When the compiled program exits it saves this data to a file called auxname.gcda for each source file. The data may be used for pro- file-directed optimizations (-fbranch-probabilities), or for test cov- erage analysis (-ftest-coverage). Each object file's auxname is gener- ated from the name of the output file, if explicitly specified and it is not the final executable, otherwise it is the basename of the source file. In both cases any suffix is removed (e.g. foo.gcda for input file dir/foo.c, or dir/foo.gcda for output file specified as -o dir/foo.o). Note that if a command line directly links source files, the corre- sponding .gcda files will be prefixed with the unsuffixed name of the output file. E.g. "gcc a.c b.c -o binary" would generate binary-a.gcda and binary-b.gcda files. -fcondition-coverage Add code so that program conditions are instrumented. During execution the program records what terms in a conditional contributes to a deci- sion, which can be used to verify that all terms in a Boolean function are tested and have an independent effect on the outcome of a decision. The result can be read with "gcov --conditions". -fpath-coverage Add code so that the paths taken are tracked. During execution the program records the prime paths taken. The number of paths grows very fast with complexity, and to avoid exploding compile times GCC will give up instrumentation if the approximate number of paths exceeds the limit controlled by -fpath-coverage-limit. The result can be read with "gcov --prime-paths --prime-paths-lines --prime-paths-source", -fpath-coverage-limit=limit The threshold at which point -fpath-coverage gives up on instrumenting a function. This limit is approximate and conservative, as GCC uses a pessimistic heuristic which slightly overcounts the running number of paths, and gives up if the threshold is reached before finding all the paths. This option is not for fine grained control over which func- tions to instrument - rather it is intended to limit the effect of path explosion and keep compile times reasonable. The default is 250000. --coverage -coverage This option is used to compile and link code instrumented for coverage analysis. The options -coverage and --coverage are equivalent; both are a synonym for -fprofile-arcs -ftest-coverage (when compiling) and -lgcov (when linking). See the documentation for those options for more details. * Compile the source files with -fprofile-arcs plus optimization and code generation options. For test coverage analysis, use the addi- tional -ftest-coverage option. You do not need to profile every source file in a program. * Compile the source files additionally with -fprofile-abs-path to create absolute path names in the .gcno files. This allows gcov to find the correct sources in projects where compilations occur with different working directories. * Link your object files with -lgcov or -fprofile-arcs (the latter implies the former). * Run the program on a representative workload to generate the arc profile information. This may be repeated any number of times. You can run concurrent instances of your program, and provided that the file system supports locking, the data files will be correctly updated. Unless a strict ISO C dialect option is in effect, "fork" calls are detected and correctly handled without double counting. Moreover, an object file can be recompiled multiple times and the corresponding .gcda file merges as long as the source file and the compiler options are unchanged. * For profile-directed optimizations, compile the source files again with the same optimization and code generation options plus -fbranch-probabilities. * For test coverage analysis, use gcov to produce human readable in- formation from the .gcno and .gcda files. Refer to the gcov docu- mentation for further information. With -fprofile-arcs, for each function of your program GCC 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 ex- ecuted. 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. With -fcondition-coverage, for each conditional in your program GCC creates a bitset and records the exercised boolean values that have an independent effect on the outcome of that expression. With -fpath-coverage, GCC finds and enumerates and records the taken prime paths of each function, unless the number of paths would exceed the limit controlled by -fpath-coverage-limit. If the limit is ex- ceeded the function is not instrumented as if -fpath-coverage was not used. A prime path is the longest sequence of unique blocks, except possibly the first and last, which is not a subpath of any other path. -ftest-coverage Produce a notes file that the gcov code-coverage utility can use to show program coverage. Each source file's note file is called aux- name.gcno. Refer to the -fprofile-arcs option above for a description of auxname and instructions on how to generate test coverage data. Coverage data matches the source files more closely if you do not opti- mize. -fprofile-abs-path Automatically convert relative source file names to absolute path names in the .gcno files. This allows gcov to find the correct sources in projects where compilations occur with different working directories. -fprofile-dir=path Set the directory to search for the profile data files in to path. This option affects only the profile data generated by -fprofile-gener- ate, -ftest-coverage, -fprofile-arcs and used by -fprofile-use and -fbranch-probabilities and its related options. Both absolute and rel- ative paths can be used. By default, GCC uses the current directory as path, thus the profile data file appears in the same directory as the object file. In order to prevent the file name clashing, if the object file name is not an absolute path, we mangle the absolute path of the sourcename.gcda file and use it as the file name of a .gcda file. See details about the file naming in -fprofile-arcs. See similar option -fprofile-note. When an executable is run in a massive parallel environment, it is rec- ommended to save profile to different folders. That can be done with variables in path that are exported during run-time: %p process ID. %q{VAR} value of environment variable VAR -fprofile-generate -fprofile-generate=path Enable options usually used for instrumenting application to produce profile useful for later recompilation with profile feedback based op- timization. You must use -fprofile-generate both when compiling and when linking your program. The following options are enabled: -fprofile-arcs, -fprofile-values, -finline-functions, and -fipa-bit-cp. If path is specified, GCC looks at the path to find the profile feed- back data files. See -fprofile-dir. To optimize the program based on the collected profile information, use -fprofile-use. -fprofile-info-section -fprofile-info-section=name Register the profile information in the specified section instead of using a constructor/destructor. The section name is name if it is specified, otherwise the section name defaults to ".gcov_info". A pointer to the profile information generated by -fprofile-arcs is placed in the specified section for each translation unit. This option disables the profile information registration through a constructor and it disables the profile information processing through a destructor. This option is not intended to be used in hosted environments such as GNU/Linux. It targets freestanding environments (for example embedded systems) with limited resources which do not support constructors/de- structors or the C library file I/O. The linker could collect the input sections in a continuous memory block and define start and end symbols. A GNU linker script example which defines a linker output section follows: .gcov_info : { PROVIDE (__gcov_info_start = .); KEEP (*(.gcov_info)) PROVIDE (__gcov_info_end = .); } The program could dump the profiling information registered in this linker set for example like this: #include <gcov.h> #include <stdio.h> #include <stdlib.h> extern const struct gcov_info *const __gcov_info_start[]; extern const struct gcov_info *const __gcov_info_end[]; static void dump (const void *d, unsigned n, void *arg) { const unsigned char *c = d; for (unsigned i = 0; i < n; ++i) printf ("%02x", c[i]); } static void filename (const char *f, void *arg) { __gcov_filename_to_gcfn (f, dump, arg ); } static void * allocate (unsigned length, void *arg) { return malloc (length); } static void dump_gcov_info (void) { const struct gcov_info *const *info = __gcov_info_start; const struct gcov_info *const *end = __gcov_info_end; /* Obfuscate variable to prevent compiler optimizations. */ __asm__ ("" : "+r" (info)); while (info != end) { void *arg = NULL; __gcov_info_to_gcda (*info, filename, dump, allocate, arg); putchar ('\n'); ++info; } } int main (void) { dump_gcov_info (); return 0; } The merge-stream subcommand of gcov-tool may be used to deserialize the data stream generated by the "__gcov_filename_to_gcfn" and "__gcov_info_to_gcda" functions and merge the profile information into .gcda files on the host filesystem. -fprofile-note=path If path is specified, GCC saves .gcno file into path location. If you combine the option with multiple source files, the .gcno file will be overwritten. -fprofile-prefix-path=path This option can be used in combination with profile-generate=pro- file_dir and profile-use=profile_dir to inform GCC where is the base directory of built source tree. By default profile_dir will contain files with mangled absolute paths of all object files in the built project. This is not desirable when directory used to build the in- strumented binary differs from the directory used to build the binary optimized with profile feedback because the profile data will not be found during the optimized build. In such setups -fprofile-pre- fix-path=path with path pointing to the base directory of the build can be used to strip the irrelevant part of the path and keep all file names relative to the main build directory. -fprofile-prefix-map=old=new When compiling files residing in directory old, record profiling infor- mation (with --coverage) describing them as if the files resided in di- rectory new instead. See also -ffile-prefix-map and -fcanon-pre- fix-map. -fprofile-update=method Alter the update method for an application instrumented for profile feedback based optimization. The method argument should be one of sin- gle, atomic or prefer-atomic. The first one is useful for sin- gle-threaded applications, while the second one prevents profile cor- ruption by emitting thread-safe code. Warning: When an application does not properly join all threads (or creates an detached thread), a profile file can be still corrupted. Using prefer-atomic would be transformed either to atomic, when sup- ported by a target, or to single otherwise. The GCC driver automati- cally selects prefer-atomic when -pthread is present in the command line, otherwise the default method is single. If atomic is selected, then the profile information is updated using atomic operations on a best-effort basis. Ideally, the profile infor- mation is updated through atomic operations in hardware. If the target platform does not support the required atomic operations in hardware, however, libatomic is available, then the profile information is up- dated through calls to libatomic. If the target platform neither sup- ports the required atomic operations in hardware nor libatomic, then the profile information is not atomically updated and a warning is is- sued. In this case, the obtained profiling information may be corrupt for multi-threaded applications. For performance reasons, if 64-bit counters are used for the profiling information and the target platform only supports 32-bit atomic opera- tions in hardware, then the performance critical profiling updates are done using two 32-bit atomic operations for each counter update. If a signal interrupts these two operations updating a counter, then the profiling information may be in an inconsistent state. -fprofile-filter-files=regex Instrument only functions from files whose name matches any of the reg- ular expressions (separated by semi-colons). For example, -fprofile-filter-files=main\.c;module.*\.c will instrument only main.c and all C files starting with 'module'. -fprofile-exclude-files=regex Instrument only functions from files whose name does not match any of the regular expressions (separated by semi-colons). For example, -fprofile-exclude-files=/usr/.* will prevent instrumenta- tion of all files that are located in the /usr/ folder. -fprofile-reproducible=[multithreaded|parallel-runs|serial] Control level of reproducibility of profile gathered by "-fprofile-gen- erate". This makes it possible to rebuild program with same outcome which is useful, for example, for distribution packages. With -fprofile-reproducible=serial the profile gathered by -fpro- file-generate is reproducible provided the trained program behaves the same at each invocation of the train run, it is not multi-threaded and profile data streaming is always done in the same order. Note that profile streaming happens at the end of program run but also before "fork" function is invoked. Note that it is quite common that execution counts of some part of pro- grams depends, for example, on length of temporary file names or memory space randomization (that may affect hash-table collision rate). Such non-reproducible part of programs may be annotated by "no_instru- ment_function" function attribute. gcov-dump with -l can be used to dump gathered data and verify that they are indeed reproducible. With -fprofile-reproducible=parallel-runs collected profile stays re- producible regardless the order of streaming of the data into gcda files. This setting makes it possible to run multiple instances of in- strumented program in parallel (such as with "make -j"). This reduces quality of gathered data, in particular of indirect call profiling. -fsanitize=address Enable AddressSanitizer, a fast memory error detector. Memory access instructions are instrumented to detect out-of-bounds and use-af- ter-free bugs. The option enables -fsanitize-address-use-after-scope. See <https://github.com/google/sanitizers/wiki/AddressSanitizer> for more details. The run-time behavior can be influenced using the ASAN_OPTIONS environment variable. When set to "help=1", the available options are shown at startup of the instrumented program. See <https://github.com/google/sanitizers/wiki/AddressSanitizer- Flags#run-time-flags> for a list of supported options. The option can- not be combined with -fsanitize=thread or -fsanitize=hwaddress. Note that the only targets -fsanitize=hwaddress is currently supported on are x86-64 (only with "-mlam=u48" or "-mlam=u57" options) and AArch64, in both cases only in ABIs with 64-bit pointers. Similarly, -fsani- tize=memtag-stack is currently only supported on AArch64 ABIs with 64-bit pointers. When compiling with -fsanitize=address, you should also use -g to pro- duce more meaningful output. To get more accurate stack traces, it is possible to use options such as -O0, -O1, or -Og (which, for instance, prevent most function inlining), -fno-optimize-sibling-calls (which prevents optimizing sibling and tail recursive calls; this option is implicit for -O0, -O1, or -Og), or -fno-ipa-icf (which disables Identi- cal Code Folding for functions). Using -fno-omit-frame-pointer also improves stack traces. Since multiple runs of the program may yield backtraces with different addresses due to ASLR (Address Space Layout Randomization), it may be desirable to turn ASLR off. On Linux, this can be achieved with setarch `uname -m` -R ./prog. -fsanitize=kernel-address Enable AddressSanitizer for Linux kernel. See <https://github.com/google/kernel-sanitizers> for more details. -fsanitize=hwaddress Enable Hardware-assisted AddressSanitizer, which uses a hardware abil- ity to ignore the top byte of a pointer to allow the detection of mem- ory errors with a low memory overhead. Memory access instructions are instrumented to detect out-of-bounds and use-after-free bugs. The op- tion enables -fsanitize-address-use-after-scope. See <https://clang.llvm.org/docs/HardwareAssistedAddressSanitizerDe- sign.html> for more details. The run-time behavior can be influenced using the HWASAN_OPTIONS environment variable. When set to "help=1", the available options are shown at startup of the instrumented program. The option cannot be combined with -fsanitize=thread or -fsanitize=ad- dress, and is currently only available on AArch64. -fsanitize=kernel-hwaddress Enable Hardware-assisted AddressSanitizer for compilation of the Linux kernel. Similar to -fsanitize=kernel-address but using an alternate instrumentation method, and similar to -fsanitize=hwaddress but with instrumentation differences necessary for compiling the Linux kernel. These differences are to avoid hwasan library initialization calls and to account for the stack pointer having a different value in its top byte. Note: This option has different defaults than -fsanitize=hwaddress. Instrumenting the stack and alloca calls are not on by default. Using a random frame tag is not implemented for kernel instrumentation. -fsanitize=memtag-stack Use Memory Tagging Extension instructions instead of instrumentation to allow the detection of memory errors. Similar to HWASAN, it is also a probabilistic method. This option is available only on those AArch64 architectures that support Memory Tagging Extensions. -fsanitize=pointer-compare Instrument comparison operation (<, <=, >, >=) with pointer operands. The option must be combined with either -fsanitize=kernel-address or -fsanitize=address The option cannot be combined with -fsani- tize=thread. Note: By default the check is disabled at run time. To enable it, add "detect_invalid_pointer_pairs=2" to the environment variable ASAN_OPTIONS. Using "detect_invalid_pointer_pairs=1" detects invalid operation only when both pointers are non-null. -fsanitize=pointer-subtract Instrument subtraction with pointer operands. The option must be com- bined with either -fsanitize=kernel-address or -fsanitize=address The option cannot be combined with -fsanitize=thread. Note: By default the check is disabled at run time. To enable it, add "detect_in- valid_pointer_pairs=2" to the environment variable ASAN_OPTIONS. Using "detect_invalid_pointer_pairs=1" detects invalid operation only when both pointers are non-null. -fsanitize=shadow-call-stack Enable ShadowCallStack, a security enhancement mechanism used to pro- tect programs against return address overwrites (e.g. stack buffer overflows.) It works by saving a function's return address to a sepa- rately allocated shadow call stack in the function prologue and restor- ing the return address from the shadow call stack in the function epi- logue. Instrumentation only occurs in functions that need to save the return address to the stack. Currently it only supports the aarch64 platform. It is specifically designed for linux kernels that enable the CONFIG_SHADOW_CALL_STACK op- tion. For the user space programs, runtime support is not currently provided in libc and libgcc. Users who want to use this feature in user space need to provide their own support for the runtime. It should be noted that this may cause the ABI rules to be broken. On aarch64, the instrumentation makes use of the platform register "x18". This generally means that any code that may run on the same thread as code compiled with ShadowCallStack must be compiled with the flag -ffixed-x18, otherwise functions compiled without -ffixed-x18 might clobber "x18" and so corrupt the shadow stack pointer. Also, because there is no userspace runtime support, code compiled with ShadowCallStack cannot use exception handling. Use -fno-exceptions to turn off exceptions. See <https://clang.llvm.org/docs/ShadowCallStack.html> for more de- tails. -fsanitize=thread Enable ThreadSanitizer, a fast data race detector. Memory access in- structions are instrumented to detect data race bugs. See <https://github.com/google/sanitizers/wiki#threadsanitizer> for more details. The run-time behavior can be influenced using the TSAN_OPTIONS environment variable; see <https://github.com/google/sanitiz- ers/wiki/ThreadSanitizerFlags> for a list of supported options. The option cannot be combined with -fsanitize=address, -fsanitize=leak. When compiling with -fsanitize=thread, you should also use -g to pro- duce more meaningful output. Note that sanitized atomic builtins cannot throw exceptions when oper- ating on invalid memory addresses with non-call exceptions (-fnon-call-exceptions). -fsanitize=leak Enable LeakSanitizer, a memory leak detector. This option only matters for linking of executables. The executable is linked against a library that overrides "malloc" and other allocator functions. See <https://github.com/google/sanitizers/wiki/AddressSanitizerLeakSani- tizer> for more details. The run-time behavior can be influenced using the LSAN_OPTIONS environment variable. The option cannot be combined with -fsanitize=thread. -fsanitize=undefined Enable UndefinedBehaviorSanitizer, a fast undefined behavior detector. Various computations are instrumented to detect undefined behavior at runtime. See <https://clang.llvm.org/docs/UndefinedBehaviorSani- tizer.html> for more details. The run-time behavior can be influenced using the UBSAN_OPTIONS environment variable. Current suboptions are: -fsanitize=shift This option enables checking that the result of a shift operation is not undefined. Note that what exactly is considered undefined differs slightly between C and C++, as well as between ISO C90 and C99, etc. This option has two suboptions, -fsanitize=shift-base and -fsanitize=shift-exponent. -fsanitize=shift-exponent This option enables checking that the second argument of a shift operation is not negative and is smaller than the precision of the promoted first argument. -fsanitize=shift-base If the second argument of a shift operation is within range, check that the result of a shift operation is not undefined. Note that what exactly is considered undefined differs slightly between C and C++, as well as between ISO C90 and C99, etc. -fsanitize=integer-divide-by-zero Detect integer division by zero. -fsanitize=unreachable With this option, the compiler turns the "__builtin_unreachable" call into a diagnostics message call instead. When reaching the "__builtin_unreachable" call, the behavior is undefined. -fsanitize=vla-bound This option instructs the compiler to check that the size of a variable length array is positive. -fsanitize=null This option enables pointer checking. Particularly, the applica- tion built with this option turned on will issue an error message when it tries to dereference a NULL pointer, or if a reference (possibly an rvalue reference) is bound to a NULL pointer, or if a method is invoked on an object pointed by a NULL pointer. -fsanitize=return This option enables return statement checking. Programs built with this option turned on will issue an error message when the end of a non-void function is reached without actually returning a value. This option works in C++ only. -fsanitize=signed-integer-overflow This option enables signed integer overflow checking. We check that the result of "+", "*", and both unary and binary "-" does not overflow in the signed arithmetics. This also detects "INT_MIN / -1" signed division. Note, integer promotion rules must be taken into account. That is, the following is not an overflow: signed char a = SCHAR_MAX; a++; -fsanitize=bounds This option enables instrumentation of array bounds. Various out of bounds accesses are detected. Flexible array members, flexible array member-like arrays, and initializers of variables with static storage are not instrumented, with the exception of flexible array member-like arrays for which "-fstrict-flex-arrays" or "-fstrict-flex-arrays=" options or "strict_flex_array" attributes say they shouldn't be treated like flexible array member-like ar- rays. -fsanitize=bounds-strict This option enables strict instrumentation of array bounds. Most out of bounds accesses are detected, including flexible array mem- ber-like arrays. Initializers of variables with static storage are not instrumented. -fsanitize=alignment This option enables checking of alignment of pointers when they are dereferenced, or when a reference is bound to insufficiently aligned target, or when a method or constructor is invoked on in- sufficiently aligned object. -fsanitize=object-size This option enables instrumentation of memory references using the "__builtin_dynamic_object_size" function. Various out of bounds pointer accesses are detected. -fsanitize=float-divide-by-zero Detect floating-point division by zero. Unlike other similar op- tions, -fsanitize=float-divide-by-zero is not enabled by -fsani- tize=undefined, since floating-point division by zero can be a le- gitimate way of obtaining infinities and NaNs. -fsanitize=float-cast-overflow This option enables floating-point type to integer conversion checking. We check that the result of the conversion does not overflow. Unlike other similar options, -fsani- tize=float-cast-overflow is not enabled by -fsanitize=undefined. This option does not work well with "FE_INVALID" exceptions en- abled. -fsanitize=nonnull-attribute This option enables instrumentation of calls, checking whether null values are not passed to arguments marked as requiring a non-null value by the "nonnull" function attribute. -fsanitize=returns-nonnull-attribute This option enables instrumentation of return statements in func- tions marked with "returns_nonnull" function attribute, to detect returning of null values from such functions. -fsanitize=bool This option enables instrumentation of loads from bool. If a value other than 0/1 is loaded, a run-time error is issued. -fsanitize=enum This option enables instrumentation of loads from an enum type. If a value outside the range of values for the enum type is loaded, a run-time error is issued. -fsanitize=vptr This option enables instrumentation of C++ member function calls, member accesses and some conversions between pointers to base and derived classes, to verify the referenced object has the correct dynamic type. -fsanitize=pointer-overflow This option enables instrumentation of pointer arithmetics. If the pointer arithmetics overflows, a run-time error is issued. -fsanitize=builtin This option enables instrumentation of arguments to selected builtin functions. If an invalid value is passed to such argu- ments, a run-time error is issued. E.g. passing 0 as the argument to "__builtin_ctz" or "__builtin_clz" invokes undefined behavior and is diagnosed by this option. Note that sanitizers tend to increase the rate of false positive warn- ings, most notably those around -Wmaybe-uninitialized. We recommend against combining -Werror and [the use of] sanitizers. While -ftrapv causes traps for signed overflows to be emitted, -fsani- tize=undefined gives a diagnostic message. This currently works only for the C family of languages. -fno-sanitize=all This option disables all previously enabled sanitizers. -fsanitize=all is not allowed, as some sanitizers cannot be used together. -fasan-shadow-offset=number This option forces GCC to use custom shadow offset in AddressSanitizer checks. It is useful for experimenting with different shadow memory layouts in Kernel AddressSanitizer. -fsanitize-sections=s1,s2,... Sanitize global variables in selected user-defined sections. si may contain wildcards. -fsanitize-recover[=opts] -fsanitize-recover= controls error recovery mode for sanitizers men- tioned in comma-separated list of opts. Enabling this option for a sanitizer component causes it to attempt to continue running the pro- gram as if no error happened. This means multiple runtime errors can be reported in a single program run, and the exit code of the program may indicate success even when errors have been reported. The -fno-sanitize-recover= option can be used to alter this behavior: only the first detected error is reported and program then exits with a non-zero exit code. Currently this feature only works for -fsanitize=undefined (and its suboptions except for -fsanitize=unreachable and -fsanitize=return), -fsanitize=float-cast-overflow, -fsanitize=float-divide-by-zero, -fsan- itize=bounds-strict, -fsanitize=kernel-address and -fsanitize=address. For these sanitizers error recovery is turned on by default, except -fsanitize=address, for which this feature is experimental. -fsani- tize-recover=all and -fno-sanitize-recover=all is also accepted, the former enables recovery for all sanitizers that support it, the latter disables recovery for all sanitizers that support it. Even if a recovery mode is turned on the compiler side, it needs to be also enabled on the runtime library side, otherwise the failures are still fatal. The runtime library defaults to "halt_on_error=0" for ThreadSanitizer and UndefinedBehaviorSanitizer, while default value for AddressSanitizer is "halt_on_error=1". This can be overridden through setting the "halt_on_error" flag in the corresponding environment vari- able. Syntax without an explicit opts parameter is deprecated. It is equiva- lent to specifying an opts list of: undefined,float-cast-overflow,float-divide-by-zero,bounds-strict -fsanitize-address-use-after-scope Enable sanitization of local variables to detect use-after-scope bugs. The option sets -fstack-reuse to none. -fsanitize-trap[=opts] The -fsanitize-trap= option instructs the compiler to report for sani- tizers mentioned in comma-separated list of opts undefined behavior us- ing "__builtin_trap" rather than a "libubsan" library routine. If this option is enabled for certain sanitizer, it takes precedence over the -fsanitizer-recover= for that sanitizer, "__builtin_trap" will be emit- ted and be fatal regardless of whether recovery is enabled or disabled using -fsanitize-recover=. The advantage of this is that the "libubsan" library is not needed and is not linked in, so this is usable even in freestanding environments. Currently this feature works with -fsanitize=undefined (and its subop- tions except for -fsanitize=vptr), -fsanitize=float-cast-overflow, -fsanitize=float-divide-by-zero and -fsanitize=bounds-strict. "-fsani- tize-trap=all" can be also specified, which enables it for "undefined" suboptions, -fsanitize=float-cast-overflow, -fsanitize=float-di- vide-by-zero and -fsanitize=bounds-strict. If "-fsanitize-trap=unde- fined" or "-fsanitize-trap=all" is used and "-fsanitize=vptr" is en- abled on the command line, the instrumentation is silently ignored as the instrumentation always needs "libubsan" support, -fsani- tize-trap=vptr is not allowed. -fsanitize-undefined-trap-on-error The -fsanitize-undefined-trap-on-error option is deprecated equivalent of -fsanitize-trap=all. -fsanitize-coverage=trace-pc Enable coverage-guided fuzzing code instrumentation. Inserts a call to "__sanitizer_cov_trace_pc" into every basic block. -fsanitize-coverage=trace-cmp Enable dataflow guided fuzzing code instrumentation. Inserts a call to "__sanitizer_cov_trace_cmp1", "__sanitizer_cov_trace_cmp2", "__sani- tizer_cov_trace_cmp4" or "__sanitizer_cov_trace_cmp8" for integral com- parison with both operands variable or "__sani- tizer_cov_trace_const_cmp1", "__sanitizer_cov_trace_const_cmp2", "__sanitizer_cov_trace_const_cmp4" or "__sani- tizer_cov_trace_const_cmp8" for integral comparison with one operand constant, "__sanitizer_cov_trace_cmpf" or "__sanitizer_cov_trace_cmpd" for float or double comparisons and "__sanitizer_cov_trace_switch" for switch statements. -fcf-protection=[full|branch|return|none|check] -fcf-protection Enable code instrumentation to increase program security by checking that target addresses of control-flow transfer instructions (such as indirect function call, function return, indirect jump) are valid. This prevents diverting the flow of control to an unexpected target. This is intended to protect against such threats as Return-oriented Programming (ROP), and similarly call/jmp-oriented programming (COP/JOP). The -fcf-protection= keywords are interpreted as follows. The value "branch" tells the compiler to implement checking of validity of control-flow transfer at the point of indirect branch instructions, i.e. call/jmp instructions. The value "return" implements checking of validity at the point of re- turning from a function. The value "full" is an alias for specifying both "branch" and "return". The value "check" is used for the final link with link-time optimiza- tion (LTO). An error is issued if LTO object files are compiled with different -fcf-protection values. The value "check" is ignored at the compile time. The value "none" turns off instrumentation. -fcf-protection is an alias for -fcf-protection=full. To override a previous -fcf-protection option on the command line, add -fcf-protec- tion=none and then -fcf-protection=kind. The macro "__CET__" is defined when -fcf-protection is used. The first bit of "__CET__" is set to 1 for the value "branch" and the second bit of "__CET__" is set to 1 for the "return". You can also use the "nocf_check" attribute to identify which functions and calls should be skipped from instrumentation. Currently the x86 GNU/Linux target provides an implementation based on Intel Control-flow Enforcement Technology (CET) which works for i686 processor or newer. -fharden-compares For every logical test that survives gimple optimizations and is not the condition in a conditional branch (for example, conditions tested for conditional moves, or to store in boolean variables), emit extra code to compute and verify the reversed condition, and to call "__builtin_trap" if the results do not match. Use with -fharden-condi- tional-branches to cover all conditionals. -fharden-conditional-branches For every non-vectorized conditional branch that survives gimple opti- mizations, emit extra code to compute and verify the reversed condi- tion, and to call "__builtin_trap" if the result is unexpected. Use with -fharden-compares to cover all conditionals. -fharden-control-flow-redundancy Emit extra code to set booleans when entering basic blocks, and to ver- ify and trap, at function exits, when the booleans do not form an exe- cution path that is compatible with the control flow graph. Verification takes place before returns, before mandatory tail calls (see below) and, optionally, before escaping exceptions with -fhard- cfr-check-exceptions, before returning calls with -fhardcfr-check-re- turning-calls, and before noreturn calls with -fhardcfr-check-nore- turn-calls). Tail call optimization takes place too late to affect control flow re- dundancy, but calls annotated as mandatory tail calls by language front-ends, and any calls marked early enough as potential tail calls would also have verification issued before the call, but these possi- bilities are merely theoretical, as these conditions can only be met when using custom compiler plugins. -fhardcfr-skip-leaf Disable -fharden-control-flow-redundancy in leaf functions. -fhardcfr-check-exceptions When -fharden-control-flow-redundancy is active, check the recorded ex- ecution path against the control flow graph at exception escape points, as if the function body was wrapped with a cleanup handler that per- formed the check and reraised. This option is enabled by default; use -fno-hardcfr-check-exceptions to disable it. -fhardcfr-check-returning-calls When -fharden-control-flow-redundancy is active, check the recorded ex- ecution path against the control flow graph before any function call immediately followed by a return of its result, if any, so as to not prevent tail-call optimization, whether or not it is ultimately opti- mized to a tail call. This option is enabled by default whenever sibling call optimizations are enabled (see -foptimize-sibling-calls), but it can be enabled (or disabled, using its negated form) explicitly, regardless of the opti- mizations. -fhardcfr-check-noreturn-calls=[always|no-xthrow|nothrow|never] When -fharden-control-flow-redundancy is active, check the recorded ex- ecution path against the control flow graph before "noreturn" calls, either all of them (always), those that aren't expected to return con- trol to the caller through an exception (no-xthrow, the default), those that may not return control to the caller through an exception either (nothrow), or none of them (never). Checking before a "noreturn" function that may return control to the caller through an exception may cause checking to be performed more than once, if the exception is caught in the caller, whether by a han- dler or a cleanup. When -fhardcfr-check-exceptions is also enabled, the compiler will avoid associating a "noreturn" call with the implic- itly-added cleanup handler, since it would be redundant with the check performed before the call, but other handlers or cleanups in the func- tion, if activated, will modify the recorded execution path and check it again when another checkpoint is hit. The checkpoint may even be another "noreturn" call, so checking may end up performed multiple times. Various optimizers may cause calls to be marked as "noreturn" and/or "nothrow", even in the absence of the corresponding attributes, which may affect the placement of checks before calls, as well as the addi- tion of implicit cleanup handlers for them. This unpredictability, and the fact that raising and reraising exceptions frequently amounts to implicitly calling "noreturn" functions, have made no-xthrow the de- fault setting for this option: it excludes from the "noreturn" treat- ment only internal functions used to (re)raise exceptions, that are not affected by these optimizations. -fhardened Enable a set of flags for C and C++ that improve the security of the generated code without affecting its ABI. The precise flags enabled may change between major releases of GCC, but are currently: -D_FORTIFY_SOURCE=3 -D_GLIBCXX_ASSERTIONS -ftrivial-auto-var-init=zero -fPIE -pie -Wl,-z,relro,-z,now -fstack-protector-strong -fs- tack-clash-protection -fcf-protection=full (x86 GNU/Linux only) The list of options enabled by -fhardened can be generated using the --help=hardened option. When the system glibc is older than 2.35, -D_FORTIFY_SOURCE=2 is used instead. This option is intended to be used in production builds, not merely in debug builds. Currently, -fhardened is only supported on GNU/Linux targets. -fhardened only enables a particular option if it wasn't already speci- fied anywhere on the command line. For instance, -fhardened -fs- tack-protector will only enable -fstack-protector, but not -fstack-pro- tector-strong. -fstack-protector Emit extra code to check for buffer overflows, such as stack smashing attacks. This is done by adding a guard variable to functions with vulnerable objects. This includes functions that call "alloca", and functions with buffers larger than or equal to 8 bytes. The guards are initialized when a function is entered and then checked when the func- tion exits. If a guard check fails, an error message is printed and the program exits. Only variables that are actually allocated on the stack are considered, optimized away variables or variables allocated in registers don't count. -fstack-protector-all Like -fstack-protector except that all functions are protected. -fstack-protector-strong Like -fstack-protector but includes additional functions to be pro- tected --- those that have local array definitions, or have references to local frame addresses. Only variables that are actually allocated on the stack are considered, optimized away variables or variables al- located in registers don't count. -fstack-protector-explicit Like -fstack-protector but only protects those functions which have the "stack_protect" attribute. -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 environ- ment with multiple threads, but you only rarely need to specify it in a single-threaded environment since stack overflow is automatically de- tected on nearly all systems if there is only one stack. Note that this switch does not actually cause checking to be done; the operating system or the language runtime must do that. The switch causes generation of code to ensure that they see the stack being ex- tended. You can additionally specify a string parameter: no means no checking, generic means force the use of old-style checking, specific means use the best checking method and is equivalent to bare -fstack-check. Old-style checking is a generic mechanism that requires no specific target support in the compiler but comes with the following drawbacks: 1. Modified allocation strategy for large objects: they are always al- located dynamically if their size exceeds a fixed threshold. Note this may change the semantics of some code. 2. Fixed limit on the size of the static frame of functions: when it is topped by a particular function, stack checking is not reliable and a warning is issued by the compiler. 3. Inefficiency: because of both the modified allocation strategy and the generic implementation, code performance is hampered. Note that old-style stack checking is also the fallback method for spe- cific if no target support has been added in the compiler. -fstack-check= is designed for Ada's needs to detect infinite recursion and stack overflows. specific is an excellent choice when compiling Ada code. It is not generally sufficient to protect against stack-clash attacks. To protect against those you want -fs- tack-clash-protection. -fstack-clash-protection Generate code to prevent stack clash style attacks. When this option is enabled, the compiler will only allocate one page of stack space at a time and each page is accessed immediately after allocation. Thus, it prevents allocations from jumping over any stack guard page provided by the operating system. Most targets do not fully support stack clash protection. However, on those targets -fstack-clash-protection will protect dynamic stack allo- cations. -fstack-clash-protection may also provide limited protection for static stack allocations if the target supports -fstack-check=spe- cific. -fstack-limit-register=reg -fstack-limit-symbol=sym -fno-stack-limit 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 a larger stack is required, a signal is raised at run time. For most targets, the signal is raised before the stack overruns the boundary, so it is possible to catch the signal without taking special precau- tions. For instance, if the stack starts at absolute address 0x80000000 and grows downwards, you can use the flags -fstack-limit-sym- bol=__stack_limit and -Wl,--defsym,__stack_limit=0x7ffe0000 to enforce a stack limit of 128KB. Note that this may only work with the GNU linker. You can locally override stack limit checking by using the "no_stack_limit" function attribute. -fsplit-stack Generate code to automatically split the stack before it overflows. The resulting program has a discontiguous stack which can only overflow if the program is unable to allocate any more memory. This is most useful when running threaded programs, as it is no longer necessary to calculate a good stack size to use for each thread. This is currently only implemented for the x86 targets running GNU/Linux. When code compiled with -fsplit-stack calls code compiled without -fs- plit-stack, there may not be much stack space available for the latter code to run. If compiling all code, including library code, with -fs- plit-stack is not an option, then the linker can fix up these calls so that the code compiled without -fsplit-stack always has a large stack. Support for this is implemented in the gold linker in GNU Binutils re- lease 2.21 and later. -fstrub=disable Disable stack scrubbing entirely, ignoring any "strub" attributes. -fstrub=strict Functions default to "strub" mode "disabled", and apply strictly the restriction that only functions associated with "strub"-"callable" modes ("at-calls", "callable" and "always_inline" "internal") are "callable" by functions with "strub"-enabled modes ("at-calls" and "in- ternal"). -fstrub=relaxed Restore the default stack scrub ("strub") setting, namely, "strub" is only enabled as required by "strub" attributes associated with function and data types. "Relaxed" means that strub contexts are only prevented from calling functions explicitly associated with "strub" mode "dis- abled". This option is only useful to override other -fstrub=* options that precede it in the command line. -fstrub=at-calls Enable "at-calls" "strub" mode where viable. The primary use of this option is for testing. It exercises the "strub" machinery in scenarios strictly local to a translation unit. This "strub" mode modifies func- tion interfaces, so any function that is visible to other translation units, or that has its address taken, will not be affected by this op- tion. Optimization options may also affect viability. See the "strub" attribute documentation for details on viability and eligibility re- quirements. -fstrub=internal Enable "internal" "strub" mode where viable. The primary use of this option is for testing. This option is intended to exercise thoroughly parts of the "strub" machinery that implement the less efficient, but interface-preserving "strub" mode. Functions that would not be af- fected by this option are quite uncommon. -fstrub=all Enable some "strub" mode where viable. When both strub modes are vi- able, "at-calls" is preferred. -fdump-ipa-strubm adds function attrib- utes that tell which mode was selected for each function. The primary use of this option is for testing, to exercise thoroughly the "strub" machinery. -fvtable-verify=[std|preinit|none] This option is only available when compiling C++ code. It turns on (or off, if using -fvtable-verify=none) the security feature that verifies at run time, for every virtual call, that the vtable pointer through which the call is made is valid for the type of the object, and has not been corrupted or overwritten. If an invalid vtable pointer is de- tected at run time, an error is reported and execution of the program is immediately halted. This option causes run-time data structures to be built at program startup, which are used for verifying the vtable pointers. The options std and preinit control the timing of when these data structures are built. In both cases the data structures are built before execution reaches "main". Using -fvtable-verify=std causes the data structures to be built after shared libraries have been loaded and initialized. -fvtable-verify=preinit causes them to be built before shared libraries have been loaded and initialized. If this option appears multiple times in the command line with differ- ent values specified, none takes highest priority over both std and preinit; preinit takes priority over std. -fvtv-debug When used in conjunction with -fvtable-verify=std or -fvtable-ver- ify=preinit, causes debug versions of the runtime functions for the vtable verification feature to be called. This flag also causes the compiler to log information about which vtable pointers it finds for each class. This information is written to a file named vtv_set_ptr_data.log in the directory named by the environment variable VTV_LOGS_DIR if that is defined or the current working directory other- wise. Note: This feature appends data to the log file. If you want a fresh log file, be sure to delete any existing one. -fvtv-counts This is a debugging flag. When used in conjunction with -fvtable-ver- ify=std or -fvtable-verify=preinit, this causes the compiler to keep track of the total number of virtual calls it encounters and the number of verifications it inserts. It also counts the number of calls to certain run-time library functions that it inserts and logs this infor- mation for each compilation unit. The compiler writes this information to a file named vtv_count_data.log in the directory named by the envi- ronment variable VTV_LOGS_DIR if that is defined or the current working directory otherwise. It also counts the size of the vtable pointer sets for each class, and writes this information to vtv_class_set_sizes.log in the same directory. Note: This feature appends data to the log files. To get fresh log files, be sure to delete any existing ones. -finstrument-functions Generate instrumentation calls for entry and exit to functions. Just after function entry and just before function exit, the following pro- filing functions are called with the address of the current function and its call site. (On some platforms, "__builtin_return_address" does not work beyond the current function, so the call site information may not be available to the profiling functions otherwise.) void __cyg_profile_func_enter (void *this_fn, void *call_site); void __cyg_profile_func_exit (void *this_fn, void *call_site); The first argument is the address of the start of the current function, which may be looked up exactly in the symbol table. This instrumentation is also done for functions expanded inline in other functions. The profiling calls 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 "extern inline" in your C code, an addressable version of such functions must be provided. (This is normally the case anyway, but if you get lucky and the optimizer always expands the func- tions inline, you might have gotten away without providing static copies.) A function may be given the attribute "no_instrument_function", in which case this instrumentation is not done. This can be used, for ex- ample, for the profiling functions listed above, high-priority inter- rupt routines, and any functions from which the profiling functions cannot safely be called (perhaps signal handlers, if the profiling rou- tines generate output or allocate memory). -finstrument-functions-once This is similar to -finstrument-functions, but the profiling functions are called only once per instrumented function, i.e. the first profil- ing function is called after the first entry into the instrumented function and the second profiling function is called before the exit corresponding to this first entry. The definition of "once" for the purpose of this option is a little vague because the implementation is not protected against data races. As a result, the implementation only guarantees that the profiling functions are called at least once per process and at most once per thread, but the calls are always paired, that is to say, if a thread calls the first function, then it will call the second function, unless it never reaches the exit of the instrumented function. -finstrument-functions-exclude-file-list=file,file,... Set the list of functions that are excluded from instrumentation (see the description of -finstrument-functions). If the file that contains a function definition matches with one of file, then that function is not instrumented. The match is done on substrings: if the file parame- ter is a substring of the file name, it is considered to be a match. For example: -finstrument-functions-exclude-file-list=/bits/stl,include/sys excludes any inline function defined in files whose pathnames contain /bits/stl or include/sys. If, for some reason, you want to include letter , in one of sym, write ,. For example, -finstrument-functions-exclude-file-list=',,tmp' (note the single quote surrounding the option). -finstrument-functions-exclude-function-list=sym,sym,... This is similar to -finstrument-functions-exclude-file-list, but this option sets the list of function names to be excluded from instrumenta- tion. The function name to be matched is its user-visible name, such as "vector<int> blah(const vector<int> &)", not the internal mangled name (e.g., "_Z4blahRSt6vectorIiSaIiEE"). The match is done on sub- strings: if the sym parameter is a substring of the function name, it is considered to be a match. For C99 and C++ extended identifiers, the function name must be given in UTF-8, not using universal character names. -fpatchable-function-entry=N[,M] Generate N NOPs right at the beginning of each function, with the func- tion entry point before the Mth NOP. If M is omitted, it defaults to 0 so the function entry points to the address just at the first NOP. The NOP instructions reserve extra space which can be used to patch in any desired instrumentation at run time, provided that the code segment is writable. The amount of space is controllable indirectly via the num- ber of NOPs; the NOP instruction used corresponds to the instruction emitted by the internal GCC back-end interface "gen_nop". This behav- ior is target-specific and may also depend on the architecture variant and/or other compilation options. For run-time identification, the starting addresses of these areas, which correspond to their respective function entries minus M, are ad- ditionally collected in the "__patchable_function_entries" section of the resulting binary. Note that the value of "__attribute__ ((patchable_function_entry (N,M)))" takes precedence over command-line option -fpatchable-func- tion-entry=N,M. This can be used to increase the area size or to re- move it completely on a single function. If "N=0", no pad location is recorded. The NOP instructions are inserted at---and maybe before, depending on M---the function entry address, even before the prologue. On PowerPC with the ELFv2 ABI, for a function with dual entry points, the local entry point is this function entry address by default. See the -msplit-patch-nops option to change this. The maximum value of N and M is 65535. On PowerPC with the ELFv2 ABI, for a function with dual entry points, the supported values for M are 0, 2, 6 and 14 when not using -msplit-patch-nops. Options Controlling the Preprocessor These options control the C preprocessor, which is run on each C source file before actual compilation. If you use the -E option, nothing is done except preprocessing. Some of these options make sense only together with -E because they cause the pre- processor output to be unsuitable for actual compilation. In addition to the options listed here, there are a number of options to control search paths for include files documented in Directory Options. Options to control preprocessor diagnostics are listed in Warning Options. -D name --define-macro=name --define-macro name Predefine name as a macro, with definition 1. -D name=definition --define-macro=name=definition --define-macro name=definition The contents of definition are tokenized and processed as if they ap- peared during translation phase three in a #define directive. In par- ticular, the definition is truncated by embedded newline characters. 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. 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 should quote the option. With sh and csh, -D'name(args...)=definition' works. -D and -U options are processed in the order they are given on the com- mand line. All -imacros file and -include file options are processed after all -D and -U options. -U name --undefine-macro=name --undefine-macro name Cancel any previous definition of name, either built in or provided with a -D option. -include file --include=file --include file Process file as if "#include "file"" appeared as the first line of the primary source file. However, the first directory searched for file is the preprocessor's working directory instead of the directory contain- ing the main source file. If not found there, it is searched for in the remainder of the "#include "..."" search chain as normal. If multiple -include options are given, the files are included in the order they appear on the command line. -imacros file --imacros=file --imacros file Exactly like -include, except that any output produced by scanning file is thrown away. Macros it defines remain defined. This allows you to acquire all the macros from a header without also processing its decla- rations. All files specified by -imacros are processed before all files speci- fied by -include. -undef Do not predefine any system-specific or GCC-specific macros. The stan- dard predefined macros remain defined. -pthread Define additional macros required for using the POSIX threads library. You should use this option consistently for both compilation and link- ing. This option is supported on GNU/Linux targets, most other Unix derivatives, and also on x86 Cygwin and MinGW targets. -M --dependencies Instead of outputting the result of preprocessing, output a rule suit- able for make describing the dependencies of the main source file. The preprocessor outputs one make rule containing the object file name for that source file, a colon, and the names of all the included files, in- cluding those coming from -include or -imacros command-line options. Unless specified explicitly (with -MT or -MQ), the object file name consists of the name of the source file with any suffix replaced with object file suffix and with any leading directory parts removed. If there are many included files then the rule is split into several lines using \-newline. The rule has no commands. This option does not suppress the preprocessor's debug output, such as -dM. To avoid mixing such debug output with the dependency rules you should explicitly specify the dependency output file with -MF, or use an environment variable like DEPENDENCIES_OUTPUT. Debug output is still sent to the regular output stream as normal. Passing -M to the driver implies -E, and suppresses warnings with an implicit -w. -MM --user-dependencies Like -M but do not mention header files that are found in system header directories, nor header files that are included, directly or indi- rectly, from such a header. This implies that the choice of angle brackets or double quotes in an #include directive does not in itself determine whether that header ap- pears in -MM dependency output. -MF file When used with -M or -MM, specifies a file to write the dependencies to. If no -MF switch is given the preprocessor sends the rules to the same place it would send preprocessed output. When used with the driver options -MD or -MMD, -MF overrides the de- fault dependency output file. If file is -, then the dependencies are written to stdout. -MG --print-missing-file-dependencies In conjunction with an option such as -M requesting dependency genera- tion, -MG assumes missing header files are generated files and adds them to the dependency list without raising an error. The dependency filename is taken directly from the "#include" directive without prepending any path. -MG also suppresses preprocessed output, as a missing header file renders this useless. This feature is used in automatic updating of makefiles. -Mno-modules Disable dependency generation for compiled module interfaces. -MP This option instructs CPP 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 make gives if you remove header files without updating the Makefile to match. This is typical output: test.o: test.c test.h test.h: -MT target Change the target of the rule emitted by dependency generation. By de- fault CPP takes the name of the main input file, deletes any directory components and any file suffix such as .c, and appends the platform's usual object suffix. The result is the target. An -MT option sets the target to be exactly the string you specify. If you want multiple targets, you can specify them as a single argument to -MT, or use multiple -MT options. For example, -MT '$(objpfx)foo.o' might give $(objpfx)foo.o: foo.c -MQ target Same as -MT, but it quotes any characters which are special to Make. -MQ '$(objpfx)foo.o' gives $$(objpfx)foo.o: foo.c The default target is automatically quoted, as if it were given with -MQ. -MD --write-dependencies -MD is equivalent to -M -MF file, except that -E is not implied. The driver determines file based on whether an -o option is given. If it is, the driver uses its argument but with a suffix of .d, otherwise it takes the name of the input file, removes any directory components and suffix, and applies a .d suffix. If -MD is used in conjunction with -E, any -o switch is understood to specify the dependency output file, but if used without -E, each -o is understood to specify a target object file. Since -E is not implied, -MD can be used to generate a dependency out- put file as a side effect of the compilation process. -MMD --write-user-dependencies Like -MD except mention only user header files, not system header files. -fpreprocessed Indicate to the preprocessor that the input file has already been pre- processed. This suppresses things like macro expansion, trigraph con- version, escaped newline splicing, and processing of most directives. The preprocessor still recognizes and removes comments, so that you can pass a file preprocessed with -C to the compiler without problems. In this mode the integrated preprocessor is little more than a tokenizer for the front ends. -fpreprocessed is implicit if the input file has one of the extensions .i, .ii or .mi. These are the extensions that GCC uses for pre- processed files created by -save-temps. -fdirectives-only When preprocessing, handle directives, but do not expand macros. The option's behavior depends on the -E and -fpreprocessed options. With -E, preprocessing is limited to the handling of directives such as "#define", "#ifdef", and "#error". Other preprocessor operations, such as macro expansion and trigraph conversion are not performed. In addi- tion, the -dD option is implicitly enabled. With -fpreprocessed, predefinition of command line and most builtin macros is disabled. Macros such as "__LINE__", which are contextually dependent, are handled normally. This enables compilation of files previously preprocessed with "-E -fdirectives-only". With both -E and -fpreprocessed, the rules for -fpreprocessed take precedence. This enables full preprocessing of files previously pre- processed with "-E -fdirectives-only". -fdollars-in-identifiers Accept $ in identifiers. -fextended-identifiers Accept universal character names and extended characters in identi- fiers. This option is enabled by default for C99 (and later C standard versions) and C++. -fno-canonical-system-headers When preprocessing, do not shorten system header paths with canonical- ization. -fmax-include-depth=depth Set the maximum depth of the nested #include. The default is 200. -fsearch-include-path[=kind] Look for input files on the #include path, not just the current direc- tory. This is particularly useful with C++20 modules, for which both header units and module interface units need to be compiled directly: g++ -c -std=c++20 -fmodules -fsearch-include-path bits/stdc++.h bits/std.cc kind defaults to user, which looks on the #include "..." search path; you can also explicitly specify system for the "#include <...>" search path. -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. -ftrack-macro-expansion[=level] Track locations of tokens across macro expansions. This allows the com- piler to emit diagnostic about the current macro expansion stack when a compilation error occurs in a macro expansion. Using this option makes the preprocessor and the compiler consume more memory. The level para- meter can be used to choose the level of precision of token location tracking thus decreasing the memory consumption if necessary. Value 0 of level de-activates this option. Value 1 tracks tokens locations in a degraded mode for the sake of minimal memory overhead. In this mode all tokens resulting from the expansion of an argument of a function-like macro have the same location. Value 2 tracks tokens locations com- pletely. This value is the most memory hungry. When this option is given no argument, the default parameter value is 2. Note that "-ftrack-macro-expansion=2" is activated by default. -fmacro-prefix-map=old=new When preprocessing files residing in directory old, expand the "__FILE__" and "__BASE_FILE__" macros as if the files resided in direc- tory new instead. This can be used to change an absolute path to a relative path by using . for new which can result in more reproducible builds that are location independent. This option also affects "__builtin_FILE()" during compilation. See also -ffile-prefix-map and -fcanon-prefix-map. -fexec-charset=charset Set the execution character set, used for string and character con- stants. The default is UTF-8. charset can be any encoding supported by the system's "iconv" library routine. -fwide-exec-charset=charset Set the wide execution character set, used for wide string and charac- ter constants. The default is one of UTF-32BE, UTF-32LE, UTF-16BE, or UTF-16LE, whichever corresponds to the width of "wchar_t" and the big-endian or little-endian byte order being used for code generation. As with -fexec-charset, charset can be any encoding supported by the system's "iconv" library routine; however, you will have problems with encodings that do not fit exactly in "wchar_t". -finput-charset=charset Set the input character set, used for translation from the character set of the input file to the source character set used by GCC. The de- fault is UTF-8. charset can be any encoding supported by the system's "iconv" library routine. If the input character set is UTF-8, warnings about ill-formed code unit sequences are issued if -Winvalid-utf8 is enabled. Otherwise no diagnostics are issued when the input character set matches the execu- tion character set. If they are different, ill-formed code unit se- quences result in an error during transcoding to the execution charac- ter set. -fpch-deps When using precompiled headers, this flag causes the dependency-output flags to also list the files from the precompiled header's dependen- cies. If not specified, only the precompiled header are listed and not the files that were used to create it, because those files are not con- sulted when a precompiled header is used. -fpch-preprocess This option allows use of a precompiled header together with -E. It inserts a special "#pragma", "#pragma GCC pch_preprocess "filename"" in the output to mark the place where the precompiled header was found, and its filename. When -fpreprocessed is in use, GCC recognizes this "#pragma" and loads the PCH. This option is off by default, because the resulting preprocessed out- put is only really suitable as input to GCC. It is switched on by -save-temps. You should not write this "#pragma" in your own code, but it is safe to edit the filename if the PCH file is available in a different location. The filename may be absolute or it may be relative to GCC's current di- rectory. -fworking-directory Enable generation of linemarkers in the preprocessor output that let the compiler know the current working directory at the time of prepro- cessing. When this option is enabled, the preprocessor emits, after the initial linemarker, a second linemarker with the current working directory followed by two slashes. GCC uses this directory, when it's present in the preprocessed input, as the directory emitted as the cur- rent working directory in some debugging information formats. This op- tion is implicitly enabled if debugging information is enabled, but this can be inhibited with the negated form -fno-working-directory. If the -P flag is present in the command line, this option has no effect, since no "#line" directives are emitted whatsoever. -C --comments 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. You should be prepared for side effects when using -C; it causes the preprocessor to treat comments as tokens in their own right. For exam- ple, 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 #. -CC --comments-in-macros Do not discard comments, including during macro expansion. This is like -C, except that comments contained within macros are also passed through to the output file where the macro is expanded. In addition to the side effects of the -C option, the -CC option causes all C++-style comments inside a macro to be converted to C-style com- ments. This is to prevent later use of that macro from inadvertently commenting out the remainder of the source line. The -CC option is generally used to support lint comments. -P --no-line-commands 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. -traditional --traditional -traditional-cpp --traditional-cpp Try to imitate the behavior of pre-standard C preprocessors, as opposed to ISO C preprocessors. See the GNU CPP manual for details. Note that GCC does not otherwise attempt to emulate a pre-standard C compiler, and these options are only supported with the -E switch, or when invoking CPP explicitly. -trigraphs --trigraphs Support ISO C trigraphs. These are three-character sequences, all starting with ??, that are defined by ISO C to stand for single charac- ters. For example, ??/ stands for \, so '??/n' is a character constant for a newline. The nine trigraphs and their replacements are Trigraph: ??( ??) ??< ??> ??= ??/ ??' ??! ??- Replacement: [ ] { } # \ ^ | ~ By default, GCC ignores trigraphs, but in standard-conforming modes it converts them. See the -std and -ansi options. -remap Enable special code to work around file systems which only permit very short file names, such as MS-DOS. -H --trace-includes Print the name of each header file used, in addition to other normal activities. Each name is indented to show how deep in the #include stack it is. Precompiled header files are also printed, even if they are found to be invalid; an invalid precompiled header file is printed with ...x and a valid one with ...! . -dletters --dump=letters --dump letters Says to make debugging dumps during compilation as specified by let- ters. The flags documented here are those relevant to the preproces- sor. Other letters are interpreted by the compiler proper, or reserved for future versions of GCC, and so are silently ignored. If you spec- ify letters whose behavior conflicts, the result is undefined. -dM --dump=M Instead of the normal output, generate a list of #define directives for all the macros defined during the execution of the preproces- sor, including predefined macros. This gives you a way of finding out what is predefined in your version of the preprocessor. Assum- ing you have no file foo.h, the command touch foo.h; cpp -dM foo.h shows all the predefined macros. If you use -dM without the -E option, -dM is interpreted as a syn- onym for -fdump-rtl-mach. -dD --dump=D Like -dM except that it outputs both the #define directives and the result of preprocessing. Both kinds of output go to the standard output file. -dN --dump=N Like -dD, but emit only the macro names, not their expansions. -dI --dump=I Output #include directives in addition to the result of preprocess- ing. -dU --dump=U Like -dD except that only macros that are expanded, or whose de- finedness is tested in preprocessor directives, are output; the output is delayed until the use or test of the macro; and #undef directives are also output for macros tested but undefined at the time. -fdebug-cpp This option is only useful for debugging GCC. When used from CPP or with -E, it dumps debugging information about location maps. Every to- ken in the output is preceded by the dump of the map its location be- longs to. When used from GCC without -E, this option has no effect. -Wp,option You can use -Wp,option to bypass the compiler driver and pass option directly through to the preprocessor. If option 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 -Wp forcibly bypasses this phase. The preprocessor's direct interface is undocumented and subject to change, so whenever possible you should avoid using -Wp and let the driver han- dle the options instead. -Xpreprocessor option Pass option as an option to the preprocessor. You can use this to sup- ply system-specific preprocessor options that GCC does not recognize. If you want to pass an option that takes an argument, you must use -Xpreprocessor twice, once for the option and once for the argument. -no-integrated-cpp --no-integrated-cpp Perform preprocessing as a separate pass before compilation. By de- fault, GCC performs preprocessing as an integrated part of input tok- enization and parsing. If this option is provided, the appropriate language front end (cc1, cc1plus, or cc1obj for C, C++, and Objec- tive-C, respectively) is instead invoked twice, once for preprocessing only and once for actual compilation of the preprocessed input. This option may be useful in conjunction with the -B or -wrapper options to specify an alternate preprocessor or perform additional processing of the program source between normal preprocessing and compilation. Passing Options to the Assembler You can pass options to the assembler. -Wa,option Pass option as an option to the assembler. If option contains commas, it is split into multiple options at the commas. -Xassembler option --for-assembler=option --for-assembler option Pass option as an option to the assembler. You can use this to supply system-specific assembler options that GCC does not recognize. If you want to pass an option that takes an argument, you must use -Xassembler twice, once for the option and once for the argument. 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. object-file-name A file name that does not end in a special recognized suffix is consid- ered to name an object file or library. (Object files are distin- guished from libraries by the linker according to the file contents.) If linking is done, these object files are used as input to the linker. -c -S -E If any of these options is used, then the linker is not run, and object file names should not be used as arguments. -flink-libatomic Enable linking of libatomic if it's supported by target, and is enabled by default. The negative form -fno-link-libatomic can be used to ex- plicitly disable linking of libatomic. -flinker-output=type This option controls code generation of the link-time optimizer. By default the linker output is automatically determined by the linker plugin. For debugging the compiler and if incremental linking with a non-LTO object file is desired, it may be useful to control the type manually. If type is exec, code generation produces a static binary. In this case -fpic and -fpie are both disabled. If type is dyn, code generation produces a shared library. In this case -fpic or -fPIC is preserved, but not enabled automatically. This allows to build shared libraries without position-independent code on architectures where this is possible, i.e. on x86. If type is pie, code generation produces an -fpie executable. This re- sults in similar optimizations as exec except that -fpie is not dis- abled if specified at compilation time. If type is rel, the compiler assumes that incremental linking is done. The sections containing intermediate code for link-time optimization are merged, pre-optimized, and output to the resulting object file. In addition, if -ffat-lto-objects is specified, binary code is produced for future non-LTO linking. The object file produced by incremental linking is smaller than a static library produced from the same object files. At link time the result of incremental linking also loads faster than a static library assuming that the majority of objects in the library are used. Finally nolto-rel configures the compiler for incremental linking where code generation is forced, a final binary is produced, and the interme- diate code for later link-time optimization is stripped. When multiple object files are linked together the resulting code is better optimized than with link-time optimizations disabled (for example, cross-module inlining happens), but most of the benefits of whole-program optimiza- tions are lost. During the incremental link (by -r) the linker plugin defaults to rel. GNU Binutils 2.44 or later is needed to incrementally link LTO objects and non-LTO objects into a single mixed object file. If any of the ob- ject files in an incremental link cannot be used for link-time opti- mization, the linker plugin issues a warning and uses nolto-rel. To maintain whole-program optimization, link such objects into a static library instead. -fuse-ld=bfd Use the bfd linker instead of the default linker. -fuse-ld=gold Use the gold linker instead of the default linker. -fuse-ld=lld Use the LLVM lld linker instead of the default linker. -fuse-ld=mold Use the Modern Linker (mold) instead of the default linker. -fuse-ld=wild Use the Wild linker (wild) instead of the default linker. -llibrary -l library Search the library named library when linking. (The second alternative with the library as a separate argument is only for POSIX compliance and is not recommended.) The -l option is passed directly to the linker by GCC. Refer to your linker documentation for exact details. The general description below applies to the GNU linker. The linker searches a standard list of directories for the library. The directories searched include several standard system directories plus any that you specify with -L. Static libraries are archives of object files, and have file names like liblibrary.a. Some targets also support shared libraries, which typi- cally have names like liblibrary.so. If both static and shared li- braries are found, the linker gives preference to linking with the shared library unless the -static option is used. 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, foo.o -lz bar.o searches library z after file foo.o but before bar.o. If bar.o refers to functions in z, those functions may not be loaded. -lobjc You need this special case of the -l option in order to link an Objec- tive-C or Objective-C++ program. -nostartfiles Do not use the standard system startup files when linking. The stan- dard system libraries are used normally, unless -nostdlib, -nolibc, or -nodefaultlibs is used. -nodefaultlibs Do not use the standard system libraries when linking. Only the li- braries you specify are passed to the linker, and options specifying linkage of the system libraries, such as -static-libgcc or -shared-libgcc, are ignored. The standard startup files are used nor- mally, unless -nostartfiles is used. The compiler may generate calls to "memcmp", "memset", "memcpy" and "memmove". These entries are usually resolved by entries in libc. These entry points should be supplied through some other mechanism when this option is specified. -nolibc Do not use the C library or system libraries tightly coupled with it when linking. Still link with the startup files, libgcc or toolchain provided language support libraries such as libgnat, libgfortran or libstdc++ unless options preventing their inclusion are used as well. This typically removes -lc from the link command line, as well as sys- tem libraries that normally go with it and become meaningless when ab- sence of a C library is assumed, for example -lpthread or -lm in some configurations. This is intended for bare-board targets when there is indeed no C library available. -nostdlib --no-standard-libraries Do not use the standard system startup files or libraries when linking. No startup files and only the libraries you specify are passed to the linker, and options specifying linkage of the system libraries, such as -static-libgcc or -shared-libgcc, are ignored. The compiler may generate calls to "memcmp", "memset", "memcpy" and "memmove". These entries are usually resolved by entries in libc. These entry points should be supplied through some other mechanism when this option is specified. One of the standard libraries bypassed by -nostdlib and -nodefaultlibs is libgcc.a, a library of internal subroutines which GCC uses to over- come shortcomings of particular machines, or special needs for some languages. In most cases, you need libgcc.a even when you want to avoid other standard libraries. In other words, when you specify -nostdlib or -nodefaultlibs you should usually specify -lgcc as well. This ensures that you have no unresolved references to internal GCC library subrou- tines. (An example of such an internal subroutine is "__main", used to ensure C++ constructors are called.) -nostdlib++ Do not implicitly link with standard C++ libraries. -e entry --entry=entry --entry entry Specify that the program entry point is entry. The argument is inter- preted by the linker; the GNU linker accepts either a symbol name or an address. -pie --pie Produce a dynamically linked position independent executable on targets that support it. For predictable results, you must also specify the same set of options used for compilation (-fpie, -fPIE, or model subop- tions) when you specify this linker option. -no-pie Don't produce a dynamically linked position independent executable. -static-pie --static-pie Produce a static position independent executable on targets that sup- port it. A static position independent executable is similar to a sta- tic executable, but can be loaded at any address without a dynamic linker. For predictable results, you must also specify the same set of options used for compilation (-fpie, -fPIE, or model suboptions) when you specify this linker option. -pthread Link with the POSIX threads library. This option is supported on GNU/Linux targets, most other Unix derivatives, and also on x86 Cygwin and MinGW targets. On some targets this option also sets flags for the preprocessor, so it should be used consistently for both compilation and linking. -r Produce a relocatable object as output. This is also known as partial linking. -rdynamic Pass the flag -export-dynamic to the ELF linker, on targets that sup- port it. This instructs the linker to add all symbols, not only used ones, to the dynamic symbol table. This option is needed for some uses of "dlopen" or to allow obtaining backtraces from within a program. -s Remove all symbol table and relocation information from the executable. -static --static On systems that support dynamic linking, this overrides -pie and pre- vents linking with the shared libraries. On other systems, this option has no effect. -shared --shared Produce a shared object which can then be linked with other objects to form an executable. Not all systems support this option. For pre- dictable results, you must also specify the same set of options used for compilation (-fpic, -fPIC, or model suboptions) when you specify this linker option.[1] -shared-libgcc -static-libgcc On systems that provide libgcc as a shared library, these options force the use of either the shared or static version, respectively. If no shared version of libgcc was built when the compiler was configured, these options have no effect. There are several situations in which an application should use the shared libgcc 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 libgcc. Therefore, the G++ driver automatically adds -shared-libgcc whenever you build a shared library or a main executable, because C++ programs typically use exceptions, so this is the right thing to do. If, instead, you use the GCC driver to create shared libraries, you may find that they are not always linked with the shared libgcc. If GCC finds, at its configuration time, that you have a non-GNU linker or a GNU linker that does not support option --eh-frame-hdr, it links the shared version of libgcc into shared libraries by default. Otherwise, it takes advantage of the linker and optimizes away the linking with the shared version of libgcc, 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. However, if a library or main executable is supposed to throw or catch exceptions, you must link it using the G++ driver, or using the option -shared-libgcc, such that it is linked with the shared libgcc. -static-libasan When the -fsanitize=address option is used to link a program, the GCC driver automatically links against libasan. If libasan is available as a shared library, and the -static option is not used, then this links against the shared version of libasan. The -static-libasan option di- rects the GCC driver to link libasan statically, without necessarily linking other libraries statically. -static-libhwasan When the -fsanitize=hwaddress option is used to link a program, the GCC driver automatically links against libhwasan. If libhwasan is avail- able as a shared library, and the -static option is not used, then this links against the shared version of libhwasan. The -static-libhwasan option directs the GCC driver to link libhwasan statically, without necessarily linking other libraries statically. -static-liblsan When the -fsanitize=leak option is used to link a program, the GCC dri- ver automatically links against liblsan. If liblsan is available as a shared library, and the -static option is not used, then this links against the shared version of liblsan. The -static-liblsan option di- rects the GCC driver to link liblsan statically, without necessarily linking other libraries statically. -static-libtsan When the -fsanitize=thread option is used to link a program, the GCC driver automatically links against libtsan. If libtsan is available as a shared library, and the -static option is not used, then this links against the shared version of libtsan. The -static-libtsan option di- rects the GCC driver to link libtsan statically, without necessarily linking other libraries statically. -static-libubsan When the -fsanitize=undefined option is used to link a program, the GCC driver automatically links against libubsan. If libubsan is available as a shared library, and the -static option is not used, then this links against the shared version of libubsan. The -static-libubsan op- tion directs the GCC driver to link libubsan statically, without neces- sarily linking other libraries statically. -static-libstdc++ When the g++ program is used to link a C++ program, it normally auto- matically links against libstdc++. If libstdc++ is available as a shared library, and the -static option is not used, then this links against the shared version of libstdc++. That is normally fine. How- ever, it is sometimes useful to freeze the version of libstdc++ used by the program without going all the way to a fully static link. The -static-libstdc++ option directs the g++ driver to link libstdc++ stat- ically, without necessarily linking other libraries statically. -symbolic --symbolic Bind references to global symbols when building a shared object. Warn about any unresolved references (unless overridden by the link editor option -Xlinker -z -Xlinker defs). Only a few systems support this op- tion. -T script Use script as the linker script. This option is supported by most sys- tems using the GNU linker. On some targets, such as bare-board targets without an operating system, the -T option may be required when linking to avoid references to undefined symbols. -Xlinker option Pass option as an option to the linker. You can use this to supply system-specific linker options that GCC does not recognize. If you want to pass an option that takes a separate argument, you must use -Xlinker twice, once for the option and once for the argument. For example, to pass -assert definitions, you must write -Xlinker -assert -Xlinker definitions. It does not work to write -Xlinker "-assert def- initions", because this passes the entire string as a single argument, which is not what the linker expects. When using the GNU linker, it is usually more convenient to pass argu- ments to linker options using the option=value syntax than as separate arguments. For example, you can specify -Xlinker -Map=output.map rather than -Xlinker -Map -Xlinker output.map. Other linkers may not support this syntax for command-line options. -Wl,option --for-linker=option --for-linker option Pass option as an option to the linker. If option contains commas, it is split into multiple options at the commas. You can use this syntax to pass an argument to the option. For example, -Wl,-Map,output.map passes -Map output.map to the linker. When using the GNU linker, you can also get the same effect with -Wl,-Map=output.map. -u symbol --force-link=symbol --force-link symbol Pretend the symbol symbol is undefined, to force linking of library modules to define it. You can use -u multiple times with different symbols to force loading of additional library modules. -Tbss=addr -Tdata=addr -Ttext=addr -N -n -t -Z -z keyword These options are passed through to the linker without interpretation by GCC. Refer to your linker documentation for the meanings of these options. Options for Directory Search These options specify directories to search for header files, for libraries and for parts of the compiler: -I dir -iquote dir -isystem dir -idirafter dir --include-directory-after=dir --include-directory-after dir --include-directory=dir --include-directory dir Add the directory dir to the list of directories to be searched for header files during preprocessing. --include-directory is an alias for -I, while --include-directory-after is an alias for -idirafter. If dir begins with = or $SYSROOT, then the = or $SYSROOT is replaced by the sysroot prefix; see --sysroot and -isysroot. Directories specified with -iquote apply only to the quote form of the directive, "#include "file"". Directories specified with -I, -isystem, or -idirafter apply to lookup for both the "#include "file"" and "#in- clude <file>" directives. You can specify any number or combination of these options on the com- mand line to search for header files in several directories. The lookup order is as follows: 1. For the quote form of the include directive, the directory of the current file is searched first. 2. For the quote form of the include directive, the directories speci- fied by -iquote options are searched in left-to-right order, as they appear on the command line. 3. Directories specified with -I options are scanned in left-to-right order. 4. Directories specified with -isystem options are scanned in left-to-right order. 5. Standard system directories are scanned. 6. Directories specified with -idirafter options are scanned in left-to-right order. You can use -I to override a system header file, substituting your own version, since these directories are searched before the standard sys- tem header file directories. However, you should not use this option to add directories that contain vendor-supplied system header files; use -isystem for that. The -isystem and -idirafter options also mark the directory as a system directory, so that it gets the same special treatment that is applied to the standard system directories. If a standard system include directory, or a directory specified with -isystem, is also specified with -I, the -I option is ignored. The di- rectory is still searched but as a system directory at its normal posi- tion in the system include chain. This is to ensure that GCC's proce- dure to fix buggy system headers and the ordering for the "#in- clude_next" directive are not inadvertently changed. If you really need to change the search order for system directories, use the -nostd- inc and/or -isystem options. -I- --include-barrier Split the include path. This option has been deprecated. Please use -iquote instead for -I directories before the -I- and remove the -I- option. Any directories specified with -I options before -I- are searched only for headers requested with "#include "file""; they are not searched for "#include <file>". If additional directories are specified with -I op- tions after the -I-, those directories are searched for all #include directives. In addition, -I- inhibits the use of the directory of the current file directory as the first search directory for "#include "file"". There is no way to override this effect of -I-. -iprefix prefix --include-prefix=prefix --include-prefix prefix Specify prefix as the prefix for subsequent -iwithprefix options. If the prefix represents a directory, you should include the final /. -iwithprefix dir -iwithprefixbefore dir --include-with-prefix=prefix --include-with-prefix prefix --include-with-prefix-after=prefix --include-with-prefix-after prefix --include-with-prefix-before=prefix --include-with-prefix-before prefix Append dir to the prefix specified previously with -iprefix, and add the resulting directory to the include search path. -iwithprefixbefore puts it in the same place -I would; -iwithprefix puts it where -idi- rafter would. --include-with-prefix and --include-with-prefix-after are both aliases for -iwithprefix, while --include-with-prefix-before is an alias for -iwithprefixbefore. -isysroot dir This option is like the --sysroot option, but applies only to header files (except for Darwin targets, where it applies to both header files and libraries). See the --sysroot option for more information. -imultilib dir Use dir as a subdirectory of the directory containing target-specific C++ headers. -imultiarch dir Use dir as a subdirectory of the directory containing architecture-spe- cific C++ headers. -nostdinc --no-standard-includes Do not search the standard system directories for header files. Only the directories explicitly specified with -I, -iquote, -isystem, and/or -idirafter options (and the directory of the current file, if appropri- ate) are searched. -nostdinc++ Do not search for header files in the C++-specific standard directo- ries, but do still search the other standard directories. (This option is used when building the C++ library.) --embed-dir=dir --embed-directory=dir --embed-directory dir Append dir directory to the list of searched directories for "#embed" preprocessing directive or "__has_embed" macro. There are no default directories for "#embed". If dir begins with = or $SYSROOT, then the = or $SYSROOT is replaced by the sysroot prefix; see --sysroot and -isysroot. -iplugindir=dir Set the directory to search for plugins that are passed by -fplu- gin=name instead of -fplugin=path/name.so. This option is not meant to be used by the user, but only passed by the driver. -Ldir --library-directory=dir --library-directory dir Add directory dir to the list of directories to be searched for -l. -Bprefix --prefix=prefix --prefix prefix This option specifies where to find the executables, libraries, include files, and data files of the compiler itself. The compiler driver program runs one or more of the subprograms cpp, cc1, as and ld. It tries prefix as a prefix for each program it tries to run, both with and without machine/version/ for the corresponding target machine and compiler version. For each subprogram to be run, the compiler driver first tries the -B prefix, if any. If that name is not found, or if -B is not specified, the driver tries two standard prefixes, /usr/lib/gcc/ and /usr/lo- cal/lib/gcc/. If neither of those results in a file name that is found, the unmodified program name is searched for using the directo- ries specified in your PATH environment variable. The compiler checks to see if the path provided by -B refers to a di- rectory, and if necessary it adds a directory separator character at the end of the path. -B prefixes that effectively specify directory names also apply to li- braries in the linker, because the compiler translates these options into -L options for the linker. They also apply to include files in the preprocessor, because the compiler translates these options into -isystem options for the preprocessor. In this case, the compiler ap- pends include to the prefix. The runtime support file libgcc.a can also be searched for using the -B 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. Another way to specify a prefix much like the -B prefix is to use the environment variable GCC_EXEC_PREFIX. As a special kludge, if the path provided by -B is [dir/]stageN/, where N is a number in the range 0 to 9, then it is replaced by [dir/]in- clude. This is to help with boot-strapping the compiler. -no-canonical-prefixes --no-canonical-prefixes Do not expand any symbolic links, resolve references to /../ or /./, or make the path absolute when generating a relative prefix. --sysroot=dir --sysroot dir Use dir as the logical root directory for headers and libraries. For example, if the compiler normally searches for headers in /usr/include and libraries in /usr/lib, it instead searches dir/usr/include and dir/usr/lib. If you use both this option and the -isysroot option, then the --sys- root option applies to libraries, but the -isysroot option applies to header files. The GNU linker (beginning with version 2.16) has the necessary support for this option. If your linker does not support this option, the header file aspect of --sysroot still works, but the library aspect does not. --no-sysroot-suffix For some targets, a suffix is added to the root directory specified with --sysroot, depending on the other options used, so that headers may for example be found in dir/suffix/usr/include instead of dir/usr/include. This option disables the addition of such a suffix. Options for Code Generation Conventions These machine-independent options control the interface conventions used in code generation. Most of them have both positive and negative forms; the negative form of -ffoo is -fno-foo. In the table below, only one of the forms is listed---the one that is not the default. You can figure out the other form by either removing no- or adding it. -fstack-reuse=reuse-level This option controls stack space reuse for user declared local/auto variables and compiler generated temporaries. reuse_level can be all, named_vars, or none. all enables stack reuse for all local variables and temporaries, named_vars enables the reuse only for user defined lo- cal variables with names, and none disables stack reuse completely. The default value is all. The option is needed when the program extends the lifetime of a scoped local variable or a compiler generated temporary beyond the end point defined by the language. When a lifetime of a variable ends, and if the variable lives in memory, the optimizing com- piler has the freedom to reuse its stack space with other temporaries or scoped local variables whose live range does not overlap with it. Legacy code extending local lifetime is likely to break with the stack reuse optimization. For example, int *p; { int local1; p = &local1; local1 = 10; .... } { int local2; local2 = 20; ... } if (*p == 10) // out of scope use of local1 { } Another example: struct A { A(int k) : i(k), j(k) { } int i; int j; }; A *ap; void foo(const A& ar) { ap = &ar; } void bar() { foo(A(10)); // temp object's lifetime ends when foo returns { A a(20); .... } ap->i+= 10; // ap references out of scope temp whose space // is reused with a. What is the value of ap->i? } The lifetime of a compiler generated temporary is well defined by the C++ standard. When a lifetime of a temporary ends, and if the temporary lives in memory, the optimizing compiler has the freedom to reuse its stack space with other temporaries or scoped local variables whose live range does not overlap with it. However some of the legacy code relies on the behavior of older compilers in which temporaries' stack space is not reused, the aggressive stack reuse can lead to runtime errors. This option is used to control the temporary stack reuse optimization. -ftrapv This option generates traps for signed overflow on addition, subtrac- tion, multiplication operations. The options -ftrapv and -fwrapv over- ride each other, so using -ftrapv -fwrapv on the command-line results in -fwrapv being effective. Note that only active options override, so using -ftrapv -fwrapv -fno-wrapv on the command-line results in -ftrapv being effective. -fwrapv This option instructs the compiler to assume that signed arithmetic overflow of addition, subtraction and multiplication wraps around using twos-complement representation. This flag enables some optimizations and disables others. The options -ftrapv and -fwrapv override each other, so using -ftrapv -fwrapv on the command-line results in -fwrapv being effective. Note that only active options override, so using -ftrapv -fwrapv -fno-wrapv on the command-line results in -ftrapv being effective. -fwrapv-pointer This option instructs the compiler to assume that pointer arithmetic overflow on addition and subtraction wraps around using twos-complement representation. This flag disables some optimizations which assume pointer overflow is invalid. -fstrict-overflow This option implies -fno-wrapv -fno-wrapv-pointer and when negated im- plies -fwrapv -fwrapv-pointer. -fexceptions Enable exception handling. Generates extra code needed to propagate exceptions. For some targets, this implies GCC generates 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, GCC enables it by default for languages like C++ that nor- mally require exception handling, and disables 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. -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 trapping instructions to throw exceptions, i.e. memory references or floating-point instruc- tions. It does not allow exceptions to be thrown from arbitrary signal handlers such as "SIGALRM". This enables -fexceptions. -fdelete-dead-exceptions Consider that instructions that may throw exceptions but don't other- wise contribute to the execution of the program can be optimized away. This does not affect calls to functions except those with the "pure" or "const" attributes. This option is enabled by default for the Ada and C++ compilers, as permitted by the language specifications. Optimiza- tion passes that cause dead exceptions to be removed are enabled inde- pendently at different optimization levels. -funwind-tables Similar to -fexceptions, except that it just generates any needed sta- tic data, but does not affect the generated code in any other way. You normally do not need to enable this option; instead, a language proces- sor that needs this handling enables it on your behalf. -fasynchronous-unwind-tables Generate unwind table in DWARF 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). -fno-gnu-unique On systems with recent GNU assembler and C library, the C++ compiler uses the "STB_GNU_UNIQUE" binding to make sure that definitions of tem- plate static data members and static local variables in inline func- tions are unique even in the presence of "RTLD_LOCAL"; this is neces- sary to avoid problems with a library used by two different "RTLD_LO- CAL" plugins depending on a definition in one of them and therefore disagreeing with the other one about the binding of the symbol. But this causes "dlclose" to be ignored for affected DSOs; if your program relies on reinitialization of a DSO via "dlclose" and "dlopen", you can use -fno-gnu-unique. -fpcc-struct-return Return "short" "struct" and "union" 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). The precise convention for returning structures in memory depends on the target configuration macros. Short structures and unions are those whose size and alignment match that of some integer type. Warning: code compiled with the -fpcc-struct-return switch is not bi- nary compatible with code compiled with the -freg-struct-return switch. Use it to conform to a non-default application binary interface. -freg-struct-return Return "struct" and "union" values in registers when possible. This is more efficient for small structures than -fpcc-struct-return. If you specify neither -fpcc-struct-return nor -freg-struct-return, GCC defaults to whichever convention is standard for the target. If there is no standard convention, GCC defaults to -fpcc-struct-return, except on targets where GCC is the principal compiler. In those cases, we can choose the standard, and we chose the more efficient register return alternative. Warning: code compiled with the -freg-struct-return switch is not bi- nary compatible with code compiled with the -fpcc-struct-return switch. Use it to conform to a non-default application binary interface. -fshort-enums Allocate to an "enum" type only as many bytes as it needs for the de- clared range of possible values. Specifically, the "enum" type is equivalent to the smallest integer type that has enough room. This op- tion has no effect for an enumeration type with a fixed underlying type. Warning: the -fshort-enums switch causes GCC 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. -fshort-wchar Override the underlying type for "wchar_t" to be "short unsigned int" instead of the default for the target. This option is useful for building programs to run under WINE. Warning: the -fshort-wchar switch causes GCC 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. -fcommon In C code, this option controls the placement of global variables de- fined without an initializer, known as tentative definitions in the C standard. Tentative definitions are distinct from declarations of a variable with the "extern" keyword, which do not allocate storage. The default is -fno-common, which specifies that the compiler places uninitialized global variables in the BSS section of the object file. This inhibits the merging of tentative definitions by the linker so you get a multiple-definition error if the same variable is accidentally defined in more than one compilation unit. The -fcommon places uninitialized global variables in a common block. This allows the linker to resolve all tentative definitions of the same variable in different compilation units to the same object, or to a non-tentative definition. This behavior is inconsistent with C++, and on many targets implies a speed and code size penalty on global vari- able references. It is mainly useful to enable legacy code to link without errors. -fno-ident -Qy -Qn -fno-ident suppresses emission of ".ident" assembler directives and causes the "#ident" preprocessor directive to be ignored. -Qy and -Qn are obsolete synonyms for -fident and -fno-ident, respectively. -finhibit-size-directive Don't output a ".size" 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 crtstuff.c; you should not need to use it for any- thing else. -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 debug- ging the compiler itself). -fno-verbose-asm, the default, causes the extra information to be omit- ted and is useful when comparing two assembler files. The added comments include: * information on the compiler version and command-line options, * the source code lines associated with the assembly instructions, in the form FILENAME:LINENUMBER:CONTENT OF LINE, * hints on which high-level expressions correspond to the various as- sembly instruction operands. For example, given this C source file: int test (int n) { int i; int total = 0; for (i = 0; i < n; i++) total += i * i; return total; } compiling to (x86_64) assembly via -S and emitting the result direct to stdout via -o - gcc -S test.c -fverbose-asm -Os -o - gives output similar to this: .file "test.c" # GNU C11 (GCC) version 7.0.0 20160809 (experimental) (x86_64-pc-linux-gnu) [...snip...] # options passed: [...snip...] .text .globl test .type test, @function test: .LFB0: .cfi_startproc # test.c:4: int total = 0; xorl %eax, %eax # <retval> # test.c:6: for (i = 0; i < n; i++) xorl %edx, %edx # i .L2: # test.c:6: for (i = 0; i < n; i++) cmpl %edi, %edx # n, i jge .L5 #, # test.c:7: total += i * i; movl %edx, %ecx # i, tmp92 imull %edx, %ecx # i, tmp92 # test.c:6: for (i = 0; i < n; i++) incl %edx # i # test.c:7: total += i * i; addl %ecx, %eax # tmp92, <retval> jmp .L2 # .L5: # test.c:10: } ret .cfi_endproc .LFE0: .size test, .-test .ident "GCC: (GNU) 7.0.0 20160809 (experimental)" .section .note.GNU-stack,"",@progbits The comments are intended for humans rather than machines and hence the precise format of the comments is subject to change. -frecord-gcc-switches This switch causes the command line used to invoke the compiler to be recorded into the object file that is being created. This switch is only implemented on some targets and the exact format of the recording is target and binary file format dependent, but it usually takes the form of a section containing ASCII text. This switch is related to the -fverbose-asm switch, but that switch only records information in the assembler output file as comments, so it never reaches the object file. See also -grecord-gcc-switches for another way of storing compiler op- tions into the object file. -fpic Generate position-independent code (PIC) suitable for use in a shared library, if supported for the target machine. Such code accesses all constant addresses through a global offset table (GOT). The dynamic loader resolves the GOT entries when the program starts (the dynamic loader is not part of GCC; it is part of the operating system). If the GOT size for the linked executable exceeds a machine-specific maximum size, you get an error message from the linker indicating that -fpic does not work; in that case, recompile with -fPIC instead. (These max- imums are 8k on the SPARC, 28k on AArch64 and 32k on the m68k and RS/6000. The x86 has no such limit.) Position-independent code requires special support, and therefore works only on certain machines. For the x86, GCC supports PIC for System V but not for the Sun 386i. Code generated for the IBM RS/6000 is always position-independent. When this flag is set, the macros "__pic__" and "__PIC__" are defined to 1. -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 AArch64, m68k, PowerPC and SPARC. Position-independent code requires special support, and therefore works only on certain machines. When this flag is set, the macros "__pic__" and "__PIC__" are defined to 2. -fpie -fPIE These options are similar to -fpic and -fPIC, but the generated posi- tion-independent code can be only linked into executables. Usually these options are used to compile code that will be linked using the -pie GCC option. -fpie and -fPIE both define the macros "__pie__" and "__PIE__". The macros have the value 1 for -fpie and 2 for -fPIE. -fno-plt Do not use the PLT for external function calls in position-independent code. Instead, load the callee address at call sites from the GOT and branch to it. This leads to more efficient code by eliminating PLT stubs and exposing GOT loads to optimizations. On architectures such as 32-bit x86 where PLT stubs expect the GOT pointer in a specific reg- ister, this gives more register allocation freedom to the compiler. Lazy binding requires use of the PLT; with -fno-plt all external sym- bols are resolved at load time. Alternatively, the function attribute "noplt" can be used to avoid calls through the PLT for specific external functions. In position-dependent code, a few targets also convert calls to func- tions that are marked to not use the PLT to use the GOT instead. -fno-jump-tables Do not use jump tables for switch statements even where it would be more efficient than other code generation strategies. This option is of use in conjunction with -fpic or -fPIC for building code that forms part of a dynamic linker and cannot reference the address of a jump ta- ble. On some targets, jump tables do not require a GOT and this option is not needed. -fno-bit-tests Do not use bit tests for switch statements even where it would be more efficient than other code generation strategies. -ffixed-reg Treat the register named reg 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). reg must be the name of a register. The register names accepted are machine-specific and are defined in the "REGISTER_NAMES" macro in the machine description macro file. This flag does not have a negative form, because it specifies a three-way choice. -fcall-used-reg Treat the register named reg 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 do not save and restore the register reg. It is an error to use this flag with the frame pointer or stack pointer. Use of this flag for other registers that have fixed perva- sive roles in the machine's execution model produces disastrous re- sults. This flag does not have a negative form, because it specifies a three-way choice. -fcall-saved-reg Treat the register named reg as an allocable register saved by func- tions. It may be allocated even for temporaries or variables that live across a call. Functions compiled this way save and restore the regis- ter reg if they use it. It is an error to use this flag with the frame pointer or stack pointer. Use of this flag for other registers that have fixed perva- sive roles in the machine's execution model produces disastrous re- sults. A different sort of disaster results from the use of this flag for a register in which function values may be returned. This flag does not have a negative form, because it specifies a three-way choice. -fpack-struct[=n] Without a value specified, pack all structure members together without holes. When a value is specified (which must be a small power of two), pack structure members according to this value, representing the maxi- mum alignment (that is, objects with default alignment requirements larger than this are output potentially unaligned at the next fitting location. Warning: the -fpack-struct switch causes GCC to generate code that is not binary compatible with code generated without that switch. Addi- tionally, it makes the code suboptimal. Use it to conform to a non-de- fault application binary interface. -fleading-underscore This option and its counterpart, -fno-leading-underscore, forcibly change the way C symbols are represented in the object file. One use is to help link with legacy assembly code. Warning: the -fleading-underscore switch causes GCC 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. -ftls-model=model Alter the thread-local storage model to be used. The model argument should be one of global-dynamic, local-dynamic, initial-exec or lo- cal-exec. Note that the choice is subject to optimization: the com- piler may use a more efficient model for symbols not visible outside of the translation unit, or if -fpic is not given on the command line. The default without -fpic is initial-exec; with -fpic the default is global-dynamic. -ftrampolines For targets that normally need trampolines for nested functions, always generate them instead of using descriptors. Otherwise, for targets that do not need them, like for example HP-PA or IA-64, do nothing. A trampoline is a small piece of code that is created at run time on the stack when the address of a nested function is taken, and is used to call the nested function indirectly. Therefore, it requires the stack to be made executable in order for the program to work properly. -fno-trampolines is enabled by default on a language by language basis to let the compiler avoid generating them, if it computes that this is safe, and replace them with descriptors. Descriptors are made up of data only, but the generated code must be prepared to deal with them. As of this writing, -fno-trampolines is enabled by default only for Ada. Moreover, code compiled with -ftrampolines and code compiled with -fno-trampolines are not binary compatible if nested functions are present. This option must therefore be used on a program-wide basis and be manipulated with extreme care. For languages other than Ada, the "-ftrampolines" and "-fno-trampo- lines" options currently have no effect, and trampolines are always generated on platforms that need them for nested functions. -ftrampoline-impl=[stack|heap] By default, trampolines are generated on stack. However, certain plat- forms (such as the Apple M1) do not permit an executable stack. Com- piling with -ftrampoline-impl=heap generate calls to "__gcc_nested_func_ptr_created" and "__gcc_nested_func_ptr_deleted" in order to allocate and deallocate trampoline space on the executable heap. These functions are implemented in libgcc, and will only be pro- vided on specific targets: x86_64 Darwin, x86_64 and aarch64 Linux. PLEASE NOTE: Heap trampolines are not guaranteed to be correctly deal- located if you "setjmp", instantiate nested functions, and then "longjmp" back to a state prior to having allocated those nested func- tions. -fvisibility=[default|internal|hidden|protected] Set the default ELF image symbol visibility to the specified op- tion---all symbols are marked with this unless overridden within the code. Using this feature can very substantially improve linking and load times of shared object libraries, produce more optimized code, provide near-perfect API export and prevent symbol clashes. It is strongly recommended that you use this in any shared objects you dis- tribute. Despite the nomenclature, default always means public; i.e., available to be linked against from outside the shared object. protected and in- ternal are pretty useless in real-world usage so the only other com- monly used option is hidden. The default if -fvisibility isn't speci- fied is default, i.e., make every symbol public. A good explanation of the benefits offered by ensuring ELF symbols have the correct visibility is given by "How To Write Shared Libraries" by Ulrich Drepper (which can be found at <https://www.akkadia.org/drep- per/>)---however a superior solution made possible by this option to marking things hidden when the default is public is to make the default hidden and mark things public. This is the norm with DLLs on Windows and with -fvisibility=hidden and "__attribute__ ((visibility("de- fault")))" instead of "__declspec(dllexport)" you get almost identical semantics with identical syntax. This is a great boon to those working with cross-platform projects. For those adding visibility support to existing code, you may find "#pragma GCC visibility" of use. This works by you enclosing the dec- larations you wish to set visibility for with (for example) "#pragma GCC visibility push(hidden)" and "#pragma GCC visibility pop". Bear in mind that symbol visibility should be viewed as part of the API inter- face contract and thus all new code should always specify visibility when it is not the default; i.e., declarations only for use within the local DSO should always be marked explicitly as hidden as so to avoid PLT indirection overheads---making this abundantly clear also aids readability and self-documentation of the code. Note that due to ISO C++ specification requirements, "operator new" and "operator delete" must always be of default visibility. Be aware that headers from outside your project, in particular system headers and headers from any other library you use, may not be expect- ing to be compiled with visibility other than the default. You may need to explicitly say "#pragma GCC visibility push(default)" before including any such headers. "extern" declarations are not affected by -fvisibility, so a lot of code can be recompiled with -fvisibility=hidden with no modifications. However, this means that calls to "extern" functions with no explicit visibility use the PLT, so it is more effective to use "__attribute ((visibility))" and/or "#pragma GCC visibility" to tell the compiler which "extern" declarations should be treated as hidden. Note that -fvisibility does affect C++ vague linkage entities. This means that, for instance, an exception class that is be thrown between DSOs must be explicitly marked with default visibility so that the type_info nodes are unified between the DSOs. An overview of these techniques, their benefits and how to use them is at <https://gcc.gnu.org/wiki/Visibility>. -fstrict-volatile-bitfields This option should be used if accesses to volatile bit-fields (or other structure fields, although the compiler usually honors those types any- way) should use a single access of the width of the field's type, aligned to a natural alignment if possible. For example, targets with memory-mapped peripheral registers might require all such accesses to be 16 bits wide; with this flag you can declare all peripheral bit-fields as "unsigned short" (assuming short is 16 bits on these tar- gets) to force GCC to use 16-bit accesses instead of, perhaps, a more efficient 32-bit access. If this option is disabled, the compiler uses the most efficient in- struction. In the previous example, that might be a 32-bit load in- struction, even though that accesses bytes that do not contain any por- tion of the bit-field, or memory-mapped registers unrelated to the one being updated. In some cases, such as when the "packed" attribute is applied to a structure field, it may not be possible to access the field with a sin- gle read or write that is correctly aligned for the target machine. In this case GCC falls back to generating multiple accesses rather than code that will fault or truncate the result at run time. Note: Due to restrictions of the C/C++11 memory model, write accesses are not allowed to touch non bit-field members. It is therefore recom- mended to define all bits of the field's type as bit-field members. The default value of this option is determined by the application bi- nary interface for the target processor. -fsync-libcalls This option controls whether any out-of-line instance of the "__sync" family of functions may be used to implement the C++11 "__atomic" fam- ily of functions. The default value of this option is enabled, thus the only useful form of the option is -fno-sync-libcalls. This option is used in the imple- mentation of the libatomic runtime library. -fzero-init-padding-bits=value Guarantee zero initialization of padding bits in automatic variable initializers. Certain languages guarantee zero initialization of padding bits in certain cases, e.g. C23 when using empty initializers ("{}"), or C++ when using zero-initialization or C guarantees that fields not specified in an initializer have their padding bits zero initialized. This option allows to change when padding bits in ini- tializers are guaranteed to be zero initialized. The default is "-fzero-init-padding-bits=standard", which makes no further guarantees than the corresponding standard. E.g. struct A { char a; unsigned long long b; char c; }; union B { char a; unsigned long long b; }; struct A a = {}; // C23 guarantees padding bits are zero. struct A b = { 1, 2, 3 }; // No guarantees. union B c = {}; // C23 guarantees padding bits are zero. union B d = { 1 }; // No guarantees. "-fzero-init-padding-bits=unions" guarantees zero initialization of padding bits in unions on top of what the standards guarantee, if the initializer of an union is empty (then all bits of the union are zero initialized) or if the initialized member of the union is smaller than the size of the union (in that case guarantees padding bits outside of the initialized member to be zero initialized). This was the GCC be- havior before GCC 15 and in the above example guarantees zero initial- ization of last "sizeof (unsigned long long) - 1" bytes in the union. "-fzero-init-padding-bits=all" guarantees additionally zero initializa- tion of padding bits of other aggregates, so the padding in between "b.a" and "b.b" (if any) and tail padding in the structure (if any). GCC Developer Options This section describes command-line options that are primarily of interest to GCC developers, including options to support compiler testing and inves- tigation of compiler bugs and compile-time performance problems. This in- cludes options that produce debug dumps at various points in the compila- tion; that print statistics such as memory use and execution time; and that print information about GCC's configuration, such as where it searches for libraries. You should rarely need to use any of these options for ordinary compilation and linking tasks. Many developer options that cause GCC to dump output to a file take an op- tional =filename suffix. You can specify stdout or - to dump to standard output, and stderr for standard error. If =filename is omitted, a default dump file name is constructed by con- catenating the base dump file name, a pass number, phase letter, and pass name. The base dump file name is the name of output file produced by the compiler if explicitly specified and not an executable; otherwise it is the source file name. The pass number is determined by the order passes are registered with the compiler's pass manager. This is generally the same as the order of execution, but passes registered by plugins, target-specific passes, or passes that are otherwise registered late are numbered higher than the pass named final, even if they are executed earlier. The phase letter is one of i (inter-procedural analysis), l (language-specific), r (RTL), or t (tree). The files are created in the directory of the output file. -fcallgraph-info -fcallgraph-info=MARKERS Makes the compiler output callgraph information for the program, on a per-object-file basis. The information is generated in the common VCG format. It can be decorated with additional, per-node and/or per-edge information, if a list of comma-separated markers is additionally spec- ified. When the "su" marker is specified, the callgraph is decorated with stack usage information; it is equivalent to -fstack-usage. When the "da" marker is specified, the callgraph is decorated with informa- tion about dynamically allocated objects. When compiling with -flto, no callgraph information is output along with the object file. At LTO link time, -fcallgraph-info may generate multiple callgraph information files next to intermediate LTO output files. -dletters --dump=letters --dump letters -fdump-rtl-pass -fdump-rtl-pass-options -fdump-rtl-pass-options=filename Says to make debugging dumps during compilation at times specified by letters when using -d or by pass when using -fdump-rtl. This is used for debugging the RTL-based passes of the compiler. Some -dletters switches have different meaning when -E is used for pre- processing. The -options form allows greater control over the details of the dump. See -fdump-tree. Here are actual instances of command-line options following these pat- terns and their meanings: -fdump-rtl-alignments Dump after branch alignments have been computed. -fdump-rtl-asmcons Dump after fixing rtl statements that have unsatisfied in/out con- straints. -fdump-rtl-auto_inc_dec Dump after auto-inc-dec discovery. This pass is only run on archi- tectures that have auto inc or auto dec instructions. -fdump-rtl-barriers Dump after cleaning up the barrier instructions. -fdump-rtl-bbpart Dump after partitioning hot and cold basic blocks. -fdump-rtl-bbro Dump after block reordering. -fdump-rtl-btl1 -fdump-rtl-btl2 -fdump-rtl-btl1 and -fdump-rtl-btl2 enable dumping after the two branch target load optimization passes. -fdump-rtl-bypass Dump after jump bypassing and control flow optimizations. -fdump-rtl-combine Dump after the RTL instruction combination pass. -fdump-rtl-compgotos Dump after duplicating the computed gotos. -fdump-rtl-ce1 -fdump-rtl-ce2 -fdump-rtl-ce3 -fdump-rtl-ce1, -fdump-rtl-ce2, and -fdump-rtl-ce3 enable dumping after the three if conversion passes. -fdump-rtl-cprop_hardreg Dump after hard register copy propagation. -fdump-rtl-csa Dump after combining stack adjustments. -fdump-rtl-cse1 -fdump-rtl-cse2 -fdump-rtl-cse1 and -fdump-rtl-cse2 enable dumping after the two common subexpression elimination passes. -fdump-rtl-dce Dump after the standalone dead code elimination passes. -fdump-rtl-dbr Dump after delayed branch scheduling. -fdump-rtl-dce1 -fdump-rtl-dce2 -fdump-rtl-dce1 and -fdump-rtl-dce2 enable dumping after the two dead store elimination passes. -fdump-rtl-eh Dump after finalization of EH handling code. -fdump-rtl-eh_ranges Dump after conversion of EH handling range regions. -fdump-rtl-expand Dump after RTL generation. -fdump-rtl-fwprop1 -fdump-rtl-fwprop2 -fdump-rtl-fwprop1 and -fdump-rtl-fwprop2 enable dumping after the two forward propagation passes. -fdump-rtl-gcse1 -fdump-rtl-gcse2 -fdump-rtl-gcse1 and -fdump-rtl-gcse2 enable dumping after global common subexpression elimination. -fdump-rtl-init-regs Dump after the initialization of the registers. -fdump-rtl-initvals Dump after the computation of the initial value sets. -fdump-rtl-into_cfglayout Dump after converting to cfglayout mode. -fdump-rtl-ira Dump after iterated register allocation. -fdump-rtl-jump Dump after the second jump optimization. -fdump-rtl-loop2 -fdump-rtl-loop2 enables dumping after the rtl loop optimization passes. -fdump-rtl-mach Dump after performing the machine dependent reorganization pass, if that pass exists. -fdump-rtl-mode_sw Dump after removing redundant mode switches. -fdump-rtl-rnreg Dump after register renumbering. -fdump-rtl-outof_cfglayout Dump after converting from cfglayout mode. -fdump-rtl-peephole2 Dump after the peephole pass. -fdump-rtl-postreload Dump after post-reload optimizations. -fdump-rtl-pro_and_epilogue Dump after generating the function prologues and epilogues. -fdump-rtl-sched1 -fdump-rtl-sched2 -fdump-rtl-sched1 and -fdump-rtl-sched2 enable dumping after the basic block scheduling passes. -fdump-rtl-ree Dump after sign/zero extension elimination. -fdump-rtl-seqabstr Dump after common sequence discovery. -fdump-rtl-shorten Dump after shortening branches. -fdump-rtl-split1 -fdump-rtl-split2 -fdump-rtl-split3 -fdump-rtl-split4 -fdump-rtl-split5 These options enable dumping after five rounds of instruction splitting. -fdump-rtl-sms Dump after modulo scheduling. This pass is only run on some archi- tectures. -fdump-rtl-stack Dump after conversion from GCC's "flat register file" registers to the x87's stack-like registers. This pass is only run on x86 vari- ants. -fdump-rtl-subreg1 -fdump-rtl-subreg2 -fdump-rtl-subreg1 and -fdump-rtl-subreg2 enable dumping after the two subreg expansion passes. -fdump-rtl-vartrack Dump after variable tracking. -fdump-rtl-vregs Dump after converting virtual registers to hard registers. -fdump-rtl-web Dump after live range splitting. -fdump-rtl-regclass -fdump-rtl-subregs_of_mode_init -fdump-rtl-subregs_of_mode_finish -fdump-rtl-dfinit -fdump-rtl-dfinish These dumps are defined but always produce empty files. -da --dump=a -fdump-rtl-all Produce all the dumps listed above. -dA --dump=A Annotate the assembler output with miscellaneous debugging informa- tion. -dD --dump=D Dump all macro definitions, at the end of preprocessing, in addi- tion to normal output. -dH --dump=H Produce a core dump whenever an error occurs. -dp --dump=p Annotate the assembler output with a comment indicating which pat- tern and alternative is used. The length and cost of each instruc- tion are also printed. -dP --dump=P Dump the RTL in the assembler output as a comment before each in- struction. Also turns on -dp annotation. -dx --dump=x Just generate RTL for a function instead of compiling it. Usually used with -fdump-rtl-expand. -fdump-debug Dump debugging information generated during the debug generation phase. -fdump-earlydebug Dump debugging information generated during the early debug generation phase. -fdump-noaddr When doing debugging dumps, suppress address output. This makes it more feasible to use diff on debugging dumps for compiler invocations with different compiler binaries and/or different text / bss / data / heap / stack / dso start locations. -freport-bug Collect and dump debug information into a temporary file if an internal compiler error (ICE) occurs. -fdump-unnumbered When doing debugging dumps, suppress instruction numbers and address output. This makes it more feasible to use diff on debugging dumps for compiler invocations with different options, in particular with and without -g. -fdump-unnumbered-links When doing debugging dumps (see -d option above), suppress instruction numbers for the links to the previous and next instructions in a se- quence. -fdump-internal-locations Dump detailed information about GCC's internal representation of source code locations. -fdump-ipa-switch -fdump-ipa-switch-options Control the dumping at various stages of inter-procedural analysis lan- guage tree to a file. The file name is generated by appending a switch specific suffix to the source file name, and the file is created in the same directory as the output file. The following dumps are possible: all Enables all inter-procedural analysis dumps. cgraph Dumps information about call-graph optimization, unused function removal, and inlining decisions. inline Dump after function inlining. strubm Dump after selecting "strub" modes, and recording the selections as function attributes. strub Dump "strub" transformations: interface changes, function wrapping, and insertion of builtin calls for stack scrubbing and watermark- ing. Additionally, the options -optimized, -missed, -note, and -all can be provided, with the same meaning as for -fopt-info, defaulting to -opti- mized. For example, -fdump-ipa-inline-optimized-missed will emit information on callsites that were inlined, along with callsites that were not in- lined. By default, the dump will contain messages about successful optimiza- tions (equivalent to -optimized) together with low-level details about the analysis. -fdump-ipa-clones Create a dump file containing information about creation of call graph node clones and removals of call graph nodes during inter-procedural optimizations and transformations. Its main intended use is that tools that create live-patches can determine the set of functions that need to be live-patched to completely replace a particular function (see -flive-patching). The file name is generated by appending suffix "ipa-clones" to the source file name, and the file is created in the same directory as the output file. Each entry in the file is on a sep- arate line containing semicolon separated fields. In the case of call graph clone creation, the individual fields are: 1. String "Callgraph clone". 2. Name of the function being cloned as it is presented to the assem- bler. 3. A number that uniquely represents the function being cloned in the call graph. Note that the number is unique only within a compila- tion unit or within whole-program analysis but is likely to be dif- ferent in the two phases. 4. The file name of the source file where the function is defined. 5. The line on which the function definition is located. 6. The column where the function definition is located. 7. Name of the new function clone as it is presented to the assembler. 8. A number that uniquely represents the new function clone in the call graph. Note that the number is unique only within a compila- tion unit or within whole-program analysis but is likely to be dif- ferent in the two phases. 9. The file name of the source file where the source code location of the new clone points to. 10. The line to which the source code location of the new clone points to. 11. The column to which the source code location of the new clone points to. 12. A string that determines the reason for cloning. In the case of call graph clone removal, the individual fields are: 1. String "Callgraph removal". 2. Name of the function being removed as it would be presented to the assembler. 3. A number that uniquely represents the function being cloned in the call graph. Note that the number is unique only within a compila- tion unit or within whole-program analysis but is likely to be dif- ferent in the two phases. 4. The file name of the source file where the function is defined. 5. The line on which the function definition is located. 6. The column where the function definition is located. -fdump-lang Dump language-specific information. The file name is made by appending .lang to the source file name. -fdump-lang-all -fdump-lang-switch -fdump-lang-switch-options -fdump-lang-switch-options=filename Control the dumping of language-specific information. The options and filename portions behave as described in the -fdump-tree option. -fdump-tree-all enables all language-specific dumps; other options vary with the language. For instance, see -fdump-passes Print on stderr the list of optimization passes that are turned on and off by the current command-line options. -fdump-statistics-option Enable and control dumping of pass statistics in a separate file. The file name is generated by appending a suffix ending in .statistics to the source file name, and the file is created in the same directory as the output file. If the -option form is used, -stats causes counters to be summed over the whole compilation unit while -details dumps every event as the passes generate them. The default with no option is to sum counters for each function compiled. -fdump-tree-all -fdump-tree-switch -fdump-tree-switch-options -fdump-tree-switch-options=filename Control the dumping at various stages of processing the intermediate language tree to a file. If the -options form is used, options is a list of - separated options which control the details of the dump. Not all options are applicable to all dumps; those that are not meaningful are ignored. The following options are available address Print the address of each node. Usually this is not meaningful as it changes according to the environment and source file. Its pri- mary use is for tying up a dump file with a debug environment. asmname If "DECL_ASSEMBLER_NAME" has been set for a given decl, use that in the dump instead of "DECL_NAME". Its primary use is ease of use working backward from mangled names in the assembly file. slimWhen dumping front-end intermediate representations, inhibit dump- ing of members of a scope or body of a function merely because that scope has been reached. Only dump such items when they are di- rectly reachable by some other path. When dumping pretty-printed trees, this option inhibits dumping the bodies of control structures. When dumping RTL, print the RTL in slim (condensed) form instead of the default LISP-like representation. raw Print a raw representation of the tree. By default, trees are pretty-printed into a C-like representation. details Enable more detailed dumps (not honored by every dump option). Also include information from the optimization passes. stats Enable dumping various statistics about the pass (not honored by every dump option). blocks Enable showing basic block boundaries (disabled in raw dumps). graph For each of the other indicated dump files (-fdump-rtl-pass), dump a representation of the control flow graph suitable for viewing with GraphViz to file.passid.pass.dot. Each function in the file is pretty-printed as a subgraph, so that GraphViz can render them all in a single plot. RTL is always dumped in slim form. vopsEnable showing virtual operands for every statement. lineno Enable showing line numbers for statements. uid Enable showing the unique ID ("DECL_UID") for each variable. verbose Enable showing the tree dump for each statement. eh Enable showing the EH region number holding each statement. scevEnable showing scalar evolution analysis details. optimized Enable showing optimization information (only available in certain passes). missed Enable showing missed optimization information (only available in certain passes). noteEnable other detailed optimization information (only available in certain passes). folding Enable dumping information about match-and-simplify (match.pd) pat- terns, when they are applied. all Turn on all options, except raw, slim, verbose and lineno. optall Turn on all optimization options, i.e., optimized, missed, and note. To determine what tree dumps are available or find the dump for a pass of interest follow the steps below. 1. Invoke GCC with -fdump-passes and in the stderr output look for a code that corresponds to the pass you are interested in. For exam- ple, the codes "tree-evrp", "tree-vrp1", and "tree-vrp2" correspond to the three Value Range Propagation passes. The number at the end distinguishes distinct invocations of the same pass. 2. To enable the creation of the dump file, append the pass code to the -fdump- option prefix and invoke GCC with it. For example, to enable the dump from the Early Value Range Propagation pass, invoke GCC with the -fdump-tree-evrp option. Optionally, you may specify the name of the dump file. If you don't specify one, GCC creates as described below. 3. Find the pass dump in a file whose name is composed of three compo- nents separated by a period: the name of the source file GCC was invoked to compile, a numeric suffix indicating the pass number followed by the letter t for tree passes (and the letter r for RTL passes), and finally the pass code. For example, the Early VRP pass dump might be in a file named myfile.c.038t.evrp in the cur- rent working directory. Note that the numeric codes are not stable and may change from one version of GCC to another. -fopt-info -fopt-info-options -fopt-info-options=filename Controls optimization dumps from various optimization passes. If the -options form is used, options is a list of - separated option keywords to select the dump details and optimizations. The options can be divided into three groups: 1. options describing what kinds of messages should be emitted, 2. options describing the verbosity of the dump, and 3. options describing which optimizations should be included. The options from each group can be freely mixed as they are non-over- lapping. However, in case of any conflicts, the later options override the earlier options on the command line. The following options control which kinds of messages should be emit- ted: optimized Print information when an optimization is successfully applied. It is up to a pass to decide which information is relevant. For exam- ple, the vectorizer passes print the source location of loops which are successfully vectorized. missed Print information about missed optimizations. Individual passes control which information to include in the output. notePrint verbose information about optimizations, such as certain transformations, more detailed messages about decisions etc. all Print detailed optimization information. This includes optimized, missed, and note. The following option controls the dump verbosity: internals By default, only "high-level" messages are emitted. This option en- ables additional, more detailed, messages, which are likely to only be of interest to GCC developers. One or more of the following option keywords can be used to describe a group of optimizations: ipa Enable dumps from all interprocedural optimizations. loopEnable dumps from all loop optimizations. inline Enable dumps from all inlining optimizations. omp Enable dumps from all OMP (Offloading and Multi Processing) opti- mizations. vec Enable dumps from all vectorization optimizations. optall Enable dumps from all optimizations. This is a superset of the op- timization groups listed above. If options is omitted, it defaults to optimized-optall, which means to dump messages about successful optimizations from all the passes, omit- ting messages that are treated as "internals". If the filename is provided, then the dumps from all the applicable op- timizations are concatenated into the filename. Otherwise the dump is output onto stderr. Though multiple -fopt-info options are accepted, only one of them can include a filename. If other filenames are pro- vided then all but the first such option are ignored. Note that the output filename is overwritten in case of multiple trans- lation units. If a combined output from multiple translation units is desired, stderr should be used instead. In the following example, the optimization info is output to stderr: gcc -O3 -fopt-info This example: gcc -O3 -fopt-info-missed=missed.all outputs missed optimization report from all the passes into missed.all, and this one: gcc -O2 -ftree-vectorize -fopt-info-vec-missed prints information about missed optimization opportunities from vector- ization passes on stderr. Note that -fopt-info-vec-missed is equiva- lent to -fopt-info-missed-vec. The order of the optimization group names and message types listed after -fopt-info does not matter. As another example, gcc -O3 -fopt-info-inline-optimized-missed=inline.txt outputs information about missed optimizations as well as optimized lo- cations from all the inlining passes into inline.txt. Finally, consider: gcc -fopt-info-vec-missed=vec.miss -fopt-info-loop-optimized=loop.opt Here the two output filenames vec.miss and loop.opt are in conflict since only one output file is allowed. In this case, only the first op- tion takes effect and the subsequent options are ignored. Thus only vec.miss is produced which contains dumps from the vectorizer about missed opportunities. -fsave-optimization-record Write a SRCFILE.opt-record.json.gz file detailing what optimizations were performed, for those optimizations that support -fopt-info. This option is experimental and the format of the data within the com- pressed JSON file is subject to change. It is roughly equivalent to a machine-readable version of -fopt-info-all, as a collection of messages with source file, line num- ber and column number, with the following additional data for each mes- sage: * the execution count of the code being optimized, along with meta- data about whether this was from actual profile data, or just an estimate, allowing consumers to prioritize messages by code hot- ness, * the function name of the code being optimized, where applicable, * the "inlining chain" for the code being optimized, so that when a function is inlined into several different places (which might themselves be inlined), the reader can distinguish between the copies, * objects identifying those parts of the message that refer to ex- pressions, statements or symbol-table nodes, which of these cate- gories they are, and, when available, their source code location, * the GCC pass that emitted the message, and * the location in GCC's own code from which the message was emitted Additionally, some messages are logically nested within other messages, reflecting implementation details of the optimization passes. -fsched-verbose=n On targets that use instruction scheduling, this option controls the amount of debugging output the scheduler prints to the dump files. For n greater than zero, -fsched-verbose outputs the same information as -fdump-rtl-sched1 and -fdump-rtl-sched2. For n greater than one, it also output basic block probabilities, detailed ready list information and unit/insn info. For n greater than two, it includes RTL at abort point, control-flow and regions info. And for n over four, -fsched-verbose also includes dependence info. -fenable-kind-pass -fdisable-kind-pass=range-list This is a set of options that are used to explicitly disable/enable op- timization passes. These options are intended for use for debugging GCC. Compiler users should use regular options for enabling/disabling passes instead. -fdisable-ipa-pass Disable IPA pass pass. pass is the pass name. If the same pass is statically invoked in the compiler multiple times, the pass name should be appended with a sequential number starting from 1. -fdisable-rtl-pass -fdisable-rtl-pass=range-list Disable RTL pass pass. pass is the pass name. If the same pass is statically invoked in the compiler multiple times, the pass name should be appended with a sequential number starting from 1. range-list is a comma-separated list of function ranges or assem- bler names. Each range is a number pair separated by a colon. The range is inclusive in both ends. If the range is trivial, the num- ber pair can be simplified as a single number. If the function's call graph node's uid falls within one of the specified ranges, the pass is disabled for that function. The uid is shown in the func- tion header of a dump file, and the pass names can be dumped by us- ing option -fdump-passes. -fdisable-tree-pass -fdisable-tree-pass=range-list Disable tree pass pass. See -fdisable-rtl for the description of option arguments. -fenable-ipa-pass Enable IPA pass pass. pass is the pass name. If the same pass is statically invoked in the compiler multiple times, the pass name should be appended with a sequential number starting from 1. -fenable-rtl-pass -fenable-rtl-pass=range-list Enable RTL pass pass. See -fdisable-rtl for option argument de- scription and examples. -fenable-tree-pass -fenable-tree-pass=range-list Enable tree pass pass. See -fdisable-rtl for the description of option arguments. Here are some examples showing uses of these options. # disable ccp1 for all functions -fdisable-tree-ccp1 # disable complete unroll for function whose cgraph node uid is 1 -fenable-tree-cunroll=1 # disable gcse2 for functions at the following ranges [1,1], # [300,400], and [400,1000] # disable gcse2 for functions foo and foo2 -fdisable-rtl-gcse2=foo,foo2 # disable early inlining -fdisable-tree-einline # disable ipa inlining -fdisable-ipa-inline # enable tree full unroll -fenable-tree-unroll -fchecking -fchecking=n Enable internal consistency checking. The default depends on the com- piler configuration. -fchecking=2 enables further internal consistency checking that might affect code generation. -frandom-seed=string This option provides a seed that GCC uses in place of random numbers in generating certain symbol names that have to be different in every com- piled file. It is also used to place unique stamps in coverage data files and the object files that produce them. You can use the -fran- dom-seed option to produce reproducibly identical object files. The string can either be a number (decimal, octal or hex) or an arbi- trary string (in which case it's converted to a number by computing CRC32). The string should be different for every file you compile. -save-temps --save-temps Store the usual "temporary" intermediate files permanently; name them as auxiliary output files, as specified described under -dumpbase and -dumpdir. When used in combination with the -x command-line option, -save-temps is sensible enough to avoid overwriting an input source file with the same extension as an intermediate file. The corresponding intermediate file may be obtained by renaming the source file before using -save-temps. -save-temps=cwd Equivalent to -save-temps -dumpdir ./. -save-temps=obj Equivalent to -save-temps -dumpdir outdir/, where outdir/ is the direc- tory of the output file specified after the -o option, including any directory separators. If the -o option is not used, the -save-temps=obj switch behaves like -save-temps=cwd. -specs=file --specs=file --specs file Process file after the compiler reads in the standard specs file, in order to override the defaults which the gcc driver program uses when determining what switches to pass to cc1, cc1plus, as, ld, etc. More than one -specs=file can be specified on the command line, and they are processed in order, from left to right. -time[=file] Report the CPU time taken by each subprocess in the compilation se- quence. For C source files, this is the compiler proper and assembler (plus the linker if linking is done). Without the specification of an output file, the output looks like this: # cc1 0.12 0.01 # as 0.00 0.01 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. With the specification of an output file, the output is appended to the named file, and it looks like this: 0.12 0.01 cc1 <options> 0.00 0.01 as <options> The "user time" and the "system time" are moved before the program name, and the options passed to the program are displayed, so that one can later tell what file was being compiled, and with which options. -fdump-final-insns[=file] Dump the final internal representation (RTL) to file. If the optional argument is omitted (or if file is "."), the name of the dump file is determined by appending ".gkd" to the dump base name, see -dumpbase. -fcompare-debug[=opts] If no error occurs during compilation, run the compiler a second time, adding opts and -fcompare-debug-second to the arguments passed to the second compilation. Dump the final internal representation in both compilations, and print an error if they differ. If the equal sign is omitted, the default -gtoggle is used. The environment variable GCC_COMPARE_DEBUG, if defined, non-empty and nonzero, implicitly enables -fcompare-debug. If GCC_COMPARE_DEBUG is defined to a string starting with a dash, then it is used for opts, otherwise the default -gtoggle is used. -fcompare-debug=, with the equal sign but without opts, is equivalent to -fno-compare-debug, which disables the dumping of the final repre- sentation and the second compilation, preventing even GCC_COMPARE_DEBUG from taking effect. To verify full coverage during -fcompare-debug testing, set GCC_COM- PARE_DEBUG to say -fcompare-debug-not-overridden, which GCC rejects as an invalid option in any actual compilation (rather than preprocessing, assembly or linking). To get just a warning, setting GCC_COMPARE_DEBUG to -w%n-fcompare-debug not overridden will do. -fcompare-debug-second This option is implicitly passed to the compiler for the second compi- lation requested by -fcompare-debug, along with options to silence warnings, and omitting other options that would cause the compiler to produce output to files or to standard output as a side effect. Dump files and preserved temporary files are renamed so as to contain the ".gk" additional extension during the second compilation, to avoid overwriting those generated by the first. When this option is passed to the compiler driver, it causes the first compilation to be skipped, which makes it useful for little other than debugging the compiler proper. -gtoggle Turn off generation of debug info, if leaving out this option generates it, or turn it on at level 2 otherwise. The position of this argument in the command line does not matter; it takes effect after all other options are processed, and it does so only once, no matter how many times it is given. This is mainly intended to be used with -fcom- pare-debug. -fvar-tracking-assignments-toggle Toggle -fvar-tracking-assignments, in the same way that -gtoggle tog- gles -g. -Q When used on the command line prior to --help=, -Q acts as a modifier to the help output. Otherwise, this option makes the compiler print out each function name as it is compiled, and print some statistics about each pass when it finishes. -ftime-report Makes the compiler print some statistics to stderr about the time con- sumed by each pass when it finishes. If SARIF output of diagnostics was requested via -fdiagnostics-for- mat=sarif-file or -fdiagnostics-format=sarif-stderr then the -ftime-re- port information is instead emitted in JSON form as part of SARIF out- put. The precise format of this JSON data is subject to change, and the values may not exactly match those emitted to stderr due to being written out at a slightly different place within the compiler. -ftime-report-details Record the time consumed by infrastructure parts separately for each pass. -fira-verbose=n Control the verbosity of the dump file for the integrated register al- locator. The default value is 5. If the value n is greater or equal to 10, the dump output is sent to stderr using the same format as n mi- nus 10. -flto-report Prints a report with internal details on the workings of the link-time optimizer. The contents of this report vary from version to version. It is meant to be useful to GCC developers when processing object files in LTO mode (via -flto). Disabled by default. -flto-report-wpa Like -flto-report, but only print for the WPA phase of link-time opti- mization. -fmem-report Makes the compiler print some statistics about permanent memory alloca- tion when it finishes. -fmem-report-wpa Makes the compiler print some statistics about permanent memory alloca- tion for the WPA phase only. -fpre-ipa-mem-report -fpost-ipa-mem-report Makes the compiler print some statistics about permanent memory alloca- tion before or after interprocedural optimization. -fmultiflags This option enables multilib-aware "TFLAGS" to be used to build target libraries with options different from those the compiler is configured to use by default, through the use of specs set up by compiler inter- nals, by the target, or by builders at configure time. Like "TFLAGS", this allows the target libraries to be built for portable baseline environments, while the compiler defaults to more de- manding ones. That's useful because users can easily override the de- faults the compiler is configured to use to build their own programs, if the defaults are not ideal for their target environment, whereas re- building the runtime libraries is usually not as easy or desirable. Unlike "TFLAGS", the use of specs enables different flags to be se- lected for different multilibs. The way to accomplish that is to build with make TFLAGS=-fmultiflags, after configuring --with-specs=%{fmulti- flags:...}. This option is discarded by the driver once it's done processing driver self spec. It is also useful to check that "TFLAGS" are being used to build all target libraries, by configuring a non-bootstrap compiler --with-specs='%{!fmultiflags:%emissing TFLAGS}' and building the com- piler and target libraries. -fprofile-report Makes the compiler print some statistics about consistency of the (es- timated) profile and effect of individual passes. -fstack-usage Makes the compiler output stack usage information for the program, on a per-function basis. The filename for the dump is made by appending .su to the auxname. auxname is generated from the name of the output file, if explicitly specified and it is not an executable, otherwise it is the basename of the source file. An entry is made up of four fields separated by tabulation characters: * The name of the function preceded by its source location * The mangled name of the function * A number of bytes * One or more qualifiers: "static", "dynamic", "bounded" The qualifier "static" means that the function manipulates the stack statically: a fixed number of bytes are allocated for the frame on function entry and released on function exit; no stack adjustments are otherwise made in the function. The second field is this fixed number of bytes. The qualifier "dynamic" means that the function manipulates the stack dynamically: in addition to the static allocation described above, stack adjustments are made in the body of the function, for example to push/pop arguments around function calls. If the qualifier "bounded" is also present, the amount of these adjustments is bounded at compile time and the second field is an upper bound of the total amount of stack used by the function. If it is not present, the amount of these adjustments is not bounded at compile time and the second field only represents the bounded part. -fstats Emit statistics about front-end processing at the end of the compila- tion. This option is supported only by the C++ front end, and the in- formation is generally only useful to the G++ development team. -fdbg-cnt-list Print the name and the counter upper bound for all debug counters. -fdbg-cnt=counter-value-list Set the internal debug counter lower and upper bound. counter-value-list is a comma-separated list of name:lower_bound1-up- per_bound1 [:lower_bound2-upper_bound2...] tuples which sets the name of the counter and list of closed intervals. The lower_bound is op- tional and is zero initialized if not set. For example, with -fdbg-cnt=dce:2-4:10-11,tail_call:10, dbg_cnt(dce) returns true only for second, third, fourth, tenth and eleventh invocation. For dbg_cnt(tail_call) true is returned for first 10 invocations. -print-autofdo-gcov-version --print-autofdo-gcov-version Print the current version of GCOV being used by the AutoFDO infrastruc- ture. -print-file-name=library --print-file-name=library --print-file-name library Print the full absolute name of the library file library that would be used when linking---and don't do anything else. With this option, GCC does not compile or link anything; it just prints the file name. -print-multi-directory --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 GCC_EXEC_PREFIX. -print-multi-lib --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 ;, and each switch starts with an @ instead of the -, without spaces between multiple switches. This is supposed to ease shell processing. -print-multi-os-directory --print-multi-os-directory Print the path to OS libraries for the selected multilib, relative to some lib subdirectory. If OS libraries are present in the lib subdi- rectory and no multilibs are used, this is usually just ., if OS li- braries are present in libsuffix sibling directories this prints e.g. ../lib64, ../lib or ../lib32, or if OS libraries are present in lib/subdir subdirectories it prints e.g. amd64, sparcv9 or ev6. -print-multiarch --print-multiarch Print the path to OS libraries for the selected multiarch, relative to some lib subdirectory. -print-prog-name=program --print-prog-name=program --print-prog-name program Like -print-file-name, but searches for a program such as cpp. -print-libgcc-file-name --print-libgcc-file-name Same as -print-file-name=libgcc.a. This is useful when you use -nostdlib or -nodefaultlibs but you do want to link with libgcc.a. You can do: gcc -nostdlib <files>... `gcc -print-libgcc-file-name` -print-search-dirs --print-search-dirs Print the name of the configured installation directory and a list of program and library directories gcc searches---and don't do anything else. This is useful when gcc prints the error message installation problem, cannot exec cpp0: No such file or directory. To resolve this you ei- ther need to put cpp0 and the other compiler components where gcc ex- pects to find them, or you can set the environment variable GCC_EXEC_PREFIX to the directory where you installed them. Don't for- get the trailing /. -print-sysroot --print-sysroot Print the target sysroot directory that is used during compilation. This is the target sysroot specified either at configure time or using the --sysroot option, possibly with an extra suffix that depends on compilation options. If no target sysroot is specified, the option prints nothing. -print-sysroot-headers-suffix --print-sysroot-headers-suffix Print the suffix added to the target sysroot when searching for head- ers, or give an error if the compiler is not configured with such a suffix---and don't do anything else. -dumpmachine Print the compiler's target machine (for example, i686-pc-linux-gnu)---and don't do anything else. -dumpversion Print the compiler version (for example, 3.0, 6.3.0 or 7)---and don't do anything else. This is the compiler version used in filesystem paths and specs. Depending on how the compiler has been configured it can be just a single number (major version), two numbers separated by a dot (major and minor version) or three numbers separated by dots (ma- jor, minor and patchlevel version). -dumpfullversion Print the full compiler version---and don't do anything else. The out- put is always three numbers separated by dots, major, minor and patch- level version. -dumpspecs Print the compiler's built-in specs---and don't do anything else. (This is used when GCC itself is being built.) --param name=value --param=name=value GCC by convention uses parameters that can be specified on the command line instead of hard-wired constants to represent arbitrary compiler limits or heuristics. Many parameters are related to optimization; for example, GCC does not inline functions that contain more than a certain number of instructions. The static analyzer similarly uses parameters to limit complexity, link-time optimization uses parameters to control partitioning, and so on. Other parameters control aspects of GCC that are completely internal, such as its memory allocation and garbage col- lection strategy. Still others control target-specific behavior. The --param option provides a uniform interface for specifying values for these compiler parameters. However, the names of specific parame- ters, and the meaning of the values, are tied to the internals of the compiler, and are subject to change without notice in future releases. You should not depend on parameter settings for correct compilation of your program. They are exposed via the command line for the conve- nience of developers in debugging compilation problems or, in some cases, to provide workarounds for compiler bugs. Target-Specific Options Each target machine supported by GCC can have its own options---for exam- ple, to allow you to compile for a particular processor variant or ABI, or to control optimizations specific to that machine. Similarly, GCC also has options that are specific to particular operating systems or runtime envi- ronments on the target. By convention, the names of machine-specific options start with -m. Some configurations of the compiler also support additional target-specific op- tions, usually for compatibility with other compilers on the same platform. AArch64 Options These options are defined for AArch64 implementations: -mabi=name Generate code for the specified data model. Permissible values are ilp32 for SysV-like data model where int, long int and pointers are 32 bits, and lp64 for SysV-like data model where int is 32 bits, but long int and pointers are 64 bits. The default depends on the specific target configuration. Note that the LP64 and ILP32 ABIs are not link-compatible; you must compile your entire program with the same ABI, and link with a compatible set of li- braries. The ilp32 model is deprecated. -mbig-endian Generate big-endian code. This is the default when GCC is configured for an aarch64_be-*-* target. -mlittle-endian Generate little-endian code. This is the default when GCC is config- ured for an aarch64-*-* but not an aarch64_be-*-* target. -menable-sysreg-checking Generates an error message if an attempt is made to access a system register which is not available on the target architecture. -mgeneral-regs-only Generate code that uses only the general-purpose registers. This pre- vents the compiler from using floating-point and Advanced SIMD regis- ters but does not impose any restrictions on the assembler. -mcmodel=tiny Generate code for the tiny code model. The program and its statically defined symbols must be within 1MB of each other. Programs can be sta- tically or dynamically linked. -mcmodel=small Generate code for the small code model. The program and its statically defined symbols must be within 4GB of each other. Programs can be sta- tically or dynamically linked. This is the default code model. -mcmodel=large Generate code for the large code model. This makes no assumptions about addresses and sizes of sections. Programs can be statically linked only. The -mcmodel=large option is incompatible with -mabi=ilp32, -fpic and -fPIC. -mtp=name Specify the system register to use as a thread pointer. The valid val- ues are tpidr_el0, tpidrro_el0, tpidr_el1, tpidr_el2, tpidr_el3. For backwards compatibility the aliases el0, el1, el2, el3 are also ac- cepted. The default setting is tpidr_el0. It is recommended to com- pile all code intended to interoperate with the same value of this op- tion to avoid accessing a different thread pointer from the wrong ex- ception level. -mstrict-align -mno-strict-align Avoid or allow generating memory accesses that may not be aligned on a natural object boundary as described in the architecture specification. -momit-leaf-frame-pointer -mno-omit-leaf-frame-pointer Omit or keep the frame pointer in leaf functions. The former behavior is the default. -mstack-protector-guard=guard -mstack-protector-guard-reg=reg -mstack-protector-guard-offset=offset Generate stack protection code using canary at guard. Supported loca- tions are global for a global canary or sysreg for a canary in an ap- propriate system register. With the latter choice the options -mstack-protector-guard-reg=reg and -mstack-protector-guard-offset=offset furthermore specify which system register to use as base register for reading the canary, and from what offset from that base register. There is no default register or offset as this is entirely for use within the Linux kernel. -mtls-dialect=desc Use TLS descriptors as the thread-local storage mechanism for dynamic accesses of TLS variables. This is the default. -mtls-dialect=traditional Use traditional TLS as the thread-local storage mechanism for dynamic accesses of TLS variables. -mtls-size=size Specify bit size of immediate TLS offsets. Valid values are 12, 24, 32, 48. This option requires binutils 2.26 or newer. -mfix-cortex-a53-835769 -mno-fix-cortex-a53-835769 Enable or disable the workaround for the ARM Cortex-A53 erratum number 835769. This involves inserting a NOP instruction between memory in- structions and 64-bit integer multiply-accumulate instructions. This flag will be ignored if an architecture or cpu is specified on the com- mand line which does not need the workaround. -mfix-cortex-a53-843419 -mno-fix-cortex-a53-843419 Enable or disable the workaround for the ARM Cortex-A53 erratum number 843419. This erratum workaround is made at link time and this will only pass the corresponding flag to the linker. This flag will be ig- nored if an architecture or cpu is specified on the command line which does not need the workaround. -mlow-precision-recip-sqrt -mno-low-precision-recip-sqrt Enable or disable the reciprocal square root approximation. This op- tion only has an effect if -ffast-math or -funsafe-math-optimizations is used as well. Enabling this reduces precision of reciprocal square root results to about 16 bits for single precision and to 32 bits for double precision. -mlow-precision-sqrt -mno-low-precision-sqrt Enable or disable the square root approximation. This option only has an effect if -ffast-math or -funsafe-math-optimizations is used as well. Enabling this reduces precision of square root results to about 16 bits for single precision and to 32 bits for double precision. If enabled, it implies -mlow-precision-recip-sqrt. -mlow-precision-div -mno-low-precision-div Enable or disable the division approximation. This option only has an effect if -ffast-math or -funsafe-math-optimizations is used as well. Enabling this reduces precision of division results to about 16 bits for single precision and to 32 bits for double precision. -mtrack-speculation -mno-track-speculation Enable or disable generation of additional code to track speculative execution through conditional branches. The tracking state can then be used by the compiler when expanding calls to "__builtin_specula- tion_safe_value" to permit a more efficient code sequence to be gener- ated. -moutline-atomics -mno-outline-atomics Enable or disable calls to out-of-line helpers to implement atomic op- erations. These helpers will, at runtime, determine if the LSE in- structions from ARMv8.1-A can be used; if not, they will use the load/store-exclusive instructions that are present in the base ARMv8.0 ISA. This option is only applicable when compiling for the base ARMv8.0 in- struction set. If using a later revision, e.g. -march=armv8.1-a or -march=armv8-a+lse, the ARMv8.1-Atomics instructions will be used di- rectly. The same applies when using -mcpu= when the selected cpu sup- ports the lse feature. This option is on by default. -mmax-vectorization -mno-max-vectorization Enable or disable an override to vectorizer cost model making vector- ization always appear profitable. This option can be combined with -mautovec-preference allowing precise control over which ISA will be used for auto-vectorization. Unlike -fno-vect-cost-model or -fvect-cost-model=unlimited this option does not turn off cost compari- son between different vector modes. -mautovec-preference=name Force an ISA selection strategy for auto-vectorization. The possible values of name are: default Use the default heuristics. asimd-only Use only Advanced SIMD for auto-vectorization. sve-only Use only SVE for auto-vectorization. prefer-asimd Use both Advanced SIMD and SVE. Prefer Advanced SIMD when the costs are deemed equal. prefer-sve Use both Advanced SIMD and SVE. Prefer SVE when the costs are deemed equal. For best performance it is highly recommended to use -mcpu or -mtune instead. This parameter should only be used for code exploration. -march=name Specify the name of the target architecture and, optionally, one or more feature modifiers. This option has the form -march=arch{+[no]fea- ture}*. The table below summarizes the permissible values for arch and the fea- tures that they enable by default: arch value : Architecture : Includes by default armv8-a : Armv8-A : +fp, +simd armv8.1-a : Armv8.1-A : armv8-a, +crc, +lse, +rdma armv8.2-a : Armv8.2-A : armv8.1-a armv8.3-a : Armv8.3-A : armv8.2-a, +pauth, +fcma, +jscvt armv8.4-a : Armv8.4-A : armv8.3-a, +flagm, +fp16fml, +dotprod, +rcpc2 armv8.5-a : Armv8.5-A : armv8.4-a, +sb, +ssbs, +predres, +frintts, +flagm2 armv8.6-a : Armv8.6-A : armv8.5-a, +bf16, +i8mm armv8.7-a : Armv8.7-A : armv8.6-a, +wfxt, +xs armv8.8-a : Armv8.8-a : armv8.7-a, +mops armv8.9-a : Armv8.9-a : armv8.8-a armv9-a : Armv9-A : armv8.5-a, +sve, +sve2 armv9.1-a : Armv9.1-A : armv9-a, +bf16, +i8mm armv9.2-a : Armv9.2-A : armv9.1-a, +wfxt, +xs armv9.3-a : Armv9.3-A : armv9.2-a, +mops armv9.4-a : Armv9.4-A : armv9.3-a, +sve2p1 armv9.5-a : Armv9.5-A : armv9.4-a, cpa, +faminmax, +lut armv8-r : Armv8-R : armv8-r The value native is available on native AArch64 GNU/Linux and causes the compiler to pick the architecture of the host system. This option has no effect if the compiler is unable to recognize the architecture of the host system. When -march=native is given and no other -mcpu or -mtune is given then GCC will pick the host CPU as the CPU to tune for as well as select the architecture features from. That is, -march=na- tive is treated as -mcpu=native. The permissible values for feature are listed in the sub-section on aarch64-feature-modifiers,,-march and -mcpu Feature Modifiers. Where conflicting feature modifiers are specified, the right-most feature is used. GCC uses name to determine what kind of instructions it can emit when generating assembly code. If -march is specified without either of -mtune or -mcpu also being specified, the code is tuned to perform well across a range of target processors implementing the target architec- ture. -mtune=name Specify the name of the target processor for which GCC should tune the performance of the code. Permissible values for this option are: generic, cortex-a35, cortex-a53, cortex-a55, cortex-a57, cortex-a72, cortex-a73, cortex-a75, cortex-a76, cortex-a76ae, cortex-a77, cor- tex-a65, cortex-a65ae, cortex-a34, cortex-a78, cortex-a78ae, cor- tex-a78c, ares, exynos-m1, emag, falkor, oryon-1, neoverse-512tvb, neo- verse-e1, neoverse-n1, neoverse-n2, neoverse-v1, neoverse-v2, grace, neoverse-v3, neoverse-v3ae, armagicpu, neoverse-n3, olympus, cor- tex-a725, cortex-x925, qdf24xx, saphira, phecda, xgene1, vulcan, octeontx, octeontx81, octeontx83, octeontx2, octeontx2t98, octeontx2t96 octeontx2t93, octeontx2f95, octeontx2f95n, octeontx2f95mm, a64fx, fujitsu-monaka, thunderx, thunderxt88, thunderxt88p1, thun- derxt81, tsv110, hip12, thunderxt83, thunderx2t99, thunderx3t110, zeus, cortex-a57.cortex-a53, cortex-a72.cortex-a53, cortex-a73.cortex-a35, cortex-a73.cortex-a53, cortex-a75.cortex-a55, cortex-a76.cortex-a55, cortex-r82, cortex-r82ae, cortex-x1, cortex-x1c, cortex-x2, cortex-x3, cortex-x4, cortex-a510, cortex-a520, cortex-a520ae, cortex-a710, cor- tex-a715, cortex-a720, cortex-a720ae, ampere1, ampere1a, ampere1b, am- pere1c, cobalt-100, apple-m1, apple-m2, apple-m3, apple-m4, apple-m5, c1-nano, c1-pro, c1-premium c1-ultra and native. The values cortex-a57.cortex-a53, cortex-a72.cortex-a53, cor- tex-a73.cortex-a35, cortex-a73.cortex-a53, cortex-a75.cortex-a55, cor- tex-a76.cortex-a55, apple-m1, apple-m2, apple-m3, gb10 specify that GCC should tune for a big.LITTLE system. The value neoverse-512tvb specifies that GCC should tune for Neoverse cores that (a) implement SVE and (b) have a total vector bandwidth of 512 bits per cycle. In other words, the option tells GCC to tune for Neoverse cores that can execute 4 128-bit Advanced SIMD arithmetic in- structions a cycle and that can execute an equivalent number of SVE arithmetic instructions per cycle (2 for 256-bit SVE, 4 for 128-bit SVE). This is more general than tuning for a specific core like Neo- verse V1 but is more specific than the default tuning described below. Additionally on native AArch64 GNU/Linux systems the value native tunes performance to the host system. This option has no effect if the com- piler is unable to recognize the processor of the host system. Where none of -mtune=, -mcpu= or -march= are specified, the code is tuned to perform well across a range of target processors. This option cannot be suffixed by feature modifiers. -mcpu=name Specify the name of the target processor, optionally suffixed by one or more feature modifiers. This option has the form -mcpu=cpu{+[no]fea- ture}*, where the permissible values for cpu are the same as those available for -mtune. The permissible values for feature are docu- mented in the sub-section on aarch64-feature-modifiers,,-march and -mcpu Feature Modifiers. Where conflicting feature modifiers are spec- ified, the right-most feature is used. GCC uses name to determine what kind of instructions it can emit when generating assembly code (as if by -march) and to determine the target processor for which to tune for performance (as if by -mtune). Where this option is used in conjunction with -march or -mtune, those options take precedence over the appropriate part of this option. -mcpu=neoverse-512tvb is special in that it does not refer to a spe- cific core, but instead refers to all Neoverse cores that (a) implement SVE and (b) have a total vector bandwidth of 512 bits a cycle. Unless overridden by -march, -mcpu=neoverse-512tvb generates code that can run on a Neoverse V1 core, since Neoverse V1 is the first Neoverse core with these properties. Unless overridden by -mtune, -mcpu=neo- verse-512tvb tunes code in the same way as for -mtune=neoverse-512tvb. -moverride=string Override tuning decisions made by the back-end in response to a -mtune= switch. The syntax, semantics, and accepted values for string in this option are not guaranteed to be consistent across releases. This option is only intended to be useful when developing GCC. -mpc-relative-literal-loads -mno-pc-relative-literal-loads Enable or disable PC-relative literal loads. With this option literal pools are accessed using a single instruction and emitted after each function. This limits the maximum size of functions to 1MB. This is enabled by default for -mcmodel=tiny. The -mpc-relative-literal-loads is deprecated. -msign-return-address=scope Select the function scope on which return address signing will be ap- plied. Permissible values are none, which disables return address signing, non-leaf, which enables pointer signing for functions which are not leaf functions, and all, which enables pointer signing for all functions. The default value is none. This option has been deprecated by -mbranch-protection. -mbranch-protection=features Select the branch protection features to use. features can have one of the following forms: none is the default and turns off all types of branch protection. standard turns on all types of branch protection features. If a fea- ture has additional tuning options, then standard sets it to its stan- dard level. pac-ret turns on return address signing to its standard level: signing functions that save the return address to memory (non-leaf functions practically always do this) using the A-key. pac-ret+leaf extends the pac-ret signing to include leaf functions. pac-ret+b-key or pac-ret+leaf+b-key can be used to sign the functions with the B-key instead of the A-key. bti turns on branch target identification mechanism. gcs turns on guarded control stack compatible code generation. -mharden-sls=opts Enable compiler hardening against straight line speculation (SLS). opts is a comma-separated list of the following options: retbr blr In addition, -mharden-sls=all enables all SLS hardening while -mharden-sls=none disables all SLS hardening. -mearly-ra=scope Determine when to enable an early register allocation pass. This pass runs before instruction scheduling and tries to find a spill-free allo- cation of floating-point and vector code. It also tries to make use of strided multi-register instructions, such as SME2's strided LD1 and ST1. The possible values of scope are: all, which runs the pass on all func- tions; strided, which runs the pass on functions that have access to strided multi-register instructions; and none, which disables the pass. -mearly-ra=all is the default for -O2 and above, and for -Os. -mearly-ra=none is the default otherwise. -mearly-ldp-fusion -mno-early-ldp-fusion Enable the copy of the AArch64 load/store pair fusion pass that runs before register allocation. Enabled by default at -O and above. -mlate-ldp-fusion -mno-late-ldp-fusion Enable the copy of the AArch64 load/store pair fusion pass that runs after register allocation. Enabled by default at -O and above. -mnarrow-gp-writes Enable conversion of 64-bit general purpose register writes to equiva- lent 32-bit operations when the upper 32 bits are known to be zero. This pass can be controlled with -mnarrow-gp-writes and is active at -O2 and above, but not enabled by default, except for -mcpu=olympus. -msve-vector-bits=bits Specify the number of bits in an SVE vector register. This option only has an effect when SVE is enabled. GCC supports two forms of SVE code generation: "vector-length agnostic" output that works with any size of vector register and "vector-length specific" output that allows GCC to make assumptions about the vector length when it is useful for optimization reasons. The possible values of bits are: scalable, 128, 256, 512, 1024 and 2048. Specifying scal- able selects vector-length agnostic output. At present -msve-vec- tor-bits=128 also generates vector-length agnostic output for big-en- dian targets. All other values generate vector-length specific code. The behavior of these values may change in future releases and no value except scalable should be relied on for producing code that is portable across different hardware SVE vector lengths. The default is -msve-vector-bits=scalable, which produces vector-length agnostic code. -march and -mcpu Feature Modifiers Feature modifiers used with -march and -mcpu can be any of the following and their inverses nofeature: crc Enable CRC extension. This is on by default for -march=armv8.1-a. crypto Enable Crypto extension. This also enables Advanced SIMD and float- ing-point instructions. fp Enable floating-point instructions. This is on by default for all pos- sible values for options -march and -mcpu. simdEnable Advanced SIMD instructions. This also enables floating-point instructions. This is on by default for all possible values for op- tions -march and -mcpu. sve Enable Scalable Vector Extension instructions. This also enables Ad- vanced SIMD and floating-point instructions. lse Enable Large System Extension instructions. This is on by default for -march=armv8.1-a. rdmaEnable Round Double Multiply Accumulate instructions. This is on by default for -march=armv8.1-a. fp16Enable FP16 extension. This also enables floating-point instructions. fp16fml Enable FP16 fmla extension. This also enables FP16 extensions and floating-point instructions. This option is enabled by default for -march=armv8.4-a. Use of this option with architectures prior to Armv8.2-A is not supported. rcpcEnable the RCpc extension. This enables the use of the LDAPR instruc- tions for load-acquire atomic semantics, and passes it on to the assem- bler, enabling inline asm statements to use instructions from the RCpc extension. dotprod Enable the Dot Product extension. This also enables Advanced SIMD in- structions. aes Enable the Armv8-a aes and pmull crypto extension. This also enables Advanced SIMD instructions. sha2Enable the Armv8-a sha2 crypto extension. This also enables Advanced SIMD instructions. sha3Enable the sha512 and sha3 crypto extension. This also enables Ad- vanced SIMD instructions. Use of this option with architectures prior to Armv8.2-A is not supported. sm4 Enable the sm3 and sm4 crypto extension. This also enables Advanced SIMD instructions. Use of this option with architectures prior to Armv8.2-A is not supported. profile Enable the Statistical Profiling extension. This option is only to en- able the extension at the assembler level and does not affect code gen- eration. rng Enable the Armv8.5-a Random Number instructions. This option is only to enable the extension at the assembler level and does not affect code generation. memtag Enable the Armv8.5-a Memory Tagging Extensions. Use of this option with architectures prior to Armv8.5-A is not supported. sb Enable the Armv8-a Speculation Barrier instruction. This option is only to enable the extension at the assembler level and does not affect code generation. This option is enabled by default for -march=armv8.5-a. ssbsEnable the Armv8-a Speculative Store Bypass Safe instruction. This op- tion is only to enable the extension at the assembler level and does not affect code generation. This option is enabled by default for -march=armv8.5-a. predres Enable the Armv8-a Execution and Data Prediction Restriction instruc- tions. This option is only to enable the extension at the assembler level and does not affect code generation. This option is enabled by default for -march=armv8.5-a. sve2Enable the Armv8-a Scalable Vector Extension 2. This also enables SVE instructions. sve2-bitperm Enable SVE2 bitperm instructions. This also enables SVE2 instructions. sve2-sm4 Enable SVE2 sm4 instructions. This also enables SVE2 instructions. sve2-aes Enable SVE2 aes instructions. This also enables SVE2 instructions. sve2-sha3 Enable SVE2 sha3 instructions. This also enables SVE2 instructions. sve2p1 Enable SVE2.1 instructions. This also enables SVE2 instructions. sve2p2 Enable SVE2.2 instructions. This also enables SVE2 and SVE2.1 instruc- tions. tme Enable the Transactional Memory Extension. i8mmEnable 8-bit Integer Matrix Multiply instructions. This also enables Advanced SIMD and floating-point instructions. This option is enabled by default for -march=armv8.6-a. Use of this option with architectures prior to Armv8.2-A is not supported. f32mm Enable 32-bit Floating point Matrix Multiply instructions. This also enables SVE instructions. Use of this option with architectures prior to Armv8.2-A is not supported. f64mm Enable 64-bit Floating point Matrix Multiply instructions. This also enables SVE instructions. Use of this option with architectures prior to Armv8.2-A is not supported. bf16Enable brain half-precision floating-point instructions. This also en- ables Advanced SIMD and floating-point instructions. This option is enabled by default for -march=armv8.6-a. Use of this option with ar- chitectures prior to Armv8.2-A is not supported. ls64Enable the 64-byte atomic load and store instructions for accelerators. mopsEnable the instructions to accelerate memory operations like "memcpy", "memmove", "memset". This option is enabled by default for -march=armv8.8-a flagm Enable the Flag Manipulation instructions Extension. flagm2 Enable the FlagM2 flag conversion instructions. pauth Enable the Pointer Authentication Extension. csscEnable the Common Short Sequence Compression instructions. cmpbr Enable the shorter compare and branch instructions, "cbb", "cbh" and "cb". sme Enable the Scalable Matrix Extension. sme-i16i64 Enable the FEAT_SME_I16I64 extension to SME. This also enables SME in- structions. sme-f64f64 Enable the FEAT_SME_F64F64 extension to SME. This also enables SME in- structions. sme2Enable the Scalable Matrix Extension 2. This also enables SME instruc- tions. sme-f8f16 Enable the FEAT_SME_F8F16 extension to SME. This also enables SME2 and FP8 instructions. sme-f8f32 Enable the FEAT_SME_F8F32 extension to SME. This also enables SME2 and FP8 instructions. sme-b16b16 Enable the FEAT_SME_B16B16 extension to SME. This also enables SME2 and SVE_B16B16 instructions. sme-f16f16 Enable the FEAT_SME_F16F16 extension to SME. This also enables SME2 instructions. sme2p1 Enable the Scalable Matrix Extension version 2.1. This also enables SME2 instructions. sme2p2 Enable the Scalable Matrix Extension version 2.2. This also enables SME2 and SME2.1 instructions. fcmaEnable the complex number SIMD extensions. jscvt Enable the "fjcvtzs" JavaScript conversion instruction. frintts Enable floating-point round to integral value instructions. wfxtEnable "wfet" and "wfit" instructions. xs Enable the XS memory attribute extension. lse128 Enable the LSE128 128-bit atomic instructions extension. This also en- ables LSE instructions. d128Enable support for 128-bit system register read/write instructions. This also enables the LSE128 extension. gcs Enable support for Armv9.4-a Guarded Control Stack extension. the Enable support for Armv8.9-a/9.4-a translation hardening extension. rcpc2 Enable the RCpc2 extension. rcpc3 Enable the RCpc3 (Release Consistency) extension. fp8 Enable the fp8 (8-bit floating point) extension. fp8fma Enable the fp8 (8-bit floating point) multiply accumulate extension. ssve-fp8fma Enable the fp8 (8-bit floating point) multiply accumulate extension in streaming mode. fp8dot4 Enable the fp8 (8-bit floating point) to single-precision 4-way dot product extension. ssve-fp8dot4 Enable the fp8 (8-bit floating point) to single-precision 4-way dot product extension in streaming mode. fp8dot2 Enable the fp8 (8-bit floating point) to half-precision 2-way dot prod- uct extension. ssve-fp8dot2 Enable the fp8 (8-bit floating point) to half-precision 2-way dot prod- uct extension in streaming mode. faminmax Enable the Floating Point Absolute Maximum/Minimum extension. lut Enable the Lookup Table extension. sme-lutv2 Enable the SME Lookup Table v2 (LUTv2) extension. cpa Enable the Checked Pointer Arithmetic instructions. sve-b16b16 Enable the SVE non-widening brain floating-point ("bf16") extension. This only has an effect when "sve2" or "sme2" are also enabled. sve-bfscale Enable the SVE_BFSCALE extension. poe2Enable the Permission Overlays Extension 2. tev Enable the TIndex Exception-like Vector Extension. tlbid Enable the TLBI Domains Extension. gcieEnable the GICv5 (Generic Interrupt Controller) CPU Interface Exten- sion. mpamv2 Enable MPAMv2 system registers. lscpEnable the load acquire and store release pair extension. mops-go Enable tag only variants of MOPS instructions. This also enables the instructions to accelerate memory operations and Armv8.5-a Memory Tag- ging Extensions. sve2p3 Enable SVE2.3. This also enables SVE2.2 instructions. sme2p3 Enable SME2.3. This also enables SME2.2 instructions. f16f32dot Enable Armv9.7-a f16f32dot instructions. This also enables Advanced SIMD, floating-point instructions and Armv8.2-a FP16 instructions. sve-b16mm Enable the SVE B16MM Extension. This also enables SVE instructions, Advanced SIMD and floating-point instructions. mtetc Enable Data cache tag block operations. This also enables Armv8.5-a Memory Tagging Extensions. f16f32mm Enable Armv9.7-a f16f32mm instructions. This also enables Advanced SIMD, floating-point instructions and Armv8.2-a FP16 instructions. f16mm Enable f16mm instructions. This also enables Advanced SIMD, float- ing-point instructions and Armv8.2-a FP16 instructions. Feature crypto implies aes, sha2, and simd, which implies fp. Conversely, nofp implies nosimd, which implies nocrypto, noaes and nosha2. Adapteva Epiphany Options These -m options are defined for Adapteva Epiphany: -mhalf-reg-file -mno-half-reg-file Don't allocate any register in the range "r32"..."r63". That allows code to run on hardware variants that lack these registers. -mprefer-short-insn-regs -mno-prefer-short-insn-regs Preferentially allocate registers that allow short instruction genera- tion. This can result in increased instruction count, so this may ei- ther reduce or increase overall code size. -mbranch-cost=num Set the cost of branches to roughly num "simple" instructions. This cost is only a heuristic and is not guaranteed to produce consistent results across releases. -mcmove -mno-cmove Enable the generation of conditional moves. -mnops=num Emit num NOPs before every other generated instruction. -mno-soft-cmpsf -msoft-cmpsf For single-precision floating-point comparisons, emit an "fsub" in- struction and test the flags. This is faster than a software compari- son, but can get incorrect results in the presence of NaNs, or when two different small numbers are compared such that their difference is cal- culated as zero. The default is -msoft-cmpsf, which uses slower, but IEEE-compliant, software comparisons. -mstack-offset=num Set the offset between the top of the stack and the stack pointer. E.g., a value of 8 means that the eight bytes in the range "sp+0...sp+7" can be used by leaf functions without stack allocation. Values other than 8 or 16 are untested and unlikely to work. Note also that this option changes the ABI; compiling a program with a different stack offset than the libraries have been compiled with generally does not work. This option can be useful if you want to evaluate if a dif- ferent stack offset would give you better code, but to actually use a different stack offset to build working programs, it is recommended to configure the toolchain with the appropriate --with-stack-offset=num option. -mno-round-nearest -mround-nearest -mno-round-nearest makes the scheduler assume that the rounding mode has been set to truncating. The default is -mround-nearest. -mlong-calls If not otherwise specified by an attribute, assume all calls might be beyond the offset range of the "b" / "bl" instructions, and therefore load the function address into a register before performing a (other- wise direct) call. This is the default. -mshort-calls If not otherwise specified by an attribute, assume all direct calls are in the range of the "b" / "bl" instructions, so use these instructions for direct calls. The default is -mlong-calls. Note that -mlong-calls is equivalent to -mno-short-calls, and similarly -mno-long-calls is equivalent to -mshort-calls. -msmall16 -mno-small16 Assume addresses can be loaded as 16-bit unsigned values. This does not apply to function addresses for which -mlong-calls semantics are in effect. -mfp-mode=mode Set the prevailing mode of the floating-point unit. This determines the floating-point mode that is provided and expected at function call and return time. Making this mode match the mode you predominantly need at function start can make your programs smaller and faster by avoiding unnecessary mode switches. mode can be set to one the following values: caller Any mode at function entry is valid, and retained or restored when the function returns, and when it calls other functions. This mode is useful for compiling libraries or other compilation units you might want to incorporate into different programs with different prevailing FPU modes, and the convenience of being able to use a single object file outweighs the size and speed overhead for any extra mode switching that might be needed, compared with what would be needed with a more specific choice of prevailing FPU mode. truncate This is the mode used for floating-point calculations with truncat- ing (i.e. round towards zero) rounding mode. That includes conver- sion from floating point to integer. round-nearest This is the mode used for floating-point calculations with round-to-nearest-or-even rounding mode. int This is the mode used to perform integer calculations in the FPU, e.g. integer multiply, or integer multiply-and-accumulate. The default is -mfp-mode=caller -mmay-round-for-trunc -mno-may-round-for-trunc This option allows floating point to integer truncation to be replaced with rounding to save mode switching. It's disabled by default. -mfp-iarith -mno-fp-iarith This option enables use of the floating-point unit for integer add and subtract. It's disabled by default. -msplit-lohi -mno-split-lohi -mpost-inc -mno-post-inc -mpost-modify -mno-post-modify Code generation tweaks that control, respectively, splitting of 32-bit loads, generation of post-increment addresses, and generation of post-modify addresses. The defaults are msplit-lohi, -mpost-inc, and -mpost-modify. -mno-vect-double Change the preferred SIMD mode to SImode. The default is -mvect-dou- ble, which uses DImode as preferred SIMD mode. -max-vect-align=num The maximum alignment for SIMD vector mode types. num may be 4 or 8. The default is 8. Note that this is an ABI change, even though many library function interfaces are unaffected if they don't use SIMD vec- tor modes in places that affect size and/or alignment of relevant types. -msplit-vecmove-early -mno-split-vecmove-early Split vector moves into single word moves before reload. In theory this can give better register allocation, but so far the reverse seems to be generally the case. -m1reg-reg Specify a register to hold the constant -1, which makes loading small negative constants and certain bitmasks faster. Allowable values for reg are r43 and r63, which specify use of that register as a fixed reg- ister, and none, which means that no register is used for this purpose. The default is -m1reg-none. AMD GCN Options These options are defined specifically for the AMD GCN port. -march=gpu -mtune=gpu Set architecture type or tuning for gpu. Supported values for gpu are gfx900 Compile for GCN5 Vega 10 devices (gfx900). gfx902 Compile for GCN5 Vega gfx902 devices. (Experimental) gfx904 Compile for GCN5 Vega gfx904 devices. (Experimental) gfx906 Compile for GCN5 Vega 20 devices (gfx906). gfx908 Compile for CDNA1 Instinct MI100 series devices (gfx908). gfx909 Compile for GCN5 Vega gfx909 devices. (Experimental) gfx90a Compile for CDNA2 Instinct MI200 series devices (gfx90a). gfx90c Compile for GCN5 Vega 7 devices (gfx90c). gfx942 Compile for CDNA3 Instinct MI300 series devices (gfx942). (Experi- mental) gfx950 Compile for the CDNA3 gfx950 devices. (Experimental) gfx9-generic Compile generic code for Vega devices, executable on the following subset of GFX9 devices: gfx900, gfx902, gfx904, gfx906, gfx909 and gfx90c. gfx9-4-generic Compile generic code for CDNA3 devices, executable on the following subset of GFX9 devices: gfx942 and gfx950. (Experimental) gfx1030 Compile for RDNA2 gfx1030 devices (GFX10 series). gfx1031 Compile for RDNA2 gfx1031 devices (GFX10 series). (Experimental) gfx1032 Compile for RDNA2 gfx1032 devices (GFX10 series). (Experimental) gfx1033 Compile for RDNA2 gfx1033 devices (GFX10 series). (Experimental) gfx1034 Compile for RDNA2 gfx1034 devices (GFX10 series). (Experimental) gfx1035 Compile for RDNA2 gfx1035 devices (GFX10 series). (Experimental) gfx1036 Compile for RDNA2 gfx1036 devices (GFX10 series). gfx10-3-generic Compile generic code for GFX10-3 devices, executable on gfx1030, gfx1031, gfx1032, gfx1033, gfx1034, gfx1035, and gfx1036. gfx1100 Compile for RDNA3 gfx1100 devices (GFX11 series). gfx1101 Compile for RDNA3 gfx1101 devices (GFX11 series). (Experimental) gfx1102 Compile for RDNA3 gfx1102 devices (GFX11 series). (Experimental) gfx1103 Compile for RDNA3 gfx1103 devices (GFX11 series). gfx1150 Compile for RDNA3 gfx1150 devices (GFX11 series). (Experimental) gfx1151 Compile for RDNA3 gfx1151 devices (GFX11 series). (Experimental) gfx1152 Compile for RDNA3 gfx1152 devices (GFX11 series). (Experimental) gfx1153 Compile for RDNA3 gfx1153 devices (GFX11 series). (Experimental) gfx11-generic Compile generic code for GFX11 devices, executable on gfx1100, gfx1101, gfx1102, gfx1103, gfx1150, gfx1151, gfx1152, and gfx1153. -mgang-private-size=bytes Set the amount of local data-share (LDS) memory to reserve for gang-private variables. The default is 512. -msram-ecc=on -msram-ecc=off -msram-ecc=any Compile binaries suitable for devices with the SRAM-ECC feature en- abled, disabled, or either mode. This feature can be enabled per-process on some devices. The compiled code must match the device mode. The default is any, for devices that support it. -mxnack=on -mxnack=off -mxnack=any Compile binaries suitable for devices with the XNACK feature enabled, disabled, or either mode. Some devices always require XNACK and some allow the user to configure XNACK. The compiled code must match the device mode. The default is -mxnack=any on devices that support Uni- fied Shared Memory, and -mxnack=no otherwise. -Wopenacc-dims -Wno-openacc-dims Control warnings about invalid OpenACC dimensions. ARC Options The following options control the architecture variant for which code is being compiled: -mbarrel-shifter Generate instructions supported by barrel shifter. This is the default unless -mcpu=ARC601 or -mcpu=ARCEM is in effect. -mjli-always Force to call a function using jli_s instruction. This option is valid only for ARCv2 architecture. -mcpu=cpu Set architecture type, register usage, and instruction scheduling para- meters for cpu. There are also shortcut alias options available for backward compatibility and convenience. Supported values for cpu are arc600 Compile for ARC600. Aliases: -mA6, -mARC600. arc601 Compile for ARC601. Alias: -mARC601. arc700 Compile for ARC700. Aliases: -mA7, -mARC700. This is the default when configured with --with-cpu=arc700. arcem Compile for ARC EM. archs Compile for ARC HS. em Compile for ARC EM CPU with no hardware extensions. em4 Compile for ARC EM4 CPU. em4_dmips Compile for ARC EM4 DMIPS CPU. em4_fpus Compile for ARC EM4 DMIPS CPU with the single-precision float- ing-point extension. em4_fpuda Compile for ARC EM4 DMIPS CPU with single-precision floating-point and double assist instructions. hs Compile for ARC HS CPU with no hardware extensions except the atomic instructions. hs34Compile for ARC HS34 CPU. hs38Compile for ARC HS38 CPU. hs38_linux Compile for ARC HS38 CPU with all hardware extensions on. hs4xCompile for ARC HS4x CPU. hs4xd Compile for ARC HS4xD CPU. hs4x_rel31 Compile for ARC HS4x CPU release 3.10a. arc600_norm Compile for ARC 600 CPU with "norm" instructions enabled. arc600_mul32x16 Compile for ARC 600 CPU with "norm" and 32x16-bit multiply instruc- tions enabled. arc600_mul64 Compile for ARC 600 CPU with "norm" and "mul64"-family instructions enabled. arc601_norm Compile for ARC 601 CPU with "norm" instructions enabled. arc601_mul32x16 Compile for ARC 601 CPU with "norm" and 32x16-bit multiply instruc- tions enabled. arc601_mul64 Compile for ARC 601 CPU with "norm" and "mul64"-family instructions enabled. nps400 Compile for ARC 700 on NPS400 chip. em_mini Compile for ARC EM minimalist configuration featuring reduced reg- ister set. -mdpfp -mdpfp-compact Generate double-precision FPX instructions, tuned for the compact im- plementation. -mdpfp-fast Generate double-precision FPX instructions, tuned for the fast imple- mentation. -mno-dpfp-lrsr -mdpfp-lrsr Control whether "lr" and "sr" instructions use FPX extension aux regis- ters. This is enabled by default. -meaGenerate extended arithmetic instructions. Currently only "divaw", "adds", "subs", and "sat16" are supported. Only valid for -mcpu=ARC700. -mmul32x16 Generate 32x16-bit multiply and multiply-accumulate instructions. -mmul64 Generate "mul64" and "mulu64" instructions. Only valid for -mcpu=ARC600. -mnorm Generate "norm" instructions. This is the default if -mcpu=ARC700 is in effect. -mspfp -mspfp-compact Generate single-precision FPX instructions, tuned for the compact im- plementation. -mspfp-fast Generate single-precision FPX instructions, tuned for the fast imple- mentation. -msimd Enable generation of ARC SIMD instructions via target-specific builtins. Only valid for -mcpu=ARC700. -msoft-float This option ignored; it is provided for compatibility purposes only. Software floating-point code is emitted by default, and this default can overridden by FPX options; -mspfp, -mspfp-compact, or -mspfp-fast for single precision, and -mdpfp, -mdpfp-compact, or -mdpfp-fast for double precision. -mswap Generate "swap" instructions. -matomic This enables use of the locked load/store conditional extension to im- plement atomic memory built-in functions. Not available for ARC 6xx or ARC EM cores. -mdiv-rem Enable "div" and "rem" instructions for ARCv2 cores. -mcode-density -mno-code-density Enable code density instructions for ARC EM. This option is on by de- fault for ARC HS. -mll64 Enable double load/store operations for ARC HS cores. -mtp-regno=regno Specify thread pointer register number. -mbitops Enable use of NPS400 bit operations. -mcmem Enable use of NPS400 xld/xst extension. -mmpy-option=multo Compile ARCv2 code with a multiplier design option. You can specify the option using either a string or numeric value for multo. wlh1 is the default value. The recognized values are: 0 noneNo multiplier available. 1 w 16x16 multiplier, fully pipelined. The following instructions are enabled: "mpyw" and "mpyuw". 2 wlh132x32 multiplier, fully pipelined (1 stage). The following in- structions are additionally enabled: "mpy", "mpyu", "mpym", "mpymu", and "mpy_s". 3 wlh232x32 multiplier, fully pipelined (2 stages). The following in- structions are additionally enabled: "mpy", "mpyu", "mpym", "mpymu", and "mpy_s". 4 wlh3Two 16x16 multipliers, blocking, sequential. The following in- structions are additionally enabled: "mpy", "mpyu", "mpym", "mpymu", and "mpy_s". 5 wlh4One 16x16 multiplier, blocking, sequential. The following instruc- tions are additionally enabled: "mpy", "mpyu", "mpym", "mpymu", and "mpy_s". 6 wlh5One 32x4 multiplier, blocking, sequential. The following instruc- tions are additionally enabled: "mpy", "mpyu", "mpym", "mpymu", and "mpy_s". 7 plus_dmpy ARC HS SIMD support. 8 plus_macd ARC HS SIMD support. 9 plus_qmacw ARC HS SIMD support. This option is only available for ARCv2 cores. -mfpu=fpu Enables support for specific floating-point hardware extensions for ARCv2 cores. Supported values for fpu are: fpusEnables support for single-precision floating-point hardware exten- sions. fpudEnables support for double-precision floating-point hardware exten- sions. The single-precision floating-point extension is also en- abled. Not available for ARC EM. fpuda Enables support for double-precision floating-point hardware exten- sions using double-precision assist instructions. The single-pre- cision floating-point extension is also enabled. This option is only available for ARC EM. fpuda_div Enables support for double-precision floating-point hardware exten- sions using double-precision assist instructions. The single-pre- cision floating-point, square-root, and divide extensions are also enabled. This option is only available for ARC EM. fpuda_fma Enables support for double-precision floating-point hardware exten- sions using double-precision assist instructions. The single-pre- cision floating-point and fused multiply and add hardware exten- sions are also enabled. This option is only available for ARC EM. fpuda_all Enables support for double-precision floating-point hardware exten- sions using double-precision assist instructions. All single-pre- cision floating-point hardware extensions are also enabled. This option is only available for ARC EM. fpus_div Enables support for single-precision floating-point, square-root and divide hardware extensions. fpud_div Enables support for double-precision floating-point, square-root and divide hardware extensions. This option includes option fpus_div. Not available for ARC EM. fpus_fma Enables support for single-precision floating-point and fused mul- tiply and add hardware extensions. fpud_fma Enables support for double-precision floating-point and fused mul- tiply and add hardware extensions. This option includes option fpus_fma. Not available for ARC EM. fpus_all Enables support for all single-precision floating-point hardware extensions. fpud_all Enables support for all single- and double-precision floating-point hardware extensions. Not available for ARC EM. -mirq-ctrl-saved=register-range, blink, lp_count Specifies general-purposes registers that the processor automatically saves/restores on interrupt entry and exit. register-range is speci- fied as two registers separated by a dash. The register range always starts with "r0", the upper limit is "fp" register. blink and lp_count are optional. This option is only valid for ARC EM and ARC HS cores. -mrgf-banked-regs=number Specifies the number of registers replicated in second register bank on entry to fast interrupt. Fast interrupts are interrupts with the high- est priority level P0. These interrupts save only PC and STATUS32 reg- isters to avoid memory transactions during interrupt entry and exit se- quences. Use this option when you are using fast interrupts in an ARC V2 family processor. Permitted values are 4, 8, 16, and 32. -mlpc-width=width Specify the width of the "lp_count" register. Valid values for width are 8, 16, 20, 24, 28 and 32 bits. The default width is fixed to 32 bits. If the width is less than 32, the compiler does not attempt to transform loops in your program to use the zero-delay loop mechanism unless it is known that the "lp_count" register can hold the required loop-counter value. Depending on the width specified, the compiler and run-time library might continue to use the loop mechanism for various needs. This option defines macro "__ARC_LPC_WIDTH__" with the value of width. -mrf16 This option instructs the compiler to generate code for a 16-entry reg- ister file. This option defines the "__ARC_RF16__" preprocessor macro. -mbranch-index Enable use of "bi" or "bih" instructions to implement jump tables. The following options are passed through to the assembler, and also define preprocessor macro symbols. -mlock Passed down to the assembler to enable the locked load/store condi- tional extension. Also sets the preprocessor symbol "__Xlock". -mswape Passed down to the assembler to enable the swap byte ordering extension instruction. Also sets the preprocessor symbol "__Xswape". -mxyPassed down to the assembler to enable the XY memory extension. Also sets the preprocessor symbol "__Xxy". The following options control how the assembly code is annotated: -misize Annotate assembler instructions with estimated addresses. The following options are passed through to the linker: -marclinux -mno-arclinux Passed through to the linker, to specify use of the "arclinux" emula- tion. This option is enabled by default in tool chains built for "arc-linux-uclibc" and "arceb-linux-uclibc" targets when profiling is not requested. -marclinux_prof -mno-arclinux_prof Passed through to the linker, to specify use of the "arclinux_prof" em- ulation. This option is enabled by default in tool chains built for "arc-linux-uclibc" and "arceb-linux-uclibc" targets when profiling is requested. The following options control the semantics of generated code: -mlong-calls Generate calls as register indirect calls, thus providing access to the full 32-bit address range. -mmedium-calls -mno-medium-calls Don't use less than 25-bit addressing range for calls, which is the offset available for an unconditional branch-and-link instruction. Conditional execution of function calls is suppressed, to allow use of the 25-bit range, rather than the 21-bit range with conditional branch-and-link. This is the default for tool chains built for "arc-linux-uclibc" and "arceb-linux-uclibc" targets. -G num Put definitions of externally-visible data in a small data section if that data is no bigger than num bytes. The default value of num is 4 for any ARC configuration, or 8 when we have double load/store opera- tions. -mno-sdata Do not generate sdata references. This is the default for tool chains built for "arc-linux-uclibc" and "arceb-linux-uclibc" targets. -mvolatile-cache -mno-volatile-cache Control how volatile references are accessed. The default is -mvolatile-cache, which uses ordinary cached memory accesses for volatile references. Use -mno-volatile-cache to enable cache bypass for volatile references. The following options fine tune code generation: -mauto-modify-reg Enable the use of pre/post modify with register displacement. -mno-brcc -mbrcc This option controls a target-specific pass in arc_reorg to generate compare-and-branch ("brcc") instructions, which is enabled by default. It has no effect on generation of these instructions driven by the com- biner pass. -mcase-vector-pcrel Use PC-relative switch case tables to enable case table shortening. This is the default for -Os. -mno-cond-exec Disable the ARCompact-specific pass to generate conditional execution instructions. Due to delay slot scheduling and interactions between operand numbers, literal sizes, instruction lengths, and the support for conditional ex- ecution, the target-independent pass to generate conditional execution is often lacking, so the ARC port has kept a special pass around that tries to find more conditional execution generation opportunities after register allocation, branch shortening, and delay slot scheduling have been done. This pass generally, but not always, improves performance and code size, at the cost of extra compilation time, which is why there is an option to switch it off. If you have a problem with call instructions exceeding their allowable offset range because they are conditionalized, you should consider using -mmedium-calls instead. -mearly-cbranchsi Enable pre-reload use of the "cbranchsi" pattern. -mindexed-loads Enable the use of indexed loads. This can be problematic because some optimizers then assume that indexed stores exist, which is not the case. -mlra-priority-none Don't indicate any priority for target registers. -mlra-priority-compact Indicate target register priority for r0..r3 / r12..r15. -mlra-priority-noncompact Reduce target register priority for r0..r3 / r12..r15. -mmillicode When optimizing for size (using -Os), prologues and epilogues that have to save or restore a large number of registers are often shortened by using call to a special function in libgcc; this is referred to as a millicode call. As these calls can pose performance issues, and/or cause linking issues when linking in a nonstandard way, this option is provided to turn on or off millicode call generation. -mcode-density-frame This option enable the compiler to emit "enter" and "leave" instruc- tions. These instructions are only valid for CPUs with code-density feature. -msize-level=level Fine-tune size optimization with regards to instruction lengths and alignment. The recognized values for level are: 0 No size optimization. This level is deprecated and treated like 1. 1 Short instructions are used opportunistically. 2 In addition, alignment of loops and of code after barriers are dropped. 3 In addition, optional data alignment is dropped, and the option Os is enabled. This defaults to 3 when -Os is in effect. Otherwise, the behavior when this is not set is equivalent to level 1. -mtune=cpu Set instruction scheduling parameters for cpu, overriding any implied by -mcpu=. Supported values for cpu are ARC600 Tune for ARC600 CPU. ARC601 Tune for ARC601 CPU. ARC700 Tune for ARC700 CPU with standard multiplier block. ARC700-xmac Tune for ARC700 CPU with XMAC block. ARC725D Tune for ARC725D CPU. ARC750D Tune for ARC750D CPU. core3 Tune for ARCv2 core3 type CPU. This option enable usage of "dbnz" instruction. release31a Tune for ARC4x release 3.10a. -mmultcost=num Cost to assume for a multiply instruction, with 4 being equal to a nor- mal instruction. ARM Options These -m options are defined for the ARM port: -mabi=name Generate code for the specified ABI. Permissible values are: apcs-gnu, atpcs, aapcs and aapcs-linux. -mapcs-frame Generate a stack frame that is compliant with the ARM Procedure Call Standard for all functions, even if this is not strictly necessary for correct execution of the code. Specifying -fomit-frame-pointer with this option causes the stack frames not to be generated for leaf func- tions. The default is -mno-apcs-frame. This option is deprecated. -mapcs This is a synonym for -mapcs-frame and is deprecated. -mthumb-interwork Generate code that supports calling between the ARM and Thumb instruc- tion sets. Without this option, on pre-v5 architectures, the two in- struction sets cannot be reliably used inside one program. The default is -mno-thumb-interwork, since slightly larger code is generated when -mthumb-interwork is specified. In AAPCS configurations this option is meaningless. -msched-prolog -mno-sched-prolog Allow or prevent the reordering of instructions in the function pro- logue, or the merging of those instruction with the instructions in the function's body. With -mno-sched-prolog, this means that all functions start with a recognizable set of instructions (or in fact one of a choice from a small set of different function prologues), and this in- formation can be used to locate the start of functions inside an exe- cutable piece of code. The default is -msched-prolog. -mfloat-abi=name Specifies which floating-point ABI to use. Permissible values are: soft, softfp and hard. Specifying soft causes GCC to generate output containing library calls for floating-point operations. softfp allows the generation of code using hardware floating-point instructions, but still uses the soft-float calling conventions. hard allows generation of float- ing-point instructions and uses FPU-specific calling conventions. The default depends on the specific target configuration. Note that the hard-float and soft-float ABIs are not link-compatible; you must compile your entire program with the same ABI, and link with a compati- ble set of libraries. -mgeneral-regs-only Generate code which uses only the general-purpose registers. This will prevent the compiler from using floating-point and Advanced SIMD regis- ters but will not impose any restrictions on the assembler. -mlittle-endian Generate code for a processor running in little-endian mode. This is the default for all standard configurations. -mbig-endian Generate code for a processor running in big-endian mode; the default is to compile code for a little-endian processor. -mbe8 -mbe32 When linking a big-endian image select between BE8 and BE32 formats. The option has no effect for little-endian images and is ignored. The default is dependent on the selected target architecture. For ARMv6 and later architectures the default is BE8, for older architectures the default is BE32. BE32 format has been deprecated by ARM. -march=name[+extension...] This specifies the name of the target ARM architecture. GCC 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 -mcpu= option. Permissible names are: armv4t, armv5t, armv5te, armv6, armv6j, armv6k, armv6kz, armv6t2, armv6z, armv6zk, armv7, armv7-a, armv7ve, armv8-a, armv8.1-a, armv8.2-a, armv8.3-a, armv8.4-a, armv8.5-a, armv8.6-a, armv9-a, armv7-r, armv8-r, armv6-m, armv6s-m, armv7-m, armv7e-m, armv8-m.base, armv8-m.main, armv8.1-m.main, iwmmxt and iwmmxt2. Additionally, the following architectures, which lack support for the Thumb execution state, are recognized but support is deprecated: armv4. Many of the architectures support extensions. These can be added by appending +extension to the architecture name. Extension options are processed in order and capabilities accumulate. An extension will also enable any necessary base extensions upon which it depends. For exam- ple, the +crypto extension will always enable the +simd extension. The exception to the additive construction is for extensions that are pre- fixed with +no...: these extensions disable the specified option and any other extensions that may depend on the presence of that extension. For example, -march=armv7-a+simd+nofp+vfpv4 is equivalent to writing -march=armv7-a+vfpv4 since the +simd option is entirely disabled by the +nofp option that follows it. Most extension names are generically named, but have an effect that is dependent upon the architecture to which it is applied. For example, the +simd option can be applied to both armv7-a and armv8-a architec- tures, but will enable the original ARMv7-A Advanced SIMD (Neon) exten- sions for armv7-a and the ARMv8-A variant for armv8-a. The table below lists the supported extensions for each architecture. Architectures not mentioned do not support any extensions. armv5te armv6 armv6j armv6k armv6kz armv6t2 armv6z armv6zk +fp The VFPv2 floating-point instructions. The extension +vfpv2 can be used as an alias for this extension. +nofp Disable the floating-point instructions. armv7 The common subset of the ARMv7-A, ARMv7-R and ARMv7-M architec- tures. +fp The VFPv3 floating-point instructions, with 16 double-precision registers. The extension +vfpv3-d16 can be used as an alias for this extension. Note that floating-point is not supported by the base ARMv7-M architecture, but is compatible with both the ARMv7-A and ARMv7-R architectures. +nofp Disable the floating-point instructions. armv7-a +mp The multiprocessing extension. +secThe security extension. +fp The VFPv3 floating-point instructions, with 16 double-precision registers. The extension +vfpv3-d16 can be used as an alias for this extension. +simd The Advanced SIMD (Neon) v1 and the VFPv3 floating-point in- structions. The extensions +neon and +neon-vfpv3 can be used as aliases for this extension. +vfpv3 The VFPv3 floating-point instructions, with 32 double-precision registers. +vfpv3-d16-fp16 The VFPv3 floating-point instructions, with 16 double-precision registers and the half-precision floating-point conversion op- erations. +vfpv3-fp16 The VFPv3 floating-point instructions, with 32 double-precision registers and the half-precision floating-point conversion op- erations. +vfpv4-d16 The VFPv4 floating-point instructions, with 16 double-precision registers. +vfpv4 The VFPv4 floating-point instructions, with 32 double-precision registers. +neon-fp16 The Advanced SIMD (Neon) v1 and the VFPv3 floating-point in- structions, with the half-precision floating-point conversion operations. +neon-vfpv4 The Advanced SIMD (Neon) v2 and the VFPv4 floating-point in- structions. +nosimd Disable the Advanced SIMD instructions (does not disable float- ing point). +nofp Disable the floating-point and Advanced SIMD instructions. armv7ve The extended version of the ARMv7-A architecture with support for virtualization. +fp The VFPv4 floating-point instructions, with 16 double-precision registers. The extension +vfpv4-d16 can be used as an alias for this extension. +simd The Advanced SIMD (Neon) v2 and the VFPv4 floating-point in- structions. The extension +neon-vfpv4 can be used as an alias for this extension. +vfpv3-d16 The VFPv3 floating-point instructions, with 16 double-precision registers. +vfpv3 The VFPv3 floating-point instructions, with 32 double-precision registers. +vfpv3-d16-fp16 The VFPv3 floating-point instructions, with 16 double-precision registers and the half-precision floating-point conversion op- erations. +vfpv3-fp16 The VFPv3 floating-point instructions, with 32 double-precision registers and the half-precision floating-point conversion op- erations. +vfpv4-d16 The VFPv4 floating-point instructions, with 16 double-precision registers. +vfpv4 The VFPv4 floating-point instructions, with 32 double-precision registers. +neon The Advanced SIMD (Neon) v1 and the VFPv3 floating-point in- structions. The extension +neon-vfpv3 can be used as an alias for this extension. +neon-fp16 The Advanced SIMD (Neon) v1 and the VFPv3 floating-point in- structions, with the half-precision floating-point conversion operations. +nosimd Disable the Advanced SIMD instructions (does not disable float- ing point). +nofp Disable the floating-point and Advanced SIMD instructions. armv8-a +crcThe Cyclic Redundancy Check (CRC) instructions. +simd The ARMv8-A Advanced SIMD and floating-point instructions. +crypto The cryptographic instructions. +nocrypto Disable the cryptographic instructions. +nofp Disable the floating-point, Advanced SIMD and cryptographic in- structions. +sb Speculation Barrier Instruction. +predres Execution and Data Prediction Restriction Instructions. armv8.1-a +simd The ARMv8.1-A Advanced SIMD and floating-point instructions. +crypto The cryptographic instructions. This also enables the Advanced SIMD and floating-point instructions. +nocrypto Disable the cryptographic instructions. +nofp Disable the floating-point, Advanced SIMD and cryptographic in- structions. +sb Speculation Barrier Instruction. +predres Execution and Data Prediction Restriction Instructions. armv8.2-a armv8.3-a +fp16 The half-precision floating-point data processing instructions. This also enables the Advanced SIMD and floating-point instruc- tions. +fp16fml The half-precision floating-point fmla extension. This also enables the half-precision floating-point extension and Ad- vanced SIMD and floating-point instructions. +simd The ARMv8.1-A Advanced SIMD and floating-point instructions. +crypto The cryptographic instructions. This also enables the Advanced SIMD and floating-point instructions. +dotprod Enable the Dot Product extension. This also enables Advanced SIMD instructions. +nocrypto Disable the cryptographic extension. +nofp Disable the floating-point, Advanced SIMD and cryptographic in- structions. +sb Speculation Barrier Instruction. +predres Execution and Data Prediction Restriction Instructions. +i8mm 8-bit Integer Matrix Multiply instructions. This also enables Advanced SIMD and floating-point instructions. +bf16 Brain half-precision floating-point instructions. This also enables Advanced SIMD and floating-point instructions. armv8.4-a +fp16 The half-precision floating-point data processing instructions. This also enables the Advanced SIMD and floating-point instruc- tions as well as the Dot Product extension and the half-preci- sion floating-point fmla extension. +simd The ARMv8.3-A Advanced SIMD and floating-point instructions as well as the Dot Product extension. +crypto The cryptographic instructions. This also enables the Advanced SIMD and floating-point instructions as well as the Dot Product extension. +nocrypto Disable the cryptographic extension. +nofp Disable the floating-point, Advanced SIMD and cryptographic in- structions. +sb Speculation Barrier Instruction. +predres Execution and Data Prediction Restriction Instructions. +i8mm 8-bit Integer Matrix Multiply instructions. This also enables Advanced SIMD and floating-point instructions. +bf16 Brain half-precision floating-point instructions. This also enables Advanced SIMD and floating-point instructions. armv8.5-a +fp16 The half-precision floating-point data processing instructions. This also enables the Advanced SIMD and floating-point instruc- tions as well as the Dot Product extension and the half-preci- sion floating-point fmla extension. +simd The ARMv8.3-A Advanced SIMD and floating-point instructions as well as the Dot Product extension. +crypto The cryptographic instructions. This also enables the Advanced SIMD and floating-point instructions as well as the Dot Product extension. +nocrypto Disable the cryptographic extension. +nofp Disable the floating-point, Advanced SIMD and cryptographic in- structions. +i8mm 8-bit Integer Matrix Multiply instructions. This also enables Advanced SIMD and floating-point instructions. +bf16 Brain half-precision floating-point instructions. This also enables Advanced SIMD and floating-point instructions. armv8.6-a +fp16 The half-precision floating-point data processing instructions. This also enables the Advanced SIMD and floating-point instruc- tions as well as the Dot Product extension and the half-preci- sion floating-point fmla extension. +simd The ARMv8.3-A Advanced SIMD and floating-point instructions as well as the Dot Product extension. +crypto The cryptographic instructions. This also enables the Advanced SIMD and floating-point instructions as well as the Dot Product extension. +nocrypto Disable the cryptographic extension. +nofp Disable the floating-point, Advanced SIMD and cryptographic in- structions. +i8mm 8-bit Integer Matrix Multiply instructions. This also enables Advanced SIMD and floating-point instructions. +bf16 Brain half-precision floating-point instructions. This also enables Advanced SIMD and floating-point instructions. armv7-r +fp.sp The single-precision VFPv3 floating-point instructions. The extension +vfpv3xd can be used as an alias for this extension. +fp The VFPv3 floating-point instructions with 16 double-precision registers. The extension +vfpv3-d16 can be used as an alias for this extension. +vfpv3xd-d16-fp16 The single-precision VFPv3 floating-point instructions with 16 double-precision registers and the half-precision float- ing-point conversion operations. +vfpv3-d16-fp16 The VFPv3 floating-point instructions with 16 double-precision registers and the half-precision floating-point conversion op- erations. +nofp Disable the floating-point extension. +idiv The ARM-state integer division instructions. +noidiv Disable the ARM-state integer division extension. armv7e-m +fp The single-precision VFPv4 floating-point instructions. +fpv5 The single-precision FPv5 floating-point instructions. +fp.dp The single- and double-precision FPv5 floating-point instruc- tions. +nofp Disable the floating-point extensions. armv8.1-m.main +dspThe DSP instructions. +mveThe M-Profile Vector Extension (MVE) integer instructions. +mve.fp The M-Profile Vector Extension (MVE) integer and single preci- sion floating-point instructions. +fp The single-precision floating-point instructions. +fp.dp The single- and double-precision floating-point instructions. +nofp Disable the floating-point extension. +cdecp0, +cdecp1, ... , +cdecp7 Enable the Custom Datapath Extension (CDE) on selected co- processors according to the numbers given in the options in the range 0 to 7. +pacbti Enable the Pointer Authentication and Branch Target Identifica- tion Extension. armv8-m.main +dspThe DSP instructions. +nodsp Disable the DSP extension. +fp The single-precision floating-point instructions. +fp.dp The single- and double-precision floating-point instructions. +nofp Disable the floating-point extension. +cdecp0, +cdecp1, ... , +cdecp7 Enable the Custom Datapath Extension (CDE) on selected co- processors according to the numbers given in the options in the range 0 to 7. armv8-r +crcThe Cyclic Redundancy Check (CRC) instructions. +fp.sp The single-precision FPv5 floating-point instructions. +simd The ARMv8-A Advanced SIMD and floating-point instructions. +crypto The cryptographic instructions. +nocrypto Disable the cryptographic instructions. +nofp Disable the floating-point, Advanced SIMD and cryptographic in- structions. -march=native causes the compiler to auto-detect the architecture of the build computer. At present, this feature is only supported on GNU/Linux, and not all architectures are recognized. If the auto-de- tect is unsuccessful the option has no effect. -march=unset causes the compiler to ignore any -march=... options that appear earlier on the command line and behave as if the option was never passed. This is useful to avoid warnings about conflicting CPU and architecture options when the two produce different architecture specifications. -mtune=name This option specifies the name of the target ARM processor for which GCC should tune the performance of the code. For some ARM implementa- tions better performance can be obtained by using this option. Permis- sible names are: arm7tdmi, arm7tdmi-s, arm710t, arm720t, arm740t, strongarm, strongarm110, strongarm1100, strongarm1110, arm8, arm810, arm9, arm9e, arm920, arm920t, arm922t, arm946e-s, arm966e-s, arm968e-s, arm926ej-s, arm940t, arm9tdmi, arm10tdmi, arm1020t, arm1026ej-s, arm10e, arm1020e, arm1022e, arm1136j-s, arm1136jf-s, mpcore, mpcoren- ovfp, arm1156t2-s, arm1156t2f-s, arm1176jz-s, arm1176jzf-s, generic-armv7-a, cortex-a5, cortex-a7, cortex-a8, cortex-a9, cor- tex-a12, cortex-a15, cortex-a17, cortex-a32, cortex-a35, cortex-a53, cortex-a55, cortex-a57, cortex-a72, cortex-a73, cortex-a75, cortex-a76, cortex-a76ae, cortex-a77, cortex-a78, cortex-a78ae, cortex-a78c, cor- tex-a710, ares, cortex-r4, cortex-r4f, cortex-r5, cortex-r7, cortex-r8, cortex-r52, cortex-r52plus, cortex-m0, cortex-m0plus, cortex-m1, cor- tex-m3, cortex-m4, cortex-m7, cortex-m23, cortex-m33, cortex-m35p, cor- tex-m52, cortex-m55, cortex-m85, cortex-x1, cortex-x1c, cor- tex-m1.small-multiply, cortex-m0.small-multiply, cor- tex-m0plus.small-multiply, exynos-m1, marvell-pj4, neoverse-n1, neo- verse-n2, neoverse-v1, xscale, iwmmxt, iwmmxt2, ep9312, fa526, fa626, fa606te, fa626te, fmp626, fa726te, star-mc1, star-mc3, xgene1. Additionally, this option can specify that GCC should tune the perfor- mance of the code for a big.LITTLE system. Permissible names are: cor- tex-a15.cortex-a7, cortex-a17.cortex-a7, cortex-a57.cortex-a53, cor- tex-a72.cortex-a53, cortex-a72.cortex-a35, cortex-a73.cortex-a53, cor- tex-a75.cortex-a55, cortex-a76.cortex-a55. -mtune=generic-arch specifies that GCC should tune the performance for a blend of processors within architecture arch. The aim is to generate code that run well on the current most popular processors, balancing between optimizations that benefit some CPUs in the range, and avoiding performance pitfalls of other CPUs. The effects of this option may change in future GCC versions as CPU models come and go. -mtune permits the same extension options as -mcpu, but the extension options do not affect the tuning of the generated code. -mtune=native causes the compiler to auto-detect the CPU of the build computer. At present, this feature is only supported on GNU/Linux, and not all architectures are recognized. If the auto-detect is unsuccess- ful the option has no effect. -mcpu=name[+extension...] This specifies the name of the target ARM processor. GCC uses this name to derive the name of the target ARM architecture (as if specified by -march) and the ARM processor type for which to tune for performance (as if specified by -mtune). Where this option is used in conjunction with -march or -mtune, those options take precedence over the appropri- ate part of this option. Many of the supported CPUs implement optional architectural extensions. Where this is so the architectural extensions are normally enabled by default. If implementations that lack the extension exist, then the extension syntax can be used to disable those extensions that have been omitted. For floating-point and Advanced SIMD (Neon) instructions, the settings of the options -mfloat-abi and -mfpu must also be considered: floating-point and Advanced SIMD instructions will only be used if -mfloat-abi is not set to soft; and any setting of -mfpu other than auto will override the available floating-point and SIMD extension in- structions. For example, cortex-a9 can be found in three major configurations: in- teger only, with just a floating-point unit or with floating-point and Advanced SIMD. The default is to enable all the instructions, but the extensions +nosimd and +nofp can be used to disable just the SIMD or both the SIMD and floating-point instructions respectively. Permissible names for this option are the same as those for -mtune. The following extension options are common to the listed CPUs: +nodsp Disable the DSP instructions on cortex-m33, cortex-m35p, cor- tex-m52, cortex-m55, cortex-m85 and star-mc3. Also disable the M-Profile Vector Extension (MVE) integer and single precision floating-point instructions on cortex-m52, cortex-m55, cortex-m85 and star-mc3. +nopacbti Disable the Pointer Authentication and Branch Target Identification Extension on cortex-m52, cortex-m85 and star-mc3. +nomve Disable the M-Profile Vector Extension (MVE) integer and single precision floating-point instructions on cortex-m52, cortex-m55, cortex-m85 and star-mc3. +nomve.fp Disable the M-Profile Vector Extension (MVE) single precision floating-point instructions on cortex-m52, cortex-m55, cortex-m85 and star-mc3. +cdecp0, +cdecp1, ... , +cdecp7 Enable the Custom Datapath Extension (CDE) on selected coprocessors according to the numbers given in the options in the range 0 to 7 on cortex-m52, cortex-m55, cortex-m85, star-mc1 and star-mc3. +nofp Disables the floating-point instructions on arm9e, arm946e-s, arm966e-s, arm968e-s, arm10e, arm1020e, arm1022e, arm926ej-s, arm1026ej-s, cortex-r5, cortex-r7, cortex-r8, cortex-m4, cortex-m7, cortex-m33, cortex-m35p, cortex-m52, cortex-m55, cortex-m85 and star-mc3. Disables the floating-point and SIMD instructions on generic-armv7-a, cortex-a5, cortex-a7, cortex-a8, cortex-a9, cor- tex-a12, cortex-a15, cortex-a17, cortex-a15.cortex-a7, cor- tex-a17.cortex-a7, cortex-a32, cortex-a35, cortex-a53 and cor- tex-a55. +nofp.dp Disables the double-precision component of the floating-point in- structions on cortex-r5, cortex-r7, cortex-r8, cortex-r52, cor- tex-r52plus and cortex-m7. +nosimd Disables the SIMD (but not floating-point) instructions on generic-armv7-a, cortex-a5, cortex-a7 and cortex-a9. +crypto Enables the cryptographic instructions on cortex-a32, cortex-a35, cortex-a53, cortex-a55, cortex-a57, cortex-a72, cortex-a73, cor- tex-a75, exynos-m1, xgene1, cortex-a57.cortex-a53, cortex-a72.cor- tex-a53, cortex-a73.cortex-a35, cortex-a73.cortex-a53 and cor- tex-a75.cortex-a55. Additionally the generic-armv7-a pseudo target defaults to VFPv3 with 16 double-precision registers. It supports the following extension op- tions: mp, sec, vfpv3-d16, vfpv3, vfpv3-d16-fp16, vfpv3-fp16, vfpv4-d16, vfpv4, neon, neon-vfpv3, neon-fp16, neon-vfpv4. The mean- ings are the same as for the extensions to -march=armv7-a. -mcpu=generic-arch is also permissible, and is equivalent to -march=arch -mtune=generic-arch. See -mtune for more information. -mcpu=native causes the compiler to auto-detect the CPU of the build computer. At present, this feature is only supported on GNU/Linux, and not all architectures are recognized. If the auto-detect is unsuccess- ful the option has no effect. -mcpu=unset causes the compiler to ignore any -mcpu=... options that appear earlier on the command line and behave as if the option was never passed. This is useful to avoid warnings about conflicting CPU and architecture options when the two produce different architecture specifications. -mfpu=name This specifies what floating-point hardware (or hardware emulation) is available on the target. Permissible names are: auto, vfpv2, vfpv3, vfpv3-fp16, vfpv3-d16, vfpv3-d16-fp16, vfpv3xd, vfpv3xd-fp16, neon-vfpv3, neon-fp16, vfpv4, vfpv4-d16, fpv4-sp-d16, neon-vfpv4, fpv5-d16, fpv5-sp-d16, fp-armv8, neon-fp-armv8 and crypto-neon-fp-armv8. Note that neon is an alias for neon-vfpv3 and vfp is an alias for vfpv2. The setting auto is the default and is special. It causes the compiler to select the floating-point and Advanced SIMD instructions based on the settings of -mcpu and -march. If the selected floating-point hardware includes the NEON extension (e.g. -mfpu=neon), note that floating-point operations are not gener- ated by GCC's auto-vectorization pass unless -funsafe-math-optimiza- tions is also specified. This is because NEON hardware does not fully implement the IEEE 754 standard for floating-point arithmetic (in par- ticular denormal values are treated as zero), so the use of NEON in- structions may lead to a loss of precision. You can also set the fpu name at function level by using the tar- get("fpu=") function attributes or pragmas. -mfp16-format=name Specify the format of the "__fp16" half-precision floating-point type. Permissible names are none, ieee, and alternative; the default is none, in which case the "__fp16" type is not defined. -mstructure-size-boundary=n The sizes of all structures and unions are rounded up to a multiple of the number of bits set by this option. Permissible values are 8, 32 and 64. The default value varies for different toolchains. For the COFF targeted toolchain the default value is 8. A value of 64 is only allowed if the underlying ABI supports it. Specifying a larger number can produce faster, more efficient code, but can also increase the size of the program. Different values are poten- tially incompatible. Code compiled with one value cannot necessarily expect to work with code or libraries compiled with another value, if they exchange information using structures or unions. This option is deprecated. -mabort-on-noreturn Generate a call to the function "abort" at the end of a "noreturn" function. It is executed if the function tries to return. -mlong-calls -mno-long-calls Tells the compiler to perform function calls by first loading the ad- dress of the function into a register and then performing a subroutine call on this register. This switch is needed if the target function lies outside of the 64-megabyte addressing range of the offset-based version of subroutine call instruction. Even if this switch is enabled, not all function calls are turned into long calls. The heuristic is that static functions, functions that have the "short_call" attribute, functions that are inside the scope of a "#pragma no_long_calls" directive, and functions whose definitions have already been compiled within the current compilation unit are not turned into long calls. The exceptions to this rule are that weak function definitions, functions with the "long_call" attribute or the "section" attribute, and functions that are within the scope of a "#pragma long_calls" directive are always turned into long calls. This feature is not enabled by default. Specifying -mno-long-calls re- stores the default behavior, as does placing the function calls within the scope of a "#pragma long_calls_off" directive. Note these switches have no effect on how the compiler generates code to handle function calls via function pointers. -msingle-pic-base Treat the register used for PIC addressing as read-only, rather than loading it in the prologue for each function. The runtime system is responsible for initializing this register with an appropriate value before execution begins. -mpic-register=reg Specify the register to be used for PIC addressing. For standard PIC base case, the default is any suitable register determined by compiler. For single PIC base case, the default is R9 if target is EABI based or stack-checking is enabled, otherwise the default is R10. -mpic-data-is-text-relative Assume that the displacement between the text and data segments is fixed at static link time. This permits using PC-relative addressing operations to access data known to be in the data segment. For non-Vx- Works RTP targets, this option is enabled by default. When disabled on such targets, it will enable -msingle-pic-base by default. -mpoke-function-name Write the name of each function into the text section, directly preced- ing the function prologue. The generated code is similar to this: 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 When performing a stack backtrace, code can inspect the value of "pc" stored at "fp + 0". If the trace function then looks at location "pc - 12" and the top 8 bits are set, then we know that there is a function name embedded immediately preceding this location and has length "((pc[-3]) & 0xff000000)". -mthumb -marm Select between generating code that executes in ARM and Thumb states. The default for most configurations is to generate code that executes in ARM state, but the default can be changed by configuring GCC with the --with-mode=state configure option. You can also override the ARM and Thumb mode for each function by using the target("thumb") and target("arm") function attributes or pragmas. -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 -mno-tpcs-frame. -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 -mno-apcs-leaf-frame. -mcallee-super-interworking Gives all externally visible functions in the file being compiled an ARM instruction set header which switches to Thumb mode before execut- ing the rest of the function. This allows these functions to be called from non-interworking code. This option is not valid in AAPCS configu- rations because interworking is enabled by default. -mcaller-super-interworking Allows calls via function pointers (including virtual functions) to ex- ecute correctly regardless of whether the target code has been compiled for interworking or not. There is a small overhead in the cost of exe- cuting a function pointer if this option is enabled. This option is not valid in AAPCS configurations because interworking is enabled by default. -mtp=name Specify the access model for the thread local storage pointer. The model soft generates calls to "__aeabi_read_tp". Other accepted models are tpidrurw, tpidruro and tpidrprw which fetch the thread pointer from the corresponding system register directly (supported from the arm6k architecture and later). These system registers are accessed through the CP15 co-processor interface and the argument cp15 is also accepted as a convenience alias of tpidruro. The argument auto uses the best available method for the selected processor. The default setting is auto. -mtls-dialect=dialect Specify the dialect to use for accessing thread local storage. Two di- alects are supported---gnu and gnu2. The gnu dialect selects the orig- inal GNU scheme for supporting local and global dynamic TLS models. The gnu2 dialect selects the GNU descriptor scheme, which provides bet- ter performance for shared libraries. The GNU descriptor scheme is compatible with the original scheme, but does require new assembler, linker and library support. Initial and local exec TLS models are un- affected by this option and always use the original scheme. -mword-relocations Only generate absolute relocations on word-sized values (i.e. R_ARM_ABS32). This is enabled by default on targets (uClinux, Sym- bianOS) where the runtime loader imposes this restriction, and when -fpic or -fPIC is specified. This option conflicts with -mslow-flash-data. -mfix-cortex-m3-ldrd Some Cortex-M3 cores can cause data corruption when "ldrd" instructions with overlapping destination and base registers are used. This option avoids generating these instructions. This option is enabled by de- fault when -mcpu=cortex-m3 is specified. -mfix-cortex-a57-aes-1742098 -mno-fix-cortex-a57-aes-1742098 -mfix-cortex-a72-aes-1655431 -mno-fix-cortex-a72-aes-1655431 Enable (disable) mitigation for an erratum on Cortex-A57 and Cortex-A72 that affects the AES cryptographic instructions. This option is en- abled by default when either -mcpu=cortex-a57 or -mcpu=cortex-a72 is specified. -munaligned-access -mno-unaligned-access Enables (or disables) reading and writing of 16- and 32- bit values from addresses that are not 16- or 32- bit aligned. By default un- aligned access is disabled for all pre-ARMv6, all ARMv6-M and for ARMv8-M Baseline architectures, and enabled for all other architec- tures. If unaligned access is not enabled then words in packed data structures are accessed a byte at a time. The ARM attribute "Tag_CPU_unaligned_access" is set in the generated object file to either true or false, depending upon the setting of this option. If unaligned access is enabled then the preprocessor symbol "__ARM_FEATURE_UNALIGNED" is also defined. -mslow-flash-data Assume loading data from flash is slower than fetching instruction. Therefore literal load is minimized for better performance. This op- tion is only supported when compiling for ARMv7 M-profile and off by default. It conflicts with -mword-relocations. -masm-syntax-unified Assume inline assembler is using unified asm syntax. The default is currently off which implies divided syntax. This option has no impact on Thumb2. However, this may change in future releases of GCC. Divided syntax should be considered deprecated. -mrestrict-it Restricts generation of IT blocks to conform to the rules of ARMv8-A. IT blocks can only contain a single 16-bit instruction from a select set of instructions. This option is on by default for ARMv8-A Thumb mode. -mpure-code Do not allow constant data to be placed in code sections. Addition- ally, when compiling for ELF object format give all text sections the ELF processor-specific section attribute "SHF_ARM_PURECODE". This op- tion is only available when generating non-pic code for M-profile tar- gets. -mcmse Generate secure code as per the "ARMv8-M Security Extensions: Require- ments on Development Tools Engineering Specification", which can be found on <https://developer.arm.com/documentation/ecm0359818/latest/>. -mfix-cmse-cve-2021-35465 Mitigate against a potential security issue with the "VLLDM" instruc- tion in some M-profile devices when using CMSE (CVE-2021-35465). This option is enabled by default when the option -mcpu= is used with "cor- tex-m33", "cortex-m35p", "cortex-m55", "cortex-m85" or "star-mc1". The option -mno-fix-cmse-cve-2021-35465 can be used to disable the mitiga- tion. -mstack-protector-guard=guard -mstack-protector-guard-offset=offset Generate stack protection code using canary at guard. Supported loca- tions are global for a global canary or tls for a canary accessible via the TLS register. The option -mstack-protector-guard-offset= is for use with -fstack-protector-guard=tls and not for use in user-land code. -mfdpic -mno-fdpic Select the FDPIC ABI, which uses 64-bit function descriptors to repre- sent pointers to functions. When the compiler is configured for "arm-*-uclinuxfdpiceabi" targets, this option is on by default and im- plies -fPIE if none of the PIC/PIE-related options is provided. On other targets, it only enables the FDPIC-specific code generation fea- tures, and the user should explicitly provide the PIC/PIE-related op- tions as needed. Note that static linking is not supported because it would still in- volve the dynamic linker when the program self-relocates. If such be- havior is acceptable, use -static and -Wl,-dynamic-linker options. The opposite -mno-fdpic option is useful (and required) to build the Linux kernel using the same ("arm-*-uclinuxfdpiceabi") toolchain as the one used to build the userland programs. -mbranch-protection=features Enable branch protection features (armv8.1-m.main only). features can have one of the following forms: none generates code without branch protection or return address sign- ing. standard generates code with all branch protection features enabled at their standard level. pac-ret generates code with return address signing set to its standard level, which is to sign all functions that save the return address to memory. pac-ret+leaf extends the pac-ret signing to include leaf functions even if they do not write the return address to memory. bti adds landing-pad instructions at the permitted targets of indirect branch instructions. If support for the +pacbti architecture extension is not enabled (e.g. via -march=), then all branch protection and return address signing op- erations are constrained to use only the instructions defined in the architectural-NOP space. The generated code remains backwards-compati- ble with earlier versions of the architecture, but the additional secu- rity can be enabled at run time on processors that support the PACBTI extension. Branch target enforcement using BTI can only be enabled at runtime if all code in the application has been compiled with at least -mbranch-protection=bti. Any setting other than none is supported only on armv8-m.main or later. The default is to generate code without branch protection or return ad- dress signing. -mvectorize-with-neon-quad -mvectorize-with-neon-double Control whether vectorization uses NEON quad-word or double-word regis- ters. The default is -mvectorize-with-neon-quad. AVR Options These options are defined for AVR implementations: -mmcu=mcu Specify the AVR instruction set architecture (ISA) or device type. The default for this option is "avr2". The following AVR devices and ISAs are supported. Note: A complete de- vice support consists of startup code "crtmcu.o", a device header "avr/io*.h", a device library "libmcu.a" and a device-specs file "specs-mcu". Only the latter is provided by the compiler according the supported "mcu"s below. The rest is supported by AVR-LibC, or by means of "atpack" files from the hardware manufacturer. "avr2" "Classic" devices with up to 8 KiB of program memory. mcu = "at- tiny22", "attiny26", "at90s2313", "at90s2323", "at90s2333", "at90s2343", "at90s4414", "at90s4433", "at90s4434", "at90c8534", "at90s8515", "at90s8535". "avr25" "Classic" devices with up to 8 KiB of program memory and with the "MOVW" instruction. mcu = "attiny13", "attiny13a", "attiny24", "attiny24a", "attiny25", "attiny261", "attiny261a", "attiny2313", "attiny2313a", "attiny43u", "attiny44", "attiny44a", "attiny45", "attiny48", "attiny441", "attiny461", "attiny461a", "attiny4313", "attiny84", "attiny84a", "attiny85", "attiny87", "attiny88", "at- tiny828", "attiny841", "attiny861", "attiny861a", "ata5272", "ata6616c", "at86rf401". "avr3" "Classic" devices with 16 KiB up to 64 KiB of program memory. mcu = "at76c711", "at43usb355". "avr31" "Classic" devices with 128 KiB of program memory. mcu = "at- mega103", "at43usb320". "avr35" "Classic" devices with 16 KiB up to 64 KiB of program memory and with the "MOVW" instruction. mcu = "attiny167", "attiny1634", "at- mega8u2", "atmega16u2", "atmega32u2", "ata5505", "ata6617c", "ata664251", "at90usb82", "at90usb162". "avr4" "Enhanced" devices with up to 8 KiB of program memory. mcu = "at- mega48", "atmega48a", "atmega48p", "atmega48pa", "atmega48pb", "at- mega8", "atmega8a", "atmega8hva", "atmega88", "atmega88a", "at- mega88p", "atmega88pa", "atmega88pb", "atmega8515", "atmega8535", "ata5795", "ata6285", "ata6286", "ata6289", "ata6612c", "at90pwm1", "at90pwm2", "at90pwm2b", "at90pwm3", "at90pwm3b", "at90pwm81". "avr5" "Enhanced" devices with 16 KiB up to 64 KiB of program memory. mcu = "atmega16", "atmega16a", "atmega16hva", "atmega16hva2", "at- mega16hvb", "atmega16hvbrevb", "atmega16m1", "atmega16u4", "at- mega161", "atmega162", "atmega163", "atmega164a", "atmega164p", "atmega164pa", "atmega165", "atmega165a", "atmega165p", "at- mega165pa", "atmega168", "atmega168a", "atmega168p", "atmega168pa", "atmega168pb", "atmega169", "atmega169a", "atmega169p", "at- mega169pa", "atmega32", "atmega32a", "atmega32c1", "atmega32hvb", "atmega32hvbrevb", "atmega32m1", "atmega32u4", "atmega32u6", "at- mega323", "atmega324a", "atmega324p", "atmega324pa", "atmega324pb", "atmega325", "atmega325a", "atmega325p", "atmega325pa", "at- mega328", "atmega328p", "atmega328pb", "atmega329", "atmega329a", "atmega329p", "atmega329pa", "atmega3250", "atmega3250a", "at- mega3250p", "atmega3250pa", "atmega3290", "atmega3290a", "at- mega3290p", "atmega3290pa", "atmega406", "atmega64", "atmega64a", "atmega64c1", "atmega64hve", "atmega64hve2", "atmega64m1", "at- mega64rfr2", "atmega640", "atmega644", "atmega644a", "atmega644p", "atmega644pa", "atmega644rfr2", "atmega645", "atmega645a", "at- mega645p", "atmega649", "atmega649a", "atmega649p", "atmega6450", "atmega6450a", "atmega6450p", "atmega6490", "atmega6490a", "at- mega6490p", "ata5790", "ata5790n", "ata5791", "ata6613c", "ata6614q", "ata5782", "ata5831", "ata8210", "ata8510", "ata5787", "ata5835", "ata5700m322", "ata5702m322", "at90pwm161", "at90pwm216", "at90pwm316", "at90can32", "at90can64", "at90scr100", "at90usb646", "at90usb647", "at94k", "m3000". "avr51" "Enhanced" devices with 128 KiB of program memory. mcu = "at- mega128", "atmega128a", "atmega128rfa1", "atmega128rfr2", "at- mega1280", "atmega1281", "atmega1284", "atmega1284p", "at- mega1284rfr2", "at90can128", "at90usb1286", "at90usb1287". "avr6" "Enhanced" devices with 3-byte PC, i.e. with more than 128 KiB of program memory. mcu = "atmega256rfr2", "atmega2560", "atmega2561", "atmega2564rfr2". "avrxmega2" "XMEGA" devices with more than 8 KiB and up to 64 KiB of program memory. mcu = "atxmega8e5", "atxmega16a4", "atxmega16a4u", "atxmega16c4", "atxmega16d4", "atxmega16e5", "atxmega32a4", "atxmega32a4u", "atxmega32c3", "atxmega32c4", "atxmega32d3", "atxmega32d4", "atxmega32e5", "avr64da28", "avr64da28s", "avr64da32", "avr64da32s", "avr64da48", "avr64da48s", "avr64da64", "avr64da64s", "avr64db28", "avr64db32", "avr64db48", "avr64db64", "avr64dd14", "avr64dd20", "avr64dd28", "avr64dd32", "avr64du28", "avr64du32", "avr64ea28", "avr64ea32", "avr64ea48", "avr64sd28", "avr64sd32", "avr64sd48". "avrxmega3" "XMEGA" devices with up to 64 KiB of combined program memory and RAM, and with program memory visible in the RAM address space. mcu = "attiny202", "attiny204", "attiny212", "attiny214", "attiny402", "attiny404", "attiny406", "attiny412", "attiny414", "attiny416", "attiny416auto", "attiny417", "attiny424", "attiny426", "at- tiny427", "attiny804", "attiny806", "attiny807", "attiny814", "at- tiny816", "attiny817", "attiny824", "attiny826", "attiny827", "at- tiny1604", "attiny1606", "attiny1607", "attiny1614", "attiny1616", "attiny1617", "attiny1624", "attiny1626", "attiny1627", "at- tiny3214", "attiny3216", "attiny3217", "attiny3224", "attiny3226", "attiny3227", "atmega808", "atmega809", "atmega1608", "atmega1609", "atmega3208", "atmega3209", "atmega4808", "atmega4809", "avr16dd14", "avr16dd20", "avr16dd28", "avr16dd32", "avr16du14", "avr16du20", "avr16du28", "avr16du32", "avr16ea28", "avr16ea32", "avr16ea48", "avr16eb14", "avr16eb20", "avr16eb28", "avr16eb32", "avr16la14", "avr16la20", "avr16la28", "avr16la32", "avr32da28", "avr32da28s", "avr32da32", "avr32da32s", "avr32da48", "avr32da48s", "avr32db28", "avr32db32", "avr32db48", "avr32dd14", "avr32dd20", "avr32dd28", "avr32dd32", "avr32du14", "avr32du20", "avr32du28", "avr32du32", "avr32ea28", "avr32ea32", "avr32ea48", "avr32eb14", "avr32eb20", "avr32eb28", "avr32eb32", "avr32la14", "avr32la20", "avr32la28", "avr32la32", "avr32sd20", "avr32sd28", "avr32sd32". "avrxmega4" "XMEGA" devices with more than 64 KiB and up to 128 KiB of program memory. mcu = "atxmega64a3", "atxmega64a3u", "atxmega64a4u", "atxmega64b1", "atxmega64b3", "atxmega64c3", "atxmega64d3", "atxmega64d4", "avr128da28", "avr128da28s", "avr128da32", "avr128da32s", "avr128da48", "avr128da48s", "avr128da64", "avr128da64s", "avr128db28", "avr128db32", "avr128db48", "avr128db64". "avrxmega5" "XMEGA" devices with more than 64 KiB and up to 128 KiB of program memory and more than 64 KiB of RAM. mcu = "atxmega64a1", "atxmega64a1u". "avrxmega6" "XMEGA" devices with more than 128 KiB of program memory. mcu = "atxmega128a3", "atxmega128a3u", "atxmega128b1", "atxmega128b3", "atxmega128c3", "atxmega128d3", "atxmega128d4", "atxmega192a3", "atxmega192a3u", "atxmega192c3", "atxmega192d3", "atxmega256a3", "atxmega256a3b", "atxmega256a3bu", "atxmega256a3u", "atxmega256c3", "atxmega256d3", "atxmega384c3", "atxmega384d3". "avrxmega7" "XMEGA" devices with more than 128 KiB of program memory and more than 64 KiB of RAM. mcu = "atxmega128a1", "atxmega128a1u", "atxmega128a4u". "avrtiny" "Reduced Tiny" Tiny core devices with only 16 general purpose reg- isters and 512 B up to 4 KiB of program memory. mcu = "attiny4", "attiny5", "attiny9", "attiny10", "attiny102", "attiny104", "at- tiny20", "attiny40". "avr1" This ISA is implemented by the minimal AVR core and supported for assembler only. mcu = "attiny11", "attiny12", "attiny15", "at- tiny28", "at90s1200". -mabsdata Assume that all data in static storage can be accessed by LDS / STS in- structions. This option has only an effect on reduced Tiny devices like ATtiny40. See also the "absdata" AVR Attributes,variable at- tribute. -masm-len-notes -mno-asm-len-notes Recognize resp. ignore "[[len=spec]]" notes that are placed in (com- ments in) inline assembly code templates. They allow to specify the exact Size of an asm,,size of "asm" constructs. This option is on per default. -mcvt Use a compact vector table. Some devices support a CVT with only four entries: 0=Reset, 1=NMI, 2=Prio1 IRQ, 3=Prio0 IRQs. This option will link startup code from "crtmcu-cvt.o" instead of the usual "crtmcu.o". Apart from providing a compact vector table, the startup code will set bit "CPUINT_CTRLA.CPUINT_CVT" which enables the CVT on the device. When you do not want the startup code to set "CPUINT_CTRLA.CPUINT_CVT", then you can satisfy symbol "__init_cvt" so that the respective code is no more pulled in from "libmcu.a". For example, you can link with "-Wl,--defsym,__init_cvt=0". The CVT startup code is available since AVR-LibC v2.3. -mdouble=bits -mlong-double=bits Set the size (in bits) of the "double" or "long double" type, respec- tively. Possible values for bits are 32 and 64. Whether or not a spe- cific value for bits is allowed depends on the "--with-double=" and "--with-long-double=" configure options, and the same applies for the default values of the options. -mgas-isr-prologues Interrupt service routines (ISRs) may use the "__gcc_isr" pseudo in- struction supported by GNU Binutils. If this option is on, the feature can still be disabled for individual ISRs by means of the AVR Attrib- utes,,"no_gccisr" function attribute. This feature is activated per default if optimization is on (but not with -Og, @pxref{Optimize Op- tions}), and if GNU Binutils support PR21683. -mint8 Assume "int" to be 8-bit integer. This affects the sizes of all types: a "char" is 1 byte, an "int" is 1 byte, a "long" is 2 bytes, and "long long" is 4 bytes. Please note that this option does not conform to the C standards, but it results in smaller code size. -mmain-is-OS_task Do not save registers in "main". The effect is the same like attaching attribute AVR Attributes,,"OS_task" to "main". It is activated per de- fault if optimization is on. -mno-call-main Don't run "main" by means of XCALL main XJMP exit Instead, put "main" in section ".init9" so that no call is required. By setting this option the user asserts that "main" will not return. This option can be used for devices with very limited resources in or- der to save a few bytes of code and stack space. It will work as ex- pected since AVR-LibC v2.3. With older versions, there will be no per- formance gain. -mno-interrupts Generated code is not compatible with hardware interrupts. Code size is smaller. -mrelax Try to replace "CALL" resp. "JMP" instruction by the shorter "RCALL" resp. "RJMP" instruction if applicable. Setting -mrelax just adds the --mlink-relax option to the assembler's command line and the --relax option to the linker's command line. Jump relaxing is performed by the linker because jump offsets are not known before code is located. Therefore, the assembler code generated by the compiler is the same, but the instructions in the executable may differ from instructions in the assembler code. Relaxing must be turned on if linker stubs are needed, see the section on "EIND" and linker stubs below. -mpmem-wrap-around Enable program counter wrap-around in linker relaxation. -mrodata-in-ram -mno-rodata-in-ram Locate the ".rodata" sections for read-only data in RAM resp. in pro- gram memory. For most devices, there is no choice and this option acts rather like an assertion. Since v14 and for the AVR64* and AVR128* devices, ".rodata" is located in flash memory per default, provided the required GNU Binutils support (PR31124) is available. In that case, -mrodata-in-ram can be used to return to the old layout with ".rodata" in RAM. -mtiny-stack Only change the lower 8 bits of the stack pointer. -mfract-convert-truncate Allow to use truncation instead of rounding towards zero for fractional fixed-point types. -nodevicelib Don't link against AVR-LibC's device specific library "libmcu.a". Notice that since AVR-LibC v2.3, that library contains code that is es- sential for the correct functioning of a program. In particular, it contains parts of the startup code like: "__init_sp" to initialize the stack pointer with symbol "__stack", "__init_cvt" to set up the hard- ware to use a compact vector table with -mcvt, "__call_main" to call "main" and "exit", and "__do_flmap_init" to set up FLMAP according to symbol "__flmap". -nodevicespecs Don't add -specs=device-specs/specs-mcu to the compiler driver's com- mand line. The user takes responsibility for supplying the sub-processes like compiler proper, assembler and linker with appropri- ate command-line options. This means that the user has to supply her private device specs file by means of -specs=path-to-specs-file. There is no more need for option -mmcu=mcu. This option can also serve as a replacement for the older way of speci- fying custom device-specs files that needed -B some-path to point to a directory which contains a folder named "device-specs" which contains a specs file named "specs-mcu", where mcu was specified by -mmcu=mcu. -Waddr-space-convert Warn about conversions between address spaces in the case where the re- sulting address space is not contained in the incoming address space. -Wasm-len-notes Warn about unrecognized "[[len=spec]]" Size of an asm,,length annota- tions in inline assembly code templates. This Warning Options,,warning is on per default. Notice that in LTO mode, the code must be compiled with option -ffat-lto-objects in order for these diagnoses to appear. -Wmisspelled-isr Warn if the ISR is misspelled, i.e. without __vector prefix. Enabled by default. AVR Optimization Options The following options are pure optimization options. Options -mgas-isr-prologues, -mmain-is-OS_task, -mno-call-main and -mrelax from above are only almost optimization options, since there are rare occasions where their different code generation matters. -maccumulate-args Accumulate outgoing function arguments and acquire/release the needed stack space for outgoing function arguments once in function pro- logue/epilogue. Without this option, outgoing arguments are pushed be- fore calling a function and popped afterwards. See also the -fde- fer-pop Optimize Options,,optimization option. Popping the arguments after the function call can be expensive on AVR so that accumulating the stack space might lead to smaller executables because arguments need not be removed from the stack after such a func- tion call. This option can lead to reduced code size for functions that perform several calls to functions that get their arguments on the stack like calls to printf-like functions. -mbranch-cost=cost Set the branch costs for conditional branch instructions to cost. Rea- sonable values for cost are small, non-negative integers. The default branch cost is 0. -mcall-prologues Functions prologues/epilogues are expanded as calls to appropriate sub- routines. Code size is smaller. -mfuse-add -mno-fuse-add -mfuse-add=level Optimize indirect memory accesses on reduced Tiny devices. The default uses "level=1" for optimizations -Og and -O1, and "level=2" for higher optimizations. Valid values for level are 0, 1 and 2. -mfuse-move -mno-fuse-move -mfuse-move=level Run a post reload optimization pass that tries to fuse move instruc- tions and to split multi-byte instructions into 8-bit operations. The default uses "level=3" for optimization -O1, and "level=23" for higher optimizations. Valid values for level are in the range 0 ... 23 which is a 3:2:2:2 mixed radix value. Each digit controls some aspect of the optimization. -mfuse-move2 Run a post combine optimization pass that tries to fuse move instruc- tions. -mstrict-X Use address register "X" in a way proposed by the hardware. This means that "X" is only used in indirect, post-increment or pre-decrement ad- dressing. Without this option, the "X" register may be used in the same way as "Y" or "Z" which then is emulated by additional instructions. For ex- ample, loading a value with "X+const" addressing with a small non-nega- tive "const < 64" to a register Rn is performed as adiw r26, const ; X += const ld <Rn>, X ; <Rn> = *X sbiw r26, const ; X -= const -msplit-bit-shift Split multi-byte shifts with a constant offset into a shift with a byte offset and a residual shift with a non-byte offset. This optimization is turned on per default for -O2 and higher, including -Os but exclud- ing -Oz. Splitting of shifts with a constant offset that is a multiple of 8 is controlled by -mfuse-move. -msplit-ldst Split multi-byte loads and stores into several byte loads and stores. This optimization is turned on per default for -O2 and higher. -muse-nonzero-bits Enable optimizations that are only possible when some bits in a regis- ter are always zero. This optimization is turned on per default for -O2 and higher. "EIND" and Devices with More Than 128 Ki Bytes of Flash Pointers in the implementation are 16 bits wide. The address of a function or label is represented as word address so that indirect jumps and calls can target any code address in the range of 64 Ki words. In order to facilitate indirect jump on devices with more than 128 Ki bytes of program memory space, there is a special function register called "EIND" that serves as most significant part of the target address when "EICALL" or "EIJMP" instructions are used. Indirect jumps and calls on these devices are handled as follows by the compiler and are subject to some limitations: * The compiler never sets "EIND". * The compiler uses "EIND" implicitly in "EICALL"/"EIJMP" instructions or might read "EIND" directly in order to emulate an indirect call/jump by means of a "RET" instruction. * The compiler assumes that "EIND" never changes during the startup code or during the application. In particular, "EIND" is not saved/restored in function or interrupt service routine prologue/epilogue. * For indirect calls to functions and computed goto, the linker generates stubs. Stubs are jump pads sometimes also called trampolines. Thus, the indirect call/jump jumps to such a stub. The stub contains a direct jump to the desired address. * Linker relaxation must be turned on so that the linker generates the stubs correctly in all situations. See the compiler option -mrelax and the linker option --relax. There are corner cases where the linker is supposed to generate stubs but aborts without relaxation and without a helpful error message. * The default linker script is arranged for code with "EIND = 0". If code is supposed to work for a setup with "EIND != 0", a custom linker script has to be used in order to place the sections whose name start with ".trampolines" into the segment where "EIND" points to. * The startup code from libgcc never sets "EIND". Notice that startup code is a blend of code from libgcc and AVR-LibC. For the impact of AVR-LibC on "EIND", see the AVR-LibC user manual. * It is legitimate for user-specific startup code to set up "EIND" early, for example by means of initialization code located in section ".init3". Such code runs prior to general startup code that initializes RAM and calls constructors, but after the bit of startup code from AVR-LibC that sets "EIND" to the segment where the vector table is lo- cated. #include <avr/io.h> static void __attribute__((section(".init3"),naked,used,no_instrument_function)) init3_set_eind (void) { __asm volatile ("ldi r24,pm_hh8(__trampolines_start)\n\t" "out %i0,r24" :: "n" (&EIND) : "r24","memory"); } The "__trampolines_start" symbol is defined in the linker script. * Stubs are generated automatically by the linker if the following two conditions are met: -<The address of a label is taken by means of the "gs" modifier> (short for generate stubs) like so: LDI r24, lo8(gs(<func>)) LDI r25, hi8(gs(<func>)) -<The final location of that label is in a code segment> outside the segment where the stubs are located. * The compiler emits such "gs" modifiers for code labels in the following situations: -<Taking address of a function or code label.> -<Computed goto.> -<If prologue-save function is used, see -mcall-prologues> command-line option. -<Switch/case dispatch tables. If you do not want such dispatch> tables you can specify the -fno-jump-tables command-line option. -<C and C++ constructors/destructors called during startup/shutdown.> -<If the tools hit a gs() modifier explained above.> * Jumping to non-symbolic addresses like so is not supported: int main (void) { /* Call function at word address 0x2 */ return ((int(*)(void)) 0x2)(); } Instead, a stub has to be set up, i.e. the function has to be called through a symbol ("func_4" in the example): int main (void) { extern int func_4 (void); /* Call function at byte address 0x4 */ return func_4(); } and the application be linked with -Wl,--defsym,func_4=0x4. Alterna- tively, "func_4" can be defined in the linker script. Handling of the "RAMPD", "RAMPX", "RAMPY" and "RAMPZ" Special Function Reg- isters Some AVR devices support memories larger than the 64 KiB range that can be accessed with 16-bit pointers. To access memory locations outside this 64 KiB range, the content of a "RAMP" register is used as high part of the ad- dress: The "X", "Y", "Z" address register is concatenated with the "RAMPX", "RAMPY", "RAMPZ" special function register, respectively, to get a wide ad- dress. Similarly, "RAMPD" is used together with direct addressing. * The startup code initializes the "RAMP" special function registers with zero. * If a AVR Named Address Spaces,,named address space other than generic or "__flash" is used, then "RAMPZ" is set as needed before the opera- tion. * If the device supports RAM larger than 64 KiB and the compiler needs to change "RAMPZ" to accomplish an operation, "RAMPZ" is reset to zero af- ter the operation. * If the device comes with a specific "RAMP" register, the ISR pro- logue/epilogue saves/restores that SFR and initializes it with zero in case the ISR code might (implicitly) use it. * RAM larger than 64 KiB is not supported by GCC for AVR targets. If you use inline assembler to read from locations outside the 16-bit address range and change one of the "RAMP" registers, you must reset it to zero after the access. AVR Built-in Macros GCC defines several built-in macros so that the user code can test for the presence or absence of features. Almost any of the following built-in macros are deduced from device capabilities and thus triggered by the -mmcu= command-line option. For even more AVR-specific built-in macros see AVR Named Address Spaces and AVR Built-in Functions. "__AVR_ARCH__" Build-in macro that resolves to a decimal number that identifies the architecture and depends on the -mmcu=mcu option. Possible values are: 2, 25, 3, 31, 35, 4, 5, 51, 6 for mcu="avr2", "avr25", "avr3", "avr31", "avr35", "avr4", "avr5", "avr51", "avr6", respectively and 100, 102, 103, 104, 105, 106, 107 for mcu="avrtiny", "avrxmega2", "avrxmega3", "avrxmega4", "avrxmega5", "avrxmega6", "avrxmega7", respectively. If mcu specifies a device, this built-in macro is set accordingly. For example, with -mmcu=atmega8 the macro is defined to 4. "__AVR_Device__" Setting -mmcu=device defines this built-in macro which reflects the de- vice's name. For example, -mmcu=atmega8 defines the built-in macro "__AVR_ATmega8__", -mmcu=attiny261a defines "__AVR_ATtiny261A__", etc. The built-in macros' names follow the scheme "__AVR_Device__" where De- vice is the device name as from the AVR user manual. The difference be- tween Device in the built-in macro and device in -mmcu=device is that the latter is always lowercase. If device is not a device but only a core architecture like avr51, this macro is not defined. "__AVR_DEVICE_NAME__" Setting -mmcu=device defines this built-in macro to the device's name. For example, with -mmcu=atmega8 the macro is defined to "atmega8". If device is not a device but only a core architecture like avr51, this macro is not defined. "__AVR_CVT__" The code is being compiled with option "-mcvt" to use a compact vector table. "__AVR_XMEGA__" The device / architecture belongs to the XMEGA family of devices. "__AVR_HAVE_ADIW__" The device has the "ADIW" and "SBIW" instructions. "__AVR_HAVE_ELPM__" The device has the "ELPM" instruction. "__AVR_HAVE_ELPMX__" The device has the "ELPM Rn,Z" and "ELPM Rn,Z+" instructions. "__AVR_HAVE_LPMX__" The device has the "LPM Rn,Z" and "LPM Rn,Z+" instructions. "__AVR_HAVE_MOVW__" The device has the "MOVW" instruction to perform 16-bit register-regis- ter moves. "__AVR_HAVE_MUL__" The device has a hardware multiplier. "__AVR_HAVE_JMP_CALL__" The device has the "JMP" and "CALL" instructions. This is the case for devices with more than 8 KiB of program memory. "__AVR_HAVE_EIJMP_EICALL__" "__AVR_3_BYTE_PC__" The device has the "EIJMP" and "EICALL" instructions. This is the case for devices with more than 128 KiB of program memory. This also means that the program counter (PC) is 3 bytes wide. "__AVR_2_BYTE_PC__" The program counter (PC) is 2 bytes wide. This is the case for devices with up to 128 KiB of program memory. "__AVR_HAVE_8BIT_SP__" "__AVR_HAVE_16BIT_SP__" The stack pointer (SP) register is treated as 8-bit respectively 16-bit register by the compiler. The definition of these macros is affected by -mtiny-stack. "__AVR_HAVE_SPH__" "__AVR_SP8__" The device has the SPH (high part of stack pointer) special function register or has an 8-bit stack pointer, respectively. The definition of these macros is affected by -mmcu= and in the cases of -mmcu=avr2 and -mmcu=avr25 also by -msp8. "__AVR_HAVE_RAMPD__" "__AVR_HAVE_RAMPX__" "__AVR_HAVE_RAMPY__" "__AVR_HAVE_RAMPZ__" The device has the "RAMPD", "RAMPX", "RAMPY", "RAMPZ" special function register, respectively. "__NO_INTERRUPTS__" This macro reflects the -mno-interrupts command-line option. "__AVR_ERRATA_SKIP__" "__AVR_ERRATA_SKIP_JMP_CALL__" Some AVR devices (AT90S8515, ATmega103) must not skip 32-bit instruc- tions because of a hardware erratum. Skip instructions are "SBRS", "SBRC", "SBIS", "SBIC" and "CPSE". The second macro is only defined if "__AVR_HAVE_JMP_CALL__" is also set. "__AVR_ISA_RMW__" The device has Read-Modify-Write instructions (XCH, LAC, LAS and LAT). "__AVR_SFR_OFFSET__=offset" Instructions that can address I/O special function registers directly like "IN", "OUT", "SBI", etc. may use a different address as if ad- dressed by an instruction to access RAM like "LD" or "STS". This offset depends on the device architecture and has to be subtracted from the RAM address in order to get the respective I/O address. "__AVR_SHORT_CALLS__" The -mshort-calls command-line option is set. "__AVR_PM_BASE_ADDRESS__=addr" Some devices support reading from flash memory by means of "LD*" in- structions. The flash memory is seen in the data address space at an offset of "__AVR_PM_BASE_ADDRESS__". If this macro is not defined, this feature is not available. If defined, the address space is linear and there is no need to put ".rodata" into RAM. This is handled by the default linker description file, and is currently available for "avrtiny" and "avrxmega3". Even more convenient, there is no need to use address spaces like "__flash" or features like attribute "progmem" and "pgm_read_*". "__AVR_HAVE_FLMAP__" This macro is defined provided the following conditions are met: *<The device has the "NVMCTRL_CTRLB.FLMAP" bitfield.> This applies to the AVR64* and AVR128* devices. *<It's not known at assembler-time which emulation will be used.> This implies the compiler was configured with GNU Binutils that imple- ment PR31124. "__AVR_RODATA_IN_RAM__" This macro is undefined when the code is compiled for a core architec- ture. When the code is compiled for a device, the macro is defined to 1 when the ".rodata" sections for read-only data is located in RAM; and de- fined to 0, otherwise. "__WITH_AVRLIBC__" The compiler is configured to be used together with AVR-LibC. See the --with-avrlibc configure option. "__HAVE_SIGNAL_N__" The compiler supports the signal(num) and interrupt(num) AVR Attrib- utes,,function attributes with an argument num that specifies the num- ber of the interrupt service routine. "__HAVE_DOUBLE_MULTILIB__" Defined if -mdouble= acts as a multilib option. "__HAVE_DOUBLE32__" "__HAVE_DOUBLE64__" Defined if the compiler supports 32-bit double resp. 64-bit double. The actual layout is specified by option -mdouble=. "__DEFAULT_DOUBLE__" The size in bits of "double" if -mdouble= is not set. To test the lay- out of "double" in a program, use the built-in macro "__SIZEOF_DOU- BLE__". "__HAVE_LONG_DOUBLE32__" "__HAVE_LONG_DOUBLE64__" "__HAVE_LONG_DOUBLE_MULTILIB__" "__DEFAULT_LONG_DOUBLE__" Same as above, but for "long double" instead of "double". "__WITH_DOUBLE_COMPARISON__" Reflects the "--with-double-comparison={tristate|bool|libf7}" config- ure option and is defined to 2 or 3. "__WITH_LIBF7_LIBGCC__" "__WITH_LIBF7_MATH__" "__WITH_LIBF7_MATH_SYMBOLS__" Reflects the "--with-libf7={libgcc|math|math-symbols}" configure op- tion. AVR Internal Options The following options are used internally by the compiler and to communi- cate between device specs files and the compiler proper. You don't need to set these options by hand, in particular they are not optimization options. Using these options in the wrong way may lead to sub-optimal or wrong code. They are documented for completeness, and in order to get a better under- standing of device specs files. -mn-flash=num Assume that the flash memory has a size of num times 64 KiB. This de- termines which "__flashN" address spaces are available. -mflmap The device has the "FLMAP" bit field located in special function regis- ter "NVMCTRL_CTRLB". -mrmw Assume that the device supports the Read-Modify-Write instructions "XCH", "LAC", "LAS" and "LAT". -mshort-calls Assume that "RJMP" and "RCALL" can target the whole program memory. This option is used for multilib generation and selection for the de- vices from architecture "avrxmega3". -mskip-bug Generate code without skips ("CPSE", "SBRS", "SBRC", "SBIS", "SBIC") over 32-bit instructions. -msp8 Treat the stack pointer register as an 8-bit register, i.e. assume the high byte of the stack pointer is zero. This option is used by the compiler to select and build multilibs for architectures "avr2" and "avr25". These architectures mix devices with and without "SPH". Blackfin Options -mcpu=cpu[-sirevision] Specifies the name of the target Blackfin processor. Currently, cpu can be one of bf512, bf514, bf516, bf518, bf522, bf523, bf524, bf525, bf526, bf527, bf531, bf532, bf533, bf534, bf536, bf537, bf538, bf539, bf542, bf544, bf547, bf548, bf549, bf542m, bf544m, bf547m, bf548m, bf549m, bf561, bf592. The optional sirevision specifies the silicon revision of the target Blackfin processor. Any workarounds available for the targeted silicon revision are enabled. If sirevision is none, no workarounds are en- abled. If sirevision is any, all workarounds for the targeted proces- sor are enabled. The "__SILICON_REVISION__" macro is defined to two hexadecimal digits representing the major and minor numbers in the sil- icon revision. If sirevision is none, the "__SILICON_REVISION__" is not defined. If sirevision is any, the "__SILICON_REVISION__" is de- fined to be 0xffff. If this optional sirevision is not used, GCC as- sumes the latest known silicon revision of the targeted Blackfin processor. GCC defines a preprocessor macro for the specified cpu. For the bfin-elf toolchain, this option causes the hardware BSP provided by libgloss to be linked in if -msim is not given. Without this option, bf532 is used as the processor by default. Note that support for bf561 is incomplete. For bf561, only the pre- processor macro is defined. -msim Specifies that the program will be run on the simulator. This causes the simulator BSP provided by libgloss to be linked in. This option has effect only for bfin-elf toolchain. Certain other options, such as -mid-shared-library and -mfdpic, imply -msim. -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. -mspecld-anomaly -mno-specld-anomaly When enabled, the compiler ensures that the generated code does not contain speculative loads after jump instructions. If this option is used, "__WORKAROUND_SPECULATIVE_LOADS" is defined. -mcsync-anomaly -mno-csync-anomaly When enabled, the compiler ensures that the generated code does not contain CSYNC or SSYNC instructions too soon after conditional branches. If this option is used, "__WORKAROUND_SPECULATIVE_SYNCS" is defined. -mlow64k -mno-low64k When enabled, the compiler is free to take advantage of the knowledge that the entire program fits into the low 64k of memory. The default behavior is to assume that the program is arbitrarily large (-mno-low64k). -mstack-check-l1 Do stack checking using information placed into L1 scratchpad memory by the uClinux kernel. -mid-shared-library -mno-id-shared-library Generate code that supports shared libraries via the library ID method. This allows for execute in place and shared libraries in an environment without virtual memory management. This option implies -fPIC. With a bfin-elf target, this option implies -msim. The default is -mno-id-shared-library, to generate code that doesn't assume ID-based shared libraries are being used. -mleaf-id-shared-library -mno-leaf-id-shared-library Generate code that supports shared libraries via the library ID method, but assumes that this library or executable won't link against any other ID shared libraries. That allows the compiler to use faster code for jumps and calls. The default is -mno-leaf-id-shared-library, in which the no assumption is made that the code being compiled won't link against any ID shared libraries. Slower code is generated for jump and call insns. -mshared-library-id=n Specifies the identification number of the ID-based shared library be- ing compiled. Specifying a value of 0 generates more compact code; specifying other values forces the allocation of that number to the current library but is no more space- or time-efficient than omitting this option. -msep-data -mno-sep-data Generate code that allows the data segment to be located in a different area of memory from the text segment. This allows for execute in place in an environment without virtual memory management by eliminating re- locations against the text section. The default is -mno-sep-data, which tells GCC to generate code that assumes that the data segment follows the text segment. -mlong-calls -mno-long-calls Tells the compiler to perform function calls by first loading the ad- dress of the function into a register and then performing a subroutine call on this register. This switch is needed if the target function lies outside of the 24-bit addressing range of the offset-based version of subroutine call instruction. This feature is not enabled by default. Specifying -mno-long-calls re- stores the default behavior. Note these switches have no effect on how the compiler generates code to handle function calls via function pointers. -mfast-fp Link with the fast floating-point library. This library relaxes some of the IEEE floating-point standard's rules for checking inputs against Not-a-Number (NAN), in the interest of performance. -minline-plt Enable inlining of PLT entries in function calls to functions that are not known to bind locally. It has no effect without -mfdpic. -mmulticore Build a standalone application for multicore Blackfin processors. This option causes proper start files and link scripts supporting multicore to be used, and defines the macro "__BFIN_MULTICORE". It can only be used with -mcpu=bf561[-sirevision]. This option can be used with -mcorea or -mcoreb, which selects the one-application-per-core programming model. Without -mcorea or -mcoreb, the single-application/dual-core programming model is used. In this model, the main function of Core B should be named as "coreb_main". If this option is not used, the single-core application programming model is used. -mcorea Build a standalone application for Core A of BF561 when using the one-application-per-core programming model. Proper start files and link scripts are used to support Core A, and the macro "__BFIN_COREA" is de- fined. This option can only be used in conjunction with -mmulticore. -mcoreb Build a standalone application for Core B of BF561 when using the one-application-per-core programming model. Proper start files and link scripts are used to support Core B, and the macro "__BFIN_COREB" is de- fined. When this option is used, "coreb_main" should be used instead of "main". This option can only be used in conjunction with -mmulticore. -msdram Build a standalone application for SDRAM. Proper start files and link scripts are used to put the application into SDRAM, and the macro "__BFIN_SDRAM" is defined. The loader should initialize SDRAM before loading the application. -micplb Assume that ICPLBs are enabled at run time. This has an effect on cer- tain anomaly workarounds. For Linux targets, the default is to assume ICPLBs are enabled; for standalone applications the default is off. C6X Options -march=name This specifies the name of the target architecture. GCC uses this name to determine what kind of instructions it can emit when generating as- sembly code. Permissible names are: c62x, c64x, c64x+, c67x, c67x+, c674x. -mbig-endian Generate code for a big-endian target. -mlittle-endian Generate code for a little-endian target. This is the default. -msim Choose startup files and linker script suitable for the simulator. -msdata=default Put small global and static data in the ".neardata" section, which is pointed to by register "B14". Put small uninitialized global and sta- tic data in the ".bss" section, which is adjacent to the ".neardata" section. Put small read-only data into the ".rodata" section. The corresponding sections used for large pieces of data are ".fardata", ".far" and ".const". -msdata=all Put all data, not just small objects, into the sections reserved for small data, and use addressing relative to the "B14" register to access them. -msdata=none Make no use of the sections reserved for small data, and use absolute addresses to access all data. Put all initialized global and static data in the ".fardata" section, and all uninitialized data in the ".far" section. Put all constant data into the ".const" section. -mdsbt Compile for the DSBT shared library ABI. This option is required to compile with -fpic or -fPIC, and implies -fpic. -mlong-calls Avoid generating PC-relative calls; use indirection instead. CRIS Options These options are defined specifically for the CRIS ports. -march=architecture-type -mcpu=architecture-type Generate code for the specified architecture. The choices for archi- tecture-type are v3, v8 and v10 for respectively ETRAX 4, ETRAX 100, and ETRAX 100 LX. Default is v0. -mtune=architecture-type Tune to architecture-type everything applicable about the generated code, except for the ABI and the set of available instructions. The choices for architecture-type are the same as for -march=architec- ture-type. -mmax-stackframe=n Warn when the stack frame of a function exceeds n bytes. -metrax4 -metrax100 The options -metrax4 and -metrax100 are synonyms for -march=v3 and -march=v8 respectively. -mmul-bug-workaround -mno-mul-bug-workaround Work around a bug in the "muls" and "mulu" instructions for CPU models where it applies. This option is disabled by default. -mpdebug Enable CRIS-specific verbose debug-related information in the assembly code. This option also has the effect of turning off the #NO_APP for- matted-code indicator to the assembler at the beginning of the assembly file. -mcc-init Do not use condition-code results from previous instruction; always emit compare and test instructions before use of condition codes. -mno-side-effects Do not emit instructions with side effects in addressing modes other than post-increment. -mstack-align -mno-stack-align -mdata-align -mno-data-align -mconst-align -mno-const-align These options (no- options) arrange (eliminate arrangements) for the stack frame, individual data and constants to be aligned for the maxi- mum single data access size for the chosen CPU model. The default is to arrange for 32-bit alignment. ABI details such as structure layout are not affected by these options. -m32-bit -m16-bit -m8-bit Similar to the stack- data- and const-align options above, these op- tions 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. -mno-prologue-epilogue -mprologue-epilogue With -mno-prologue-epilogue, the normal function prologue and epilogue which set up the stack frame are omitted and no return instructions or return sequences are generated in the code. Use this option only to- gether with visual inspection of the compiled code: no warnings or er- rors are generated when call-saved registers must be saved, or storage for local variables needs to be allocated. -mbest-lib-options -moverride-best-lib-options -mbest-lib-options selects the most feature-enabling options allowed by other options. This option has no no- form, but -mover- ride-best-lib-options disables it regardless of the relative order of the two options on the command line. -mtrap-using-break8 Emit traps as break 8. This is the default for CRIS v3 and up. If disabled, calls to "abort" are used instead. -mtrap-unaligned-atomic Emit checks causing break 8 instructions to execute when applying atomic builtins on misaligned memory. -munaligned-atomic-may-use-library Handle atomic builtins that may be applied to unaligned data by calling library functions. This option overrides -mtrap-unaligned-atomic. -simThis option arranges to link with input-output functions from a simula- tor library. Code, initialized data and zero-initialized data are al- located consecutively. -sim2 Like -sim, but pass linker options to locate initialized data at 0x40000000 and zero-initialized data at 0x80000000. C-SKY Options GCC supports these options when compiling for C-SKY V2 processors. -march=arch Specify the C-SKY target architecture. Valid values for arch are: ck801, ck802, ck803, ck807, and ck810. The default is ck810. -mcpu=cpu Specify the C-SKY target processor. Valid values for cpu are: ck801, ck801t, ck802, ck802t, ck802j, ck803, ck803h, ck803t, ck803ht, ck803f, ck803fh, ck803e, ck803eh, ck803et, ck803eht, ck803ef, ck803efh, ck803ft, ck803eft, ck803efht, ck803r1, ck803hr1, ck803tr1, ck803htr1, ck803fr1, ck803fhr1, ck803er1, ck803ehr1, ck803etr1, ck803ehtr1, ck803efr1, ck803efhr1, ck803ftr1, ck803eftr1, ck803efhtr1, ck803s, ck803st, ck803se, ck803sf, ck803sef, ck803seft, ck807e, ck807ef, ck807, ck807f, ck810e, ck810et, ck810ef, ck810eft, ck810, ck810v, ck810f, ck810t, ck810fv, ck810tv, ck810ft, and ck810ftv. -mbig-endian -mlittle-endian Select big- or little-endian code. The default is little-endian. -mfloat-abi=name Specifies which floating-point ABI to use. Permissible values are: soft, softfp and hard. Specifying soft causes GCC to generate output containing library calls for floating-point operations. softfp allows the generation of code using hardware floating-point instructions, but still uses the soft-float calling conventions. hard allows generation of float- ing-point instructions and uses FPU-specific calling conventions. The default depends on the specific target configuration. Note that the hard-float and soft-float ABIs are not link-compatible; you must compile your entire program with the same ABI, and link with a compati- ble set of libraries. -mdouble-float -mno-double-float When -mhard-float is in effect, enable generation of double-precision float instructions. This is the default except when compiling for CK803. -mfdivdu -mno-fdivdu When -mhard-float is in effect, enable generation of "frecipd", "fsqrtd", and "fdivd" instructions. This is the default except when compiling for CK803. -mfpu=fpu Select the floating-point processor. This option can only be used with -mhard-float. Values for fpu are fpv2_sf (equivalent to -mno-dou- ble-float -mno-fdivdu), fpv2 (-mdouble-float -mno-divdu), and fpv2_divd (-mdouble-float -mdivdu). -melrw -mno-elrw Enable the extended "lrw" instruction. This option defaults to on for CK801 and off otherwise. -mistack -mno-istack Enable interrupt stack instructions; the default is off. The -mistack option is required to handle the "interrupt" and "isr" function attributes. -mmp -mno-mp Enable multiprocessor instructions; the default is off. -mcp -mno-cp Enable coprocessor instructions; the default is off. -mcache -mno-cache Enable coprocessor instructions; the default is off. -msecurity -mno-security Enable C-SKY security instructions; the default is off. -mtrust -mno-trust Enable C-SKY trust instructions; the default is off. -mdsp -mno-dsp -medsp -mno-edsp -mvdsp -mno-vdsp Enable C-SKY DSP, Enhanced DSP, or Vector DSP instructions, respec- tively. All of these options default to off. -mdiv -mno-div Generate divide instructions. Default is off. -msmart -mno-smart Generate code for Smart Mode, using only registers numbered 0-7 to al- low use of 16-bit instructions. This option is ignored for CK801 where this is the required behavior, and it defaults to on for CK802. For other targets, the default is off. -mhigh-registers -mno-high-registers Generate code using the high registers numbered 16-31. This option is not supported on CK801, CK802, or CK803, and is enabled by default for other processors. -manchor -mno-anchor Generate code using global anchor symbol addresses. -mpushpop -mno-pushpop Generate code using "push" and "pop" instructions. This option de- faults to on. -mmultiple-stld -mno-multiple-stld Generate code using "stm" and "ldm" instructions. This option isn't supported on CK801 but is enabled by default on other processors. -mconstpool -mno-constpool Create constant pools in the compiler instead of deferring it to the assembler. This option is the default and required for correct code generation on CK801 and CK802, and is optional on other processors. -mstack-size -mno-stack-size Emit ".stack_size" directives for each function in the assembly output. This option defaults to off. -mccrt -mno-ccrt Generate code for the C-SKY compiler runtime instead of libgcc. This option defaults to off. -mbranch-cost=n Set the branch costs to roughly "n" instructions. The default is 1. -msched-prolog -mno-sched-prolog Permit scheduling of function prologue and epilogue sequences. Using this option can result in code that is not compliant with the C-SKY V2 ABI prologue requirements and that cannot be debugged or backtraced. It is disabled by default. -msim -mno-sim Links the library libsemi.a which is in compatible with simulator. Ap- plicable to ELF compiler only. Cygwin and MinGW Options These additional options are available for Microsoft Windows targets: -mconsole This option specifies that a console application is to be generated, by instructing the linker to set the PE header subsystem type required for console applications. This option is available for Cygwin and MinGW targets and is enabled by default on those targets. -mcrtdll=library Preprocess, compile or link with specified C RunTime DLL library. This option adjust predefined macros "__CRTDLL__", "__MSVCRT__", "_UCRT" and "__MSVCRT_VERSION__" for specified CRT library, choose start file for CRT library and link with CRT library. Recognized CRT library names for proprocessor are: "crtdll*", "msvcrt10*", "msvcrt20*", "msvcrt40*", "msvcr40*", "msvcrtd*", "msvcrt-os*", "msvcr70*", "msvcr71*", "msvcr80*", "msvcr90*", "msvcr100*", "msvcr110*", "msvcr120*" and "ucrt*". If this options is not specified then the default MinGW im- port library "msvcrt" is used for linking and no other adjustment for preprocessor is done. MinGW import library "msvcrt" is just a symlink to (or a copy of) another MinGW CRT import library chosen during MinGW compilation. MinGW import library "msvcrt-os" is for Windows system CRT DLL library "msvcrt.dll" and in most cases is the default MinGW import library. Generally speaking, changing the CRT DLL requires recompiling the entire MinGW CRT. This option is for experimental and testing pur- poses only. This option is available for MinGW targets. -mdll This option is available for Cygwin and MinGW targets. It specifies that a DLL---a dynamic link library---is to be generated, enabling the selection of the required runtime startup object and entry point. -mnop-fun-dllimport This option is available for Cygwin and MinGW targets. It specifies that the "dllimport" attribute should be ignored. -mthreads Support thread-safe exception handling on MinGW. Programs that rely on thread-safe exception handling must compile and link all code with the -mthreads option. When compiling, -mthreads defines -D_MT; when link- ing, it links in a special thread helper library -lmingwthrd which cleans up per-thread exception-handling data. -municode This option is available for MinGW-w64 targets. It causes the "UNI- CODE" preprocessor macro to be predefined, and chooses Unicode-capable runtime startup code. -mwin32 This option is available for Cygwin and MinGW targets. It specifies that the typical Microsoft Windows predefined macros are to be set in the pre-processor, but does not influence the choice of runtime li- brary/startup code. -mwindows This option is available for Cygwin and MinGW targets. It specifies that a GUI application is to be generated by instructing the linker to set the PE header subsystem type appropriately. -fno-set-stack-executable This option is available for MinGW targets. It specifies that the exe- cutable flag for the stack used by nested functions isn't set. This is necessary for binaries running in kernel mode of Microsoft Windows, as there the User32 API, which is used to set executable privileges, isn't available. -fwritable-relocated-rdata This option is available for MinGW and Cygwin targets. It specifies that relocated-data in read-only section is put into the ".data" sec- tion. This is a necessary for older runtimes not supporting modifica- tion of ".rdata" sections for pseudo-relocation. -mpe-aligned-commons This option is available for Cygwin and MinGW targets. It specifies that the GNU extension to the PE file format that permits the correct alignment of COMMON variables should be used when generating code. It is enabled by default if GCC detects that the target assembler found during configuration supports the feature. -muse-libstdc-wrappers Use Cygwin DLL wrappers to support C++ operators "new" and "delete". See also under x86 Options for standard options. Darwin Options These options are defined for all architectures running the Darwin operat- ing system. FSF GCC on Darwin does not create "fat" object files; it creates an object file for the single architecture that GCC was built to target. Apple's GCC on Darwin does create "fat" files if multiple -arch options are used; it does so by running the compiler or linker multiple times and joining the results together with lipo. The subtype of the file created (like ppc7400 or ppc970 or i686) is deter- mined by the flags that specify the ISA that GCC is targeting, like -mcpu or -march. The -force_cpusubtype_ALL option can be used to override this. The Darwin tools vary in their behavior when presented with an ISA mis- match. The assembler, as, only permits instructions to be used that are valid for the subtype of the file it is generating, so you cannot put 64-bit instructions in a ppc750 object file. The linker for shared li- braries, /usr/bin/libtool, fails and prints an error if asked to create a shared library with a less restrictive subtype than its input files (for instance, trying to put a ppc970 object file in a ppc7400 library). The linker for executables, ld, quietly gives the executable the most restric- tive subtype of any of its input files. -Fdir Add the framework directory dir to the head of the list of directories to be searched for header files. These directories are interleaved with those specified by -I options and are scanned in a left-to-right order. A framework directory is a directory with frameworks in it. A frame- work is a directory with a Headers and/or PrivateHeaders directory con- tained directly in it that ends in .framework. The name of a framework is the name of this directory excluding the .framework. Headers asso- ciated with the framework are found in one of those two directories, with Headers being searched first. A subframework is a framework di- rectory that is in a framework's Frameworks directory. Includes of subframework headers can only appear in a header of a framework that contains the subframework, or in a sibling subframework header. Two subframeworks are siblings if they occur in the same framework. A sub- framework should not have the same name as a framework; a warning is issued if this is violated. Currently a subframework cannot have sub- frameworks; in the future, the mechanism may be extended to support this. The standard frameworks can be found in /System/Library/Frame- works and /Library/Frameworks. An example include looks like "#include <Framework/header.h>", where Framework denotes the name of the frame- work and header.h is found in the PrivateHeaders or Headers directory. -iframeworkdir Like -F except the directory is a treated as a system directory. The main difference between this -iframework and -F is that with -iframe- work the compiler does not warn about constructs contained within header files found via dir. This option is valid only for the C family of languages. -arch name Generate output for architecture name. As described above, GCC gener- ates output for the architecture it was configured for, using its usual options to select subarchitecture variants. The -arch option is ac- cepted for compatibility, but an error is diagnosed if name is incon- sistent with GCC's own idea of the target architecture. -dependency-file filename Alias for the preprocessor option -MF filename. -fapple-kext Generate code for Darwin loadable kernel extensions. -gused Emit debugging information for symbols that are used. For stabs debug- ging format, this enables -feliminate-unused-debug-symbols. This is by default ON. -gfull Emit debugging information for all symbols and types. -matt-stubs -mno-att-stubs Enable AT&T-style PIC stubs. This is the default when supported by the target architecture (currently x86 only). -mconstant-cfstrings -fconstant-cfstrings When the NeXT runtime is being used (the default on these systems), override any -fconstant-string-class setting and cause "@"..."" liter- als to be laid out as constant CoreFoundation strings. -fconstant-cfstrings is an alias for -mconstant-cfstrings. -mdynamic-no-pic Generate code suitable for executables (not shared libraries). This option is incompatible with -fpic, -fPIC, -fpie, or -fPIE. -mfix-and-continue -ffix-and-continue -findirect-data Generate code suitable for fast turnaround development, such as to al- low GDB to dynamically load .o files into already-running programs. -findirect-data and -ffix-and-continue are provided for backwards com- patibility. -mkernel Enable kernel development mode. The -mkernel option sets -static, -fno-common, -fno-use-cxa-atexit, -fno-exceptions, -fno-non-call-excep- tions, -fapple-kext, -fno-weak and -fno-rtti where applicable. This mode also sets -mno-altivec, -msoft-float, -fno-builtin and -mlong-branch for PowerPC targets. -mmacosx-version-min=version -asm_macosx_version_min=version The -mmacosx-version-min option specifies the earliest version of MacOS X that this executable will run on is version. Typical values sup- ported for version include 12, 10.12, and 10.5.8. If the compiler was built to use the system's headers by default, then the default for this option is the system version on which the compiler is running, otherwise the default is to make choices that are compati- ble with as many systems and code bases as possible. -asm_macosx_version_min=version is similar, but the GCC driver passes its version information only to the assembler. -mone-byte-bool Override the defaults for "bool" so that "sizeof(bool)==1". By default sizeof(bool) is 4 when compiling for Darwin/PowerPC and 1 when compil- ing for Darwin/x86, so this option has no effect on x86. Warning: The -mone-byte-bool switch causes GCC to generate code that is not binary compatible with code generated without that switch. Using this switch may require recompiling all other modules in a program, in- cluding system libraries. Use this switch to conform to a non-default data model. -msymbol-stubs -mno-symbol-stubs Force generation of external symbol indirection stubs for PIC refer- ences. By default, this option is enabled automatically if the target linker version (-mtarget-linker) is old enough to require them. -mtarget-linker=version -mtarget-linker version Specify the target ld64 version, overriding any version specified in the GCC configuration. Newer linker versions support improved code generation in some cases, for example for PIC code. -ObjC Equivalent to -x objective-c; specifies that the input is is Objec- tive-C source code. -ObjC++ Equivalent to -x objective-c++; specifies that the input is is Objec- tive-C++ source code. -Wnonportable-cfstrings -Wno-nonportable-cfstrings Warn if constant CoreFoundation string objects contain non-portable characters. This warning is enabled by default. -all_load Loads all members of static archive libraries. See man ld(1) for more information. -arch_errors_fatal Cause the errors having to do with files that have the wrong architec- ture to be fatal. -bind_at_load Causes the output file to be marked such that the dynamic linker will bind all undefined references when the file is loaded or launched. -bundle Produce a Mach-o bundle format file. See man ld(1) for more informa- tion. -bundle_loader executable This option specifies the executable that will load the build output file being linked. See man ld(1) for more information. -dynamiclib When passed this option, GCC produces a dynamic library instead of an executable when linking, using the Darwin libtool command. -force_cpusubtype_ALL This causes GCC's output file to have the ALL subtype, instead of one controlled by the -mcpu or -march option. -nodefaultrpaths Do not add default run paths for the compiler library directories to executables, modules or dynamic libraries. On macOS 10.5 and later, the embedded runpath is added by default unless the user adds -nodefaultr- paths to the link line. Run paths are needed (and therefore enforced) to build on macOS version 10.11 or later. -nodefaultexport Do not add default symbol exports to modules or dynamic libraries. -allowable_client client_name -client_name -compatibility_version -current_version -dead_strip -dylib_file -dylinker -dylinker_install_name -dynamic -exported_symbols_list -filelist -flat_namespace -force_flat_namespace -framework -headerpad_max_install_names -image_base -init symbol-name -install_name -keep_private_externs -pagezero_size -preload -read_only_relocs -sectalign -sectcreate -seg_addr_table -seg1addr -segaddr -segprot -segs_read_only_addr -segs_read_write_addr -sub_library -sub_umbrella -twolevel_namespace -twolevel_namespace_hints -umbrella -undefined -unexported_symbols_list -weak_framework -weak_reference_mismatches -whatsloaded -whyload These options are passed to the Darwin linker. The Darwin linker man page describes them in detail. DEC Alpha Options These -m options are defined for the DEC Alpha implementations: -mno-soft-float -msoft-float Use (do not use) the hardware floating-point instructions for float- ing-point operations. When -msoft-float is specified, functions in libgcc.a are 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 rou- tines issue floating-point operations. If you are compiling for an Alpha without floating-point operations, you must ensure that the li- brary is built so as not to call them. Note that Alpha implementations without floating-point operations are required to have floating-point registers. -mfp-regs -mno-fp-regs Generate code that uses (does not use) the floating-point register set. -mno-fp-regs implies -msoft-float. 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 $0 in- stead of $f0. This is a non-standard calling sequence, so any function with a floating-point argument or return value called by code compiled with -mno-fp-regs must also be compiled with that option. 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. -mieee The Alpha architecture implements floating-point hardware optimized for maximum performance. It is mostly compliant with the IEEE float- ing-point standard. However, for full compliance, software assistance is required. This option generates code fully IEEE-compliant code ex- cept that the inexact-flag is not maintained (see below). If this op- tion is turned on, the preprocessor macro "_IEEE_FP" is defined during compilation. The resulting code is less efficient but is able to cor- rectly support denormalized numbers and exceptional IEEE values such as not-a-number and plus/minus infinity. Other Alpha compilers call this option -ieee_with_no_inexact. -mieee-with-inexact This is like -mieee except the generated code also maintains the IEEE inexact-flag. Turning on this option causes the generated code to im- plement fully-compliant IEEE math. In addition to "_IEEE_FP", "_IEEE_FP_EXACT" is defined as a preprocessor macro. On some Alpha im- plementations the resulting code may execute significantly slower than the code generated by default. Since there is very little code that depends on the inexact-flag, you should normally not specify this op- tion. Other Alpha compilers call this option -ieee_with_inexact. -mfp-trap-mode=trap-mode This option controls what floating-point related traps are enabled. Other Alpha compilers call this option -fptm trap-mode. The trap mode can be set to one of four values: n This is the default (normal) setting. The only traps that are en- abled are the ones that cannot be disabled in software (e.g., divi- sion by zero trap). u In addition to the traps enabled by n, underflow traps are enabled as well. su Like u, but the instructions are marked to be safe for software completion (see Alpha architecture manual for details). sui Like su, but inexact traps are enabled as well. -mfp-rounding-mode=rounding-mode Selects the IEEE rounding mode. Other Alpha compilers call this option -fprm rounding-mode. The rounding-mode can be one of: n Normal IEEE rounding mode. Floating-point numbers are rounded to- wards the nearest machine number or towards the even machine number in case of a tie. m Round towards minus infinity. c Chopped rounding mode. Floating-point numbers are rounded towards zero. d Dynamic rounding mode. A field in the floating-point control reg- ister (fpcr, 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 mod- ifies the fpcr, d corresponds to round towards plus infinity. -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. GCC can generate code that can assist operating system trap handlers in determining the exact location that caused a floating-point trap. De- pending on the requirements of an application, different levels of pre- cisions can be selected: p Program precision. This option is the default and means a trap handler can only identify which program caused a floating-point ex- ception. f Function precision. The trap handler can determine the function that caused a floating-point exception. i Instruction precision. The trap handler can determine the exact instruction that caused a floating-point exception. Other Alpha compilers provide the equivalent options called -scope_safe and -resumption_safe. -mieee-conformant This option marks the generated code as IEEE conformant. You must not use this option unless you also specify -mtrap-precision=i and either -mfp-trap-mode=su or -mfp-trap-mode=sui. Its only effect is to emit the line .eflag 48 in the function prologue of the generated assembly file. -mbuild-constants Normally GCC 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 outputs the constant as a literal and generates code to load it from the data segment at run time. Use this option to require GCC to construct all integer constants using code, even if it takes more instructions (the maximum is six). You 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. -mbwx -mno-bwx -mcix -mno-cix -mfix -mno-fix -mmax -mno-max Indicate whether GCC should generate code to use the optional BWX, CIX, FIX and MAX instruction sets. The default is to use the instruction sets supported by the CPU type specified via -mcpu= option or that of the CPU on which GCC was built if none is specified. -msafe-bwa -mno-safe-bwa Indicate whether in the absence of the optional BWX instruction set GCC should generate multi-thread and async-signal safe code for byte and aligned word memory accesses. -msafe-partial -mno-safe-partial Indicate whether GCC should generate multi-thread and async-signal safe code for partial memory accesses, including piecemeal accesses to un- aligned data as well as block accesses to leading and trailing parts of aggregate types or other objects in memory that do not respectively start and end on an aligned 64-bit data boundary. -mfloat-vax -mfloat-ieee Generate code that uses (does not use) VAX F and G floating-point arithmetic instead of IEEE single and double precision. -mexplicit-relocs -mno-explicit-relocs Older Alpha assemblers provided no way to generate symbol relocations except via assembler macros. Use of these macros does not allow opti- mal instruction scheduling. GNU Binutils as of version 2.12 supports a new syntax that allows the compiler to explicitly mark which reloca- tions should apply to which instructions. This option is mostly useful for debugging, as GCC detects the capabilities of the assembler when it is built and sets the default accordingly. -msmall-data -mlarge-data When -mexplicit-relocs is in effect, static data is accessed via gp-relative relocations. When -msmall-data is used, objects 8 bytes long or smaller are placed in a small data area (the ".sdata" and ".sbss" sections) and are accessed via 16-bit relocations off of the $gp register. This limits the size of the small data area to 64KB, but allows the variables to be directly accessed via a single instruction. The default is -mlarge-data. With this option the data area is limited to just below 2GB. Programs that require more than 2GB of data must use "malloc" or "mmap" to allocate the data in the heap instead of in the program's data segment. When generating code for shared libraries, -fpic implies -msmall-data and -fPIC implies -mlarge-data. -msmall-text -mlarge-text When -msmall-text is used, the compiler assumes that the code of the entire program (or shared library) fits in 4MB, and is thus reachable with a branch instruction. When -msmall-data is used, the compiler can assume that all local symbols share the same $gp value, and thus reduce the number of instructions required for a function call from 4 to 1. The default is -mlarge-text. -mcpu=cpu_type Set the instruction set and instruction scheduling parameters for ma- chine type cpu_type. You can specify either the EV style name or the corresponding chip number. GCC supports scheduling parameters for the EV4, EV5 and EV6 family of processors and chooses the default values for the instruction set from the processor you specify. If you do not specify a processor type, GCC defaults to the processor on which the compiler was built. Supported values for cpu_type are ev4 ev45 21064 Schedules as an EV4 and has no instruction set extensions. ev5 21164 Schedules as an EV5 and has no instruction set extensions. ev56 21164a Schedules as an EV5 and supports the BWX extension. pca56 21164pc 21164PC Schedules as an EV5 and supports the BWX and MAX extensions. ev6 21264 Schedules as an EV6 and supports the BWX, FIX, and MAX extensions. ev67 21264a Schedules as an EV6 and supports the BWX, CIX, FIX, and MAX exten- sions. Native toolchains also support the value native, which selects the best architecture option for the host processor. -mcpu=native has no effect if GCC does not recognize the processor. -mtune=cpu_type Set only the instruction scheduling parameters for machine type cpu_type. The instruction set is not changed. Native toolchains also support the value native, which selects the best architecture option for the host processor. -mtune=native has no ef- fect if GCC does not recognize the processor. -mmemory-latency=time Sets the latency the scheduler should assume for typical memory refer- ences 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. Valid options for time are number A decimal number representing clock cycles. L1 L2 L3 mainThe compiler contains estimates of the number of clock cycles for "typical" EV4 & EV5 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 EV5. -mtls-kernel Emit "rdval" instead of "rduniq" for thread pointer. -mtls-size=bitsize Specify bit size of immediate TLS offsets. Valid values for bitsize are 16, 32, and 64; it defaults to 32. -mlong-double-128 -mlong-double-64 Specify the size of the "long double" type. Note that -mlong-dou- ble-128 is incompatible with VAX floating point. eBPF Options -mframe-limit=bytes This specifies the hard limit for frame sizes, in bytes. Currently, the value that can be specified should be less than or equal to 32767. Defaults to whatever limit is imposed by the version of the Linux ker- nel targeted. -mbig-endian Generate code for a big-endian target. -mlittle-endian Generate code for a little-endian target. This is the default. -mjmpext -mno-jmpext Enable or disable generation of extra conditional-branch instructions. Enabled for CPU v2 and above. -mjmp32 -mno-jmp32 Enable or disable generation of 32-bit jump instructions. Enabled for CPU v3 and above. -malu32 -mno-alu32 Enable or disable generation of 32-bit ALU instructions. Enabled for CPU v3 and above. -mv3-atomics -mno-v3-atomics Enable or disable instructions for general atomic operations introduced in CPU v3. Enabled for CPU v3 and above. -mbswap -mno-bswap Enable or disable byte swap instructions. Enabled for CPU v4 and above. -msdiv -mno-sdiv Enable or disable signed division and modulus instructions. Enabled for CPU v4 and above. -msmov -mno-smov Enable or disable sign-extending move and memory load instructions. Enabled for CPU v4 and above. -mcpu=version This specifies which version of the eBPF ISA to target. Newer versions may not be supported by all kernels. The default is v4. Supported values for version are: v1 The first stable eBPF ISA with no special features or extensions. v2 Supports the jump extensions, as in -mjmpext. v3 All features of v2, plus: -<32-bit jump operations, as in -mjmp32> -<32-bit ALU operations, as in -malu32> -<general atomic operations, as in -mv3-atomics> v4 All features of v3, plus: -<Byte swap instructions, as in -mbswap> -<Signed division and modulus instructions, as in -msdiv> -<Sign-extending move and memory load instructions, as in -msmov> -mco-re -mno-co-re Enable or disable BPF Compile Once - Run Everywhere (CO-RE) support. BPF CO-RE support is enabled by default when generating BTF debug in- formation for the BPF target (-gbtf). -mxbpf Generate code for an expanded version of BPF, which relaxes some of the restrictions imposed by the BPF architecture: -<Save and restore callee-saved registers at function entry and> exit, respectively. -masm=dialect Outputs assembly instructions using eBPF selected dialect. The default is pseudoc. Supported values for dialect are: normal Outputs normal assembly dialect. pseudoc Outputs pseudo-c assembly dialect. -minline-memops-threshold=bytes Specifies a size threshold in bytes at or below which memmove, memcpy and memset shall always be expanded inline. Operations dealing with sizes larger than this threshold would have to be implemented using a library call instead of being expanded inline, but since BPF doesn't allow libcalls, exceeding this threshold results in a compile-time er- ror. The default is 1024 bytes. -Wco-re Enable warnings for scenarios where -mco-re is enabled, but it may not be possible to generate CO-RE compatible code. FR30 Options These options are defined specifically for the FR30 port. -msmall-model Use the small address space model. This can produce smaller code, but it does assume that all symbolic values and addresses fit into a 20-bit range. -mno-lsim Assume that runtime support has been provided and so there is no need to include the simulator library (libsim.a) on the linker command line. FRV Options -mgpr-32 Only use the first 32 general-purpose registers. -mgpr-64 Use all 64 general-purpose registers. -mfpr-32 Use only the first 32 floating-point registers. -mfpr-64 Use all 64 floating-point registers. -mhard-float Use hardware instructions for floating-point operations. -msoft-float Use library routines for floating-point operations. -malloc-cc Dynamically allocate condition code registers. -mfixed-cc Do not try to dynamically allocate condition code registers, only use "icc0" and "fcc0". -mdword -mno-dword Control whether the ABI uses double-word instructions. -mdouble -mno-double Enable or disable use of floating-point double instructions. -mmedia -mno-media Enable or disable use of media instructions. -mmuladd -mno-muladd Enable or disable use of multiply and add/subtract instructions. -mfdpic Select the FDPIC ABI, which uses function descriptors to represent pointers to functions. Without any PIC/PIE-related options, it implies -fPIE. With -fpic or -fpie, it assumes GOT entries and small data are within a 12-bit range from the GOT base address; with -fPIC or -fPIE, GOT offsets are computed with 32 bits. With a bfin-elf target, this option implies -msim. -minline-plt Enable inlining of PLT entries in function calls to functions that are not known to bind locally. It has no effect without -mfdpic. It's en- abled by default if optimizing for speed and compiling for shared li- braries (i.e., -fPIC or -fpic), or when an optimization option such as -O3 or above is present in the command line. -mTLS Assume a large TLS segment when generating thread-local code. -mtls Do not assume a large TLS segment when generating thread-local code. -mgprel-ro Enable the use of "GPREL" relocations in the FDPIC ABI for data that is known to be in read-only sections. It's enabled by default, except for -fpic or -fpie: even though it may help make the global offset table smaller, it trades 1 instruction for 4. With -fPIC or -fPIE, it trades 3 instructions for 4, one of which may be shared by multiple symbols, and it avoids the need for a GOT entry for the referenced symbol, so it's more likely to be a win. If it is not, -mno-gprel-ro can be used to disable it. -multilib-library-pic Link with the (library, not FD) pic libraries. It's implied by -mli- brary-pic, as well as by -fPIC and -fpic without -mfdpic. You should never have to use it explicitly. -mlinked-fp Follow the EABI requirement of always creating a frame pointer whenever a stack frame is allocated. This option is enabled by default and can be disabled with -mno-linked-fp. -mlong-calls Use indirect addressing to call functions outside the current compila- tion unit. This allows the functions to be placed anywhere within the 32-bit address space. -malign-labels Try to align labels to an 8-byte boundary by inserting NOPs into the previous packet. This option only has an effect when VLIW packing is enabled. It doesn't create new packets; it merely adds NOPs to exist- ing ones. -mlibrary-pic Generate position-independent EABI code. -macc-4 Use only the first four media accumulator registers. -macc-8 Use all eight media accumulator registers. -mpack -mno-pack Enable or disable packing VLIW instructions. -mno-eflags Do not mark ABI switches in e_flags. -mcond-move -mno-cond-move Enable or disable the use of conditional-move instructions; it is en- abled by default. This switch is mainly for debugging the compiler and will likely be re- moved in a future version. -mscc -mno-scc Enable or disable the use of conditional set instructions; it is en- abled by default. This switch is mainly for debugging the compiler and will likely be re- moved in a future version. -mcond-exec -mno-cond-exec Enable or disable the use of conditional execution; it is enabled by default. This switch is mainly for debugging the compiler and will likely be re- moved in a future version. -mvliw-branch -mno-vliw-branch Enable or disable an optimization pass to pack branches into VLIW in- structions; it is enabled by default. This switch is mainly for debugging the compiler and will likely be re- moved in a future version. -mmulti-cond-exec -mno-multi-cond-exec Enable or disable optimization of "&&" and "||" in conditional execu- tion; it is enabled by default. This switch is mainly for debugging the compiler and will likely be re- moved in a future version. -mnested-cond-exec -mno-nested-cond-exec Enable or disable nested conditional execution optimizations; it is en- abled by default. This switch is mainly for debugging the compiler and will likely be re- moved in a future version. -moptimize-membar -mno-optimize-membar This switch removes redundant "membar" instructions from the com- piler-generated code. It is enabled by default. -mtomcat-stats Cause gas to print out tomcat statistics. -mcpu=cpu Select the processor type for which to generate code. Possible values are frv, fr550, tomcat, fr500, fr450, fr405, fr400, fr300 and simple. FT32 Options These options are defined specifically for the FT32 port. -msim Specifies that the program will be run on the simulator. This causes an alternate runtime startup and library to be linked. You must not use this option when generating programs that will run on real hard- ware; you must provide your own runtime library for whatever I/O func- tions are needed. -mnodiv Do not use div and mod instructions. -mft32b Enable use of the extended instructions of the FT32B processor. -mcompress Compress all code using the Ft32B code compression scheme. -mnopm Do not generate code that reads program memory. GNU/Linux Options These -m options are defined for GNU/Linux targets: -mglibc Use the GNU C library. This is the default except on *-*-linux-*uclibc*, *-*-linux-*musl* and *-*-linux-*android* targets. -muclibc Use uClibc C library. This is the default on *-*-linux-*uclibc* tar- gets. -mmusl Use the musl C library. This is the default on *-*-linux-*musl* tar- gets. -mbionic Use Bionic C library. This is the default on *-*-linux-*android* tar- gets. -mandroid -mno-android Compile code compatible with Android platform. This is the default on *-*-linux-*android* targets. When compiling, this option enables -mbionic, -fPIC, -fno-exceptions and -fno-rtti by default. When linking, this option makes the GCC dri- ver pass Android-specific options to the linker. Finally, this option causes the preprocessor macro "__ANDROID__" to be defined. This option can be disabled completely with -mno-android. -tno-android-cc Disable compilation effects of -mandroid, i.e., do not enable -mbionic, -fPIC, -fno-exceptions and -fno-rtti by default. -tno-android-ld Disable linking effects of -mandroid, i.e., pass standard Linux linking options to the linker. H8/300 Options These -m options are defined for the H8/300 implementations: -mrelax Shorten some address references at link time, when possible; uses the linker option -relax. -mh Generate code for the H8/300H. -ms Generate code for the H8S. -mn Generate code for the H8S and H8/300H in the normal mode. This switch must be used with either -mh or -ms. -msxGenerate H8SX code. -ms2600 Generate code for the H8S/2600. This switch must be used with -ms. -mquickcall Use registers for argument passing. -mslowbyte Consider access to byte-sized memory slow. -mexr -mno-exr Store extended registers on the stack before execution of functions with the "monitor" attribute. The default is -mexr. This option is valid only for H8S targets. -mint32 Make "int" data 32 bits by default. -malign-300 On the H8/300H and H8S, use the same alignment rules as for the H8/300. The default for the H8/300H and H8S is to align longs and floats on 4-byte boundaries. -malign-300 causes them to be aligned on 2-byte boundaries. This option has no effect on the H8/300. HPPA Options These -m options are defined for the HPPA family of computers: -march=architecture-type Generate code for the specified architecture. The choices for archi- tecture-type are 1.0 for PA 1.0, 1.1 for PA 1.1, and 2.0 for PA 2.0 processors. Refer to /usr/lib/sched.models on an HP-UX system to de- termine the proper architecture option for your machine. Code compiled for lower numbered architectures runs on higher numbered architectures, but not the other way around. -mpa-risc-1-0 -mpa-risc-1-1 -mpa-risc-2-0 Synonyms for -march=1.0, -march=1.1, and -march=2.0, respectively. -matomic-libcalls -mno-atomic-libcalls Generate libcalls for atomic loads and stores when sync libcalls are disabled. This option is enabled by default. It only affects the gen- eration of atomic libcalls by the HPPA backend. Both the sync and libatomic libcall implementations use locking. As a result, processor stores are not atomic with respect to other atomic operations. Processor loads up to DImode are atomic with respect to other atomic operations provided they are implemented as a single ac- cess. The PA-RISC architecture does not support any atomic operations in hardware except for the "ldcw" instruction. Thus, all atomic support is implemented using sync and atomic libcalls. Sync libcall support is in libgcc.a. Atomic libcall support is in libatomic. This option generates "__atomic_exchange" calls for atomic stores. It also provides special handling for atomic DImode accesses on 32-bit targets. -mcaller-copies The caller copies function arguments passed by hidden reference. This option should be used with care as it is not compatible with the de- fault 32-bit runtime. However, only aggregates larger than eight bytes are passed by hidden reference and the option provides better compati- bility with OpenMP. -mcoherent-ldcw Use ldcw/ldcd coherent cache-control hint. -mdisable-fpregs Disable floating-point registers. Equivalent to -msoft-float. -mdisable-indexing Prevent the compiler from using indexing address modes. This avoids some rather obscure problems when compiling MIG generated code under MACH. -mfast-indirect-calls Generate code that assumes calls never cross space boundaries. This allows GCC to emit code that performs faster indirect calls. This option does not work in the presence of shared libraries or nested functions. -mfixed-range=register-range Generate code treating the given register range as fixed registers. A fixed register is one that the register allocator cannot 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. -mgas Enable the use of assembler directives only GAS understands. -mgnu-ld Use options specific to GNU ld. This passes -shared to ld when build- ing a shared library. It is the default when GCC is configured, ex- plicitly or implicitly, with the GNU linker. This option does not af- fect which ld is called; it only changes what parameters are passed to that ld. The ld that is called is determined by the --with-ld config- ure option, GCC's program search path, and finally by the user's PATH. The linker used by GCC can be printed using which `gcc -print-prog-name=ld`. This option is only available on the 64-bit HP-UX GCC, i.e. configured with hppa*64*-*-hpux*. -mhp-ld Use options specific to HP ld. This passes -b to ld when building a shared library and passes +Accept TypeMismatch to ld on all links. It is the default when GCC is configured, explicitly or implicitly, with the HP linker. This option does not affect which ld is called; it only changes what parameters are passed to that ld. The ld that is called is determined by the --with-ld configure option, GCC's program search path, and finally by the user's PATH. The linker used by GCC can be printed using which `gcc -print-prog-name=ld`. This option is only available on the 64-bit HP-UX GCC, i.e. configured with hppa*64*-*-hpux*. -mlinker-opt Enable the optimization pass in the HP-UX linker. Note this makes sym- bolic debugging impossible. -mlong-calls Generate code that uses long call sequences. This ensures that a call is always able to reach linker generated stubs. The default is to gen- erate long calls only when the distance from the call site to the be- ginning of the function or translation unit, as the case may be, ex- ceeds a predefined limit set by the branch type being used. The limits for normal calls are 7,600,000 and 240,000 bytes, respectively for the PA 2.0 and PA 1.X architectures. Sibling calls are always limited at 240,000 bytes. Distances are measured from the beginning of functions when using the -ffunction-sections option, or when using the -mgas and -mno-portable-runtime options together under HP-UX with the SOM linker. It is normally not desirable to use this option as it degrades perfor- mance. However, it may be useful in large applications, particularly when partial linking is used to build the application. The types of long calls used depends on the capabilities of the assem- bler and linker, and the type of code being generated. The impact on systems that support long absolute calls, and long PIC symbol-differ- ence or PC-relative calls should be relatively small. However, an in- direct call is used on 32-bit ELF systems in PIC code and it is quite long. -mlong-load-store Generate 3-instruction load and store sequences as sometimes required by the HP-UX 10 linker. This is equivalent to the +k option to the HP compilers. -mno-space-regs Generate code that assumes the target has no space registers. This al- lows GCC to generate faster indirect calls and use unscaled index ad- dress modes. Such code is suitable for level 0 PA systems and kernels. -mordered Assume memory references are ordered and barriers are not needed. -mportable-runtime Use the portable calling conventions proposed by HP for ELF systems. -mschedule=cpu-type Schedule code according to the constraints for the machine type cpu-type. The choices for cpu-type are 700 7100, 7100LC, 7200, 7300 and 8000. Refer to /usr/lib/sched.models on an HP-UX system to deter- mine the proper scheduling option for your machine. The default sched- uling is 8000. -msio -mwsio The -msio generates the predefine, "_SIO", for server IO. The default is -mwsio. This generates the predefines, "__hp9000s700", "__hp9000s700__" and "_WSIO", for workstation IO. These options are available under HP-UX and HI-UX. -msoft-float Generate output containing library calls for floating point. Warning: the requisite libraries are not available for all HPPA targets. Nor- mally 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-compi- lation. -msoft-float changes the calling convention in the output file; there- fore, it is only useful if you compile all of a program with this op- tion. In particular, you need to compile libgcc.a, the library that comes with GCC, with -msoft-float in order for this to work. -msoft-mult Use software integer multiplication. This disables the use of the "xmpyu" instruction. -munix=unix-std Generate compiler predefines and select a startfile for the specified UNIX standard. The choices for unix-std are 93, 95 and 98. 93 is sup- ported on all HP-UX versions. 95 is available on HP-UX 10.10 and later. 98 is available on HP-UX 11.11 and later. The default values are 93 for HP-UX 10.00, 95 for HP-UX 10.10 though to 11.00, and 98 for HP-UX 11.11 and later. -munix=93 provides the same predefines as GCC 3.3 and 3.4. -munix=95 provides additional predefines for "XOPEN_UNIX" and "_XOPEN_SOURCE_EX- TENDED", and the startfile unix95.o. -munix=98 provides additional predefines for "_XOPEN_UNIX", "_XOPEN_SOURCE_EXTENDED", "_IN- CLUDE__STDC_A1_SOURCE" and "_INCLUDE_XOPEN_SOURCE_500", and the start- file unix98.o. It is important to note that this option changes the interfaces for various library routines. It also affects the operational behavior of the C library. Thus, extreme care is needed in using this option. Library code that is intended to operate with more than one UNIX stan- dard must test, set and restore the variable "__xpg4_extended_mask" as appropriate. Most GNU software doesn't provide this capability. -nolibdld Suppress the generation of link options to search libdld.sl when the -static option is specified on HP-UX 10 and later. -static The HP-UX C library implementation of "setlocale" has a dependency on libdld.sl. There isn't an archive version of libdld.sl. Thus, when the -static option is specified, special link options are needed to re- solve this dependency. On HP-UX 10 and later, the GCC driver adds the necessary options to link with libdld.sl when the -static option is specified. This causes the resulting binary to be dynamic. On the 64-bit port, the linkers generate dynamic binaries by default in any case. The -nolibdld option can be used to prevent the GCC driver from adding these link options. -threads Add support for multithreading with the dce thread library under HP-UX. This option sets flags for both the preprocessor and linker. IA-64 Options These are the -m options defined for the Intel IA-64 architecture. -mbig-endian Generate code for a big-endian target. This is the default for HP-UX. -mlittle-endian Generate code for a little-endian target. This is the default for AIX5 and GNU/Linux. -mgnu-as -mno-gnu-as Generate (or don't) code for the GNU assembler. This is the default. -mgnu-ld -mno-gnu-ld Generate (or don't) code for the GNU linker. This is the default. -mno-pic Generate code that does not use a global pointer register. The result is not position independent code, and violates the IA-64 ABI. -mvolatile-asm-stop -mno-volatile-asm-stop Generate (or don't) a stop bit immediately before and after volatile asm statements. -mregister-names -mno-register-names Generate (or don't) in, loc, and out register names for the stacked registers. This may make assembler output more readable. -mno-sdata -msdata Disable (or enable) optimizations that use the small data section. This may be useful for working around optimizer bugs. -mconstant-gp Generate code that uses a single constant global pointer value. This is useful when compiling kernel code. -mauto-pic Generate code that is self-relocatable. This implies -mconstant-gp. This is useful when compiling firmware code. -minline-float-divide-min-latency Generate code for inline divides of floating-point values using the minimum latency algorithm. -minline-float-divide-max-throughput Generate code for inline divides of floating-point values using the maximum throughput algorithm. -mno-inline-float-divide Do not generate inline code for divides of floating-point values. -minline-int-divide-min-latency Generate code for inline divides of integer values using the minimum latency algorithm. -minline-int-divide-max-throughput Generate code for inline divides of integer values using the maximum throughput algorithm. -mno-inline-int-divide Do not generate inline code for divides of integer values. -minline-sqrt-min-latency Generate code for inline square roots using the minimum latency algo- rithm. -minline-sqrt-max-throughput Generate code for inline square roots using the maximum throughput al- gorithm. -mno-inline-sqrt Do not generate inline code for "sqrt". -mno-dwarf2-asm -mdwarf2-asm Don't (or do) generate assembler code for the DWARF line number debug- ging info. This may be useful when not using the GNU assembler. -mearly-stop-bits -mno-early-stop-bits Allow stop bits to be placed earlier than immediately preceding the in- struction that triggered the stop bit. This can improve instruction scheduling, but does not always do so. -mfixed-range=register-range Generate code treating the given register range as fixed registers. A fixed register is one that the register allocator cannot 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. -mtls-size=tls-size Specify bit size of immediate TLS offsets. Valid values are 14, 22, and 64. -mtune=cpu-type Tune the instruction scheduling for a particular CPU, Valid values are itanium, itanium1, merced, itanium2, and mckinley. -milp32 -mlp64 Generate code for a 32-bit or 64-bit environment. The 32-bit environ- ment sets int, long and pointer to 32 bits. The 64-bit environment sets int to 32 bits and long and pointer to 64 bits. These are HP-UX specific flags. -mno-sched-br-data-spec -msched-br-data-spec (Dis/En)able data speculative scheduling before reload. This results in generation of "ld.a" instructions and the corresponding check in- structions ("ld.c" / "chk.a"). The default setting is disabled. -msched-ar-data-spec -mno-sched-ar-data-spec (En/Dis)able data speculative scheduling after reload. This results in generation of "ld.a" instructions and the corresponding check instruc- tions ("ld.c" / "chk.a"). The default setting is enabled. -mno-sched-control-spec -msched-control-spec (Dis/En)able control speculative scheduling. This feature is available only during region scheduling (i.e. before reload). This results in generation of the "ld.s" instructions and the corresponding check in- structions "chk.s". The default setting is disabled. -msched-br-in-data-spec -mno-sched-br-in-data-spec (En/Dis)able speculative scheduling of the instructions that are depen- dent on the data speculative loads before reload. This is effective only with -msched-br-data-spec enabled. The default setting is en- abled. -msched-ar-in-data-spec -mno-sched-ar-in-data-spec (En/Dis)able speculative scheduling of the instructions that are depen- dent on the data speculative loads after reload. This is effective only with -msched-ar-data-spec enabled. The default setting is en- abled. -msched-in-control-spec -mno-sched-in-control-spec (En/Dis)able speculative scheduling of the instructions that are depen- dent on the control speculative loads. This is effective only with -msched-control-spec enabled. The default setting is enabled. -mno-sched-count-spec-in-critical-path -msched-count-spec-in-critical-path If enabled, speculative dependencies are considered during computation of the instructions priorities. This makes the use of the speculation a bit more conservative. The default setting is disabled. -msched-spec-ldc -mno-sched-spec-ldc Use a simple data speculation check. This option is on by default. -msched-control-spec-ldc -mno-sched-control-spec-ldc Use a simple check for control speculation. This option is on by de- fault. -msched-stop-bits-after-every-cycle -mno-sched-stop-bits-after-every-cycle Place a stop bit after every cycle when scheduling. This option is on by default. -msched-fp-mem-deps-zero-cost -mno-sched-fp-mem-deps-zero-cost Assume that floating-point stores and loads are not likely to cause a conflict when placed into the same instruction group. This option is disabled by default. -msel-sched-dont-check-control-spec -mno-sel-sched-dont-check-control-spec Generate checks for control speculation in selective scheduling. This flag is disabled by default. -msched-max-memory-insns=max-insns Limit on the number of memory insns per instruction group, giving lower priority to subsequent memory insns attempting to schedule in the same instruction group. Frequently useful to prevent cache bank conflicts. The default value is 1. -msched-max-memory-insns-hard-limit -mno-sched-max-memory-insns-hard-limit Makes the limit specified by msched-max-memory-insns a hard limit, dis- allowing more than that number in an instruction group. Otherwise, the limit is "soft", meaning that non-memory operations are preferred when the limit is reached, but memory operations may still be scheduled. LM32 Options These -m options are defined for the LatticeMico32 architecture: -mbarrel-shift-enabled Enable barrel-shift instructions. -mdivide-enabled Enable divide and modulus instructions. -mmultiply-enabled Enable multiply instructions. -msign-extend-enabled Enable sign extend instructions. -muser-enabled Enable user-defined instructions. LoongArch Options These command-line options are defined for LoongArch targets: -march=arch-type Generate instructions for the machine type arch-type. -march=arch-type allows GCC to generate code that may not run at all on processors other than the one indicated. The choices for arch-type are: native Local processor type detected by the native compiler. loongarch64 Generic LoongArch 64-bit processor. la464 LoongArch LA464-based processor with LSX, LASX. la664 LoongArch LA664-based processor with LSX, LASX and all LoongArch v1.1 instructions. la64v1.0 LoongArch64 ISA version 1.0. la64v1.1 LoongArch64 ISA version 1.1. la32v1.0 LoongArch32 ISA version 1.0. la32rv1.0 LoongArch32 Reduced ISA version 1.0. More information about LoongArch ISA versions can be found at <https://github.com/loongson/la-toolchain-conventions>. -mtune=tune-type Optimize the generated code for the given processor target. The choices for tune-type are: native Local processor type detected by the native compiler. generic Generic LoongArch processor. loongarch64 Generic LoongArch 64-bit processor. la464 LoongArch LA464 core. la664 LoongArch LA664 core. loongarch32 Generic LoongArch 32-bit processor. -mabi=base-abi-type Generate code for the specified calling convention. base-abi-type can be one of: lp64d Uses 64-bit general purpose registers and 32/64-bit floating-point registers for parameter passing. Data model is LP64, where int is 32 bits, while long int and pointers are 64 bits. lp64f Uses 64-bit general purpose registers and 32-bit floating-point registers for parameter passing. Data model is LP64, where int is 32 bits, while long int and pointers are 64 bits. lp64s Uses 64-bit general purpose registers and no floating-point regis- ters for parameter passing. Data model is LP64, where int is 32 bits, while long int and pointers are 64 bits. -mfpu=fpu-type Generate code for the specified FPU type, which can be one of: 64 Allow the use of hardware floating-point instructions for 32-bit and 64-bit operations. 32 Allow the use of hardware floating-point instructions for 32-bit operations. none 0 Prevent the use of hardware floating-point instructions. -msimd=simd-type Enable generation of LoongArch SIMD instructions for vectorization and via builtin functions. The value can be one of: lasxEnable generating instructions from the 256-bit LoongArch Advanced SIMD Extension (LASX) and the 128-bit LoongArch SIMD Extension (LSX). lsx Enable generating instructions from the 128-bit LoongArch SIMD Ex- tension (LSX). noneNo LoongArch SIMD instruction may be generated. -msoft-float Force -mfpu=none and prevent the use of floating-point registers for parameter passing. This option may change the target ABI. -msingle-float Force -mfpu=32 and allow the use of 32-bit floating-point registers for parameter passing. This option may change the target ABI. -mdouble-float Force -mfpu=64 and allow the use of 32/64-bit floating-point registers for parameter passing. This option may change the target ABI. -mlasx -mno-lasx -mlsx -mno-lsx Incrementally adjust the scope of the SIMD extensions (none / LSX / LASX) that can be used by the compiler for code generation. Enabling LASX with -mlasx automatically enables LSX, and disabling LSX with -mno-lsx automatically disables LASX. These driver-only options act upon the final -msimd configuration state and make incremental changes in the order they appear on the GCC driver's command line, deriving the final / canonicalized -msimd option that is passed to the compiler proper. -mbranch-cost=n Set the cost of branches to roughly n instructions. -maddr-reg-reg-cost=n Set the cost of ADDRESS_REG_REG to the value calculated by n. -mcheck-zero-division -mno-check-zero-division Trap (do not trap) on integer division by zero. The default is -mcheck-zero-division for -O0 or -Og, and -mno-check-zero-division for other optimization levels. -mbreak-code=code Emit a "break" code instruction for irrecoverable traps from "__builtin_trap" or inserted by the compiler (for example an erroneous path isolated with -fisolate-erroneous-paths-dereference), or an "am- swap.w $r0, $r1, $r0" instruction which will cause the hardware to trigger an Instruction Not-defined Exception if code is negative or greater than 32767. The default is -1, meaning to use the "amswap.w" instruction. -mcond-move-int -mno-cond-move-int Conditional moves for integral data in general-purpose registers are enabled (disabled). The default is -mcond-move-int. -mcond-move-float -mno-cond-move-float Conditional moves for floating-point registers are enabled (disabled). The default is -mcond-move-float. -mmemcpy -mno-memcpy Force (do not force) the use of "memcpy" for non-trivial block moves. The default is -mno-memcpy, which allows GCC to inline most con- stant-sized copies. Setting optimization level to -Os also forces the use of "memcpy", but -mno-memcpy may override this behavior if explic- itly specified, regardless of the order these options on the command line. -mstrict-align -mno-strict-align Avoid or allow generating memory accesses that may not be aligned on a natural object boundary as described in the architecture specification. The default is -mno-strict-align. -G num Put global and static data smaller than num bytes into a small data section. The default value is 0. -mmax-inline-memcpy-size=n Inline all block moves (such as calls to "memcpy" or structure copies) less than or equal to n bytes. The default value of n is 1024. -mcmodel=code-model Set the code model to one of: tiny-static (Not implemented yet) tiny (Not implemented yet) normal The text segment must be within 128MB addressing space. The data segment must be within 2GB addressing space. medium The text segment and data segment must be within 2GB addressing space. This is the default code model unless GCC has been config- ured with --with-cmodel= specifying a different default code model. large (Not implemented yet) extreme This mode does not limit the size of the code segment and data seg- ment. The -mcmodel=extreme option is incompatible with -fplt and/or -mexplicit-relocs=none. -mexplicit-relocs=style -mexplicit-relocs -mno-explicit-relocs Set when to use assembler relocation operators when dealing with sym- bolic addresses. The alternative is to use assembler macros instead, which may limit instruction scheduling but allow linker relaxation. With -mexplicit-relocs=none, the assembler macros are always used; with -mexplicit-relocs=always, the assembler relocation operators are always used; and with -mexplicit-relocs=auto the compiler uses the relocation operators where linker relaxation is impossible to improve the code quality, and macros elsewhere. The default value for the option is determined with the assembler capa- bility detected during GCC build-time and the setting of -mrelax: -mex- plicit-relocs=none if the assembler does not support relocation opera- tors at all, -mexplicit-relocs=always if the assembler supports reloca- tion operators but -mrelax is not enabled, -mexplicit-relocs=auto if the assembler supports relocation operators and -mrelax is enabled. For backward compatibility, -mexplicit-relocs is equivalent to -mex- plicit-relocs=always, while -mno-explicit-relocs is equivalent to -mex- plicit-relocs=none. -mdirect-extern-access -mno-direct-extern-access Control use of the GOT to access external symbols. The default is -mno-direct-extern-access: the GOT is used for external symbols with default visibility, but not used for other external symbols. With -mdirect-extern-access, the GOT is not used and all external sym- bols are PC-relatively addressed. It is only suitable for environments where no dynamic link is performed, like firmwares, OS kernels, exe- cutables linked with -static or -static-pie. -mdirect-extern-access is not compatible with -fPIC or -fpic. -mrelax -mno-relax Take (do not take) advantage of linker relaxations. If -mpass-mre- lax-to-as is enabled, this option is also passed to the assembler. The default is determined during GCC build-time by detecting corresponding assembler support: -mrelax if the assembler supports both the -mrelax option and the conditional branch relaxation (it's required or the ".align" directives and conditional branch instructions in the assembly code outputted by GCC may be rejected by the assembler because of a re- location overflow), -mno-relax otherwise. -mpass-mrelax-to-as -mno-pass-mrelax-to-as Pass (do not pass) the -mrelax or -mno-relax option to the assembler. The default is determined during GCC build-time by detecting corre- sponding assembler support: -mpass-mrelax-to-as if the assembler sup- ports the -mrelax option, -mno-pass-mrelax-to-as otherwise. This op- tion is mostly useful for debugging, or interoperation with assemblers different from the build-time one. -mrecip This option enables use of the reciprocal estimate and reciprocal square root estimate instructions with additional Newton-Raphson steps to increase precision instead of doing a divide or square root and di- vide for floating-point arguments. These instructions are generated only when -funsafe-math-optimizations is enabled together with -ffi- nite-math-only and -fno-trapping-math. This option is off by default. Before you can use this option, you must sure the target CPU supports the "frecipe" and "frsqrte" instructions. Note that while the through- put of the sequence is higher than the throughput of the non-reciprocal instruction, the precision of the sequence can be decreased by up to 2 ulp (i.e. the inverse of 1.0 equals 0.99999994). -mrecip=opt This option controls which reciprocal estimate instructions may be used. opt is a comma-separated list of options, which may be preceded by a ! to invert the option: all Enable all estimate instructions. default Enable the default instructions, equivalent to -mrecip. noneDisable all estimate instructions, equivalent to -mno-recip. div Enable the approximation for scalar division. vec-div Enable the approximation for vectorized division. sqrtEnable the approximation for scalar square root. vec-sqrt Enable the approximation for vectorized square root. rsqrt Enable the approximation for scalar reciprocal square root. vec-rsqrt Enable the approximation for vectorized reciprocal square root. So, for example, -mrecip=all,!sqrt enables all of the reciprocal ap- proximations, except for scalar square root. -mfrecipe -mno-frecipe Use (do not use) "frecipe.{s/d}" and "frsqrte.{s/d}" instructions. When compiling with -march=la664, it is enabled by default. Otherwise the default is -mno-frecipe. -mdiv32 -mno-div32 Use (do not use) "div.w[u]" and "mod.w[u]" instructions with input not sign-extended. When compiling with -march=la664, it is enabled by de- fault. Otherwise the default is -mno-div32. -mlam-bh -mno-lam-bh Use (do not use) "am{swap/add}[_db].{b/h}" instructions. When compil- ing with -march=la664, it is enabled by default. Otherwise the default is -mno-lam-bh. -mlamcas -mno-lamcas Use (do not use) "amcas[_db].{b/h/w/d}" instructions. When compiling with -march=la664, it is enabled by default. Otherwise the default is -mno-lamcas. -mld-seq-sa -mno-ld-seq-sa Whether a same-address load-load barrier ("dbar 0x700") is needed. When compiling with -march=la664, it is enabled by default. Otherwise the default is -mno-ld-seq-sa, the load-load barrier is needed. -mscq -mno-scq Use (do not use) the 16-byte conditional store instruction "sc.q". The default is -mscq if the machine type specified with -march= supports this instruction, -mno-scq otherwise. -mtls-dialect=opt This option controls which TLS dialect may be used for general dynamic and local dynamic TLS models. The opt argument can be one of: tradUse traditional TLS. This is the default. descUse TLS descriptors. -mannotate-tablejump -mno-annotate-tablejump Create an annotation section ".discard.tablejump_annotate" to correlate the "jirl" instruction and the jump table when a jump table is used to optimize the "switch" statement. Some external tools, for example obj- tool of the Linux kernel building system, need the annotation to ana- lyze the control flow. The default is -mno-annotate-tablejump. LynxOS Options These options are available for LynxOS targets. -mshared Use shared libraries. The default is to link with static libraries. -mthreads Support multi-threading. -mlegacy-threads Support legacy multi-threading. This option is incompatible with -mthreads. M32R/D Options These -m options are defined for Renesas M32R/D architectures: -m32r2 Generate code for the M32R/2. -m32rx Generate code for the M32R/X. -m32r Generate code for the M32R. This is the default. -mmodel=small Assume all objects live in the lower 16MB of memory (so that their ad- dresses can be loaded with the "ld24" instruction), and assume all sub- routines are reachable with the "bl" instruction. This is the default. The addressability of a particular object can be set with the "model" attribute. -mmodel=medium Assume objects may be anywhere in the 32-bit address space (the com- piler generates "seth/add3" instructions to load their addresses), and assume all subroutines are reachable with the "bl" instruction. -mmodel=large Assume objects may be anywhere in the 32-bit address space (the com- piler generates "seth/add3" instructions to load their addresses), and assume subroutines may not be reachable with the "bl" instruction (the compiler generates the much slower "seth/add3/jl" instruction se- quence). -msdata=none Disable use of the small data area. Variables are put into one of ".data", ".bss", or ".rodata" (unless the "section" attribute has been specified). This is the default. The small data area consists of sections ".sdata" and ".sbss". Objects may be explicitly put in the small data area with the "section" at- tribute using one of these sections. -msdata=sdata Put small global and static data in the small data area, but do not generate special code to reference them. -msdata=use Put small global and static data in the small data area, and generate special instructions to reference them. -G num Put global and static objects less than or equal to num bytes into the small data or BSS sections instead of the normal data or BSS sections. The default value of num is 8. The -msdata option must be set to one of sdata or use for this option to have any effect. All modules should be compiled with the same -G num value. Compiling with different values of num may or may not work; if it doesn't the linker gives an error message---incorrect code is not generated. -mdebug Makes the M32R-specific code in the compiler display some statistics that might help in debugging programs. -malign-loops -mno-align-loops Align all loops to a 32-byte boundary. This option is disabled by de- fault. -missue-rate=number Issue number instructions per cycle. number can only be 1 or 2. -mbranch-cost=number number can only be 1 or 2. If it is 1 then branches are preferred over conditional code, if it is 2, then the opposite applies. -mflush-trap=number Specifies the trap number to use to flush the cache. The default is 12. Valid numbers are between 0 and 15 inclusive. -mno-flush-trap Specifies that the cache cannot be flushed by using a trap. -mflush-func=name Specifies the name of the operating system function to call to flush the cache. The default is _flush_cache, but a function call is only used if a trap is not available. -mno-flush-func Indicates that there is no OS function for flushing the cache. M680x0 Options These are the -m options defined for M680x0 and ColdFire processors. The default settings depend on which architecture was selected when the com- piler was configured; the defaults for the most common choices are given below. -march=arch Generate code for a specific M680x0 or ColdFire instruction set archi- tecture. Permissible values of arch for M680x0 architectures are: 68000, 68010, 68020, 68030, 68040, 68060 and cpu32. ColdFire architec- tures are selected according to Freescale's ISA classification and the permissible values are: isaa, isaaplus, isab and isac. GCC defines a macro "__mcfarch__" whenever it is generating code for a ColdFire target. The arch in this macro is one of the -march arguments given above. When used together, -march and -mtune select code that runs on a family of similar processors but that is optimized for a particular microar- chitecture. -mcpu=cpu Generate code for a specific M680x0 or ColdFire processor. The M680x0 cpus are: 68000, 68010, 68020, 68030, 68040, 68060, 68302, 68332 and cpu32. The ColdFire cpus are given by the table below, which also classifies the CPUs into families: Family : -mcpu arguments 51 : 51 51ac 51ag 51cn 51em 51je 51jf 51jg 51jm 51mm 51qe 51qm 5206 : 5202 5204 5206 5206e : 5206e 5208 : 5207 5208 5211a : 5210a 5211a 5213 : 5211 5212 5213 5216 : 5214 5216 52235 : 52230 52231 52232 52233 52234 52235 5225 : 5224 5225 52259 : 52252 52254 52255 52256 52258 52259 5235 : 5232 5233 5234 5235 523x 5249 : 5249 5250 : 5250 5271 : 5270 5271 5272 : 5272 5275 : 5274 5275 5282 : 5280 5281 5282 528x 53017 : 53011 53012 53013 53014 53015 53016 53017 5307 : 5307 5329 : 5327 5328 5329 532x 5373 : 5372 5373 537x 5407 : 5407 5475 : 5470 5471 5472 5473 5474 5475 547x 5480 5481 5482 5483 5484 5485 -mcpu=cpu overrides -march=arch if arch is compatible with cpu. Other combinations of -mcpu and -march are rejected. GCC defines the macro "__mcf_cpu_cpu" when ColdFire target cpu is se- lected. It also defines "__mcf_family_family", where the value of fam- ily is given by the table above. -mtune=tune Tune the code for a particular microarchitecture within the constraints set by -march and -mcpu. The M680x0 microarchitectures are: 68000, 68010, 68020, 68030, 68040, 68060 and cpu32. The ColdFire microarchi- tectures are: cfv1, cfv2, cfv3, cfv4 and cfv4e. You can also use -mtune=68020-40 for code that needs to run relatively well on 68020, 68030 and 68040 targets. -mtune=68020-60 is similar but includes 68060 targets as well. These two options select the same tun- ing decisions as -m68020-40 and -m68020-60 respectively. GCC defines the macros "__mcarch" and "__mcarch__" when tuning for 680x0 architecture arch. It also defines "mcarch" unless either -ansi or a non-GNU -std option is used. If GCC is tuning for a range of ar- chitectures, as selected by -mtune=68020-40 or -mtune=68020-60, it de- fines the macros for every architecture in the range. GCC also defines the macro "__muarch__" when tuning for ColdFire mi- croarchitecture uarch, where uarch is one of the arguments given above. -m68000 -mc68000 Generate output for a 68000. This is the default when the compiler is configured for 68000-based systems. It is equivalent to -march=68000. Use this option for microcontrollers with a 68000 or EC000 core, in- cluding the 68008, 68302, 68306, 68307, 68322, 68328 and 68356. -m68010 Generate output for a 68010. This is the default when the compiler is configured for 68010-based systems. It is equivalent to -march=68010. -m68020 -mc68020 Generate output for a 68020. This is the default when the compiler is configured for 68020-based systems. It is equivalent to -march=68020. -m68030 Generate output for a 68030. This is the default when the compiler is configured for 68030-based systems. It is equivalent to -march=68030. -m68040 Generate output for a 68040. This is the default when the compiler is configured for 68040-based systems. It is equivalent to -march=68040. 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. -m68060 Generate output for a 68060. This is the default when the compiler is configured for 68060-based systems. It is equivalent to -march=68060. 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. -m68302 Generate code for a 68302. -m68332 Generate code for a 68332. -m68851 The 68851 was an external MMU for the 68020 processor. GCC accepts this option, but does not use it. -mcpu32 Generate output for a CPU32. This is the default when the compiler is configured for CPU32-based systems. It is equivalent to -march=cpu32. Use this option for microcontrollers with a CPU32 or CPU32+ core, in- cluding the 68330, 68331, 68332, 68333, 68334, 68336, 68340, 68341, 68349 and 68360. -mfidoa Generate code for a Fido A. -m5200 Generate output for a 520X ColdFire CPU. This is the default when the compiler is configured for 520X-based systems. It is equivalent to -mcpu=5206, and is now deprecated in favor of that option. Use this option for microcontroller with a 5200 core, including the MCF5202, MCF5203, MCF5204 and MCF5206. -m5206e Generate output for a 5206e ColdFire CPU. The option is now deprecated in favor of the equivalent -mcpu=5206e. -m528x Generate output for a member of the ColdFire 528X family. The option is now deprecated in favor of the equivalent -mcpu=528x. -m5307 Generate output for a ColdFire 5307 CPU. The option is now deprecated in favor of the equivalent -mcpu=5307. -m5407 Generate output for a ColdFire 5407 CPU. The option is now deprecated in favor of the equivalent -mcpu=5407. -mcfv4e Generate output for a ColdFire V4e family CPU (e.g. 547x/548x). This includes use of hardware floating-point instructions. The option is equivalent to -mcpu=547x, and is now deprecated in favor of that op- tion. -m68020-40 Generate output for a 68040, without using any of the new instructions. This results in code that 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. The option is equivalent to -march=68020 -mtune=68020-40. -m68020-60 Generate output for a 68060, without using any of the new instructions. This results in code that 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. The option is equivalent to -march=68020 -mtune=68020-60. -mhard-float -m68881 Generate floating-point instructions. This is the default for 68020 and above, and for ColdFire devices that have an FPU. It defines the macro "__HAVE_68881__" on M680x0 targets and "__mcffpu__" on ColdFire targets. -msoft-float Do not generate floating-point instructions; use library calls instead. This is the default for 68000, 68010, and 68832 targets. It is also the default for ColdFire devices that have no FPU. -mdiv -mno-div Generate (do not generate) ColdFire hardware divide and remainder in- structions. If -march is used without -mcpu, the default is "on" for ColdFire architectures and "off" for M680x0 architectures. Otherwise, the default is taken from the target CPU (either the default CPU, or the one specified by -mcpu). For example, the default is "off" for -mcpu=5206 and "on" for -mcpu=5206e. GCC defines the macro "__mcfhwdiv__" when this option is enabled. -mshort -mno-short -mnoshort Consider type "int" to be 16 bits wide, like "short int". Addition- ally, parameters passed on the stack are also aligned to a 16-bit boundary even on targets whose API mandates promotion to 32-bit. This option is disabled by default. -mbitfield -mno-bitfield -mnobitfield Control use of the bit-field instructions. The -m68000, -mcpu32 and -m5200 options imply -mnobitfield; the -m68020 option implies -mbit- field. -mrtd -mno-rtd -mnortd Control use of a different function-calling convention, in which func- tions that take a fixed number of arguments return with the "rtd" in- struction, which pops their arguments while returning. This saves one instruction in the caller since there is no need to pop the arguments there. 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. Also, you must provide function prototypes for all functions that take variable numbers of arguments (including "printf"); otherwise incorrect code is generated for calls to those functions. In addition, seriously incorrect code results if you call a function with too many arguments. (Normally, extra arguments are harmlessly ig- nored.) The "rtd" instruction is supported by the 68010, 68020, 68030, 68040, 68060 and CPU32 processors, but not by the 68000 or 5200. The default is -mno-rtd. -malign-int -mno-align-int Control whether GCC aligns "int", "long", "long long", "float", "dou- ble", and "long double" variables on a 32-bit boundary (-malign-int) or a 16-bit boundary (-mno-align-int). Aligning variables on 32-bit boundaries produces code that runs somewhat faster on processors with 32-bit busses at the expense of more memory. Warning: if you use the -malign-int switch, GCC aligns structures con- taining the above types differently than most published application bi- nary interface specifications for the m68k. Use the pc-relative addressing mode of the 68000 directly, instead of using a global offset table. At present, this option implies -fpic, allowing at most a 16-bit offset for pc-relative addressing. -fPIC is not presently supported with -mpcrel, though this could be supported for 68020 and higher processors. -mno-strict-align -mstrict-align Do not (do) assume that unaligned memory references are handled by the system. -msep-data -mno-sep-data With -msep-data, generate code that allows the data segment to be lo- cated in a different area of memory from the text segment. This allows for execute-in-place in an environment without virtual memory manage- ment. This option implies -fPIC. This option is disabled by default; GCC generates code that assumes that the data segment follows the text segment. -mid-shared-library -mno-id-shared-library If enabled, generate code that supports shared libraries via the li- brary ID method. This allows for execute-in-place and shared libraries in an environment without virtual memory management. This option im- plies -fPIC. This option is disabled by default. -mshared-library-id=n Specifies the identification number of the ID-based shared library be- ing compiled. Specifying a value of 0 generates more compact code; specifying other values forces the allocation of that number to the current library, but is no more space- or time-efficient than omitting this option. -mxgot -mno-xgot When generating position-independent code for ColdFire, generate code that works if the GOT has more than 8192 entries. This code is larger and slower than code generated without this option. On M680x0 proces- sors, this option is not needed; -fPIC suffices. GCC normally uses a single instruction to load values from the GOT. While this is relatively efficient, it only works if the GOT is smaller than about 64k. Anything larger causes the linker to report an error such as: relocation truncated to fit: R_68K_GOT16O foobar If this happens, you should recompile your code with -mxgot. It should then work with very large GOTs. However, code generated with -mxgot is less efficient, since it takes 4 instructions to fetch the value of a global symbol. Note that some linkers, including newer versions of the GNU linker, can create multiple GOTs and sort GOT entries. If you have such a linker, you should only need to use -mxgot when compiling a single object file that accesses more than 8192 GOT entries. Very few do. These options have no effect unless GCC is generating position-indepen- dent code. -mxtls Support TLS segment larger than 64K. The considerations for using this option are similar to those for -mxgot above; the default 16-bit offset addressing for TLS is more efficient, but this may be inadequate for some programs. -mlong-jump-table-offsets Use 32-bit offsets in "switch" tables. The default is to use 16-bit offsets. MCore Options These are the -m options defined for the Motorola M*Core processors. -mhardlit -mno-hardlit Inline constants into the code stream if it can be done in two instruc- tions or less. -mdiv -mno-div Use the divide instruction. (Enabled by default). -mrelax-immediates -mno-relax-immediates Allow arbitrary-sized immediates in bit operations. -mwide-bitfields -mno-wide-bitfields Always treat bit-fields as "int"-sized. -m4byte-functions -mno-4byte-functions Force all functions to be aligned to a 4-byte boundary. -mcallgraph-data -mno-callgraph-data Emit callgraph information. -mslow-bytes -mno-slow-bytes Prefer word access when reading byte quantities. -mlittle-endian -mbig-endian Generate code for a little- or big-endian target, respectively. The default is big-endian. Little-endian code is supported only with -m340. -m210 Generate code for the 210 processor. -m340 Generate code for the 340 processor. -mno-lsim Assume that runtime support has been provided and so omit the simulator library (libsim.a) from the linker command line. -mstack-increment=size Set the maximum amount for a single stack increment operation. Large values can increase the speed of programs that contain functions that need a large amount of stack space, but they can also trigger a segmen- tation fault if the stack is extended too much. The default value is 0x1000. MicroBlaze Options -msoft-float Use software emulation for floating point (default). -mhard-float Use hardware floating-point instructions. -mmemcpy Do not optimize block moves, use "memcpy". -mcpu=cpu-type Use features of, and schedule code for, the given CPU. Supported val- ues are in the format vX.YY.Z, where X is a major version, YY is the minor version, and Z is compatibility code. Example values are v3.00.a, v4.00.b, v5.00.a, v5.00.b, v6.00.a. -mxl-soft-mul -mno-xl-soft-mul Use software multiply emulation. This is enabled by default. -mxl-soft-div -mno-xl-soft-div Use software emulation for divides. This is enabled by default. -mxl-barrel-shift Use the hardware barrel shifter. -mxl-pattern-compare Use pattern compare instructions. -msmall-divides Use table lookup optimization for small signed integer divisions. -mxl-gp-opt Use GP-relative ".sdata"/".sbss" sections. -mxl-multiply-high Use multiply high instructions for high part of 32x32 multiply. -mxl-float-convert Use hardware floating-point conversion instructions. -mxl-float-sqrt Use hardware floating-point square root instruction. -mbig-endian Generate code for a big-endian target. -mlittle-endian Generate code for a little-endian target. -mxl-reorder Use reorder instructions (swap and byte reversed load/store). -mxl-mode-app-model Select application model app-model. Valid models are executable normal executable (default), uses startup code crt0.o. xmdstub for use with Xilinx Microprocessor Debugger (XMD) based software intrusive debug agent called xmdstub. This uses startup file crt1.o and sets the start address of the program to 0x800. bootstrap for applications that are loaded using a bootloader. This model uses startup file crt2.o which does not contain a processor reset vector handler. This is suitable for transferring control on a processor reset to the bootloader rather than the application. novectors for applications that do not require any of the MicroBlaze vectors. This option may be useful for applications running within a moni- toring application. This model uses crt3.o as a startup file. -mxl-prefetch Enable insertion of prefetch ("wic") instructions at call sites. -mpic-data-is-text-relative Assume that the displacement between the text and data segments is fixed at static link time. This allows data to be referenced by offset from start of text address instead of GOT since PC-relative addressing is not supported. MIPS Options -EB -mebGenerate big-endian code. -EL -melGenerate little-endian code. This is the default for mips*el-*-* con- figurations. -march=arch Generate code that runs on arch, which can be the name of a generic MIPS ISA, or the name of a particular processor. The ISA names are: mips1, mips2, mips3, mips4, mips32, mips32r2, mips32r3, mips32r5, mips32r6, mips64, mips64r2, mips64r3, mips64r5 and mips64r6. The processor names are: 4kc, 4km, 4kp, 4ksc, 4kec, 4kem, 4kep, 4ksd, 5kc, 5kf, 20kc, 24kc, 24kf2_1, 24kf1_1, 24kec, 24kef2_1, 24kef1_1, 34kc, 34kf2_1, 34kf1_1, 34kn, 74kc, 74kf2_1, 74kf1_1, 74kf3_2, 1004kc, 1004kf2_1, 1004kf1_1, i6400, i6500, interaptiv, loongson2e, loongson2f, loongson3a, gs464, gs464e, gs264e, m4k, m14k, m14kc, m14ke, m14kec, m5100, m5101, octeon, octeon+, octeon2, octeon3, orion, p5600, p6600, r2000, r3000, r3900, r4000, r4400, r4600, r4650, r4700, r5900, r6000, r8000, rm7000, rm9000, r10000, r12000, r14000, r16000, sb1, sr71000, vr4100, vr4111, vr4120, vr4130, vr4300, vr5000, vr5400, vr5500, xlr and xlp. allegrex, The special value from-abi selects the most compatible architecture for the selected ABI (that is, mips1 for 32-bit ABIs and mips3 for 64-bit ABIs). The native Linux/GNU toolchain also supports the value native, which selects the best architecture option for the host processor. -march=native has no effect if GCC does not recognize the processor. In processor names, a final 000 can be abbreviated as k (for example, -march=r2k). Prefixes are optional, and vr may be written r. Names of the form nf2_1 refer to processors with FPUs clocked at half the rate of the core, names of the form nf1_1 refer to processors with FPUs clocked at the same rate as the core, and names of the form nf3_2 refer to processors with FPUs clocked a ratio of 3:2 with respect to the core. For compatibility reasons, nf is accepted as a synonym for nf2_1 while nx and bfx are accepted as synonyms for nf1_1. GCC defines two macros based on the value of this option. The first is "_MIPS_ARCH", which gives the name of target architecture, as a string. The second has the form "_MIPS_ARCH_foo", where foo is the capitalized value of "_MIPS_ARCH". For example, -march=r2000 sets "_MIPS_ARCH" to "r2000" and defines the macro "_MIPS_ARCH_R2000". Note that the "_MIPS_ARCH" macro uses the processor names given above. In other words, it has the full prefix and does not abbreviate 000 as k. In the case of from-abi, the macro names the resolved architecture (either "mips1" or "mips3"). It names the default architecture when no -march option is given. -mtune=arch Optimize for arch. Among other things, this option controls the way instructions are scheduled, and the perceived cost of arithmetic opera- tions. The list of arch values is the same as for -march. When this option is not used, GCC optimizes for the processor specified by -march. By using -march and -mtune together, it is possible to gen- erate code that runs on a family of processors, but optimize the code for one particular member of that family. -mtune defines the macros "_MIPS_TUNE" and "_MIPS_TUNE_foo", which work in the same way as the -march ones described above. -mips1 Equivalent to -march=mips1. -mips2 Equivalent to -march=mips2. -mips3 Equivalent to -march=mips3. -mips4 Equivalent to -march=mips4. -mips32 Equivalent to -march=mips32. -mips32r3 Equivalent to -march=mips32r3. -mips32r5 Equivalent to -march=mips32r5. -mips32r6 Equivalent to -march=mips32r6. -mips64 Equivalent to -march=mips64. -mips64r2 Equivalent to -march=mips64r2. -mips64r3 Equivalent to -march=mips64r3. -mips64r5 Equivalent to -march=mips64r5. -mips64r6 Equivalent to -march=mips64r6. -mips16 -mno-mips16 Generate (do not generate) MIPS16 code. If GCC is targeting a MIPS32 or MIPS64 architecture, it makes use of the MIPS16e ASE. MIPS16 code generation can also be controlled on a per-function basis by means of "mips16" and "nomips16" attributes. -mmips16e2 -mno-mips16e2 Use (do not use) the MIPS16e2 ASE. This option modifies the behavior of the -mips16 option such that it targets the MIPS16e2 ASE. -mflip-mips16 -mflip-mips16 Generate MIPS16 code on alternating functions. This option is provided for regression testing of mixed MIPS16/non-MIPS16 code generation, and is not intended for ordinary use in compiling user code. -minterlink-compressed -mno-interlink-compressed Require (do not require) that code using the standard (uncompressed) MIPS ISA be link-compatible with MIPS16 and microMIPS code, and vice versa. For example, code using the standard ISA encoding cannot jump directly to MIPS16 or microMIPS code; it must either use a call or an indirect jump. -minterlink-compressed therefore disables direct jumps unless GCC knows that the target of the jump is not compressed. -minterlink-mips16 -mno-interlink-mips16 Aliases of -minterlink-compressed and -mno-interlink-compressed. These options predate the microMIPS ASE and are retained for backwards com- patibility. -mabi=32 -mabi=o64 -mabi=n32 -mabi=64 -mabi=eabi Generate code for the given ABI. Note that the EABI has a 32-bit and a 64-bit variant. GCC normally generates 64-bit code when you select a 64-bit architecture, but you can use -mgp32 to get 32-bit code instead. For information about the O64 ABI, see <https://gcc.gnu.org/projects/mipso64-abi.html>. GCC supports a variant of the o32 ABI in which floating-point registers are 64 rather than 32 bits wide. You can select this combination with -mabi=32 -mfp64. This ABI relies on the "mthc1" and "mfhc1" instruc- tions and is therefore only supported for MIPS32R2, MIPS32R3 and MIPS32R5 processors. The register assignments for arguments and return values remain the same, but each scalar value is passed in a single 64-bit register rather than a pair of 32-bit registers. For example, scalar float- ing-point values are returned in $f0 only, not a $f0/$f1 pair. The set of call-saved registers also remains the same in that the even-numbered double-precision registers are saved. Two additional variants of the o32 ABI are supported to enable a tran- sition from 32-bit to 64-bit registers. These are FPXX (-mfpxx) and FP64A (-mfp64 -mno-odd-spreg). The FPXX extension mandates that all code must execute correctly when run using 32-bit or 64-bit registers. The code can be interlinked with either FP32 or FP64, but not both. The FP64A extension is similar to the FP64 extension but forbids the use of odd-numbered single-precision registers. This can be used in conjunction with the "FRE" mode of FPUs in MIPS32R5 processors and al- lows both FP32 and FP64A code to interlink and run in the same process without changing FPU modes. -mabicalls -mno-abicalls Generate (do not generate) code that is suitable for SVR4-style dynamic objects. -mabicalls is the default for SVR4-based systems. -mshared -mno-shared Generate (do not generate) code that is fully position-independent, and that can therefore be linked into shared libraries. This option only affects -mabicalls. All -mabicalls code has traditionally been position-independent, re- gardless of options like -fPIC and -fpic. However, as an extension, the GNU toolchain allows executables to use absolute accesses for lo- cally-binding symbols. It can also use shorter GP initialization se- quences and generate direct calls to locally-defined functions. This mode is selected by -mno-shared. -mno-shared depends on binutils 2.16 or higher and generates objects that can only be linked by the GNU linker. However, the option does not affect the ABI of the final executable; it only affects the ABI of relocatable objects. Using -mno-shared generally makes executables both smaller and quicker. -mshared is the default. -mplt -mno-plt Assume (do not assume) that the static and dynamic linkers support PLTs and copy relocations. This option only affects -mno-shared -mabicalls. For the n64 ABI, this option has no effect without -msym32. You can make -mplt the default by configuring GCC with --with-mips-plt. The default is -mno-plt otherwise. -mxgot -mno-xgot Lift (do not lift) the usual restrictions on the size of the global offset table. GCC normally uses a single instruction to load values from the GOT. While this is relatively efficient, it only works if the GOT is smaller than about 64k. Anything larger causes the linker to report an error such as: relocation truncated to fit: R_MIPS_GOT16 foobar If this happens, you should recompile your code with -mxgot. This works with very large GOTs, although the code is also less efficient, since it takes three instructions to fetch the value of a global sym- bol. Note that some linkers can create multiple GOTs. If you have such a linker, you should only need to use -mxgot when a single object file accesses more than 64k's worth of GOT entries. Very few do. These options have no effect unless GCC is generating position indepen- dent code. -mgp32 Assume that general-purpose registers are 32 bits wide. -mgp64 Assume that general-purpose registers are 64 bits wide. -mfp32 Assume that floating-point registers are 32 bits wide. -mfp64 Assume that floating-point registers are 64 bits wide. -mfpxx Do not assume the width of floating-point registers. -mhard-float Use floating-point coprocessor instructions. -msoft-float Do not use floating-point coprocessor instructions. Implement float- ing-point calculations using library calls instead. -mno-float Equivalent to -msoft-float, but additionally asserts that the program being compiled does not perform any floating-point operations. This option is presently supported only by some bare-metal MIPS configura- tions, where it may select a special set of libraries that lack all floating-point support (including, for example, the floating-point "printf" formats). If code compiled with -mno-float accidentally con- tains floating-point operations, it is likely to suffer a link-time or run-time failure. -msingle-float Assume that the floating-point coprocessor only supports single-preci- sion operations. -mdouble-float Assume that the floating-point coprocessor supports double-precision operations. This is the default. -modd-spreg -mno-odd-spreg Enable the use of odd-numbered single-precision floating-point regis- ters for the o32 ABI. This is the default for processors that are known to support these registers. When using the o32 FPXX ABI, -mno-odd-spreg is set by default. -mabs=2008 -mabs=legacy These options control the treatment of the special not-a-number (NaN) IEEE 754 floating-point data with the "abs.fmt" and "neg.fmt" machine instructions. By default or when -mabs=legacy is used the legacy treatment is se- lected. In this case these instructions are considered arithmetic and avoided where correct operation is required and the input operand might be a NaN. A longer sequence of instructions that manipulate the sign bit of floating-point datum manually is used instead unless the -ffi- nite-math-only option has also been specified. The -mabs=2008 option selects the IEEE 754-2008 treatment. In this case these instructions are considered non-arithmetic and therefore op- erating correctly in all cases, including in particular where the input operand is a NaN. These instructions are therefore always used for the respective operations. -mnan=2008 -mnan=legacy These options control the encoding of the special not-a-number (NaN) IEEE 754 floating-point data. The -mnan=legacy option selects the legacy encoding. In this case quiet NaNs (qNaNs) are denoted by the first bit of their trailing sig- nificand field being 0, whereas signaling NaNs (sNaNs) are denoted by the first bit of their trailing significand field being 1. The -mnan=2008 option selects the IEEE 754-2008 encoding. In this case qNaNs are denoted by the first bit of their trailing significand field being 1, whereas sNaNs are denoted by the first bit of their trailing significand field being 0. The default is -mnan=legacy unless GCC has been configured with --with-nan=2008. -mllsc -mno-llsc Use (do not use) ll, sc, and sync instructions to implement atomic mem- ory built-in functions. When neither option is specified, GCC uses the instructions if the target architecture supports them. -mllsc is useful if the runtime environment can emulate the instruc- tions and -mno-llsc can be useful when compiling for nonstandard ISAs. You can make either option the default by configuring GCC with --with-llsc and --without-llsc respectively. --with-llsc is the de- fault for some configurations; see the installation documentation for details. -mdsp -mno-dsp Use (do not use) revision 1 of the MIPS DSP ASE. This option defines the preprocessor macro "__mips_dsp". It also de- fines "__mips_dsp_rev" to 1. -mdspr2 -mno-dspr2 Use (do not use) revision 2 of the MIPS DSP ASE. This option defines the preprocessor macros "__mips_dsp" and "__mips_dspr2". It also defines "__mips_dsp_rev" to 2. -msmartmips -mno-smartmips Use (do not use) the MIPS SmartMIPS ASE. -mpaired-single -mno-paired-single Use (do not use) paired-single floating-point instructions. This option requires hardware floating-point support to be enabled. -mdmx -mno-mdmx Use (do not use) MIPS Digital Media Extension instructions. This op- tion can only be used when generating 64-bit code and requires hardware floating-point support to be enabled. -mips3d -mno-mips3d Use (do not use) the MIPS-3D ASE. The option -mips3d implies -mpaired-single. -mmicromips -mno-micromips Generate (do not generate) microMIPS code. MicroMIPS code generation can also be controlled on a per-function ba- sis by means of "micromips" and "nomicromips" attributes. -mmt -mno-mt Use (do not use) MT Multithreading instructions. -mmcu -mno-mcu Use (do not use) the MIPS MCU ASE instructions. -meva -mno-eva Use (do not use) the MIPS Enhanced Virtual Addressing instructions. -mvirt -mno-virt Use (do not use) the MIPS Virtualization (VZ) instructions. -mxpa -mno-xpa Use (do not use) the MIPS eXtended Physical Address (XPA) instructions. -mcrc -mno-crc Use (do not use) the MIPS Cyclic Redundancy Check (CRC) instructions. -mginv -mno-ginv Use (do not use) the MIPS Global INValidate (GINV) instructions. -mmsa -mno-msa Use (do not use) the MIPS MSA extension instructions. -mloongson-mmi -mno-loongson-mmi Use (do not use) the MIPS Loongson MultiMedia extensions Instructions (MMI). -mloongson-ext -mno-loongson-ext Use (do not use) the MIPS Loongson EXTensions (EXT) instructions. -mloongson-ext2 -mno-loongson-ext2 Use (do not use) the MIPS Loongson EXTensions r2 (EXT2) instructions. -mlong64 Force "long" types to be 64 bits wide. See -mlong32 for an explanation of the default and the way that the pointer size is determined. -mlong32 Force "long", "int", and pointer types to be 32 bits wide. The default size of "int"s, "long"s and pointers depends on the ABI. All the supported ABIs use 32-bit "int"s. The n64 ABI uses 64-bit "long"s, as does the 64-bit EABI; the others use 32-bit "long"s. Pointers are the same size as "long"s, or the same size as integer reg- isters, whichever is smaller. -msym32 -mno-sym32 Assume (do not assume) that all symbols have 32-bit values, regardless of the selected ABI. This option is useful in combination with -mabi=64 and -mno-abicalls because it allows GCC to generate shorter and faster references to symbolic addresses. -G num Put definitions of externally-visible data in a small data section if that data is no bigger than num bytes. GCC can then generate more ef- ficient accesses to the data; see -mgpopt for details. The default -G option depends on the configuration. -mlocal-sdata -mno-local-sdata Extend (do not extend) the -G behavior to local data too, such as to static variables in C. -mlocal-sdata is the default for all configura- tions. If the linker complains that an application is using too much small data, you might want to try rebuilding the less performance-critical parts with -mno-local-sdata. You might also want to build large li- braries with -mno-local-sdata, so that the libraries leave more room for the main program. -mextern-sdata -mno-extern-sdata Assume (do not assume) that externally-defined data is in a small data section if the size of that data is within the -G limit. -mex- tern-sdata is the default for all configurations. If you compile a module Mod with -mextern-sdata -G num -mgpopt, and Mod references a variable Var that is no bigger than num bytes, you must make sure that Var is placed in a small data section. If Var is de- fined by another module, you must either compile that module with a high-enough -G setting or attach a "section" attribute to Var's defini- tion. If Var is common, you must link the application with a high-enough -G setting. The easiest way of satisfying these restrictions is to compile and link every module with the same -G option. However, you may wish to build a library that supports several different small data limits. You can do this by compiling the library with the highest supported -G setting and additionally using -mno-extern-sdata to stop the library from making assumptions about externally-defined data. -mgpopt -mno-gpopt Use (do not use) GP-relative accesses for symbols that are known to be in a small data section; see -G, -mlocal-sdata and -mextern-sdata. -mgpopt is the default for all configurations. -mno-gpopt is useful for cases where the $gp register might not hold the value of "_gp". For example, if the code is part of a library that might be used in a boot monitor, programs that call boot monitor rou- tines pass an unknown value in $gp. (In such situations, the boot mon- itor itself is usually compiled with -G0.) -mno-gpopt implies -mno-local-sdata and -mno-extern-sdata. -membedded-data -mno-embedded-data 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 RAM required when executing, and thus may be preferred for some embedded systems. -muninit-const-in-rodata -mno-uninit-const-in-rodata Put uninitialized "const" variables in the read-only data section. This option is only meaningful in conjunction with -membedded-data. -mcode-readable=setting Specify whether GCC may generate code that reads from executable sec- tions. There are three possible settings: -mcode-readable=yes Instructions may freely access executable sections. This is the default setting. -mcode-readable=pcrel MIPS16 PC-relative load instructions can access executable sec- tions, but other instructions must not do so. This option is use- ful on 4KSc and 4KSd processors when the code TLBs have the Read Inhibit bit set. It is also useful on processors that can be con- figured to have a dual instruction/data SRAM interface and that, like the M4K, automatically redirect PC-relative loads to the in- struction RAM. -mcode-readable=no Instructions must not access executable sections. This option can be useful on targets that are configured to have a dual instruc- tion/data SRAM interface but that (unlike the M4K) do not automati- cally redirect PC-relative loads to the instruction RAM. On SDE targets, -mcode-data-in-code is available as a traditional alias for -mcode-readable=no, and -mcode-xonly for -mcode-readable=pcrel. -msplit-addresses -mno-split-addresses Enable (disable) use of the %hi() and %lo() assembler relocation opera- tors. This option has been superseded by -mexplicit-relocs but is re- tained for backwards compatibility. -mexplicit-relocs=none -mexplicit-relocs=base -mexplicit-relocs=pcrel -mexplicit-relocs -mno-explicit-relocs These options control whether explicit relocs (such as %gp_rel) are used. The default value depends on the version of GAS when GCC itself was built. The "base" explicit-relocs support was introduced into GAS in 2001. The "pcrel" explicit-relocs support was introduced into GAS in 2014, which supports %pcrel_hi and %pcrel_lo. -mcheck-zero-division -mno-check-zero-division Trap (do not trap) on integer division by zero. The default is -mcheck-zero-division. -mdivide-traps -mdivide-breaks MIPS systems check for division by zero by generating either a condi- tional trap or a break instruction. Using traps results in smaller code, but is only supported on MIPS II and later. Also, some versions of the Linux kernel have a bug that prevents trap from generating the proper signal ("SIGFPE"). Use -mdivide-traps to allow conditional traps on architectures that support them and -mdivide-breaks to force the use of breaks. The default is usually -mdivide-traps, but this can be overridden at configure time using --with-divide=breaks. Divide-by-zero checks can be completely disabled using -mno-check-zero-division. -mload-store-pairs -mno-load-store-pairs Enable (disable) an optimization that pairs consecutive load or store instructions to enable load/store bonding. This option is enabled by default but only takes effect when the selected architecture is known to support bonding. -mstrict-align -mno-strict-align -munaligned-access -mno-unaligned-access Disable (enable) direct unaligned access for MIPS Release 6. MIPSr6 requires load/store unaligned-access support, either by hardware or by trapping and emulation. In the latter case -mstrict-align may be needed by the operating system kernel. The options -munaligned-access and -mno-unaligned-access are obsolete, and only provided for backward compatibility. -mmemcpy -mno-memcpy Force (do not force) the use of "memcpy" for non-trivial block moves. The default is -mno-memcpy, which allows GCC to inline most con- stant-sized copies. -mlong-calls -mno-long-calls Disable (do not disable) use of the "jal" instruction. Calling func- tions using "jal" is more efficient but requires the caller and callee to be in the same 256 megabyte segment. This option has no effect on abicalls code. The default is -mno-long-calls. -mmad -mno-mad Enable (disable) use of the "mad", "madu" and "mul" instructions, as provided by the R4650 ISA. -mimadd -mno-imadd Enable (disable) use of the "madd" and "msub" integer instructions. The default is -mimadd on architectures that support "madd" and "msub" except for the 74k architecture where it was found to generate slower code. -mfused-madd -mno-fused-madd Enable (disable) use of the floating-point multiply-accumulate instruc- tions, when they are available. The default is -mfused-madd. On the R8000 CPU when multiply-accumulate instructions are used, the intermediate product is calculated to infinite precision and is not subject to the FCSR Flush to Zero bit. This may be undesirable in some circumstances. On other processors the result is numerically identical to the equivalent computation using separate multiply, add, subtract and negate instructions. -nocpp Tell the MIPS assembler to not run its preprocessor over user assembler files (with a .s suffix) when assembling them. -mfix-24k -mno-fix-24k Work around the 24K E48 (lost data on stores during refill) errata. The workarounds are implemented by the assembler rather than by GCC. -mfix-r4000 -mno-fix-r4000 Work around certain R4000 CPU errata: - A double-word or a variable shift may give an incorrect result if executed immediately after starting an integer division. - A double-word or a variable shift may give an incorrect result if executed while an integer multiplication is in progress. - An integer division may give an incorrect result if started in a delay slot of a taken branch or a jump. -mfix-r4400 -mno-fix-r4400 Work around certain R4400 CPU errata: - A double-word or a variable shift may give an incorrect result if executed immediately after starting an integer division. -mfix-r10000 -mno-fix-r10000 Work around certain R10000 errata: - "ll"/"sc" sequences may not behave atomically on revisions prior to 3.0. They may deadlock on revisions 2.6 and earlier. This option can only be used if the target architecture supports branch-likely instructions. -mfix-r10000 is the default when -march=r10000 is used; -mno-fix-r10000 is the default otherwise. -mfix-r5900 -mno-fix-r5900 Do not attempt to schedule the preceding instruction into the delay slot of a branch instruction placed at the end of a short loop of six instructions or fewer and always schedule a "nop" instruction there in- stead. The short loop bug under certain conditions causes loops to ex- ecute only once or twice, due to a hardware bug in the R5900 chip. The workaround is implemented by the assembler rather than by GCC. -mfix-rm7000 -mno-fix-rm7000 Work around the RM7000 "dmult"/"dmultu" errata. The workarounds are implemented by the assembler rather than by GCC. -mfix-vr4120 -mno-fix-vr4120 Work around certain VR4120 errata: - "dmultu" does not always produce the correct result. - "div" and "ddiv" do not always produce the correct result if one of the operands is negative. The workarounds for the division errata rely on special functions in libgcc.a. At present, these functions are only provided by the "mips64vr*-elf" configurations. Other VR4120 errata require a NOP to be inserted between certain pairs of instructions. These errata are handled by the assembler, not by GCC itself. -mfix-vr4130 -mno-fix-vr4130 Work around the VR4130 "mflo"/"mfhi" errata. The workarounds are im- plemented by the assembler rather than by GCC, although GCC avoids us- ing "mflo" and "mfhi" if the VR4130 "macc", "macchi", "dmacc" and "dmacchi" instructions are available instead. -mfix-sb1 -mno-fix-sb1 Work around certain SB-1 CPU core errata. (This flag currently works around the SB-1 revision 2 "F1" and "F2" floating-point errata.) -mfix4300 -mno-fix4300 Work around a bug in early VR4300 silicon that causes multiplies with certain operands to corrupt immediately following multiplies. -mr10k-cache-barrier=setting Specify whether GCC should insert cache barriers to avoid the side ef- fects of speculation on R10K processors. In common with many processors, the R10K tries to predict the outcome of a conditional branch and speculatively executes instructions from the "taken" branch. It later aborts these instructions if the pre- dicted outcome is wrong. However, on the R10K, even aborted instruc- tions can have side effects. This problem only affects kernel stores and, depending on the system, kernel loads. As an example, a speculatively-executed store may load the target memory into cache and mark the cache line as dirty, even if the store itself is later aborted. If a DMA operation writes to the same area of memory before the "dirty" line is flushed, the cached data overwrites the DMA-ed data. See the R10K processor manual for a full description, including other potential problems. One workaround is to insert cache barrier instructions before every memory access that might be speculatively executed and that might have side effects even if aborted. -mr10k-cache-barrier=setting controls GCC's implementation of this workaround. It assumes that aborted ac- cesses to any byte in the following regions does not have side effects: 1. the memory occupied by the current function's stack frame; 2. the memory occupied by an incoming stack argument; 3. the memory occupied by an object with a link-time-constant address. It is the kernel's responsibility to ensure that speculative accesses to these regions are indeed safe. If the input program contains a function declaration such as: void foo (void); then the implementation of "foo" must allow "j foo" and "jal foo" to be executed speculatively. GCC honors this restriction for functions it compiles itself. It expects non-GCC functions (such as hand-written assembly code) to do the same. The option has three forms: -mr10k-cache-barrier=load-store Insert a cache barrier before a load or store that might be specu- latively executed and that might have side effects even if aborted. -mr10k-cache-barrier=store Insert a cache barrier before a store that might be speculatively executed and that might have side effects even if aborted. -mr10k-cache-barrier=none Disable the insertion of cache barriers. This is the default set- ting. -mflush-func=func -mno-flush-func 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 ar- guments as the common "_flush_func", 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 "_flush_func" or "__cpu_flush". -mbranch-cost=num Set the cost of branches to roughly num "simple" instructions. This cost is only a heuristic and is not guaranteed to produce consistent results across releases. A zero cost redundantly selects the default, which is based on the -mtune setting. -mbranch-likely -mno-branch-likely Enable or disable use of Branch Likely instructions, regardless of the default for the selected architecture. By default, Branch Likely in- structions may be generated if they are supported by the selected ar- chitecture. An exception is for the MIPS32 and MIPS64 architectures and processors that implement those architectures; for those, Branch Likely instructions are not be generated by default because the MIPS32 and MIPS64 architectures specifically deprecate their use. -mcompact-branches=never -mcompact-branches=optimal -mcompact-branches=always These options control which form of branches are generated. The de- fault is -mcompact-branches=optimal. The -mcompact-branches=never option ensures that compact branch in- structions are never generated. The -mcompact-branches=always option ensures that a compact branch in- struction is generated if available for MIPS Release 6 onwards. If a compact branch instruction is not available (or pre-R6), a delay slot form of the branch is used instead. If it is used for MIPS16/microMIPS targets, it is just ignored now. The behavior for MIPS16/microMIPS may change in future, since they do have some compact branch instructions. The -mcompact-branches=optimal option causes a delay slot branch to be used if one is available in the current ISA and the delay slot is suc- cessfully filled. If the delay slot is not filled, a compact branch is chosen if one is available. -mfp-exceptions -mno-fp-exceptions Specifies whether FP exceptions are enabled. This affects how FP in- structions are scheduled for some processors. The default is that FP exceptions are enabled. For instance, on the SB-1, if FP exceptions are disabled, and we are emitting 64-bit code, then we can use both FP pipes. Otherwise, we can only use one FP pipe. -mvr4130-align -mno-vr4130-align The VR4130 pipeline is two-way superscalar, but can only issue two in- structions together if the first one is 8-byte aligned. When this op- tion is enabled, GCC aligns pairs of instructions that it thinks should execute in parallel. This option only has an effect when optimizing for the VR4130. It nor- mally makes code faster, but at the expense of making it bigger. It is enabled by default at optimization level -O3. -msynci -mno-synci Enable (disable) generation of "synci" instructions on architectures that support it. The "synci" instructions (if enabled) are generated when "__builtin___clear_cache" is compiled. This option defaults to -mno-synci, but the default can be overridden by configuring GCC with --with-synci. When compiling code for single processor systems, it is generally safe to use "synci". However, on many multi-core (SMP) systems, it does not invalidate the instruction caches on all cores and may lead to unde- fined behavior. -mrelax-pic-calls -mno-relax-pic-calls Try to turn PIC calls that are normally dispatched via register $25 into direct calls. This is only possible if the linker can resolve the destination at link time and if the destination is within range for a direct call. -mrelax-pic-calls is the default if GCC was configured to use an assem- bler and a linker that support the ".reloc" assembly directive and -mexplicit-relocs is in effect. With -mno-explicit-relocs, this opti- mization can be performed by the assembler and the linker alone without help from the compiler. -mmcount-ra-address -mno-mcount-ra-address Emit (do not emit) code that allows "_mcount" to modify the calling function's return address. When enabled, this option extends the usual "_mcount" interface with a new ra-address parameter, which has type "intptr_t *" and is passed in register $12. "_mcount" can then modify the return address by doing both of the following: * Returning the new address in register $31. * Storing the new address in "*ra-address", if ra-address is nonnull. The default is -mno-mcount-ra-address. -mframe-header-opt -mno-frame-header-opt Enable (disable) frame header optimization in the o32 ABI. When using the o32 ABI, calling functions allocates 16 bytes on the stack for the called function to write out register arguments. When enabled, this optimization suppresses the allocation of the frame header if it can be determined that it is unused. This optimization is off by default at all optimization levels. -mlxc1-sxc1 -mno-lxc1-sxc1 When applicable, enable (disable) the generation of "lwxc1", "swxc1", "ldxc1", "sdxc1" instructions. Enabled by default. -mmadd4 -mno-madd4 When applicable, enable (disable) the generation of 4-operand "madd.s", "madd.d" and related instructions. Enabled by default. MMIX Options These options are defined for the MMIX: -mlibfuncs -mno-libfuncs Specify that intrinsic library functions are being compiled, passing all values in registers, no matter the size. -mepsilon -mno-epsilon Generate floating-point comparison instructions that compare with re- spect to the "rE" epsilon register. -mabi=mmixware -mabi=gnu Generate code that passes function parameters and return values that (in the called function) are seen as registers $0 and up, as opposed to the GNU ABI which uses global registers $231 and up. -mzero-extend -mno-zero-extend 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. -mknuthdiv -mno-knuthdiv Make the result of a division yielding a remainder have the same sign as the divisor. With the default, -mno-knuthdiv, the sign of the re- mainder follows the sign of the dividend. Both methods are arithmeti- cally valid, the latter being almost exclusively used. -mtoplevel-symbols -mno-toplevel-symbols Prepend (do not prepend) a : to all global symbols, so the assembly code can be used with the "PREFIX" assembly directive. -melf Generate an executable in the ELF format, rather than the default mmo format used by the mmix simulator. -mbranch-predict -mno-branch-predict Use (do not use) the probable-branch instructions, when static branch prediction indicates a probable branch. -mbase-addresses -mno-base-addresses Generate (do not generate) code that uses base addresses. 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 reg- ister 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 sta- tic data may require -mno-base-addresses. -msingle-exit -mno-single-exit Force (do not force) generated code to have a single exit point in each function. -mset-data-start=address When linking, set the start of the data section to address. -mset-program-start=address -mno-set-program-start When linking, set the program start address to address. It defaults to 0x100 unless -mno-set-program-start is used to suppress this option en- tirely. MN10300 Options These -m options are defined for Matsushita MN10300 architectures: -mmult-bug -mno-mult-bug When enabled, generate code to avoid bugs in the multiply instructions for the MN10300 processors. This is the default. -mam33 -mno-am33 Generate code using features specific to the AM33 processor. The de- fault is -mno-am33. -mam33-2 -mno-am33-2 Generate code using features specific to the AM33/2.0 processor. The default is -mno-am33-2. -mam34 -mno-am34 Generate code using features specific to the AM34 processor. The de- fault is -mno-am34. -mtune=cpu-type Use the timing characteristics of the indicated CPU type when schedul- ing instructions. This does not change the targeted processor type. The CPU type must be one of mn10300, am33, am33-2 or am34. -mreturn-pointer-on-d0 -mno-return-pointer-on-d0 When generating a function that returns a pointer, return the pointer in both "a0" and "d0". Otherwise, the pointer is returned only in "a0", and attempts to call such functions without a prototype result in errors. Note that this option is on by default; use -mno-re- turn-pointer-on-d0 to disable it. -mno-crt0 Do not link in the C run-time initialization object file. -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. This option makes symbolic debugging impossible. -mliw -mno-liw Allow the compiler to generate Long Instruction Word instructions if the target is the AM33 or later. This option is enabled by default. -mliw defines the preprocessor macro "__LIW__"; -mno-liw defines the preprocessor macro "__NO_LIW__". -msetlb -mno-setlb Allow the compiler to generate the SETLB and Lcc instructions if the target is the AM33 or later. This option is enabled by default. -msetlb defines the preprocessor macro "__SETLB__"; -mno-setlb defines the preprocessor macro "__NO_SETLB__". Moxie Options -mebGenerate big-endian code. This is the default for moxie-*-* configura- tions. -melGenerate little-endian code. -mmul.x -mno-mul.x Generate mul.x and umul.x instructions. This option is enabled by de- fault for moxiebox-*-* configurations. -mno-crt0 Do not link in the C run-time initialization object file. MSP430 Options These options are defined for the MSP430: -masm-hex Force assembly output to always use hex constants. Normally such con- stants are signed decimals, but this option is available for testsuite and/or aesthetic purposes. -mmcu=name Select the MCU to target. This is used to create a C preprocessor sym- bol based upon the MCU name, converted to upper case and pre- and post-fixed with __. This in turn is used by the msp430.h header file to select an MCU-specific supplementary header file. The option also sets the ISA to use. If the MCU name is one that is known to only support the 430 ISA then that is selected, otherwise the 430X ISA is selected. A generic MCU name of msp430 can also be used to select the 430 ISA. Similarly the generic msp430x MCU name selects the 430X ISA. In addition an MCU-specific linker script is added to the linker com- mand line. The script's name is the name of the MCU with .ld appended. Thus specifying -mmcu=xxx on the gcc command line defines the C pre- processor symbol "__XXX__" and cause the linker to search for a script called xxx.ld. The ISA and hardware multiply supported for the different MCUs is hard-coded into GCC. However, an external devices.csv file can be used to extend device support beyond those that have been hard-coded. GCC searches for the devices.csv file using the following methods in the given precedence order, where the first method takes precedence over the second which takes precedence over the third. Include path specified with -I and -L devices.csv is searched for in each of the directories specified by include paths and linker library search paths. Path specified by the environment variable MSP430_GCC_INCLUDE_DIR Define the value of the global environment variable MSP430_GCC_IN- CLUDE_DIR to the full path to the directory containing devices.csv, and GCC will search this directory for devices.csv. If devices.csv is found, this directory is also registered as an include path and linker library path. Header files and linker scripts in this di- rectory can therefore be used without manually specifying -I and -L on the command line. The msp430-elf{,bare}/include/devices directory Finally, GCC examines msp430-elf{,bare}/include/devices from the toolchain root directory. This directory does not exist in a de- fault installation, but if you have created it and copied de- vices.csv there, then the MCU data is read. As above, this direc- tory is also registered as an include path and linker library path. If none of the above search methods find devices.csv, then the hard-coded MCU data is used. -mwarn-mcu -mno-warn-mcu This option enables or disables warnings about conflicts between the MCU name specified by the -mmcu option and the ISA set by the -mcpu op- tion and/or the hardware multiply support set by the -mhwmult option. It also toggles warnings about unrecognized MCU names. This option is on by default. -msim Link to the simulator runtime libraries and linker script. Overrides any scripts that would be selected by the -mmcu= option. -mlarge Use large-model addressing (20-bit pointers, 20-bit "size_t"). -msmall Use small-model addressing (16-bit pointers, 16-bit "size_t"). -mrelax This option is passed to the assembler and linker, and allows the linker to perform certain optimizations that cannot be done until the final link. mhwmult=type Describes the type of hardware multiply supported by the target. Ac- cepted values for type are none for no hardware multiply, 16bit for the original 16-bit-only multiply supported by early MCUs. 32bit for the 16/32-bit multiply supported by later MCUs and f5series for the 16/32-bit multiply supported by F5-series MCUs. A value of auto can also be given. This tells GCC to deduce the hardware multiply support based upon the MCU name provided by the -mmcu option. If no -mmcu op- tion is specified or if the MCU name is not recognized, then no hard- ware multiply support is assumed. "auto" is the default setting. Hardware multiplies are normally performed by calling a library rou- tine. This saves space in the generated code. When compiling at -O3 or higher however the hardware multiplier is invoked inline. This makes for bigger, but faster code. The hardware multiply routines disable interrupts whilst running and restore the previous interrupt state when they finish. This makes them safe to use inside interrupt handlers as well as in normal code. -minrt Enable the use of a minimum runtime environment without support for static initializers or constructors. This is intended for memory-con- strained devices. The compiler includes special symbols in some ob- jects that tell the linker and runtime which code fragments are re- quired. -mtiny-printf Enable reduced code size "printf" and "puts" library functions. The tiny implementations of these functions are not reentrant, so must be used with caution in multi-threaded applications. Support for streams has been removed and the string to be printed are always sent to stdout via the "write" syscall. The string is not buffered before it is sent to write. This option requires Newlib Nano IO, so GCC must be configured with --enable-newlib-nano-formatted-io. -mmax-inline-shift=n This option takes an integer n between 0 and 64 inclusive, and sets the maximum number of inline shift instructions which should be emitted to perform a shift operation by a constant amount. When this value needs to be exceeded, an mspabi helper function is used instead. The default value is 4. This only affects cases where a shift by multiple positions cannot be completed with a single instruction (e.g. all shifts >1 on the 430 ISA). Shifts of a 32-bit value are at least twice as costly, so the value passed for this option is divided by 2 and the resulting value used in- stead. -mcode-region=where -mdata-region=where These options tell the compiler where to place functions and data that do not have one of the "lower", "upper", "either" or "section" attrib- utes. Possible values for where are lower, upper, either or any. The first three behave like the corresponding attribute. The fourth possi- ble value, any, is the default. It leaves placement entirely up to the linker script and how it assigns the standard sections (".text", ".data", etc) to the memory regions. -muse-lower-region-prefix Add the .lower prefix to section names when compiling with -mcode-re- gion=lower or -mdata-region=lower. Disabled by default. -msilicon-errata=name[,name...] This option passes on a request to assembler to enable the fixes for the named silicon errata. Refer to the assembler documentation for de- tails. -msilicon-errata-warn=name[,name...] This option passes on a request to the assembler to enable warning mes- sages when a named silicon errata might need to be applied. Refer to the assembler documentation for details. -mwarn-devices-csv -mno-warn-devices-csv Warn if devices.csv is not found or there are problems parsing it (de- fault: on). NDS32 Options These options are defined for NDS32 implementations: -mbig-endian -EB Generate code in big-endian mode. -mlittle-endian -EL Generate code in little-endian mode. -mabi=2 -mfloat-abi=soft Use the soft floating-point ABI. -mabi=2fp+ -mfloat-abi=hard Use the hard floating-point ABI. -mreduced-regs Use reduced-set registers for register allocation. -mfull-regs Use full-set registers for register allocation. -malways-align Always align function entry, jump targets, and return address. -malign-functions Align function entry to 4 bytes. -mfp-as-gp -mno-fp-as-gp Enable/disable fp-as-gp optimization. -mcmov -mno-cmov Enable/disable generation of conditional move instructions. -mhw-abs -mno-hw-abs Enable/disable generation of hardware abs instructions. -mext-perf -mno-ext-perf Enable/disable generation of performance extension instructions. -mext-perf2 -mno-ext-perf2 Enable/disable generation of performance extension 2 instructions. -mext-string -mno-ext-string Enable/disable generation of string extension instructions. -mext-dsp -mno-ext-dsp Enable/disable generation of DSP extension instructions. -mext-fpu-fma -mno-ext-fpu-fma Enable/disable generation of floating-point multiply-accumulation in- structions. -mext-fpu-sp -mno-ext-fpu-sp Enable/disable generation of single-precision floating-point instruc- tions. -mext-fpu-dp -mno-ext-fpu-dp Enable/disable generation of double-precision floating-point instruc- tions. -mv3push -mno-v3push Enable/disable generation of v3 push25/pop25 instructions. -m16-bit -mno-16-bit Enable/disable generation of 16-bit instructions. -mvh -mno-vh Enable/disable Virtual Hosting support. -misr-vector-size=num Specify the size of each interrupt vector, which must be 4 or 16. -misr-secure=num Specify the security level of c-isr for the whole file. -mcache-block-size=num Specify the size of each cache block, which must be a power of 2 be- tween 4 and 512. -march=arch Specify the target architecture. arch may be one of v2, v3, v3j, v3m, v3f, or v3s. -mcpu=cpu Specify the CPU to compile for. cpu may be one of n6, n650, n7, n705, n8, n801, sn8, sn801, s8, s801, e8, e801, n820, s830, e830, n9, n903, n903a, n968, n968a, n10, n1033, n1033a, n1033-fpu, n1033-spu, n1068, n1068a, n1068-fpu, n1068a-fpu, d10, d1088, d1088-fpu, d1088-spu, n15, d15, n15s, d15s, n15f, d15f, n12, n1213, n1233, n1233-fpu, n1233-spu, n13, n1337, n1337-fpu, n1337-spu, or simple. -mconfig-fpu=num Specify a FPU configuration value from 0 to 7; 0--3 is as FPU spec says, and 4--7 correspond to 0--3. -mconfig-mul=type Specify configuration for multiply instruction. type can be one of fast, fast1 (equivalent to fast), fast2, or slow. The default is fast1. -mconfig-register-ports=kind Specify the numbers of read/write ports for n9/n10 cores. The value should be 3r2w or 2r1w. -mcmodel=code-model Set the code model to one of: small All the data and read-only data segments must be within 512KB ad- dressing space. The text segment must be within 16MB addressing space. medium The data segment must be within 512KB while the read-only data seg- ment can be within 4GB addressing space. The text segment should be still within 16MB addressing space. large All the text and data segments can be within 4GB addressing space. The default is large on GNU/Linux targets and medium on other ELF tar- gets. -mctor-dtor -mno-ctor-dtor Enable/disable constructor/destructor feature. -mrelax -mno-relax Enable/disable linker option to relax instructions. -mrelax-hint -mno-relax-hint Enable/disable insertion of hints for linker to do relaxation. -msched-prolog-epilog -mno-sched-prolog-epilog Enable/disable scheduling of a function's prologue and epilogue se- quence. -mret-in-naked-func -mno-ret-in-naked-func Enable/disable generation of return instructions in naked functions. This option is enabled by default. -malways-save-lp -mno-always-save-lp Enable/disable always saving $lp on the stack. -munaligned-access -mno-unaligned-access Enable/disable unaligned word and halfword accesses to packed data. -minline-asm-r15 -mno-inline-asm-r15 Allow/disallow use of r15 for inline asm. Nvidia PTX Options These options are defined for Nvidia PTX: -m64Ignored, but preserved for backward compatibility. Only 64-bit ABI is supported. -march=architecture-string Generate code for the specified PTX ISA target architecture. Valid ar- chitecture strings are sm_30, sm_35, sm_37, sm_50, sm_52, sm_53, sm_61, sm_70, sm_75, sm_80, and sm_89. The default depends on how the com- piler has been configured, see --with-arch. This option sets the value of the preprocessor macro "__PTX_SM__"; for instance, for sm_35, it has the value 350. -misa=architecture-string Alias of -march=. -march-map=architecture-string Select the closest available -march= value that is not more capable. For instance, for -march-map=sm_50 select -march=sm_37, and for -march-map=sm_53 select -march=sm_53. -mptx=version-string Generate code for the specified PTX ISA version. Valid version strings are 3.1, 4.0, 4.1, 4.2, 5.0, 6.0, 6.3, 7.0, 7.3, and 7.8. The default PTX ISA version is the one that added support for the selected PTX ISA target architecture, see -march=, but at least 6.3, or 7.3 for -march=sm_52 and higher. This option sets the values of the preprocessor macros "__PTX_ISA_VER- SION_MAJOR__" and "__PTX_ISA_VERSION_MINOR__"; for instance, for 3.1 the macros have the values 3 and 1, respectively. -mmainkernel Link in code for a __main kernel. This is for stand-alone instead of offloading execution. -moptimize -mno-optimize Enable/disable partitioned execution optimizations. This option is en- abled by default when any level of optimization is selected. -msoft-stack -mno-soft-stack For -mno-soft-stack (the default, unless -mgomp has been specified), use PTX "native" stacks, that is, generate code that uses ".local" mem- ory or PTX "alloca" directly for stack storage. Unless -mptx=7.3 or higher and -march=sm_52 or higher are active, variable-length arrays and dynamically allocating memory on the stack with "alloca" are not supported. For -msoft-stack (implied by -mgomp), generate code that does not use ".local" memory or PTX "alloca" directly for stack storage. Instead, a per-warp stack pointer is maintained explicitly. This enables vari- able-length stack allocation (with variable-length arrays or "alloca"), and when global memory is used for underlying storage, makes it possi- ble to access automatic variables from other threads, or with atomic instructions. This code generation variant is used for OpenMP offload- ing, but the option is exposed on its own for the purpose of testing the compiler; to generate code suitable for linking into programs using OpenMP offloading, use option -mgomp. -msoft-stack-reserve-local=size Specify the size of ".local" memory used for the stack when the exact amount is not known. It defaults to 128. -muniform-simt -mno-uniform-simt Enable/disable code generation variant that allows execution of all threads in each warp, while maintaining memory state and side effects as if only one thread in each warp was active outside of OpenMP SIMD regions. All atomic operations and calls to runtime ("malloc", "free", "vprintf") are conditionally executed (iff current lane index equals the master lane index), and the register being assigned is copied via a shuffle instruction from the master lane. Outside of SIMD regions lane 0 is the master; inside, each thread sees itself as the master. Shared memory array "int __nvptx_uni[]" stores all-zeros or all-ones bitmasks for each warp, indicating current mode (0 outside of SIMD regions). Each thread can bitwise-and the bitmask at position "tid.y" with cur- rent lane index to compute the master lane index. -mgomp -mno-gomp Enable/disable generation of code for use in OpenMP offloading. -mgomp enables -msoft-stack and -muniform-simt options, and selects a corre- sponding multilib variant. OpenRISC Options These options are defined for OpenRISC: -mboard=name Configure a board specific runtime. This is passed to the linker for newlib board library linking. The default is "or1ksim". -msoft-div -mhard-div Select software or hardware divide ("l.div", "l.divu") instructions. This default is hardware divide. -msoft-mul -mhard-mul Select software or hardware multiply ("l.mul", "l.muli") instructions. This default is hardware multiply. -msoft-float -mhard-float Select software or hardware for floating point operations. The default is software. -mdouble-float When -mhard-float is selected, enables generation of double-precision floating point instructions. By default functions from libgcc are used to perform double-precision floating point operations. -munordered-float When -mhard-float is selected, enables generation of unordered floating point compare and set flag ("lf.sfun*") instructions. By default func- tions from libgcc are used to perform unordered floating point compare and set flag operations. -mcmov Enable generation of conditional move ("l.cmov") instructions. By de- fault the equivalents are generated using set and branch. -mror Enable generation of rotate right ("l.ror") instructions. By default functions from libgcc are used to perform rotate right operations. -mrori Enable generation of rotate right with immediate ("l.rori") instruc- tions. By default functions from libgcc are used to perform rotate right with immediate operations. -msext Enable generation of sign extension ("l.ext*") instructions. By de- fault memory loads are used to perform sign extension. -msfimm Enable generation of compare and set flag with immediate ("l.sf*i") in- structions. By default extra instructions are generated to store the immediate to a register first. -mshftimm Enable generation of shift with immediate ("l.srai", "l.srli", "l.slli") instructions. By default extra instructions are generated to store the immediate to a register first. -mcmodel=small Generate OpenRISC code for the small model: The GOT is limited to 64k and function call jumps are limited to 64M offsets. This is the default model. -mcmodel=large Generate OpenRISC code for the large model: The GOT may grow up to 4G in size and function call jumps can target the full 4G address space. PDP-11 Options These options are defined for the PDP-11: -mfpu Use hardware FPP floating point. This is the default. (FIS floating point on the PDP-11/40 is not supported.) Implies -m45. -msoft-float Do not use hardware floating point. -mac0 -mno-ac0 With -mac0, return floating-point results in ac0 (fr0 in Unix assembler syntax). The default, -mno-ac0, is to return floating-point results in memory. -m40Generate code for a PDP-11/40. Implies -msoft-float -mno-split. -m45Generate code for a PDP-11/45. This is the default. -m10Generate code for a PDP-11/10. Implies -msoft-float -mno-split. -mint16 -mno-int32 Use 16-bit "int". This is the default. -mint32 -mno-int16 Use 32-bit "int". -msplit Target has split instruction and data space. Implies -m45. -munix-asm Use Unix assembler syntax. -mdec-asm Use DEC assembler syntax. -mgnu-asm Use GNU assembler syntax. This is the default. -mlra Use the new LRA register allocator. By default, the old "reload" allo- cator is used. Picolibc Options These options control compilation and linking when using Picolibc: --oslib=library Search the library named library after the C library, permitting sym- bols undefined by the C library to be defined by this library. The C library, libgcc and this library are placed between --start-group and --end-group flags so that each can refer to symbols in the others. For many targets, Picolibc provides a semihost variant (specified with --oslib=semihost) which provides enough basic OS functionality to sup- port console and file I/O when run in an emulator or when using an in-circuit debugger. --crt0=[none|minimal|hosted|semihost] Replace the default crt0.o name with crt0-variant.o. The none variant provides no startup code at all, allowing you to supply your own. mini- mal performs basic memory setup but does not invoke any constructors. When no -crt0 option is provided, the default initialization code adds calls to all constructors. hosted adds a call to "exit" when "main" re- turns. semihost accesses a command-line parameter supplied via the semihosting interface and splits that into arguments at whitespace boundaries, passing the resulting array of strings to "main" in "argc" and "argv". On some targets, including AArch64, ARC, ARM, LoongArch, M680x0, RISC-V, SH, and x86, semihost also traps hardware exceptions and prints information to the console. Note that --crt0=semihost de- pends upon APIs provided by --oslib=semihost. --printf=[d|f|l|i|m] Select the "printf" variant. Picolibc provides five different "printf" variants which offer decreasing levels of functionality along with de- creasing code size. d is the default level, offering full C17 and POSIX.1-2024 conformance. f provides the same feature set, but supports "float" values instead of "double" which are passed using the "printf_float" macro. l elides all floating-point and POSIX positional parameter support. i limits integers to those no larger than "long". m removes support for most formatting options including width and preci- sion. The formats and arguments are still parsed correctly, but output does not respect those parameters. --scanf=[d|f|l|i|m] Select the "scanf" variant. Picolibc provides five different "scanf" variants which offer decreasing levels of functionality along with de- creasing code size. d is the default level, offering full C17 and POSIX.1-2024 conformance. f removes support for "double" values. l elides all floating point support. i limits integers to those no larger than "long". m removes support for %[ conversion specifiers. PowerPC Options These are listed under PRU Options These command-line options are defined for PRU target: -minrt Link with a minimum runtime environment. This can significantly reduce the size of the final ELF binary, but some standard C runtime features are removed. This option disables support for static initializers and constructors. Beware that the compiler could still generate code with static initial- izers and constructors. It is up to the programmer to ensure that the source program does not use those features. The minimal startup code does not pass "argc" and "argv" arguments to "main", so the latter must be declared as "int main (void)". This is already the norm for most firmware projects. -mmcu=mcu Specify the PRU hardware variant to use. A correspondingly-named spec file is loaded, passing the memory region sizes to the linker and defining hardware-specific C macros. Newlib provides only the "sim" spec, intended for running regression tests using a simulator. Specs for real hardware can be obtained by installing the GnuPruMcu ("https://github.com/dinuxbg/gnuprumcu/") package. -mno-relax Make GCC pass the --no-relax command-line option to the linker instead of the --relax option. -mloop -mno-loop Allow (or do not allow) GCC to use the LOOP instruction. -mmul -mno-mul Allow (or do not allow) GCC to use the PRU multiplier unit. -mfillzero -mno-fillzero Allow (or do not allow) GCC to use the FILL and ZERO instructions. -mabi=variant Specify the ABI variant to output code for. -mabi=ti selects the un- modified TI ABI, while -mabi=gnu selects a GNU variant that copes more naturally with certain GCC assumptions. These are the differences: Function Pointer Size TI ABI specifies that function (code) pointers are 16-bit, whereas GNU supports only 32-bit data and code pointers. Optional Return Value Pointer Function return values larger than 64 bits are passed by using a hidden pointer as the first argument of the function. TI ABI, though, mandates that the pointer can be NULL in case the caller is not using the returned value. GNU always passes and expects a valid return value pointer. Size Of Struct Containing Bit-fields TI ABI mandates that struct size is determined by the bit-field type, if it contains any. On the other hand, GNU allocates the smallest amount of bytes which would fit the bit-field. For example, TI ABI reserves 4 bytes for this struct, whereas GNU reserves a single byte: struct S { int i:1; }; Access Size For Volatile Bit-fields TI ABI mandates that volatile bit-fields are accessed using their type. In contrast, GNU ABI uses the smallest integer type fitting the bit-field. For example, TI ABI requires a single load of 4 bytes for the fol- lowing bit-field. GNU generates a load of 1 byte: struct S { volatile int i:1; }; The current -mabi=ti implementation simply raises a compile error when any of the above code constructs is detected. As a consequence the standard C library cannot be built and it is omitted when linking with -mabi=ti. Relaxation is a GNU feature and for safety reasons is disabled when us- ing -mabi=ti. The TI toolchain does not emit relocations for QBBx in- structions, so the GNU linker cannot adjust them when shortening adja- cent LDI32 pseudo instructions. RISC-V Options These command-line options are defined for RISC-V targets: -mbranch-cost=n Set the cost of branches to roughly n instructions. -mabi=ABI-string Specify integer and floating-point calling convention. ABI-string con- tains two parts: the size of integer types and the registers used for floating-point types. For example -march=rv64ifd -mabi=lp64d means that long and pointers are 64-bit (implicitly defining int to be 32-bit), and that floating-point values up to 64 bits wide are passed in F registers. Contrast this with -march=rv64ifd -mabi=lp64f, which still allows the compiler to generate code that uses the F and D exten- sions but only allows floating-point values up to 32 bits long to be passed in registers; or -march=rv64ifd -mabi=lp64, in which no float- ing-point arguments are passed in registers. The default for this argument is system dependent; if you want a spe- cific calling convention you should specify one explicitly. The valid calling conventions are: ilp32, ilp32f, ilp32d, lp64, lp64f, and lp64d. Some calling conventions are impossible to implement on some ISAs: for example, -march=rv32if -mabi=ilp32d is invalid because the ABI requires 64-bit values be passed in F registers, but F registers are only 32 bits wide. There are also the ilp32e ABI that can only be used with the rv32e architecture and the lp64e ABI that can only be used with the rv64e. Those ABIs are not well-specified at present, and are subject to change. -mfdiv -mno-fdiv Do or don't use hardware floating-point divide and square root instruc- tions. This requires the F or D extensions for floating-point regis- ters. The default is to use them if the specified architecture has these instructions. -mfence-tso -mno-fence-tso Do or don't use the fence.tso instruction, which is unimplemented on some processors (including those from T-Head). If the fence.tso in- struction is not available then a stronger fence is used instead. -mdiv -mno-div Do or don't use hardware instructions for integer division. This re- quires the M extension. The default is to use them if the specified architecture has these instructions. -misa-spec=ISA-spec-string Specify the version of the RISC-V Unprivileged (formerly User-Level) ISA specification generated code should conform to. The possibilities for ISA-spec-string are: 2.2 Produce code conforming to version 2.2. 20190608 Produce code conforming to version 20190608. 20191213 Produce code conforming to version 20191213. The default is -misa-spec=20191213 unless GCC has been configured with --with-isa-spec= specifying a different default version. -march=[ISA|Profile|Profile_ISA|processor-string] Generate code for given RISC-V ISA or profile or a combination of them (e.g. rv64im rvi20u64 rvi20u64_zbb). The names of ISAs and profiles must be lower case. Examples include rv64i, rv32g, rv32e, rv32imaf, rva22u64 and rva23u64. To combine a named profile with optional RISC-V ISA extensions, give the profile first and then append the extension name(s) using an underscore as a delimiter (e.g. rvi20u64_zca_zcb rva23u64_zacas). Additionally, a special value help (-march=help) is accepted to list all supported extensions. -march=unset causes the compiler to ignore any -march=... options that appear earlier on the command line, behaving as if the option was never passed. This is useful for ensuring that the architecture is taken from the -mcpu option, and an error results if no -mcpu option is given when -march=unset is used. The syntax of the ISA string is defined as follows: * The string must start with rv32 or rv64, followed by i, e, or g, referred to as the base ISA. * The subsequent part of the string is a list of extension names. Extension names can be categorized as multi-letter (e.g. zba) and single-letter (e.g. v). Single-letter extensions can appear con- secutively, but multi-letter extensions must be separated by under- scores. * An underscore can appear anywhere after the base ISA. It has no specific effect but is used to improve readability and can act as a separator. * Extension names may include an optional version number, following the syntax <major>p<minor> or <major>, (e.g. m2p1 or m2). Supported extensions are listed below: Extension Name : Supported Version : Description g @tab - @tab General-purpose computing base extension; g expands to i, m, a, f, d, zicsr and zifencei. e @tab 2.0 @tab Reduced base integer extension i @tab 2.0 2.1 @tab Base integer extension m @tab 2.0 @tab Integer multiplication and division extension a @tab 2.0 2.1 @tab Atomic extension f @tab 2.0 2.2 @tab Single-precision floating-point extension d @tab 2.0 2.2 @tab Double-precision floating-point extension c @tab 2.0 @tab Compressed extension b @tab 1.0 @tab Standard extension for bit manipulation functions v @tab 1.0 @tab Vector extension h @tab 1.0 @tab Hypervisor extension zic64b @tab 1.0 @tab Cache block size is 64 bytes zicbom @tab 1.0 @tab Cache-block management extension zicbop @tab 1.0 @tab Cache-block prefetch extension zicboz @tab 1.0 @tab Cache-block zero extension ziccamoa @tab 1.0 @tab Main memory supports all atomics in A ziccif @tab 1.0 @tab Main memory supports instruction fetch with atomicity requirement zicclsm @tab 1.0 @tab Main memory supports misaligned loads/stores ziccrse @tab 1.0 @tab Main memory supports forward progress on LR/SC se- quences zicfilp @tab 1.0 @tab Control-flow integrity landing pad extension zicfiss @tab 1.0 @tab Control-flow integrity shadow stack extension zicntr @tab 2.0 @tab Standard extension for base counters and timers zicond @tab 1.0 @tab Integer conditional operations extension zicsr @tab 2.0 @tab Control and status register access extension zifencei @tab 2.0 @tab Instruction-fetch fence extension zihintntl @tab 1.0 @tab Non-temporal locality hints extension zihintpause @tab 2.0 @tab Pause hint extension zihpm @tab 2.0 @tab Standard extension for hardware performance counters zimop @tab 1.0 @tab May-be-operations extension zilsd @tab 1.0 @tab Load/store pair instructions extension zmmul @tab 1.0 @tab Integer multiplication extension za128rs @tab 1.0 @tab Reservation set size of 128 bytes za64rs @tab 1.0 @tab Reservation set size of 64 bytes zaamo @tab 1.0 @tab Atomic memory operations extension zabha @tab 1.0 @tab Byte and halfword atomic memory operations extension zacas @tab 1.0 @tab Atomic compare-and-swap instructions extension zalasr @tab 1.0 @tab Atomic load-acquire and store-release extension zalrsc @tab 1.0 @tab Load-reserved/store-conditional subset of the A ex- tension zawrs @tab 1.0 @tab Wait-on-reservation-set extension zama16b @tab 1.0 @tab Misaligned loads, stores, and AMOs that are fully contained within a naturally-aligned 16-byte boundary are atomic zfa @tab 1.0 @tab Additional floating-point extension zfbfmin @tab 1.0 @tab Minimal BF16 support extension zfh @tab 1.0 @tab Half-precision floating-point extension zfhmin @tab 1.0 @tab Minimal half-precision floating-point extension zfinx @tab 1.0 @tab Single-precision floating-point in integer registers extension zdinx @tab 1.0 @tab Double-precision floating-point in integer registers extension zca @tab 1.0 @tab Integer compressed instruction extension zcb @tab 1.0 @tab Simple compressed instruction extension zcd @tab 1.0 @tab Compressed double-precision floating point loads and stores extension zce @tab 1.0 @tab Compressed instruction extensions for embedded processors zcf @tab 1.0 @tab Compressed single-precision floating point loads and stores extension zcmop @tab 1.0 @tab Compressed may-be-operations extension zcmp@tab 1.0 @tab Compressed push pop extension zcmt@tab 1.0 @tab Table jump instruction extension zclsd @tab 1.0 @tab Compressed load/store pair instructions extension zba @tab 1.0 @tab Address calculation extension zbb @tab 1.0 @tab Basic bit manipulation extension zbc @tab 1.0 @tab Carry-less multiplication extension zbkb@tab 1.0 @tab Cryptography bit-manipulation extension zbkc@tab 1.0 @tab Cryptography carry-less multiply extension zbkx@tab 1.0 @tab Cryptography crossbar permutation extension zbs @tab 1.0 @tab Single-bit operation extension zk @tab 1.0 @tab Standard scalar cryptography extension zkn @tab 1.0 @tab NIST algorithm suite extension zknd@tab 1.0 @tab AES Decryption extension zkne@tab 1.0 @tab AES Encryption extension zknh@tab 1.0 @tab Hash function extension zkr @tab 1.0 @tab Entropy source extension zks @tab 1.0 @tab ShangMi algorithm suite extension zksed @tab 1.0 @tab SM4 block cipher extension zksh@tab 1.0 @tab SM3 hash function extension zkt @tab 1.0 @tab Data independent execution latency extension ztso@tab 1.0 @tab Total store ordering extension zvbb@tab 1.0 @tab Vector basic bit-manipulation extension zvbc@tab 1.0 @tab Vector carry-less multiplication extension zve32f @tab 1.0 @tab Vector extensions for embedded processors zve32x @tab 1.0 @tab Vector extensions for embedded processors zve64d @tab 1.0 @tab Vector extensions for embedded processors zve64f @tab 1.0 @tab Vector extensions for embedded processors zve64x @tab 1.0 @tab Vector extensions for embedded processors zvfbfmin @tab 1.0 @tab Vector BF16 converts extension zvfofp8min @tab 0.2 @tab Vector FP8 minimum extension zvfbfwma @tab 1.0 @tab Vector BF16 widening multiply/add extension zvfh@tab 1.0 @tab Vector half-precision floating-point extension zvfhmin @tab 1.0 @tab Vector minimal half-precision floating-point exten- sion zvkb@tab 1.0 @tab Vector cryptography bit-manipulation extension zvkg@tab 1.0 @tab Vector GCM/GMAC extension zvkn@tab 1.0 @tab Vector NIST Algorithm Suite extension, zvkn will ex- pand to zvknc @tab 1.0 @tab Vector NIST Algorithm Suite with carry-less multiply extension, zvknc zvkned @tab 1.0 @tab Vector AES block cipher extension zvkng @tab 1.0 @tab Vector NIST Algorithm Suite with GCM extension, zvkng will expand zvknha @tab 1.0 @tab Vector SHA-2 secure hash extension zvknhb @tab 1.0 @tab Vector SHA-2 secure hash extension zvks@tab 1.0 @tab Vector ShangMi algorithm suite extension, zvks will expand zvksc @tab 1.0 @tab Vector ShangMi algorithm suite with carry-less multi- plication extension, zvksed @tab 1.0 @tab Vector SM4 block cipher extension zvksg @tab 1.0 @tab Vector ShangMi algorithm suite with GCM extension zvksh @tab 1.0 @tab Vector SM3 secure hash extension zvkt@tab 1.0 @tab Vector data independent execution latency extension zvl1024b @tab 1.0 @tab Minimum vector length standard extensions zvl128b @tab 1.0 @tab Minimum vector length standard extensions zvl16384b @tab 1.0 @tab Minimum vector length standard extension zvl2048b @tab 1.0 @tab Minimum vector length standard extensions zvl256b @tab 1.0 @tab Minimum vector length standard extensions zvl32768b @tab 1.0 @tab Minimum vector length standard extension zvl32b @tab 1.0 @tab Minimum vector length standard extensions zvl4096b @tab 1.0 @tab Minimum vector length standard extensions zvl512b @tab 1.0 @tab Minimum vector length standard extensions zvl64b @tab 1.0 @tab Minimum vector length standard extensions zvl65536b @tab 1.0 @tab Minimum vector length standard extension zvl8192b @tab 1.0 @tab Minimum vector length standard extension zhinx @tab 1.0 @tab Half-precision floating-point in integer registers extension zhinxmin @tab 1.0 @tab Minimal half-precision floating-point in integer reg- isters extension sdtrig @tab 1.0 @tab Debug triggers extension sha @tab 1.0 @tab The augmented hypervisor extension shcounterenw @tab 1.0 @tab Support writeable enables for any supported counter shgatpa @tab 1.0 @tab SvNNx4 mode supported for all modes supported by satp shlcofideleg @tab 1.0 @tab Delegating LCOFI interrupts to VS-mode shtvala @tab 1.0 @tab The htval register provides all needed values shvstvala @tab 1.0 @tab The vstval register provides all needed values shvstvecd @tab 1.0 @tab The vstvec register supports direct mode shvsatpa @tab 1.0 @tab The vsatp register supports all modes supported by satp smaia @tab 1.0 @tab Advanced interrupt architecture extension smcntrpmf @tab 1.0 @tab Cycle and instret privilege mode filtering smcsrind @tab 1.0 @tab Machine-level indirect CSR access smepmp @tab 1.0 @tab PMP enhancements for memory access and execution pre- vention on machine mode smmpm @tab 1.0 @tab Supervisor-mode pointer masking extension smnpm @tab 1.0 @tab Supervisor-mode pointer masking extension smrnmi @tab 1.0 @tab Resumable non-maskable interrupts smstateen @tab 1.0 @tab State enable extension smdbltrp @tab 1.0 @tab Double trap extensions ssaia @tab 1.0 @tab Advanced interrupt architecture extension for super- visor mode ssccptr @tab 1.0 @tab Main memory supports page table reads sscofpmf @tab 1.0 @tab Count overflow and filtering extension sscounterenw @tab 1.0 @tab Support writeable enables for any supported counter sscsrind @tab 1.0 @tab Supervisor-mode indirect CSR access ssnpm @tab 1.0 @tab Supervisor-mode pointer masking extension sspm@tab 1.0 @tab Supervisor-mode pointer masking extension ssstateen @tab 1.0 @tab Supervisor-mode state-enable extension sstc@tab 1.0 @tab Supervisor-mode timer interrupts extension sstvala @tab 1.0 @tab Stval provides all needed values sstvecd @tab 1.0 @tab Stvec supports direct mode ssstrict @tab 1.0 @tab Unimplemented reserved encodings raise illegal in- struction exceptions and no non-conforming extensions are present ssdbltrp @tab 1.0 @tab Double trap extensions ssu64xl @tab 1.0 @tab UXLEN=64 must be supported supm@tab 1.0 @tab User-mode pointer masking extension svinval @tab 1.0 @tab Fine-grained address-translation cache invalidation extension svnapot @tab 1.0 @tab NAPOT translation contiguity extension svpbmt @tab 1.0 @tab Page-based memory types extension svvptc @tab 1.0 @tab Extension for obviating memory-management instruc- tions after marking PTEs valid svadu @tab 1.0 @tab Hardware updating of A/D bits extension svade @tab 1.0 @tab Cause exception when hardware updating of A/D bits is disabled svbare @tab 1.0 @tab Satp mode bare is supported xcvalu @tab 1.0 @tab Core-V miscellaneous ALU extension xcvbi @tab 1.0 @tab Core-V immediate branch extension xcvelw @tab 1.0 @tab Core-V event load word extension xcvmac @tab 1.0 @tab Core-V multiply-accumulate extension xcvsimd @tab 1.0 @tab Core-V SIMD extension xsfcease @tab 1.0 @tab SiFive CEASE instruction extension xsfvcp @tab 1.0 @tab SiFive VCIX vector coprocessor extension xsfvfnrclipxfqf @tab 1.0 @tab SiFive FP32-to-int8 ranged clip instructions xsfvqmaccdod @tab 1.0 @tab SiFive int8 matrix multiplication extension xsfvqmaccqoq @tab 1.0 @tab SiFive int8 matrix multiplication extension xtheadba @tab 1.0 @tab T-head address calculation extension xtheadbb @tab 1.0 @tab T-head basic bit-manipulation extension xtheadbs @tab 1.0 @tab T-head single-bit instructions extension xtheadcmo @tab 1.0 @tab T-head cache management operations extension xtheadcondmov @tab 1.0 @tab T-head conditional move extension xtheadfmemidx @tab 1.0 @tab T-head indexed memory operations for floating-point registers extension xtheadfmv @tab 1.0 @tab T-head double floating-point high-bit data transmis- sion extension xtheadint @tab 1.0 @tab T-head acceleration interruption extension xtheadmac @tab 1.0 @tab T-head multiply-accumulate extension xtheadmemidx @tab 1.0 @tab T-head indexed memory operation extension xtheadmempair @tab 1.0 @tab T-head two-GPR memory operation extension xtheadsync @tab 1.0 @tab T-head multi-core synchronization extension xtheadvector @tab 1.0 @tab T-head vector extension xventanacondops @tab 1.0 @tab Ventana integer conditional operations extension xmipscmov @tab 1.0 @tab Mips conditional move extension xmipscbop @tab 1.0 @tab Mips prefetch extension xandesperf @tab 5.0 @tab Andes performance extension xandesbfhcvt @tab 5.0 @tab Andes bfloat16 conversion extension xandesvbfhcvt @tab 5.0 @tab Andes vector bfloat16 conversion extension xandesvsintload @tab 5.0 @tab Andes vector INT4 load extension xandesvpackfph @tab 5.0 @tab Andes vector packed FP16 extension xandesvdot @tab 5.0 @tab Andes vector dot product extension xsmtvdot @tab 1.0 @tab SpacemiT vector dot product extension When -march= is not specified, GCC uses the setting from -mcpu. If both -march and -mcpu= are not specified, the default for this argu- ment is system dependent; if you want a specific architecture exten- sion, you should specify one explicitly. When the RISC-V specifications define an extension as depending on other extensions, GCC implicitly adds the dependent extensions to the enabled extension set if they weren't added explicitly. Core Name -mcpu=processor-string Use architecture of and optimize the output for the given processor, specified by particular CPU name. Permissible values for this option are: sifive-e20, sifive-e21, sifive-e24, sifive-e31, sifive-e34, sifive-e76, sifive-s21, sifive-s51, sifive-s54, sifive-s76, sifive-u54, sifive-u74, sifive-x280, sifive-p450, sifive-p670, thead-c906, xt-c908, xt-c908v, xt-c910, xt-c910v2, xt-c920, xt-c920v2, xt-c9501fdvt, tt-ascalon-x, xiangshan-nanhu, xiangshan-kunminghu, mips-p8700, andes-n22, andes-n25, andes-a25, andes-nx25, andes-ax25, andes-a27, andes-ax27, andes-n225, andes-d23, andes-n45, andes-nx45, andes-a45, andes-ax45, spacemit-x60. Note that -mcpu does not override -march or -mtune. Tune Name -mtune=processor-string Optimize the output for the given processor, specified by microarchi- tecture or particular CPU name. Permissible values for this option are: generic, rocket, sifive-3-series, sifive-5-series, sifive-7-series, sifive-p400-series, sifive-p600-series, tt-ascalon-x, thead-c906, xt-c908, xt-c908v, xt-c910, xt-c910v2, xt-c920, xt-c920v2, xt-c9501fdvt, xiangshan-nanhu, xiangshan-kunminghu, spacemit-x60, arc-v-rhx-100-series, generic-ooo, size, mips-p8700, andes-25-series, andes-23-series, andes-45-series, arc-v-rmx-100-series, and all valid options for -mcpu=. When -mtune= is not specified, GCC uses the setting from -mcpu. The default is generic if neither is specified. The size choice is not intended for use by end-users. This is used when -Os is specified. It overrides the instruction cost info provided by -mtune=, but does not override the pipeline info. This helps reduce code size while still giving good performance. -mpreferred-stack-boundary=num Attempt to keep the stack boundary aligned to a 2 raised to num byte boundary. If -mpreferred-stack-boundary is not specified, the default is 4 (16 bytes or 128-bits). Warning: If you use this switch, then you must build all modules with the same value, including any libraries. This includes the system li- braries and startup modules. -msmall-data-limit=n Put global and static data smaller than n bytes into a special section (on some targets). -msave-restore -mno-save-restore Do or don't use smaller but slower prologue and epilogue code that uses library function calls. The default is to use fast inline prologues and epilogues. -mmovcc -mno-movcc Do or don't produce branchless conditional-move code sequences even with targets that do not have specific instructions for conditional op- erations. If enabled, sequences of ALU operations are produced using base integer ISA instructions where profitable. -minline-atomics -mno-inline-atomics Do or don't use smaller but slower subword atomic emulation code that uses libatomic function calls. The default is to use fast inline sub- word atomics that do not require libatomic. -minline-strlen -mno-inline-strlen Do or do not attempt to inline "strlen" calls if possible. Inlining can only be done if the string is properly aligned and instructions for accelerated processing are available. The default is to inline "strlen" calls. -minline-strcmp -mno-inline-strcmp Do or do not attempt to inline "strcmp" calls if possible. Inlining can only be done if the strings are properly aligned and instructions for accelerated processing are available. The default is to inline "strcmp" calls. -minline-strncmp -mno-inline-strncmp Do or do not attempt to inline "strncmp" calls if possible. Inlining can only be done if the strings are properly aligned and instructions for accelerated processing are available. The default is to inline "strncmp" calls. -mstringop-strategy=strategy Specify a particular strategy for inlining string and memory opera- tions. strategy may be one of auto, libcall, scalar, or vector. -mshorten-memrefs -mno-shorten-memrefs Do or do not attempt to make more use of compressed load/store instruc- tions by replacing a load/store of 'base register + large offset' with a new load/store of 'new base + small offset'. If the new base gets stored in a compressed register, then the new load/store can be com- pressed. Currently targets 32-bit integer load/stores only. -mstrict-align -mno-strict-align Do not or do generate unaligned memory accesses. The default is set depending on whether the processor we are optimizing for supports fast unaligned access or not. -mscalar-strict-align -mno-scalar-strict-align Do not or do generate unaligned memory accesses. The default is set depending on whether the processor we are optimizing for supports fast unaligned access or not. This is an alias for -mstrict-align. -mvector-strict-align -mno-vector-strict-align Do not or do generate unaligned vector memory accesses. The default is set to off unless the processor we are optimizing for explicitly sup- ports element-misaligned vector memory access. -mzilsd-word-align Allow Zilsd/Zclsd memory accesses to be generated when they are known to be 4-byte aligned. -mzilsd-strict-align Require Zilsd/Zclsd memory accesses to be naturally 8-byte aligned. The precedence among -mzilsd-word-align, -mzilsd-strict-align, -mstrict-align, -mno-strict-align, -mscalar-strict-align, and -mno-scalar-strict-align is determined by the last one specified. -mmax-vectorization -mno-max-vectorization Enable or disable an override to vectorizer cost model making vector- ization always appear profitable. Unlike -fno-vect-cost-model or -fvect-cost-model=unlimited this option does not turn off cost compari- son between different vector modes. -mcmodel=medlow Generate code for the medium-low code model. The program and its stati- cally defined symbols must lie within a single 2 GiB address range and must lie between absolute addresses -2 GiB and +2 GiB. Programs can be statically or dynamically linked. This is the default code model unless GCC has been configured with --with-cmodel= specifying a different de- fault code model. -mcmodel=medany Generate code for the medium-any code model. The program and its stati- cally defined symbols must be within any single 2 GiB address range. Programs can be statically or dynamically linked. The code generated by the medium-any code model is position-indepen- dent, but is not guaranteed to function correctly when linked into po- sition-independent executables or libraries. -mcmodel=large Generate code for a large code model, which has no restrictions on size or placement of symbols. -mexplicit-relocs -mno-explicit-relocs Use or do not use assembler relocation operators when dealing with sym- bolic addresses. The alternative is to use assembler macros instead, which may limit optimization. -mrelax -mno-relax Take advantage of linker relaxations to reduce the number of instruc- tions required to materialize symbol addresses. The default is to take advantage of linker relaxations. -mriscv-attribute -mno-riscv-attribute Emit (do not emit) RISC-V attribute to record extra information into ELF objects. This feature requires at least binutils 2.32. -mcsr-check -mno-csr-check Enables or disables the CSR checking. -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. -malign-data=type Control how GCC aligns variables and constants of array, structure, or union types. Supported values for type are xlen which uses x register width as the alignment value, and natural which uses natural alignment. xlen is the default. -mbig-endian Generate big-endian code. This is the default when GCC is configured for a riscv64be-*-* or riscv32be-*-* target. Support for RISC-V big-endian is experimental. The ABI is not yet stable and could change in incompatible ways in future releases. -mlittle-endian Generate little-endian code. This is the default when GCC is config- ured for a riscv64-*-* or riscv32-*-* but not a riscv64be-*-* or riscv32be-*-* target. -mstack-protector-guard=guard -mstack-protector-guard-reg=reg -mstack-protector-guard-offset=offset Generate stack protection code using canary at guard. Supported loca- tions are global for a global canary or tls for per-thread canary in the TLS block. With the latter choice the options -mstack-protector-guard-reg=reg and -mstack-protector-guard-offset=offset furthermore specify which regis- ter to use as base register for reading the canary, and from what off- set from that base register. There is no default register or offset as this is entirely for use within the Linux kernel. -mtls-dialect=desc Use TLS descriptors as the thread-local storage mechanism for dynamic accesses of TLS variables. -mtls-dialect=trad Use traditional TLS as the thread-local storage mechanism for dynamic accesses of TLS variables. This is the default. -mrvv-vector-bits=value Specify how the number of bits for an RVV vector register, as taken from the -march= option, is interpreted. The value parameter is speci- fied as a string keyword and may be one of scalable or zvl. The de- fault is scalable, which tells GCC to interpret the number as a mini- mum, while zvl tells GCC to use exactly the number of bits specified. -mrvv-max-lmul=value This option allows explicit control over the maximum length multiplier (LMUL) used when generating code for the RISC-V Vector Extensions (RVV). The value parameter is specified as a string keyword and may be one of m1, m2, m4, m8, or dynamic. The default is m1 for compatibility with existing hardware that does not support the other options. -madjust-lmul-cost -mno-adjust-lmul-cost This option adjusts the cost model used to schedule vector instructions to multiply the latency of instructions by the RVV length multiplier, LMUL. It is disabled by default. -mautovec-segment -mno-autovec-segment Enable or disable generation of vector segment load/store instructions. This option is enabled by default. RL78 Options -msim Links in additional target libraries to support operation within a sim- ulator. -mmul=none -mmul=g10 -mmul=g13 -mmul=g14 -mmul=rl78 Specifies the type of hardware multiplication and division support to be used. The simplest is "none", which uses software for both multi- plication and division. This is the default. The "g13" value is for the hardware multiply/divide peripheral found on the RL78/G13 (S2 core) targets. The "g14" value selects the use of the multiplication and di- vision instructions supported by the RL78/G14 (S3 core) parts. The value "rl78" is an alias for "g14" and the value "mg10" is an alias for "none". In addition a C preprocessor macro is defined, based upon the setting of this option. Possible values are: "__RL78_MUL_NONE__", "__RL78_MUL_G13__" or "__RL78_MUL_G14__". -mcpu=g10 -mcpu=g13 -mcpu=g14 -mcpu=rl78 Specifies the RL78 core to target. The default is the G14 core, also known as an S3 core or just RL78. The G13 or S2 core does not have multiply or divide instructions, instead it uses a hardware peripheral for these operations. The G10 or S1 core does not have register banks, so it uses a different calling convention. If this option is set it also selects the type of hardware multiply support to use, unless this is overridden by an explicit -mmul=none op- tion on the command line. Thus specifying -mcpu=g13 enables the use of the G13 hardware multiply peripheral and specifying -mcpu=g10 disables the use of hardware multiplications altogether. Note, although the RL78/G14 core is the default target, specifying -mcpu=g14 or -mcpu=rl78 on the command line does change the behavior of the toolchain since it also enables G14 hardware multiply support. If these options are not specified on the command line, then software mul- tiplication routines are used even though the code targets the RL78 core. This is for backward compatibility with older toolchains which did not have hardware multiply and divide support. In addition a C preprocessor macro is defined, based upon the setting of this option. Possible values are: "__RL78_G10__", "__RL78_G13__" or "__RL78_G14__". -mg10 -mg13 -mg14 -mrl78 These are aliases for the corresponding -mcpu= option. They are pro- vided for backwards compatibility. -mallregs Allow the compiler to use all of the available registers. By default registers "r24..r31" are reserved for use in interrupt handlers. With this option enabled these registers can be used in ordinary functions as well. -mrelax -mno-relax Enable/disable assembler and linker relaxation. This is enabled by de- fault at -Os. -mes0 Assume "ES" is zero throughout program execution, and use it to address read-only data. -msave-mduc-in-interrupts -mno-save-mduc-in-interrupts Specifies that interrupt handler functions should preserve the MDUC registers. This is only necessary if normal code might use the MDUC registers, for example because it performs multiplication and division operations. The default is to ignore the MDUC registers as this makes the interrupt handlers faster. The target option -mg13 needs to be passed for this to work as this feature is only available on the G13 target (S2 core). The MDUC registers are only saved if the interrupt handler performs a multiplication or division operation or it calls an- other function. IBM RS/6000 and PowerPC Options These -m options are defined for the IBM RS/6000 and PowerPC: -mcpu=cpu_type Set architecture type, register usage, and instruction scheduling para- meters for machine type cpu_type. Supported values for cpu_type are 401, 403, 405, 405fp, 440, 440fp, 464, 464fp, 476, 476fp, 505, 601, 602, 603, 603e, 604, 604e, 620, 630, 740, 7400, 7450, 750, 801, 821, 823, 860, 970, 8540, a2, e300c2, e300c3, e500mc, e500mc64, e5500, e6500, ec603e, G3, G4, G5, titan, power3, power4, power5, power5+, power6, power6x, power7, power8, power9, power10, power11, future, pow- erpc, powerpc64, powerpc64le, rs64, and native. -mcpu=powerpc, -mcpu=powerpc64, and -mcpu=powerpc64le specify pure 32-bit PowerPC (either endian), 64-bit big endian PowerPC and 64-bit little endian PowerPC architecture machine types, with an appropriate, generic processor model assumed for scheduling purposes. Specifying native as cpu type detects and selects the architecture op- tion that corresponds to the host processor of the system performing the compilation. -mcpu=native has no effect if GCC does not recognize the processor. The other options specify a specific processor. Code generated under those options runs best on that processor, and may not run at all on others. The -mcpu options automatically enable or disable the following op- tions: -maltivec -mfprnd -mhard-float -mmfcrf -mmultiple -mpopcntb -mpopcntd -mpowerpc64 -mpowerpc-gpopt -mpowerpc-gfxopt -mmulhw -mdlmzb -mmfpgpr -mvsx -mcrypto -mhtm -mpower8-fusion -mquad-memory -mquad-memory-atomic -mfloat128 -mfloat128-hardware -mprefixed -mpcrel -mmma -mrop-protect The particular options set for any particular CPU varies between com- piler versions, depending on what setting seems to produce optimal code for that CPU; it doesn't necessarily reflect the actual hardware's ca- pabilities. If you wish to set an individual option to a particular value, you may specify it after the -mcpu option, like -mcpu=970 -mno-altivec. On AIX, the -maltivec and -mpowerpc64 options are not enabled or dis- abled by the -mcpu option at present because AIX does not have full support for these options. You may still enable or disable them indi- vidually if you're sure it'll work in your environment. In other cases, we recommend you use the -mcpu=cpu_type option rather than the options that control generation of specific instructions. -mtune=cpu_type Set the instruction scheduling parameters for machine type cpu_type, but do not set the architecture type or register usage, as -mcpu=cpu_type does. The same values for cpu_type are used for -mtune as for -mcpu. If both are specified, the code generated uses the ar- chitecture and registers set by -mcpu, but the scheduling parameters set by -mtune. -mpowerpc64 -mno-powerpc64 The -mpowerpc64 option allows GCC to generate the additional 64-bit in- structions that are found in the full PowerPC64 architecture and to treat GPRs as 64-bit, doubleword quantities. GCC defaults to -mno-pow- erpc64. -mcmodel=small Generate PowerPC64 code for the small model: The TOC is limited to 64k. -mcmodel=medium Generate PowerPC64 code for the medium model: The TOC and other static data may be up to a total of 4G in size. This is the default for 64-bit Linux. -mcmodel=large Generate PowerPC64 code for the large model: The TOC may be up to 4G in size. Other data and code is only limited by the 64-bit address space. -mprofile-kernel This option is available on PowerPC64 GNU/Linux targets. When used with -pg, it causes calls to "mcount" to be inserted before the func- tion prologue instead of after it. -maltivec -mno-altivec Generate code that uses (does not use) AltiVec instructions, and also enable the use of built-in functions that allow more direct access to the AltiVec instruction set. You may also need to set -mabi=altivec to adjust the current ABI with AltiVec ABI enhancements. When -maltivec is used, the element order for AltiVec intrinsics such as "vec_splat", "vec_extract", and "vec_insert" match array element or- der corresponding to the endianness of the target. That is, element zero identifies the leftmost element in a vector register when target- ing a big-endian platform, and identifies the rightmost element in a vector register when targeting a little-endian platform. -mpowerpc-gpopt -mno-powerpc-gpopt Specifying -mpowerpc-gpopt allows GCC to use the optional PowerPC ar- chitecture instructions in the General Purpose group, including float- ing-point square root. Specifying -mpowerpc-gfxopt -mno-powerpc-gfxopt -mpowerpc-gfxopt allows GCC to use the optional PowerPC architecture instructions in the Graphics group, including floating-point select. -mmfcrf -mno-mfcrf The -mmfcrf option allows GCC to generate the move from condition reg- ister field instruction implemented on the POWER4 processor and other processors that support the PowerPC V2.01 architecture. -mpopcntb -mno-popcntb The -mpopcntb option allows GCC to generate the popcount and dou- ble-precision FP reciprocal estimate instruction implemented on the POWER5 processor and other processors that support the PowerPC V2.02 architecture. -mpopcntd -mno-popcntd The -mpopcntd option allows GCC to generate the popcount instruction implemented on the POWER7 processor and other processors that support the PowerPC V2.06 architecture. -mfprnd -mno-fprnd The -mfprnd option allows GCC to generate the FP round to integer in- structions implemented on the POWER5+ processor and other processors that support the PowerPC V2.03 architecture. -mcmpb -mno-cmpb The -mcmpb option allows GCC to generate the compare bytes instruction implemented on the POWER6 processor and other processors that support the PowerPC V2.05 architecture. -mhard-dfp -mno-hard-dfp The -mhard-dfp option allows GCC to generate the decimal floating-point instructions implemented on some POWER processors. -mvrsave -mno-vrsave Generate VRSAVE instructions when generating AltiVec code. -msecure-plt Generate code that allows ld and ld.so to build executables and shared libraries with non-executable ".plt" and ".got" sections. This is a PowerPC 32-bit SYSV ABI option. -mbss-plt Generate code that uses a BSS ".plt" section that ld.so fills in, and requires ".plt" and ".got" sections that are both writable and exe- cutable. This is a PowerPC 32-bit SYSV ABI option. -msplit-patch-nops When adding NOPs for a patchable area via the -fpatchable-function-en- try option emit the "before" NOPs in front of the global entry point and the "after" NOPs after the local entry point. This makes the se- quence of NOPs not consecutive when a global entry point is generated. Without this option the NOPs are emitted directly before and after the local entry point, making them consecutive but moving global and local entry point further apart. If only a single entry point is generated this option has no effect. -misel -mno-isel This switch enables or disables the generation of ISEL instructions. -mvsx -mno-vsx Generate code that uses (does not use) vector/scalar (VSX) instruc- tions, and also enable the use of built-in functions that allow more direct access to the VSX instruction set. -mcrypto -mno-crypto Enable the use (disable) of the built-in functions that allow direct access to the cryptographic instructions that were added in version 2.07 of the PowerPC ISA. -mhtm -mno-htm Enable (disable) the use of the built-in functions that allow direct access to the Hardware Transactional Memory (HTM) instructions that were added in version 2.07 of the PowerPC ISA. -mpower8-fusion -mno-power8-fusion Generate code that keeps (does not keeps) some integer operations adja- cent so that the instructions can be fused together on power8 and later processors. -mquad-memory -mno-quad-memory Generate code that uses (does not use) the non-atomic quad word memory instructions. The -mquad-memory option requires use of 64-bit mode. -mquad-memory-atomic -mno-quad-memory-atomic Generate code that uses (does not use) the atomic quad word memory in- structions. The -mquad-memory-atomic option requires use of 64-bit mode. -mfloat128 -mno-float128 Enable/disable the __float128 keyword for IEEE 128-bit floating point and use either software emulation for IEEE 128-bit floating point or hardware instructions. The VSX instruction set (-mvsx) must be enabled to use the IEEE 128-bit floating point support. The IEEE 128-bit floating point is only sup- ported on Linux. The default for -mfloat128 is enabled on PowerPC Linux systems using the VSX instruction set, and disabled on other systems. If you use the ISA 3.0 instruction set (-mcpu=power9) on a 64-bit sys- tem, the IEEE 128-bit floating point support also enables the genera- tion of ISA 3.0 IEEE 128-bit floating point instructions. Otherwise, if you do not specify generation of ISA 3.0 instructions or you are targeting a 32-bit big-endian system, IEEE 128-bit floating point is handled with software emulation. -mfloat128-hardware -mno-float128-hardware Enable/disable using ISA 3.0 hardware instructions to support the __float128 data type. The default for -mfloat128-hardware is enabled on PowerPC Linux systems using the ISA 3.0 instruction set, and disabled on other systems. -m32 -m64Generate code for 32-bit or 64-bit environments of Darwin and SVR4 tar- gets (including GNU/Linux). The 32-bit environment sets int, long and pointer to 32 bits and generates code that runs on any PowerPC variant. The 64-bit environment sets int to 32 bits and long and pointer to 64 bits, and generates code for PowerPC64, as for -mpowerpc64. -mfull-toc -mno-fp-in-toc -mno-sum-in-toc -mminimal-toc Modify generation of the TOC (Table Of Contents), which is created for every executable file. The -mfull-toc option is selected by default. In that case, GCC allocates at least one TOC entry for each unique non-automatic variable reference in your program. GCC also places floating-point constants in the TOC. However, only 16,384 entries are available in the TOC. If you receive a linker error message that saying you have overflowed the available TOC space, you can reduce the amount of TOC space used with the -mno-fp-in-toc and -mno-sum-in-toc options. -mno-fp-in-toc prevents GCC from putting floating-point constants in the TOC and -mno-sum-in-toc forces GCC to generate code to calculate the sum of an address and a constant at run time instead of putting that sum into the TOC. You may specify one or both of these options. Each causes GCC to produce very slightly slower and larger code at the expense of conserv- ing TOC space. If you still run out of space in the TOC even when you specify both of these options, specify -mminimal-toc instead. This option causes GCC to make only one TOC entry for every file. When you specify this op- tion, GCC produces code that is slower and larger but which uses ex- tremely little TOC space. You may wish to use this option only on files that contain less frequently-executed code. -maix64 -maix32 Enable 64-bit AIX ABI and calling convention: 64-bit pointers, 64-bit "long" type, and the infrastructure needed to support them. Specifying -maix64 implies -mpowerpc64, while -maix32 disables the 64-bit ABI and implies -mno-powerpc64. GCC defaults to -maix32. -mxl-compat -mno-xl-compat Produce code that conforms more closely to IBM XL compiler semantics when using AIX-compatible ABI. Pass floating-point arguments to proto- typed functions beyond the register save area (RSA) on the stack in ad- dition to argument FPRs. Do not assume that most significant double in 128-bit long double value is properly rounded when comparing values and converting to double. Use XL symbol names for long double support rou- tines. The AIX calling convention was extended but not initially documented to handle an obscure K&R C case of calling a function that takes the ad- dress of its arguments with fewer arguments than declared. IBM XL com- pilers access floating-point arguments that do not fit in the RSA 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 neces- sary when calling subroutines compiled by IBM XL compilers without op- timization. -mpeSupport IBM RS/6000 SP Parallel Environment (PE). Link an application written to use message passing with special startup code to enable the application to run. The system must have PE installed in the standard location (/usr/lpp/ppe.poe/), or the specs file must be overridden with the -specs= option to specify the appropriate directory location. The Parallel Environment does not support threads, so the -mpe option and the -pthread option are incompatible. -malign-natural -malign-power On AIX, 32-bit Darwin, and 64-bit PowerPC GNU/Linux, the option -ma- lign-natural overrides the ABI-defined alignment of larger types, such as floating-point doubles, on their natural size-based boundary. The option -malign-power instructs GCC to follow the ABI-specified align- ment rules. GCC defaults to the standard alignment defined in the ABI. On 64-bit Darwin, natural alignment is the default, and -malign-power is not supported. -msoft-float -mhard-float Generate code that does not use (uses) the floating-point register set. Software floating-point emulation is provided if you use the -msoft-float option, and pass the option to GCC when linking. -mmultiple -mno-multiple Generate code that uses (does not use) the load multiple word instruc- tions and the store multiple word instructions. These instructions are generated by default on POWER systems, and not generated on PowerPC systems. Do not use -mmultiple on little-endian PowerPC systems, since those instructions do not work when the processor is in little-endian mode. The exceptions are PPC740 and PPC750 which permit these instruc- tions in little-endian mode. -mupdate -mno-update 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 -mno-update, 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 sig- nals may get corrupted data. -mavoid-indexed-addresses -mno-avoid-indexed-addresses Generate code that tries to avoid (not avoid) the use of indexed load or store instructions. These instructions can incur a performance penalty on Power6 processors in certain situations, such as when step- ping through large arrays that cross a 16M boundary. This option is enabled by default when targeting Power6 and disabled otherwise. -mfused-madd -mno-fused-madd Generate code that uses (does not use) the floating-point multiply and accumulate instructions. These instructions are generated by default if hardware floating point is used. The machine-dependent -mfused-madd option is now mapped to the machine-independent -ffp-contract=fast op- tion, and -mno-fused-madd is mapped to -ffp-contract=off. -mmulhw -mno-mulhw Generate code that uses (does not use) the half-word multiply and mul- tiply-accumulate instructions on the IBM 405, 440, 464 and 476 proces- sors. These instructions are generated by default when targeting those processors. -mdlmzb -mno-dlmzb Generate code that uses (does not use) the string-search dlmzb instruc- tion on the IBM 405, 440, 464 and 476 processors. This instruction is generated by default when targeting those processors. -mno-bit-align -mbit-align 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. For example, by default a structure containing nothing but 8 "unsigned" bit-fields of length 1 is aligned to a 4-byte boundary and has a size of 4 bytes. By using -mno-bit-align, the structure is aligned to a 1-byte boundary and is 1 byte in size. -mbit-word -mno-bit-word Allow bit-fields to cross word boundaries. -mno-strict-align -mstrict-align On System V.4 and embedded PowerPC systems do not (do) assume that un- aligned memory references are handled by the system. -mrelocatable -mno-relocatable Generate code that allows (does not allow) a static executable to be relocated to a different address at run time. A simple embedded Pow- erPC system loader should relocate the entire contents of ".got2" and 4-byte locations listed in the ".fixup" section, a table of 32-bit ad- dresses generated by this option. For this to work, all objects linked together must be compiled with -mrelocatable or -mrelocatable-lib. -mrelocatable code aligns the stack to an 8-byte boundary. -mrelocatable-lib -mno-relocatable-lib Like -mrelocatable, -mrelocatable-lib generates a ".fixup" section to allow static executables to be relocated at run time, but -mrelocat- able-lib does not use the smaller stack alignment of -mrelocatable. Objects compiled with -mrelocatable-lib may be linked with objects com- piled with any combination of the -mrelocatable options. -mlittle -mlittle-endian On System V.4 and embedded PowerPC systems compile code for the proces- sor in little-endian mode. The -mlittle-endian option is the same as -mlittle. -mbig -mbig-endian On System V.4 and embedded PowerPC systems compile code for the proces- sor in big-endian mode. The -mbig-endian option is the same as -mbig. -mdynamic-no-pic On Darwin / macOS systems, compile code so that it is not relocatable, but that its external references are relocatable. The resulting code is suitable for applications, but not shared libraries. -msingle-pic-base Treat the register used for PIC addressing as read-only, rather than loading it in the prologue for each function. The runtime system is responsible for initializing this register with an appropriate value before execution begins. -mprioritize-restricted-insns=priority This option controls the priority that is assigned to dispatch-slot re- stricted instructions during the second scheduling pass. The argument priority takes the value 0, 1, or 2 to assign no, highest, or sec- ond-highest (respectively) priority to dispatch-slot restricted in- structions. -msched-costly-dep=dependence_type This option controls which dependences are considered costly by the target during instruction scheduling. The argument dependence_type takes one of the following values: no No dependence is costly. all All dependences are costly. true_store_to_load A true dependence from store to load is costly. store_to_load Any dependence from store to load is costly. number Any dependence for which the latency is greater than or equal to number is costly. -minsert-sched-nops=scheme This option controls which NOP insertion scheme is used during the sec- ond scheduling pass. The argument scheme takes one of the following values: no Don't insert NOPs. pad Pad with NOPs any dispatch group that has vacant issue slots, ac- cording to the scheduler's grouping. regroup_exact Insert NOPs to force costly dependent insns into separate groups. Insert exactly as many NOPs as needed to force an insn to a new group, according to the estimated processor grouping. number Insert NOPs to force costly dependent insns into separate groups. Insert number NOPs to force an insn to a new group. -mcall-sysv On System V.4 and embedded PowerPC systems compile code using calling conventions that adhere to the March 1995 draft of the System V Appli- cation Binary Interface, PowerPC processor supplement. This is the de- fault unless you configured GCC using powerpc-*-eabiaix. -mcall-sysv-eabi -mcall-eabi Specify both -mcall-sysv and -meabi options. -mcall-sysv-noeabi Specify both -mcall-sysv and -mno-eabi options. -mcall-aixdesc On System V.4 and embedded PowerPC systems compile code for the AIX op- erating system. -mcall-linux On System V.4 and embedded PowerPC systems compile code for the Linux-based GNU system. -mcall-freebsd On System V.4 and embedded PowerPC systems compile code for the FreeBSD operating system. -mcall-netbsd On System V.4 and embedded PowerPC systems compile code for the NetBSD operating system. -mcall-openbsd On System V.4 and embedded PowerPC systems compile code for the OpenBSD operating system. -mtraceback=traceback_type Select the type of traceback table. Valid values for traceback_type are full, part, and no. -maix-struct-return Return all structures in memory (as specified by the AIX ABI). -msvr4-struct-return Return structures smaller than 8 bytes in registers (as specified by the SVR4 ABI). -mabi=abi-type Extend the current ABI with a particular extension, or remove such ex- tension. Valid values are: altivec, no-altivec, ibmlongdouble, ieee- longdouble, elfv1, elfv2, and for AIX: vec-extabi, vec-default. -mabi=ibmlongdouble Change the current ABI to use IBM extended-precision long double. This is not likely to work if your system defaults to using IEEE ex- tended-precision long double. If you change the long double type from IEEE extended-precision, the compiler issues a warning unless you use the -Wno-psabi option. Requires -mlong-double-128 to be enabled. -mabi=ieeelongdouble Change the current ABI to use IEEE extended-precision long double. This is not likely to work if your system defaults to using IBM ex- tended-precision long double. If you change the long double type from IBM extended-precision, the compiler issues a warning unless you use the -Wno-psabi option. Requires -mlong-double-128 to be enabled. -mabi=elfv1 Change the current ABI to use the ELFv1 ABI. This is the default ABI for big-endian PowerPC 64-bit Linux. Overriding the default ABI re- quires special system support and is likely to fail in spectacular ways. -mabi=elfv2 Change the current ABI to use the ELFv2 ABI. This is the default ABI for little-endian PowerPC 64-bit Linux. Overriding the default ABI re- quires special system support and is likely to fail in spectacular ways. -mgnu-attribute -mno-gnu-attribute Emit .gnu_attribute assembly directives to set tag/value pairs in a .gnu.attributes section that specify ABI variations in function parame- ters or return values. -mprototype -mno-prototype 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 ("CR") to indicate whether floating-point values are passed in the floating-point regis- ters in case the function takes variable arguments. With -mprototype, only calls to prototyped variable argument functions set or clear the bit. -msim On embedded PowerPC systems, assume that the startup module is called sim-crt0.o and that the standard C libraries are libsim.a and libc.a. This is the default for powerpc-*-eabisim configurations. -mmvme On embedded PowerPC systems, assume that the startup module is called crt0.o and the standard C libraries are libmvme.a and libc.a. -mads On embedded PowerPC systems, assume that the startup module is called crt0.o and the standard C libraries are libads.a and libc.a. -myellowknife On embedded PowerPC systems, assume that the startup module is called crt0.o and the standard C libraries are libyk.a and libc.a. -mvxworks On System V.4 and embedded PowerPC systems, specify that you are com- piling for a VxWorks system. -memb On embedded PowerPC systems, set the "PPC_EMB" bit in the ELF flags header to indicate that eabi extended relocations are used. -meabi -mno-eabi On System V.4 and embedded PowerPC systems do (do not) adhere to the Embedded Applications Binary Interface (EABI), which is a set of modi- fications to the System V.4 specifications. Selecting -meabi means that the stack is aligned to an 8-byte boundary, a function "__eabi" is called from "main" to set up the EABI environment, and the -msdata op- tion can use both "r2" and "r13" to point to two separate small data areas. Selecting -mno-eabi means that the stack is aligned to a 16-byte boundary, no EABI initialization function is called from "main", and the -msdata option only uses "r13" to point to a single small data area. The -meabi option is on by default if you configured GCC using one of the powerpc*-*-eabi* options. -msdata=eabi On System V.4 and embedded PowerPC systems, put small initialized "const" global and static data in the ".sdata2" section, which is pointed to by register "r2". Put small initialized non-"const" global and static data in the ".sdata" section, which is pointed to by regis- ter "r13". Put small uninitialized global and static data in the ".sbss" section, which is adjacent to the ".sdata" section. The -ms- data=eabi option is incompatible with the -mrelocatable option. The -msdata=eabi option also sets the -memb option. -msdata=sysv On System V.4 and embedded PowerPC systems, put small global and static data in the ".sdata" section, which is pointed to by register "r13". Put small uninitialized global and static data in the ".sbss" section, which is adjacent to the ".sdata" section. The -msdata=sysv option is incompatible with the -mrelocatable option. -msdata=default -msdata On System V.4 and embedded PowerPC systems, if -meabi is used, compile code the same as -msdata=eabi, otherwise compile code the same as -ms- data=sysv. -msdata=data On System V.4 and embedded PowerPC systems, put small global data in the ".sdata" section. Put small uninitialized global data in the ".sbss" section. Do not use register "r13" to address small data how- ever. This is the default behavior unless other -msdata options are used. -msdata=none -mno-sdata On embedded PowerPC systems, put all initialized global and static data in the ".data" section, and all uninitialized data in the ".bss" sec- tion. -mreadonly-in-sdata Put read-only objects in the ".sdata" section as well. This is the de- fault. -mblock-move-inline-limit=num Inline all block moves (such as calls to "memcpy" or structure copies) less than or equal to num bytes. The minimum value for num is 32 bytes on 32-bit targets and 64 bytes on 64-bit targets. The default value is target-specific. -mblock-compare-inline-limit=num Generate non-looping inline code for all block compares (such as calls to "memcmp" or structure compares) less than or equal to num bytes. If num is 0, all inline expansion (non-loop and loop) of block compare is disabled. The default value is target-specific. -mblock-compare-inline-loop-limit=num Generate an inline expansion using loop code for all block compares that are less than or equal to num bytes, but greater than the limit for non-loop inline block compare expansion. If the block length is not constant, at most num bytes are compared before "memcmp" is called to compare the remainder of the block. The default value is tar- get-specific. -mstring-compare-inline-limit=num Compare at most num string bytes with inline code. If the difference or end of string is not found at the end of the inline compare, a call to "strcmp" or "strncmp" takes care of the rest of the comparison. The default is 64 bytes. -G num On embedded PowerPC systems, put global and static items less than or equal to num bytes into the small data or BSS sections instead of the normal data or BSS section. By default, num is 8. The -G num switch is also passed to the linker. All modules should be compiled with the same -G num value. -mregnames -mno-regnames On System V.4 and embedded PowerPC systems do (do not) emit register names in the assembly language output using symbolic forms. -mlongcall -mno-longcall By default assume that all calls are far away so that a longer and more expensive calling sequence is required. This is required for calls farther than 32 megabytes (33,554,432 bytes) from the current location. A short call is generated if the compiler knows the call cannot be that far away. This setting can be overridden by the "shortcall" function attribute, or by #pragma longcall(0). Some linkers are capable of detecting out-of-range calls and generating glue code on the fly. On these systems, long calls are unnecessary and generate slower code. As of this writing, the AIX linker can do this, as can the GNU linker for PowerPC/64. It is planned to add this fea- ture to the GNU linker for 32-bit PowerPC systems as well. On PowerPC64 ELFv2 and 32-bit PowerPC systems with newer GNU linkers, GCC can generate long calls using an inline PLT call sequence (see -mpltseq). PowerPC with -mbss-plt and PowerPC64 ELFv1 (big-endian) do not support inline PLT calls. On Darwin/PPC systems, "#pragma longcall" generates "jbsr callee, L42", plus a branch island (glue code). The two target addresses represent the callee and the branch island. The Darwin/PPC linker prefers the first address and generates a "bl callee" if the PPC "bl" instruction reaches the callee directly; otherwise, the linker generates "bl L42" to call the branch island. The branch island is appended to the body of the calling function; it computes the full 32-bit address of the callee and jumps to it. On Mach-O (Darwin) systems, this option directs the compiler emit to the glue for every direct call, and the Darwin linker decides whether to use or discard it. In the future, GCC may ignore all longcall specifications when the linker is known to generate glue. -mpltseq -mno-pltseq Implement (do not implement) -fno-plt and long calls using an inline PLT call sequence that supports lazy linking and long calls to func- tions in dlopen'd shared libraries. Inline PLT calls are only sup- ported on PowerPC64 ELFv2 and 32-bit PowerPC systems with newer GNU linkers, and are enabled by default if the support is detected when configuring GCC, and, in the case of 32-bit PowerPC, if GCC is config- ured with --enable-secureplt. -mpltseq code and -mbss-plt 32-bit Pow- erPC relocatable objects may not be linked together. -mtls-markers -mno-tls-markers Mark (do not mark) calls to "__tls_get_addr" with a relocation specify- ing the function argument. The relocation allows the linker to reli- ably associate function call with argument setup instructions for TLS optimization, which in turn allows GCC to better schedule the sequence. -mrecip -mno-recip This option enables use of the reciprocal estimate and reciprocal square root estimate instructions with additional Newton-Raphson steps to increase precision instead of doing a divide or square root and di- vide for floating-point arguments. You should use the -ffast-math op- tion when using -mrecip (or at least -funsafe-math-optimizations, -ffi- nite-math-only, -freciprocal-math and -fno-trapping-math). Note that while the throughput of the sequence is generally higher than the throughput of the non-reciprocal instruction, the precision of the se- quence can be decreased by up to 2 ulp (i.e. the inverse of 1.0 equals 0.99999994) for reciprocal square roots. -mrecip=opt This option controls which reciprocal estimate instructions may be used. opt is a comma-separated list of options, which may be preceded by a "!" to invert the option: all Enable all estimate instructions. default Enable the default instructions, equivalent to -mrecip. noneDisable all estimate instructions, equivalent to -mno-recip. div Enable the reciprocal approximation instructions for both single and double precision. divfEnable the single-precision reciprocal approximation instructions. divdEnable the double-precision reciprocal approximation instructions. rsqrt Enable the reciprocal square root approximation instructions for both single and double precision. rsqrtf Enable the single-precision reciprocal square root approximation instructions. rsqrtd Enable the double-precision reciprocal square root approximation instructions. So, for example, -mrecip=all,!rsqrtd enables all of the reciprocal es- timate instructions, except for the "FRSQRTE", "XSRSQRTEDP", and "XVRSQRTEDP" instructions which handle the double-precision reciprocal square root calculations. -mrecip-precision -mno-recip-precision Assume (do not assume) that the reciprocal estimate instructions pro- vide higher-precision estimates than is mandated by the PowerPC ABI. Selecting -mcpu=power6, -mcpu=power7 or -mcpu=power8 automatically se- lects -mrecip-precision. The double-precision square root estimate in- structions are not generated by default on low-precision machines, since they do not provide an estimate that converges after three steps. -mveclibabi=type Specifies the ABI type to use for vectorizing intrinsics using an ex- ternal library. The only type supported at present is mass, which specifies to use IBM's Mathematical Acceleration Subsystem (MASS) li- braries for vectorizing intrinsics using external libraries. GCC cur- rently emits calls to "acosd2", "acosf4", "acoshd2", "acoshf4", "asind2", "asinf4", "asinhd2", "asinhf4", "atan2d2", "atan2f4", "atand2", "atanf4", "atanhd2", "atanhf4", "cbrtd2", "cbrtf4", "cosd2", "cosf4", "coshd2", "coshf4", "erfcd2", "erfcf4", "erfd2", "erff4", "exp2d2", "exp2f4", "expd2", "expf4", "expm1d2", "expm1f4", "hypotd2", "hypotf4", "lgammad2", "lgammaf4", "log10d2", "log10f4", "log1pd2", "log1pf4", "log2d2", "log2f4", "logd2", "logf4", "powd2", "powf4", "sind2", "sinf4", "sinhd2", "sinhf4", "sqrtd2", "sqrtf4", "tand2", "tanf4", "tanhd2", and "tanhf4" when generating code for power7. Both -ftree-vectorize and -funsafe-math-optimizations must also be enabled. The MASS libraries must be specified at link time. -mfriz -mno-friz Generate (do not generate) the "friz" instruction when the -fun- safe-math-optimizations option is used to optimize rounding of float- ing-point values to 64-bit integer and back to floating point. The "friz" instruction does not return the same value if the floating-point number is too large to fit in an integer. -mpointers-to-nested-functions -mno-pointers-to-nested-functions Generate (do not generate) code to load up the static chain register ("r11") when calling through a pointer on AIX and 64-bit Linux systems where a function pointer points to a 3-word descriptor giving the func- tion address, TOC value to be loaded in register "r2", and static chain value to be loaded in register "r11". The -mpointers-to-nested-func- tions is on by default. You cannot call through pointers to nested functions or pointers to functions compiled in other languages that use the static chain if you use -mno-pointers-to-nested-functions. -msave-toc-indirect -mno-save-toc-indirect Generate (do not generate) code to save the TOC value in the reserved stack location in the function prologue if the function calls through a pointer on AIX and 64-bit Linux systems. If the TOC value is not saved in the prologue, it is saved just before the call through the pointer. The -mno-save-toc-indirect option is the default. -mcompat-align-parm -mno-compat-align-parm Generate (do not generate) code to pass structure parameters with a maximum alignment of 64 bits, for compatibility with older versions of GCC. Older versions of GCC (prior to 4.9.0) incorrectly did not align a structure parameter on a 128-bit boundary when that structure contained a member requiring 128-bit alignment. This is corrected in more recent versions of GCC. This option may be used to generate code that is com- patible with functions compiled with older versions of GCC. The -mno-compat-align-parm option is the default. -mstack-protector-guard=guard -mstack-protector-guard-reg=reg -mstack-protector-guard-offset=offset Generate stack protection code using canary at guard. Supported loca- tions are global for global canary or tls for per-thread canary in the TLS block (the default with GNU libc version 2.4 or later). With the latter choice the options -mstack-protector-guard-reg=reg and -mstack-protector-guard-offset=offset furthermore specify which regis- ter to use as base register for reading the canary, and from what off- set from that base register. The default for those is as specified in the relevant ABI. -mpcrel -mno-pcrel Generate (do not generate) pc-relative addressing. The -mpcrel option requires that the medium code model (-mcmodel=medium) and prefixed ad- dressing (-mprefixed) options are enabled. -mprefixed -mno-prefixed Generate (do not generate) addressing modes using prefixed load and store instructions. The -mprefixed option requires that the option -mcpu=power10 (or later) is enabled. -mmma -mno-mma Generate (do not generate) the MMA instructions. The -mma option re- quires that the option -mcpu=power10 (or later) is enabled. -mrop-protect -mno-rop-protect Generate (do not generate) ROP protection instructions when the target processor supports them. Currently this option disables the shrink-wrap optimization (-fshrink-wrap). -mprivileged -mno-privileged Generate (do not generate) code that runs in privileged state. -mblock-ops-unaligned-vsx -mno-block-ops-unaligned-vsx Generate (do not generate) unaligned vsx loads and stores for inline expansion of "memcpy" and "memmove". -msplat-word-constant -mno-splat-word-constant Generate (do not generate) code that uses the "XXSPLTIW" instruction. This option is enabled by default. -msplat-float-constant -mno-splat-float-constant Generate (do not generate) code that uses the "XXSPLTIDP" instruction. This option is enabled by default. -mieee128-constant -mno-ieee128-constant Generate (do not generate) code that uses the "LXVKQ" instruction. This option is enabled by default. -mwarn-altivec-long -mno-warn-altivec-long Enable or disable warnings about deprecated vector long ... Altivec type usage. This option is enabled by default. RX Options These command-line options are defined for RX targets: -m64bit-doubles -m32bit-doubles Make the "double" data type be 64 bits (-m64bit-doubles) or 32 bits (-m32bit-doubles) in size. The default is -m32bit-doubles. Note RX floating-point hardware only works on 32-bit values, which is why the default is -m32bit-doubles. -fpu -nofpu Enables (-fpu) or disables (-nofpu) the use of RX floating-point hard- ware. The default is enabled for the RX600 series and disabled for the RX200 series. Floating-point instructions are only generated for 32-bit float- ing-point values, however, so the FPU hardware is not used for doubles if the -m64bit-doubles option is used. Note If the -fpu option is enabled then -funsafe-math-optimizations is also enabled automatically. This is because the RX FPU instructions are themselves unsafe. -mcpu=name Selects the type of RX CPU to be targeted. Currently three types are supported, the generic RX600 and RX200 series hardware and the specific RX610 CPU. The default is RX600. The only difference between RX600 and RX610 is that the RX610 does not support the "MVTIPL" instruction. The RX200 series does not have a hardware floating-point unit and so -nofpu is enabled by default when this type is selected. -mbig-endian-data -mlittle-endian-data Store data (but not code) in the big-endian format. The default is -mlittle-endian-data, i.e. to store data in the little-endian format. -msmall-data-limit=N Specifies the maximum size in bytes of global and static variables that can be placed into the small data area. Using the small data area can lead to smaller and faster code, but the size of area is limited and it is up to the programmer to ensure that the area does not overflow. Also when the small data area is used one of the RX's registers (usu- ally "r13") is reserved for use pointing to this area, so it is no longer available for use by the compiler. This could result in slower and/or larger code if variables are pushed onto the stack instead of being held in this register. Note, common variables (variables that have not been initialized) and constants are not placed into the small data area as they are assigned to other sections in the output executable. The default value is zero, which disables this feature. Note, this feature is not enabled by default with higher optimization levels (-O2 etc) because of the potentially detrimental effects of reserving a reg- ister. It is up to the programmer to experiment and discover whether this feature is of benefit to their program. See the description of the -mpid option for a description of how the actual register to hold the small data area pointer is chosen. -msim -mno-sim Use the simulator runtime. The default is to use the libgloss board-specific runtime. -mas100-syntax -mno-as100-syntax When generating assembler output use a syntax that is compatible with Renesas's AS100 assembler. This syntax can also be handled by the GAS assembler, but it has some restrictions so it is not generated by de- fault. -mmax-constant-size=N Specifies the maximum size, in bytes, of a constant that can be used as an operand in a RX instruction. Although the RX instruction set does allow constants of up to 4 bytes in length to be used in instructions, a longer value equates to a longer instruction. Thus in some circum- stances it can be beneficial to restrict the size of constants that are used in instructions. Constants that are too big are instead placed into a constant pool and referenced via register indirection. The value N can be between 0 and 4. A value of 0 (the default) or 4 means that constants of any size are allowed. -mrelax Enable linker relaxation. Linker relaxation is a process whereby the linker attempts to reduce the size of a program by finding shorter ver- sions of various instructions. Disabled by default. -mint-register=N Specify the number of registers to reserve for fast interrupt handler functions. The value N can be between 0 and 4. A value of 1 means that register "r13" is reserved for the exclusive use of fast interrupt handlers. A value of 2 reserves "r13" and "r12". A value of 3 re- serves "r13", "r12" and "r11", and a value of 4 reserves "r13" through "r10". A value of 0, the default, does not reserve any registers. -msave-acc-in-interrupts Specifies that interrupt handler functions should preserve the accumu- lator register. This is only necessary if normal code might use the accumulator register, for example because it performs 64-bit multipli- cations. The default is to ignore the accumulator as this makes the interrupt handlers faster. -mpid -mno-pid Enables the generation of position-independent data. When enabled, any access to constant data is done via an offset from a base address held in a register. This allows the location of constant data to be deter- mined at run time without requiring the executable to be relocated, which is a benefit to embedded applications with tight memory con- straints. Data that can be modified is not affected by this option. Note, using this feature reserves a register, usually "r13", for the constant data base address. This can result in slower and/or larger code, especially in complicated functions. The actual register chosen to hold the constant data base address de- pends upon whether the -msmall-data-limit and/or the -mint-register command-line options are enabled. Starting with register "r13" and proceeding downwards, registers are allocated first to satisfy the re- quirements of -mint-register, then -mpid and finally -ms- mall-data-limit. Thus it is possible for the small data area register to be "r8" if both -mint-register=4 and -mpid are specified on the com- mand line. By default this feature is not enabled. The default can be restored via the -mno-pid command-line option. -mno-warn-multiple-fast-interrupts -mwarn-multiple-fast-interrupts Prevents GCC from issuing a warning message if it finds more than one fast interrupt handler when it is compiling a file. The default is to issue a warning for each extra fast interrupt handler found, as the RX only supports one such interrupt. -mallow-string-insns -mno-allow-string-insns Enables or disables the use of the string manipulation instructions "SMOVF", "SCMPU", "SMOVB", "SMOVU", "SUNTIL" "SWHILE" and also the "RMPA" instruction. These instructions may prefetch data, which is not safe to do if accessing an I/O register. (See section 12.2.7 of the RX62N Group User's Manual for more information). The default is to allow these instructions, but it is not possible for GCC to reliably detect all circumstances where a string instruction might be used to access an I/O register, so their use cannot be dis- abled automatically. Instead it is reliant upon the programmer to use the -mno-allow-string-insns option if their program accesses I/O space. When the instructions are enabled GCC defines the C preprocessor symbol "__RX_ALLOW_STRING_INSNS__", otherwise it defines the symbol "__RX_DIS- ALLOW_STRING_INSNS__". -mjsr -mno-jsr Use only (or not only) "JSR" instructions to access functions. This option can be used when code size exceeds the range of "BSR" instruc- tions. Note that -mno-jsr does not mean to not use "JSR" but instead means that any type of branch may be used. -mlra Use the new LRA register allocator. By default, the old "reload" allo- cator is used. Note: The generic GCC command-line option -ffixed-reg has special signifi- cance to the RX port when used with the "interrupt" function attribute. This attribute indicates a function intended to process fast interrupts. GCC ensures that it only uses the registers "r10", "r11", "r12" and/or "r13" and only provided that the normal use of the corresponding registers have been restricted via the -ffixed-reg or -mint-register command-line op- tions. S/390 and zSeries Options These are the -m options defined for the S/390 and zSeries architecture. -mhard-float -msoft-float Use (do not use) the hardware floating-point instructions and registers for floating-point operations. When -msoft-float is specified, func- tions in libgcc.a are used to perform floating-point operations. When -mhard-float is specified, the compiler generates IEEE floating-point instructions. This is the default. -mhard-dfp -mno-hard-dfp Use (do not use) the hardware decimal-floating-point instructions for decimal-floating-point operations. When -mno-hard-dfp is specified, functions in libgcc.a are used to perform decimal-floating-point opera- tions. When -mhard-dfp is specified, the compiler generates deci- mal-floating-point hardware instructions. This is the default for -march=z9-ec or higher. -mlong-double-64 -mlong-double-128 These switches control the size of "long double" type. A size of 64 bits makes the "long double" type equivalent to the "double" type. This is the default. -mbackchain -mno-backchain Store (do not store) the address of the caller's frame as backchain pointer into the callee's stack frame. A backchain may be needed to allow debugging using tools that do not understand DWARF call frame in- formation. When -mno-packed-stack is in effect, the backchain pointer is stored at the bottom of the stack frame; when -mpacked-stack is in effect, the backchain is placed into the topmost word of the 96/160 byte register save area. In general, code compiled with -mbackchain is call-compatible with code compiled with -mno-backchain; however, use of the backchain for debug- ging purposes usually requires that the whole binary is built with -mbackchain. Note that the combination of -mbackchain, -mpacked-stack and -mhard-float is not supported. In order to build a linux kernel use -msoft-float. The default is to not maintain the backchain. -mpacked-stack -mno-packed-stack Use (do not use) the packed stack layout. When -mno-packed-stack is specified, the compiler uses the all fields of the 96/160 byte register save area only for their default purpose; unused fields still take up stack space. When -mpacked-stack is specified, register save slots are densely packed at the top of the register save area; unused space is reused for other purposes, allowing for more efficient use of the available stack space. However, when -mbackchain is also in effect, the topmost word of the save area is always used to store the backchain, and the return address register is always saved two words below the backchain. As long as the stack frame backchain is not used, code generated with -mpacked-stack is call-compatible with code generated with -mno-packed-stack. Note that some non-FSF releases of GCC 2.95 for S/390 or zSeries generated code that uses the stack frame backchain at run time, not just for debugging purposes. Such code is not call-com- patible with code compiled with -mpacked-stack. Also, note that the combination of -mbackchain, -mpacked-stack and -mhard-float is not sup- ported. In order to build a linux kernel use -msoft-float. The default is to not use the packed stack layout. -msmall-exec -mno-small-exec Generate (or do not generate) code using the "bras" instruction to do subroutine calls. This only works reliably if the total executable size does not exceed 64k. The default is to use the "basr" instruction instead, which does not have this limitation. -m64 -m31When -m31 is specified, generate code compliant to the GNU/Linux for S/390 ABI. When -m64 is specified, generate code compliant to the GNU/Linux for zSeries ABI. This allows GCC in particular to generate 64-bit instructions. For the s390 targets, the default is -m31, while the s390x targets default to -m64. Note, -m31 is deprecated and sup- port will be removed. -mzarch -mesa When -mzarch is specified, generate code using the instructions avail- able on z/Architecture. When -mesa is specified, generate code using the instructions available on ESA/390. Note that -mesa is not possible with -m64. When generating code compliant to the GNU/Linux for S/390 ABI, the default is -mesa. When generating code compliant to the GNU/Linux for zSeries ABI, the default is -mzarch. -mhtm -mno-htm The -mhtm option enables a set of builtins making use of instructions available with the transactional execution facility introduced with the IBM zEnterprise EC12 machine generation S/390 System z Built-in Func- tions. -mhtm is enabled by default when using -march=zEC12. -mvx -mno-vx When -mvx is specified, generate code using the instructions available with the vector extension facility introduced with the IBM z13 machine generation. This option changes the ABI for some vector type values with regard to alignment and calling conventions. In case vector type values are being used in an ABI-relevant context, a GAS .gnu_attribute command is added to mark the resulting binary with the ABI used. -mvx is enabled by default when using -march=z13. -mzvector -mno-zvector The -mzvector option enables vector language extensions and builtins using instructions available with the vector extension facility intro- duced with the IBM z13 machine generation. This option adds support for vector to be used as a keyword to define vector type variables and arguments. vector is only available when GNU extensions are enabled. It is not expanded when requesting strict standard compliance e.g. with -std=c99. In addition to the GCC low-level builtins, -mzvector enables a set of builtins added for compatibility with AltiVec-style implemen- tations like Power and Cell. In order to make use of these builtins, you must include the header file vecintrin.h. -mzvector is disabled by default. -mmvcle -mno-mvcle Generate (or do not generate) code using the "mvcle" instruction to perform block moves. When -mno-mvcle is specified, use a "mvc" loop instead. This is the default unless optimizing for size. -mdebug -mno-debug Print (or do not print) additional debug information when compiling. The default is to not print debug information. -march=cpu-type Generate code that runs on cpu-type, which is the name of a system rep- resenting a certain processor type. Possible values for cpu-type are z900/arch5, z990/arch6, z9-109, z9-ec/arch7, z10/arch8, z196/arch9, zEC12, z13/arch11, z14/arch12, z15/arch13, z16/arch14, z17/arch15, and native. The default is -march=z900. Specifying native as cpu type can be used to select the best architec- ture option for the host processor. -march=native has no effect if GCC does not recognize the processor. -mtune=cpu-type Tune to cpu-type everything applicable about the generated code, except for the ABI and the set of available instructions. The list of cpu-type values is the same as for -march. The default is the value used for -march. -mtpf-trace -mno-tpf-trace Generate code that adds (does not add) in TPF OS specific branches to trace routines in the operating system. This option is off by default, even when compiling for the TPF OS. -mtpf-trace-skip -mno-tpf-trace-skip Generate code that changes (does not change) the default branch targets enabled by -mtpf-trace to point to specialized trace routines providing the ability of selectively skipping function trace entries for the TPF OS. This option is off by default, even when compiling for the TPF OS and specifying -mtpf-trace. -mmain For TPF OS target, use this option when linking to add the startup code and other linker options to produce a main object. -mfused-madd -mno-fused-madd Generate code that uses (does not use) the floating-point multiply and accumulate instructions. These instructions are generated by default if hardware floating point is used. -mwarn-framesize=framesize Emit a warning if the current function exceeds the given frame size. Because this is a compile-time check it doesn't need to be a real prob- lem when the program runs. It is intended to identify functions hat most probably cause a stack overflow. It is useful for environments with limited stack size e.g. the Linux kernel. A value of zero disables this warning; that is the default. -mwarn-dynamicstack -mno-warn-dynamicstack Emit a warning if the function calls "alloca" or uses dynamically-sized arrays. This is generally a bad idea with a limited stack size. -mstack-guard=stack-guard -mstack-size=stack-size -mno-stack-guard -mno-stack-size If these options are enabled, the S/390 back end emits additional in- structions in the function prologue that trigger a trap if the stack size is stack-guard bytes above the stack-size (remember that the stack on S/390 grows downward). If the stack-guard option is omitted the smallest power of 2 larger than the frame size of the compiled function is chosen. These options are intended to be used to help debugging stack overflow problems. The additionally emitted code causes only little overhead and hence can also be used in production-like systems without greater performance degradation. The given values have to be exact powers of 2 and stack-size has to be greater than stack-guard without exceeding 64k. In order to be effi- cient the extra code makes the assumption that the stack starts at an address aligned to the value given by stack-size. The -mstack-guard= option can only be used in conjunction with -mstack-size=. You can override these options on the command line with -mno-stack-guard and -mno-stack-size, respectively. -mhotpatch=pre-halfwords,post-halfwords If the hotpatch option is enabled, a "hot-patching" function prologue is generated for all functions in the compilation unit. The function label is prepended with the given number of two-byte NOP instructions (pre-halfwords, maximum 1000000). After the label, 2 * post-halfwords bytes are appended, using the largest NOP-like instructions the archi- tecture allows (maximum 1000000). If both arguments are zero, hotpatching is disabled. This option can be overridden for individual functions with the "hot- patch" attribute. -mpic-data-is-text-relative -mno-pic-data-is-text-relative When compiling for S/390 with -fpic or -fPIC, normally GCC emits code using relative addressing between code and data. However, for hot- patching it might be required to introduce new ".text" parts while us- ing the existing ".data" and ".bss" sections. In this case, use -mno-pic-data-is-text-relative to force addressing through the GOT in- stead. -mstack-protector-guard=guard -mstack-protector-guard-record Generate stack protection code using canary at guard. Supported loca- tions are global for a global canary or tls for a per-thread canary in the TLS block (the default). Option -mstack-protector-guard-record results in the generation of sec- tion "__stack_protector_loc" containing pointers to all instructions which load the address of the global guard. Thus, this option has only an effect in conjunction with -mstack-protector-guard=global. The in- tended use is for the Linux kernel. -mindirect-branch=choice -mindirect-branch-jump=choice -mindirect-branch-call=choice -mfunction-return=choice -mfunction-return-mem=choice -mfunction-return-reg=choice This group of options addresses security vulnerabilities related to speculative execution and indirect branch prediction by enabling re- placement of indirect branches and function returns with direct branches to a thunk. Specifying a choice of keep causes generation of the default code. thunk triggers generation of out-of-line thunks and replaces the for- merly indirect branch with a direct branch to the thunk. thunk-extern does the branch replacement like thunk but does not emit the thunks. thunk-inline is only available with -mindirect-branch-jump; it should be used in preference to thunk in user-space applications to support correct stack unwinding and exception handling. -mindirect-branch sets the value of -mindirect-branch-jump and -mindi- rect-branch-call. -mfunction-return sets the value of -mfunction-re- turn-reg and -mfunction-return-mem. All of these options can also be set on a per-function basis using function attributes. -mindirect-branch-table -mno-indirect-branch-table This option is useful in conjunction with the -mindirect-branch and -mfunction-return options. When enabled, it causes generation of ta- bles pointing to the branch locations which have been patched by those options. The tables are emitted in sections named ".s390_indi- rect_jump", ".s390_indirect_call", ".s390_return_reg", and ".s390_re- turn_mem". Each section consists of an array of 32-bit elements; each entry holds the offset from the entry to the patched location. -mfentry -mno-fentry When used in conjunction with the -pg option, emit profiling code using the "__fentry__" hook provided by GLIBC 2.29 or later. This is only available for 64-bit code. If this option is not enabled, profiling uses the less efficient "_mcount" hook instead. -mrecord-mcount -mno-record-mcount When enabled, generate a "__mcount_loc" section with the locations of all generated profiling calls to "_mcount" or "__fentry__". mnop-mcount mno-nop-mcount Instead of generating calls to "_mcount" or "__fentry__" with -pg, in- sert a sequence no-op instructions of the same length at the locations where the calls would have been inserted. This can be used in conjunc- tion with the -mrecord-mcount option to patch the call sequences into the object file without recompiling it. -mpreserve-args -mno-preserve-args When enabled, save all argument registers to the stack, and generate corresponding CFI information. This is useful for applications that want to implement their own stack unwinding and need access to function arguments. -munaligned-symbols -mno-unaligned-symbols Assume that external symbols with a natural alignment of 1 are poten- tially unaligned. By default, all symbols without explicit alignment are assumed to be aligned on a 2-byte boundary as mandated by the IBM Z ABI. SH Options These -m options are defined for the SH implementations: -m1 Generate code for the SH1. -m2 Generate code for the SH2. -m2eGenerate code for the SH2e. -m2a-nofpu Generate code for the SH2a without FPU, or for a SH2a-FPU in such a way that the floating-point unit is not used. -m2a-single-only Generate code for the SH2a-FPU, in such a way that no double-precision floating-point operations are used. -m2a-single Generate code for the SH2a-FPU assuming the floating-point unit is in single-precision mode by default. -m2aGenerate code for the SH2a-FPU assuming the floating-point unit is in double-precision mode by default. -m3 Generate code for the SH3. -m3eGenerate code for the SH3e. -m4-nofpu Generate code for the SH4 without a floating-point unit. -m4-single-only Generate code for the SH4 with a floating-point unit that only supports single-precision arithmetic. -m4-single Generate code for the SH4 assuming the floating-point unit is in sin- gle-precision mode by default. -m4 Generate code for the SH4. -m4-100 Generate code for SH4-100. -m4-100-nofpu Generate code for SH4-100 in such a way that the floating-point unit is not used. -m4-100-single Generate code for SH4-100 assuming the floating-point unit is in sin- gle-precision mode by default. -m4-100-single-only Generate code for SH4-100 in such a way that no double-precision float- ing-point operations are used. -m4-200 Generate code for SH4-200. -m4-200-nofpu Generate code for SH4-200 without in such a way that the floating-point unit is not used. -m4-200-single Generate code for SH4-200 assuming the floating-point unit is in sin- gle-precision mode by default. -m4-200-single-only Generate code for SH4-200 in such a way that no double-precision float- ing-point operations are used. -m4-300 Generate code for SH4-300. -m4-300-nofpu Generate code for SH4-300 without in such a way that the floating-point unit is not used. -m4-300-single Generate code for SH4-300 in such a way that no double-precision float- ing-point operations are used. -m4-300-single-only Generate code for SH4-300 in such a way that no double-precision float- ing-point operations are used. -m4-340 Generate code for SH4-340 (no MMU, no FPU). -m4-400 Generate code for SH4-400 (no MMU, no FPU). -m4-500 Generate code for SH4-500 (no FPU). Passes -isa=sh4-nofpu to the as- sembler. -m4a-nofpu Generate code for the SH4al-dsp, or for a SH4a in such a way that the floating-point unit is not used. -m4a-single-only Generate code for the SH4a, in such a way that no double-precision floating-point operations are used. -m4a-single Generate code for the SH4a assuming the floating-point unit is in sin- gle-precision mode by default. -m4aGenerate code for the SH4a. -m4al Same as -m4a-nofpu, except that it implicitly passes -dsp to the assem- bler. GCC doesn't generate any DSP instructions at the moment. -mb Compile code for the processor in big-endian mode. -ml Compile code for the processor in little-endian mode. -mdalign Align doubles at 64-bit boundaries. Note that this changes the calling conventions, and thus some functions from the standard C library do not work unless you recompile it first with -mdalign. -mrelax Shorten some address references at link time, when possible; uses the linker option -relax. -mbigtable Use 32-bit offsets in "switch" tables. The default is to use 16-bit offsets. -mbitops Enable the use of bit manipulation instructions on SH2A. -mfmovd Enable the use of the instruction "fmovd". Check -mdalign for align- ment constraints. -mrenesas -mno-renesas Comply with the calling conventions defined by Renesas. The default for all targets of the SH toolchain is -mno-renesas, which uses the calling conventions defined for GCC before the Renesas conventions were available. -mnomacsave Mark the "MAC" register as call-clobbered, even if -mrenesas is given. -mieee -mno-ieee Control the IEEE compliance of floating-point comparisons, which af- fects the handling of cases where the result of a comparison is un- ordered. By default -mieee is implicitly enabled. If -ffi- nite-math-only is enabled -mno-ieee is implicitly set, which results in faster floating-point greater-equal and less-equal comparisons. The implicit settings can be overridden by specifying either -mieee or -mno-ieee. -minline-ic_invalidate -mno-inline-ic_invalidate Inline code to invalidate instruction cache entries after setting up nested function trampolines. This option has no effect if -musermode is in effect and the selected code generation option (e.g. -m4) does not allow the use of the "icbi" instruction. If the selected code gen- eration option does not allow the use of the "icbi" instruction, and -musermode is not in effect, the inlined code manipulates the instruc- tion cache address array directly with an associative write. This not only requires privileged mode at run time, but it also fails if the cache line had been mapped via the TLB and has become unmapped. -misize Dump instruction size and location in the assembly code. -matomic-model=model Sets the model of atomic operations and additional parameters as a comma-separated list. For details on the atomic built-in functions see __atomic Builtins. The following models and parameters are supported: noneDisable compiler generated atomic sequences and emit library calls for atomic operations. This is the default if the target is not "sh*-*-linux*". soft-gusa Generate GNU/Linux-compatible gUSA software atomic sequences for the atomic built-in functions. The generated atomic sequences re- quire additional support from the interrupt/exception handling code of the system and are only suitable for SH3* and SH4* single-core systems. This option is enabled by default when the target is "sh*-*-linux*" and SH3* or SH4*. When the target is SH4A, this op- tion also partially utilizes the hardware atomic instructions "movli.l" and "movco.l" to create more efficient code, unless strict is specified. soft-tcb Generate software atomic sequences that use a variable in the thread control block. This is a variation of the gUSA sequences which can also be used on SH1* and SH2* targets. The generated atomic sequences require additional support from the interrupt/ex- ception handling code of the system and are only suitable for sin- gle-core systems. When using this model, the gbr-offset= parameter has to be specified as well. soft-imask Generate software atomic sequences that temporarily disable inter- rupts by setting "SR.IMASK = 1111". This model works only when the program runs in privileged mode and is only suitable for sin- gle-core systems. Additional support from the interrupt/exception handling code of the system is not required. This model is enabled by default when the target is "sh*-*-linux*" and SH1* or SH2*. hard-llcs Generate hardware atomic sequences using the "movli.l" and "movco.l" instructions only. This is only available on SH4A and is suitable for multi-core systems. Since the hardware instructions support only 32-bit atomic variables, access to 8- or 16-bit vari- ables is emulated with 32-bit accesses. Code compiled with this option is also compatible with other software atomic model inter- rupt/exception handling systems if executed on an SH4A system. Ad- ditional support from the interrupt/exception handling code of the system is not required for this model. gbr-offset= This parameter specifies the offset in bytes of the variable in the thread control block structure that should be used by the generated atomic sequences when the soft-tcb model has been selected. For other models this parameter is ignored. The specified value must be an integer multiple of four and in the range 0-1020. strict This parameter prevents mixed usage of multiple atomic models, even if they are compatible, and makes the compiler generate atomic se- quences of the specified model only. -mtas Generate the "tas.b" opcode for "__atomic_test_and_set". Notice that depending on the particular hardware and software configuration this can degrade overall performance due to the operand cache line flushes that are implied by the "tas.b" instruction. On multi-core SH4A processors the "tas.b" instruction must be used with caution since it can result in data corruption for certain cache configurations. -mprefergot When generating position-independent code, emit function calls using the Global Offset Table instead of the Procedure Linkage Table. -musermode -mno-usermode Don't allow (allow) the compiler to generate privileged mode code. Specifying -musermode also implies -mno-inline-ic_invalidate if the in- lined code would not work in user mode. -musermode is the default when the target is "sh*-*-linux*". If the target is SH1* or SH2* -musermode has no effect, since there is no user mode. -multcost=number Set the cost to assume for a multiply instruction. -mdiv=strategy Set the division strategy to be used for integer division operations. strategy can be one of: call-div1 Calls a library function that uses the single-step division in- struction "div1" to perform the operation. Division by zero calcu- lates an unspecified result and does not trap. This is the default except for SH4, SH2A and SHcompact. call-fp Calls a library function that performs the operation in double pre- cision floating point. Division by zero causes a floating-point exception. This is the default for SHcompact with FPU. Specifying this for targets that do not have a double-precision FPU defaults to "call-div1". call-table Calls a library function that uses a lookup table for small divi- sors and the "div1" instruction with case distinction for larger divisors. Division by zero calculates an unspecified result and does not trap. This is the default for SH4. Specifying this for targets that do not have dynamic shift instructions defaults to "call-div1". When a division strategy has not been specified, the default strategy is selected based on the current target. For SH2A the default strategy is to use the "divs" and "divu" instructions instead of library func- tion calls. -maccumulate-outgoing-args -mno-accumulate-outgoing-args Reserve space once for outgoing arguments in the function prologue rather than around each call. This is generally beneficial for perfor- mance and size, and also needed for unwinding to avoid changing the stack frame around conditional code. -maccumulate-outgoing-args is en- abled the default. -mdivsi3_libfunc=name Set the name of the library function used for 32-bit signed division to name. This only affects the name used in the call division strategies, and the compiler still expects the same sets of input/output/clobbered registers as if this option were not present. -mfixed-range=register-range Generate code treating the given register range as fixed registers. A fixed register is one that the register allocator cannot 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. -mbranch-cost=num Assume num to be the cost for a branch instruction. Higher numbers make the compiler try to generate more branch-free code if possible. If not specified the value is selected depending on the processor type that is being compiled for. -mzdcbranch -mno-zdcbranch Assume (do not assume) that zero displacement conditional branch in- structions "bt" and "bf" are fast. If -mzdcbranch is specified, the compiler prefers zero displacement branch code sequences. This is en- abled by default when generating code for SH4 and SH4A. It can be ex- plicitly disabled by specifying -mno-zdcbranch. -mcbranch-force-delay-slot Force the usage of delay slots for conditional branches, which stuffs the delay slot with a "nop" if a suitable instruction cannot be found. By default this option is disabled. It can be enabled to work around hardware bugs as found in the original SH7055. -mfsca -mno-fsca Allow or disallow the compiler to emit the "fsca" instruction for sine and cosine approximations. The option -mfsca must be used in combina- tion with -funsafe-math-optimizations. It is enabled by default when generating code for SH4A. Using -mno-fsca disables sine and cosine ap- proximations even if -funsafe-math-optimizations is in effect. -mfsrra -mno-fsrra Allow or disallow the compiler to emit the "fsrra" instruction for rec- iprocal square root approximations. The option -mfsrra must be used in combination with -funsafe-math-optimizations and -ffinite-math-only. It is enabled by default when generating code for SH4A. Using -mno-fs- rra disables reciprocal square root approximations even if -fun- safe-math-optimizations and -ffinite-math-only are in effect. -mpretend-cmove -mno-pretend-cmove Prefer or don't prefer zero-displacement conditional branches for con- ditional move instruction patterns. This can result in faster code on the SH4 processor. -mfdpic -mno-fdpic Generate code using the FDPIC ABI. -mlra -mno-lra Use the new LRA register allocator. By default, the old "reload" allo- cator is used. Solaris 2 Options These options are supported on Solaris 2: -mclear-hwcap -mno-clear-hwcap -mclear-hwcap tells the compiler to remove the hardware capabilities generated by the Solaris assembler. This is only necessary when object files use ISA extensions not supported by the current machine, but check at runtime whether or not to use them. -mimpure-text -mno-impure-text -mimpure-text, used in addition to -shared, tells the compiler to not pass -z text to the linker when linking a shared object. Using this option, you can link position-dependent code into a shared object. -mimpure-text suppresses the "relocations remain against allocatable but non-writable sections" linker error message. However, the neces- sary relocations trigger copy-on-write, and the shared object is not actually shared across processes. Instead of using -mimpure-text, you should compile all source code with -fpic or -fPIC. -gsctf Generate Solaris CTF. Needs to be used both for compilation and link- ing. See ctf(7) for more information. This is only supported since Solaris 11.4 SRU 84 where the necessary toolchain support was added. SPARC Options These -m options are supported on the SPARC: -mno-app-regs -mapp-regs Specify -mapp-regs to generate output using the global registers 2 through 4, which the SPARC SVR4 ABI reserves for applications. Like the global register 1, each global register 2 through 4 is then treated as an allocable register that is clobbered by function calls. This is the default. To be fully SVR4 ABI-compliant at the cost of some performance loss, specify -mno-app-regs. You should compile libraries and system soft- ware with this option. -mflat -mno-flat With -mflat, the compiler does not generate save/restore instructions and uses a "flat" or single register window model. This model is com- patible with the regular register window model. The local registers and the input registers (0--5) are still treated as "call-saved" regis- ters and are saved on the stack as needed. With -mno-flat (the default), the compiler generates save/restore in- structions (except for leaf functions). This is the normal operating mode. -mfpu -mhard-float Generate output containing floating-point instructions. This is the default. -mno-fpu -msoft-float Generate output containing library calls for floating point. Warning: the requisite libraries are not available for all SPARC targets. Nor- mally 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-compi- lation. The embedded targets sparc-*-aout and sparclite-*-* do provide software floating-point support. -msoft-float changes the calling convention in the output file; there- fore, it is only useful if you compile all of a program with this op- tion. In particular, you need to compile libgcc.a, the library that comes with GCC, with -msoft-float in order for this to work. -mhard-quad-float Generate output containing quad-word (long double) floating-point in- structions. -msoft-quad-float Generate output containing library calls for quad-word (long double) floating-point instructions. The functions called are those specified in the SPARC ABI. This is the default. As of this writing, there are no SPARC implementations that have hard- ware 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 ABI library rou- tines. Thus the -msoft-quad-float option is the default. -mno-unaligned-doubles -munaligned-doubles Assume that doubles have 8-byte alignment. This is the default. With -munaligned-doubles, GCC assumes that doubles have 8-byte align- ment only if they are contained in another type, or if they have an ab- solute 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. -muser-mode -mno-user-mode Do not generate code that can only run in supervisor mode. This is relevant only for the "casa" instruction emitted for the LEON3 proces- sor. This is the default. -mfaster-structs -mno-faster-structs With -mfaster-structs, the compiler assumes that structures should have 8-byte alignment. This enables the use of pairs of "ldd" and "std" in- structions for copies in structure assignment, in place of twice as many "ld" and "st" pairs. However, the use of this changed alignment directly violates the SPARC ABI. Thus, it's intended only for use on targets where the developer acknowledges that their resulting code is not directly in line with the rules of the ABI. -mstd-struct-return -mno-std-struct-return With -mstd-struct-return, the compiler generates checking code in func- tions returning structures or unions to detect size mismatches between the two sides of function calls, as per the 32-bit ABI. The default is -mno-std-struct-return. This option has no effect in 64-bit mode. -mcpu=cpu_type Set the instruction set, register set, and instruction scheduling para- meters for machine type cpu_type. Supported values for cpu_type are v7, cypress, v8, supersparc, hypersparc, leon, leon3, leon3v7, leon5, sparclite, f930, f934, sparclite86x, sparclet, tsc701, v9, ultrasparc, ultrasparc3, niagara, niagara2, niagara3, niagara4, niagara7 and m8. Native Solaris and GNU/Linux toolchains also support the value native, which selects the best architecture option for the host processor. -mcpu=native has no effect if GCC does not recognize the processor. Default instruction scheduling parameters are used for values that se- lect an architecture and not an implementation. These are v7, v8, sparclite, sparclet, v9. Here is a list of each supported architecture and their supported im- plementations. v7 cypress, leon3v7 v8 supersparc, hypersparc, leon, leon3, leon5 sparclite f930, f934, sparclite86x sparclet tsc701 v9 ultrasparc, ultrasparc3, niagara, niagara2, niagara3, niagara4, ni- agara7, m8 By default (unless configured otherwise), GCC generates code for the V7 variant of the SPARC architecture. With -mcpu=cypress, the compiler additionally optimizes it for the Cypress CY7C602 chip, as used in the SPARCStation/SPARCServer 3xx series. This is also appropriate for the older SPARCStation 1, 2, IPX etc. With -mcpu=v8, GCC generates code for the V8 variant of the SPARC ar- chitecture. The only difference from V7 code is that the compiler emits the integer multiply and integer divide instructions which exist in SPARC-V8 but not in SPARC-V7. With -mcpu=supersparc, the compiler additionally optimizes it for the SuperSPARC chip, as used in the SPARCStation 10, 1000 and 2000 series. With -mcpu=sparclite, GCC generates code for the SPARClite variant of the SPARC architecture. This adds the integer multiply, integer divide step and scan ("ffs") instructions which exist in SPARClite but not in SPARC-V7. With -mcpu=f930, the compiler additionally optimizes it for the Fujitsu MB86930 chip, which is the original SPARClite, with no FPU. With -mcpu=f934, the compiler additionally optimizes it for the Fujitsu MB86934 chip, which is the more recent SPARClite with FPU. With -mcpu=sparclet, GCC generates code for the SPARClet variant of the SPARC architecture. This adds the integer multiply, multiply/accumu- late, integer divide step and scan ("ffs") instructions which exist in SPARClet but not in SPARC-V7. With -mcpu=tsc701, the compiler addi- tionally optimizes it for the TEMIC SPARClet chip. With -mcpu=v9, GCC generates code for the V9 variant of the SPARC ar- chitecture. This adds 64-bit integer and floating-point move instruc- tions, 3 additional floating-point condition code registers and condi- tional move instructions. With -mcpu=ultrasparc, the compiler addi- tionally optimizes it for the Sun UltraSPARC I/II/IIi chips. With -mcpu=ultrasparc3, the compiler additionally optimizes it for the Sun UltraSPARC III/III+/IIIi/IIIi+/IV/IV+ chips. With -mcpu=niagara, the compiler additionally optimizes it for Sun UltraSPARC T1 chips. With -mcpu=niagara2, the compiler additionally optimizes it for Sun Ultra- SPARC T2 chips. With -mcpu=niagara3, the compiler additionally opti- mizes it for Sun UltraSPARC T3 chips. With -mcpu=niagara4, the com- piler additionally optimizes it for Sun UltraSPARC T4 chips. With -mcpu=niagara7, the compiler additionally optimizes it for Oracle SPARC M7 chips. With -mcpu=m8, the compiler additionally optimizes it for Oracle M8 chips. -mtune=cpu_type Set the instruction scheduling parameters for machine type cpu_type, but do not set the instruction set or register set that the option -mcpu=cpu_type does. The same values for -mcpu=cpu_type can be used for -mtune=cpu_type, but the only useful values are those that select a particular CPU implemen- tation. Those are cypress, supersparc, hypersparc, leon, leon3, leon3v7, leon5, f930, f934, sparclite86x, tsc701, ultrasparc, ultra- sparc3, niagara, niagara2, niagara3, niagara4, niagara7 and m8. With native Solaris and GNU/Linux toolchains, native can also be used. -mv8plus -mno-v8plus With -mv8plus, GCC generates code for the SPARC-V8+ ABI. The differ- ence from the V8 ABI is that the global and out registers are consid- ered 64 bits wide. This is enabled by default on Solaris in 32-bit mode for all SPARC-V9 processors. -mvis -mno-vis With -mvis, GCC generates code that takes advantage of the UltraSPARC Visual Instruction Set extensions. The default is -mno-vis. -mvis2 -mno-vis2 With -mvis2, GCC generates code that takes advantage of version 2.0 of the UltraSPARC Visual Instruction Set extensions. The default is -mvis2 when targeting a cpu that supports such instructions, such as UltraSPARC-III and later. Setting -mvis2 also sets -mvis. -mvis3 -mno-vis3 With -mvis3, GCC generates code that takes advantage of version 3.0 of the UltraSPARC Visual Instruction Set extensions. The default is -mvis3 when targeting a cpu that supports such instructions, such as niagara-3 and later. Setting -mvis3 also sets -mvis2 and -mvis. -mvis3b -mno-vis3b With -mvis3b, GCC generates code that takes advantage of version 3.0 of the UltraSPARC Visual Instruction Set extensions, plus the additional VIS instructions introduced in the Oracle SPARC Architecture 2011. The default is -mvis3b when targeting a cpu that supports such instruc- tions, such as niagara-7 and later. Setting -mvis3b also sets -mvis3, -mvis2 and -mvis. -mvis4 -mno-vis4 With -mvis4, GCC generates code that takes advantage of version 4.0 of the UltraSPARC Visual Instruction Set extensions. The default is -mvis4 when targeting a cpu that supports such instructions, such as niagara-7 and later. Setting -mvis4 also sets -mvis3b, -mvis3, -mvis2 and -mvis. -mvis4b -mno-vis4b With -mvis4b, GCC generates code that takes advantage of version 4.0 of the UltraSPARC Visual Instruction Set extensions, plus the additional VIS instructions introduced in the Oracle SPARC Architecture 2017. The default is -mvis4b when targeting a cpu that supports such instruc- tions, such as m8 and later. Setting -mvis4b also sets -mvis4, -mvis3b, -mvis3, -mvis2 and -mvis. -mcbcond -mno-cbcond With -mcbcond, GCC generates code that takes advantage of the Ultra- SPARC Compare-and-Branch-on-Condition instructions. The default is -mcbcond when targeting a CPU that supports such instructions, such as Niagara-4 and later. -mfmaf -mno-fmaf With -mfmaf, GCC generates code that takes advantage of the UltraSPARC Fused Multiply-Add Floating-point instructions. The default is -mfmaf when targeting a CPU that supports such instructions, such as Niagara-3 and later. -mfsmuld -mno-fsmuld With -mfsmuld, GCC generates code that takes advantage of the Float- ing-point Multiply Single to Double (FsMULd) instruction. The default is -mfsmuld when targeting a CPU supporting the architecture versions V8 or V9 with FPU except -mcpu=leon. -mpopc -mno-popc With -mpopc, GCC generates code that takes advantage of the UltraSPARC Population Count instruction. The default is -mpopc when targeting a CPU that supports such an instruction, such as Niagara-2 and later. -msubxc -mno-subxc With -msubxc, GCC generates code that takes advantage of the UltraSPARC Subtract-Extended-with-Carry instruction. The default is -msubxc when targeting a CPU that supports such an instruction, such as Niagara-7 and later. -mfix-at697f Enable the documented workaround for the single erratum of the Atmel AT697F processor (which corresponds to erratum #13 of the AT697E processor). -mfix-ut699 Enable the documented workarounds for the floating-point errata and the data cache nullify errata of the UT699 processor. -mfix-ut700 Enable the documented workaround for the back-to-back store errata of the UT699E/UT700 processor. -mfix-gr712rc Enable the documented workaround for the back-to-back store errata of the GR712RC processor. These -m options are supported in addition to the above on SPARC-V9 proces- sors in 64-bit environments: -m32 -m64Generate code for a 32-bit or 64-bit environment. The 32-bit environ- ment sets int, long and pointer to 32 bits. The 64-bit environment sets int to 32 bits and long and pointer to 64 bits. -mptr32 -mptr64 Use 32- or 64-bit pointers, respectively. Unlike the -m32 and -m64 op- tions, this affects only the pointer size and not the ABI. -mcmodel=which Set the code model to one of medlow The Medium/Low code model: 64-bit addresses, programs must be linked in the low 32 bits of memory. Programs can be statically or dynamically linked. medmid The Medium/Middle code model: 64-bit addresses, programs must be linked in the low 44 bits of memory, the text and data segments must be less than 2GB in size and the data segment must be located within 2GB of the text segment. medany The Medium/Anywhere code model: 64-bit addresses, programs may be linked anywhere in memory, the text and data segments must be less than 2GB in size and the data segment must be located within 2GB of the text segment. embmedany The Medium/Anywhere code model for embedded systems: 64-bit ad- dresses, the text and data segments must be less than 2GB in size, both starting anywhere in memory (determined at link time). The global register %g4 points to the base of the data segment. Pro- grams are statically linked and PIC is not supported. -mmemory-model=mem-model Set the memory model in force on the processor to one of default The default memory model for the processor and operating system. rmo Relaxed Memory Order pso Partial Store Order tso Total Store Order sc Sequential Consistency These memory models are formally defined in Appendix D of the SPARC-V9 architecture manual, as set in the processor's "PSTATE.MM" field. -mstack-bias -mno-stack-bias With -mstack-bias, GCC assumes that the stack pointer, and frame pointer if present, are offset by -2047 which must be added back when making stack frame references. This is the default in 64-bit mode. Otherwise, assume no such offset is present. Options for System V These additional options are available on System V Release 4 for compati- bility with other compilers on those systems: -G Create a shared object. It is recommended that -symbolic or -shared be used instead. -YP,dirs Search the directories dirs, and no others, for libraries specified with -l. -Ym,dir Look in the directory dir to find the M4 preprocessor. The assembler uses this option. V850 Options These -m options are defined for V850 implementations: -mlong-calls -mno-long-calls Treat all calls as being far away (near). If calls are assumed to be far away, the compiler always loads the function's address into a reg- ister, and calls indirect through the pointer. -mno-ep -mepDo not optimize (do optimize) basic blocks that use the same index pointer 4 or more times to copy pointer into the "ep" register, and use the shorter "sld" and "sst" instructions. The -mep option is on by de- fault if you optimize. -mno-prolog-function -mprolog-function Do not use (do use) external functions to save and restore registers at the prologue and epilogue 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 -mprolog-function option is on by de- fault if you optimize. -mspace Try to make the code as small as possible. At present, this just turns on the -mep and -mprolog-function options. -mtda=n Put static or global variables whose size is n bytes or less into the tiny data area that register "ep" points to. The tiny data area can hold up to 256 bytes in total (128 bytes for byte references). -msda=n Put static or global variables whose size is n bytes or less into the small data area that register "gp" points to. The small data area can hold up to 64 kilobytes. -mzda=n Put static or global variables whose size is n bytes or less into the first 32 kilobytes of memory. -mv850 Specify that the target processor is the V850. -mv850e3v5 Specify that the target processor is the V850E3V5. The preprocessor constant "__v850e3v5__" is defined if this option is used. -mv850e2v4 Specify that the target processor is the V850E3V5. This is an alias for the -mv850e3v5 option. -mv850e2v3 Specify that the target processor is the V850E2V3. The preprocessor constant "__v850e2v3__" is defined if this option is used. -mv850e2 Specify that the target processor is the V850E2. The preprocessor con- stant "__v850e2__" is defined if this option is used. -mv850e1 Specify that the target processor is the V850E1. The preprocessor con- stants "__v850e1__" and "__v850e__" are defined if this option is used. -mv850es Specify that the target processor is the V850ES. This is an alias for the -mv850e1 option. -mv850e Specify that the target processor is the V850E. The preprocessor con- stant "__v850e__" is defined if this option is used. If neither -mv850 nor -mv850e nor -mv850e1 nor -mv850e2 nor -mv850e2v3 nor -mv850e3v5 are defined then a default target processor is chosen and the relevant __v850*__ preprocessor constant is defined. The preprocessor constants "__v850" and "__v851__" are always defined, regardless of which processor variant is the target. -mdisable-callt -mno-disable-callt This option suppresses generation of the "CALLT" instruction for the v850e, v850e1, v850e2, v850e2v3 and v850e3v5 flavors of the v850 archi- tecture. This option is enabled by default when the RH850 ABI is in use (see -mrh850-abi), and disabled by default when the GCC ABI is in use. If "CALLT" instructions are being generated then the C preprocessor symbol "__V850_CALLT__" is defined. -mrelax -mno-relax Pass on (or do not pass on) the -mrelax command-line option to the as- sembler. -mlong-jumps -mno-long-jumps Disable (or re-enable) the generation of PC-relative jump instructions. -msoft-float -mhard-float Disable (or re-enable) the generation of hardware floating point in- structions. This option is only significant when the target architec- ture is V850E2V3 or higher. If hardware floating point instructions are being generated then the C preprocessor symbol "__FPU_OK__" is de- fined, otherwise the symbol "__NO_FPU__" is defined. -mloop Enables the use of the e3v5 LOOP instruction. The use of this instruc- tion is not enabled by default when the e3v5 architecture is selected because its use is still experimental. -mrh850-abi -mghs Enables support for the RH850 version of the V850 ABI. This is the de- fault. With this version of the ABI the following rules apply: * Integer sized structures and unions are returned via a memory pointer rather than a register. * Large structures and unions (more than 8 bytes in size) are passed by value. * Functions are aligned to 16-bit boundaries. * The -m8byte-align command-line option is supported. * The -mdisable-callt command-line option is enabled by default. The -mno-disable-callt command-line option is not supported. When this version of the ABI is enabled the C preprocessor symbol "__V850_RH850_ABI__" is defined. -mgcc-abi Enables support for the old GCC version of the V850 ABI. With this version of the ABI the following rules apply: * Integer sized structures and unions are returned in register "r10". * Large structures and unions (more than 8 bytes in size) are passed by reference. * Functions are aligned to 32-bit boundaries, unless optimizing for size. * The -m8byte-align command-line option is not supported. * The -mdisable-callt command-line option is supported but not en- abled by default. When this version of the ABI is enabled the C preprocessor symbol "__V850_GCC_ABI__" is defined. -m8byte-align -mno-8byte-align Enables support for "double" and "long long" types to be aligned on 8-byte boundaries. The default is to restrict the alignment of all ob- jects to at most 4-bytes. When -m8byte-align is in effect the C pre- processor symbol "__V850_8BYTE_ALIGN__" is defined. -mbig-switch -mno-big-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. -mapp-regs -mno-app-regs -mapp-regs causes r2 and r5 to be used in the code generated by the compiler. This setting is the default. -mno-app-regs causes r2 and r5 to be treated as fixed registers. -msmall-sld -mno-small-sld Enable or disable the use of the short load instructions. -mno-strict-align Do not enforce strict data alignment. -mjump-tables-in-data-section -mno-jump-tables-in-data-section Enable or disable placement of jump tables for switch statements in the ".data" section rather than the ".code" section. The default is -mno-jump-tables-in-data-section. VAX Options These -m options are defined for the VAX: -munix Do not output certain jump instructions ("aobleq" and so on) that the Unix assembler for the VAX cannot handle across long ranges. -mgnu Do output those jump instructions, on the assumption that the GNU as- sembler is being used. -md -md-float Use the D_floating data format for double-precision floating-point num- bers instead of G_floating. -mg -mg-float Use the G_floating data format for double-precision floating-point num- bers instead of D_floating. -mlra -mno-lra Enable Local Register Allocation. This is still experimental for the VAX, so by default the compiler uses standard reload. -mvaxc-alignment Use VAXC conventions for alignment of structure members. -mqmath -mno-qmath Enable or disable new instruction patterns for 64-bit integer addition and subtraction. Visium Options -mdebug Use this option when linking programs that perform file I/O and are destined to run on an MCM target. It causes the libraries libc.a and libdebug.a to be linked. You should run program on the the target un- der the control of the GDB remote debugging stub. -msim Use this option when linking programs that perform file I/O and are destined to run on the simulator. It causes the libraries libc.a and libsim.a to be linked. -mfpu -mhard-float Generate code containing floating-point instructions. This is the de- fault. -mno-fpu -msoft-float Generate code containing library calls for floating-point. -msoft-float changes the calling convention in the output file; there- fore, it is only useful if you compile all of a program with this op- tion. In particular, you need to compile libgcc.a, the library that comes with GCC, with -msoft-float in order for this to work. -mcpu=cpu_type Set the instruction set, register set, and instruction scheduling para- meters for machine type cpu_type. Supported values for cpu_type are mcm, gr5 and gr6. mcm is a synonym of gr5 present for backward compatibility. By default (unless configured otherwise), GCC generates code for the GR5 variant of the Visium architecture. With -mcpu=gr6, GCC generates code for the GR6 variant of the Visium architecture. The only difference from GR5 code is that the compiler will generate block move instructions. -mtune=cpu_type Set the instruction scheduling parameters for machine type cpu_type, but do not set the instruction set or register set that the option -mcpu=cpu_type would. -msv-mode Generate code for the supervisor mode, where there are no restrictions on the access to general registers. This is the default. -muser-mode Generate code for the user mode, where the access to some general reg- isters is forbidden: on the GR5, registers r24 to r31 cannot be ac- cessed in this mode; on the GR6, only registers r29 to r31 are af- fected. VMS Options These -m options are defined for the VMS implementations: -mvms-return-codes Return VMS condition codes from "main". The default is to return POSIX-style condition (e.g. error) codes. -mdebug-main=prefix Flag the first routine whose name starts with prefix as the main rou- tine for the debugger. -mmalloc64 Default to 64-bit memory allocation routines. -mpointer-size=size Set the default size of pointers. Possible options for size are 32 or short for 32 bit pointers, 64 or long for 64 bit pointers, and no for supporting only 32 bit pointers. The later option disables "pragma pointer_size". VxWorks Options The options in this section are defined for all VxWorks targets. Options specific to the target hardware are listed with the other options for that target. -mrtp GCC can generate code for both VxWorks kernels and real time processes (RTPs). This option switches from the former to the latter. It also defines the preprocessor macro "__RTP__". -msmp Select SMP runtimes for linking. Not available on architectures other than PowerPC, nor on VxWorks version 7 or later, in which the selection is part of the VxWorks build configuration and the library paths are the same for either choice. -mvthreads Link against the VxWorks AE vThread runtime environment. -non-static Link an RTP executable against shared libraries rather than static li- braries. The options -static and -shared can also be used for RTPs; -static is the default. -Bstatic -Bdynamic These options are passed down to the linker. They are defined for com- patibility with Diab. -Xbind-lazy Enable lazy binding of function calls. This option is equivalent to -Wl,-z,now and is defined for compatibility with Diab. -Xbind-now Disable lazy binding of function calls. This option is the default and is defined for compatibility with Diab. x86 Options This section documents -m options available for the x86 family of comput- ers. The following group of options allows compilation to target a specific processor. -march=cpu-type Generate instructions for the machine type cpu-type. In contrast to -mtune=cpu-type, which merely tunes the generated code for the speci- fied cpu-type, -march=cpu-type allows GCC to generate code that may not run at all on processors other than the one indicated. Specifying -march=cpu-type implies -mtune=cpu-type, except where noted otherwise. The choices for cpu-type are: native This selects the CPU to generate code for at compilation time by determining the processor type of the compiling machine. Using -march=native enables all instruction subsets supported by the lo- cal machine (hence the result might not run on different machines). Using -mtune=native produces code optimized for the local machine under the constraints of the selected instruction set. x86-64 A generic CPU with 64-bit extensions, MMX, SSE, SSE2, and FXSR in- struction set support. x86-64-v2 x86-64-v3 x86-64-v4 These choices for cpu-type select the corresponding micro-architec- ture level from the x86-64 psABI. On ABIs other than the x86-64 psABI they select the same CPU features as the x86-64 psABI docu- ments for the particular micro-architecture level. Since these cpu-type values do not have a corresponding -mtune set- ting, using -march with these values enables generic tuning. Spe- cific tuning can be enabled using the -mtune=other-cpu-type option with an appropriate other-cpu-type value. i386Original Intel i386 CPU. i486Intel i486 CPU. (No scheduling is implemented for this chip.) i586 pentium Intel Pentium CPU with no MMX support. lakemont Intel Lakemont MCU, based on Intel Pentium CPU. pentium-mmx Intel Pentium MMX CPU, based on Pentium core with MMX instruction set support. pentiumpro Intel Pentium Pro CPU with no MMX support. i686When used with -march, the Pentium Pro instruction set is used, so the code runs on all i686 family chips. When used with -mtune, it has the same meaning as generic. pentium2 Intel Pentium II CPU, based on Pentium Pro core with MMX and FXSR instruction set support. pentium3 pentium3m Intel Pentium III CPU, based on Pentium Pro core with MMX, FXSR and SSE instruction set support. pentium-m Intel Pentium M; low-power version of Intel Pentium III CPU with MMX, SSE, SSE2 and FXSR instruction set support. Used by Centrino notebooks. pentium4 pentium4m Intel Pentium 4 CPU with MMX, SSE, SSE2 and FXSR instruction set support. prescott Improved version of Intel Pentium 4 CPU with MMX, SSE, SSE2, SSE3 and FXSR instruction set support. nocona Improved version of Intel Pentium 4 CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3, CX16 and FXSR instruction set support. core2 Intel Core 2 CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3, SSSE3, CX16, SAHF and FXSR instruction set support. nehalem corei7 Intel Nehalem CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, CX16, SAHF and FXSR instruction set support. westmere Intel Westmere CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, CX16, SAHF, FXSR and PCLMUL instruc- tion set support. sandybridge corei7-avx Intel Sandy Bridge CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, CX16, SAHF, FXSR, AVX, XSAVE and PCLMUL instruction set support. ivybridge core-avx-i Intel Ivy Bridge CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, CX16, SAHF, FXSR, AVX, XSAVE, PCLMUL, FSGSBASE, RDRND and F16C instruction set support. haswell core-avx2 Intel Haswell CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, CX16, SAHF, FXSR, AVX, XSAVE, PCLMUL, FSGSBASE, RDRND, F16C, AVX2, BMI, BMI2, LZCNT, FMA, MOVBE and HLE instruction set support. broadwell Intel Broadwell CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, CX16, SAHF, FXSR, AVX, XSAVE, PCLMUL, FSGSBASE, RDRND, F16C, AVX2, BMI, BMI2, LZCNT, FMA, MOVBE, HLE, RDSEED, ADCX and PREFETCHW instruction set support. skylake Intel Skylake CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, CX16, SAHF, FXSR, AVX, XSAVE, PCLMUL, FSGSBASE, RDRND, F16C, AVX2, BMI, BMI2, LZCNT, FMA, MOVBE, HLE, RDSEED, ADCX, PREFETCHW, AES, CLFLUSHOPT, XSAVEC, XSAVES and SGX instruction set support. skylake-avx512 Intel Skylake Server CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, CX16, SAHF, FXSR, AVX, XSAVE, PCLMUL, FSGSBASE, RDRND, F16C, AVX2, BMI, BMI2, LZCNT, FMA, MOVBE, HLE, RDSEED, ADCX, PREFETCHW, AES, CLFLUSHOPT, XSAVEC, XSAVES, SGX, AVX512F, CLWB, AVX512VL, AVX512BW, AVX512DQ and AVX512CD instruc- tion set support. cascadelake Intel Cascade Lake CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, CX16, SAHF, FXSR, AVX, XSAVE, PCLMUL, FSGSBASE, RDRND, F16C, AVX2, BMI, BMI2, LZCNT, FMA, MOVBE, HLE, RDSEED, ADCX, PREFETCHW, AES, CLFLUSHOPT, XSAVEC, XSAVES, SGX, AVX512F, CLWB, AVX512VL, AVX512BW, AVX512DQ, AVX512CD and AVX512VNNI instruction set support. cannonlake Intel Cannon Lake Server CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, CX16, SAHF, FXSR, AVX, XSAVE, PCLMUL, FSGSBASE, RDRND, F16C, AVX2, BMI, BMI2, LZCNT, FMA, MOVBE, HLE, RDSEED, ADCX, PREFETCHW, AES, CLFLUSHOPT, XSAVEC, XSAVES, SGX, AVX512F, AVX512VL, AVX512BW, AVX512DQ, AVX512CD, PKU, AVX512VBMI, AVX512IFMA and SHA instruction set support. cooperlake Intel Cooper Lake CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, CX16, SAHF, FXSR, AVX, XSAVE, PCLMUL, FSGSBASE, RDRND, F16C, AVX2, BMI, BMI2, LZCNT, FMA, MOVBE, HLE, RDSEED, ADCX, PREFETCHW, AES, CLFLUSHOPT, XSAVEC, XSAVES, SGX, AVX512F, CLWB, AVX512VL, AVX512BW, AVX512DQ, AVX512CD, AVX512VNNI and AVX512BF16 instruction set support. icelake-client Intel Ice Lake Client CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, CX16, SAHF, FXSR, AVX, XSAVE, PCLMUL, FSGSBASE, RDRND, F16C, AVX2, BMI, BMI2, LZCNT, FMA, MOVBE, HLE, RDSEED, ADCX, PREFETCHW, AES, CLFLUSHOPT, XSAVEC, XSAVES, SGX, AVX512F, AVX512VL, AVX512BW, AVX512DQ, AVX512CD, PKU, AVX512VBMI, AVX512IFMA, SHA, AVX512VNNI, GFNI, VAES, AVX512VBMI2 , VPCLMULQDQ, AVX512BITALG, RDPID and AVX512VPOPCNTDQ instruction set support. icelake-server Intel Ice Lake Server CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, CX16, SAHF, FXSR, AVX, XSAVE, PCLMUL, FSGSBASE, RDRND, F16C, AVX2, BMI, BMI2, LZCNT, FMA, MOVBE, HLE, RDSEED, ADCX, PREFETCHW, AES, CLFLUSHOPT, XSAVEC, XSAVES, SGX, AVX512F, AVX512VL, AVX512BW, AVX512DQ, AVX512CD, PKU, AVX512VBMI, AVX512IFMA, SHA, AVX512VNNI, GFNI, VAES, AVX512VBMI2 , VPCLMULQDQ, AVX512BITALG, RDPID, AVX512VPOPCNTDQ, PCONFIG, WBNOINVD and CLWB instruction set support. tigerlake Intel Tiger Lake CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, CX16, SAHF, FXSR, AVX, XSAVE, PCLMUL, FSGSBASE, RDRND, F16C, AVX2, BMI, BMI2, LZCNT, FMA, MOVBE, HLE, RDSEED, ADCX, PREFETCHW, AES, CLFLUSHOPT, XSAVEC, XSAVES, SGX, AVX512F, AVX512VL, AVX512BW, AVX512DQ, AVX512CD PKU, AVX512VBMI, AVX512IFMA, SHA, AVX512VNNI, GFNI, VAES, AVX512VBMI2, VPCLMULQDQ, AVX512BITALG, RDPID, AVX512VPOPCNTDQ, MOVDIRI, MOVDIR64B, CLWB, AVX512VP2INTERSECT and KEYLOCKER instruction set support. rocketlake Intel Rocket Lake CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, CX16, SAHF, FXSR, AVX, XSAVE, PCLMUL, FSGSBASE, RDRND, F16C, AVX2, BMI, BMI2, LZCNT, FMA, MOVBE, HLE, RDSEED, ADCX, PREFETCHW, AES, CLFLUSHOPT, XSAVEC, XSAVES, AVX512F, AVX512VL, AVX512BW, AVX512DQ, AVX512CD PKU, AVX512VBMI, AVX512IFMA, SHA, AVX512VNNI, GFNI, VAES, AVX512VBMI2, VPCLMULQDQ, AVX512BITALG, RDPID and AVX512VPOPCNTDQ instruction set support. alderlake raptorlake meteorlake gracemont Intel Alder Lake/Raptor Lake/Meteor Lake/Gracemont CPU with 64-bit extensions, MOVBE, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, CX16, AES, PREFETCHW, PCLMUL, RDRND, XSAVE, XSAVEC, XSAVES, XSAVEOPT, FSGSBASE, PTWRITE, RDPID, SGX, GFNI-SSE, CLWB, MOVDIRI, MOVDIR64B, WAITPKG, ADCX, AVX, AVX2, BMI, BMI2, F16C, FMA, LZCNT, PCONFIG, PKU, VAES, VPCLMULQDQ, SERIALIZE, HRESET, KL, WIDEKL and AVX-VNNI instruction set support. arrowlake Intel Arrow Lake CPU with 64-bit extensions, MOVBE, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, CX16, AES, PREFETCHW, PCLMUL, RDRND, XSAVE, XSAVEC, XSAVES, XSAVEOPT, FSGSBASE, PTWRITE, RDPID, SGX, GFNI-SSE, CLWB, MOVDIRI, MOVDIR64B, WAITPKG, ADCX, AVX, AVX2, BMI, BMI2, F16C, FMA, LZCNT, PCONFIG, PKU, VAES, VPCLMULQDQ, SERI- ALIZE, HRESET, KL, WIDEKL, AVX-VNNI, UINTR, AVXIFMA, AVXVNNIINT8, AVXNECONVERT and CMPCCXADD instruction set support. arrowlake-s lunarlake Intel Arrow Lake S/Lunar Lake CPU with 64-bit extensions, MOVBE, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, CX16, AES, PREFETCHW, PCLMUL, RDRND, XSAVE, XSAVEC, XSAVES, XSAVEOPT, FSGS- BASE, PTWRITE, RDPID, SGX, GFNI-SSE, CLWB, MOVDIRI, MOVDIR64B, WAITPKG, ADCX, AVX, AVX2, BMI, BMI2, F16C, FMA, LZCNT, PCONFIG, PKU, VAES, VPCLMULQDQ, SERIALIZE, HRESET, KL, WIDEKL, AVX-VNNI, UINTR, AVXIFMA, AVXVNNIINT8, AVXNECONVERT, CMPCCXADD, AVXVNNIINT16, SHA512, SM3 and SM4 instruction set support. pantherlake wildcatlake Intel Panther Lake/Wildcat Lake CPU with 64-bit extensions, MOVBE, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, CX16, AES, PREFETCHW, PCLMUL, RDRND, XSAVE, XSAVEC, XSAVES, XSAVEOPT, FSGS- BASE, PTWRITE, RDPID, SGX, GFNI-SSE, CLWB, MOVDIRI, MOVDIR64B, WAITPKG, ADCX, AVX, AVX2, BMI, BMI2, F16C, FMA, LZCNT, PCONFIG, PKU, VAES, VPCLMULQDQ, SERIALIZE, HRESET, AVX-VNNI, UINTR, AVXIFMA, AVXVNNIINT8, AVXNECONVERT, CMPCCXADD, AVXVNNIINT16, SHA512, SM3 and SM4 instruction set support. novalake Intel Nova Lake CPU with 64-bit extensions, MOVBE, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, CX16, AES, PREFETCHW, PCLMUL, RDRND, XSAVE, XSAVEC, XSAVES, XSAVEOPT, FSGSBASE, PTWRITE, RDPID, SGX, GFNI-SSE, CLWB, MOVDIRI, MOVDIR64B, WAITPKG, ADCX, AVX, AVX2, BMI, BMI2, F16C, FMA, LZCNT, PCONFIG, PKU, VAES, VPCLMULQDQ, SERI- ALIZE, HRESET, AVX-VNNI, UINTR, AVXIFMA, AVXVNNIINT8, AVXNECONVERT, CMPCCXADD, AVXVNNIINT16, SHA512, SM3, SM4, PREFETCHI, APX_F, AVX10.1, AVX10.2 and MOVRS instruction set support. sapphirerapids emeraldrapids Intel Sapphire Rapids/Emerald Rapids CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, CX16, SAHF, FXSR, AVX, XSAVE, PCLMUL, FSGSBASE, RDRND, F16C, AVX2, BMI, BMI2, LZCNT, FMA, MOVBE, HLE, RDSEED, ADCX, PREFETCHW, AES, CLFLUSHOPT, XSAVEC, XSAVES, SGX, AVX512F, AVX512VL, AVX512BW, AVX512DQ, AVX512CD, PKU, AVX512VBMI, AVX512IFMA, SHA, AVX512VNNI, GFNI, VAES, AVX512VBMI2, VPCLMULQDQ, AVX512BITALG, RDPID, AVX512VPOPCNTDQ, PCONFIG, WBNOINVD, CLWB, MOVDIRI, MOVDIR64B, ENQCMD, CLDEMOTE, PTWRITE, WAITPKG, SERIALIZE, TSXLDTRK, UINTR, AMX-BF16, AMX-TILE, AMX-INT8, AVX-VNNI, AVX512-FP16 and AVX512BF16 instruction set sup- port. graniterapids Intel Granite Rapids CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, CX16, SAHF, FXSR, AVX, XSAVE, PCLMUL, FSGSBASE, RDRND, F16C, AVX2, BMI, BMI2, LZCNT, FMA, MOVBE, HLE, RDSEED, ADCX, PREFETCHW, AES, CLFLUSHOPT, XSAVEC, XSAVES, SGX, AVX512F, AVX512VL, AVX512BW, AVX512DQ, AVX512CD, PKU, AVX512VBMI, AVX512IFMA, SHA, AVX512VNNI, GFNI, VAES, AVX512VBMI2, VPCLMULQDQ, AVX512BITALG, RDPID, AVX512VPOPCNTDQ, PCONFIG, WBNOINVD, CLWB, MOVDIRI, MOVDIR64B, ENQCMD, CLDEMOTE, PTWRITE, WAITPKG, SERIALIZE, TSXLDTRK, UINTR, AMX-BF16, AMX-TILE, AMX-INT8, AVX-VNNI, AVX512-FP16, AVX512BF16, AMX-FP16 and PREFETCHI instruction set support. graniterapids-d Intel Granite Rapids D CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, CX16, SAHF, FXSR, AVX, XSAVE, PCLMUL, FSGSBASE, RDRND, F16C, AVX2, BMI, BMI2, LZCNT, FMA, MOVBE, HLE, RDSEED, ADCX, PREFETCHW, AES, CLFLUSHOPT, XSAVEC, XSAVES, SGX, AVX512F, AVX512VL, AVX512BW, AVX512DQ, AVX512CD, PKU, AVX512VBMI, AVX512IFMA, SHA, AVX512VNNI, GFNI, VAES, AVX512VBMI2, VPCLMULQDQ, AVX512BITALG, RDPID, AVX512VPOPCNTDQ, PCONFIG, WBNOINVD, CLWB, MOVDIRI, MOVDIR64B, ENQCMD, CLDEMOTE, PTWRITE, WAITPKG, SERIALIZE, TSXLDTRK, UINTR, AMX-BF16, AMX-TILE, AMX-INT8, AVX-VNNI, AVX512FP16, AVX512BF16, AMX-FP16, PREFETCHI and AMX-COMPLEX in- struction set support. diamondrapids Intel Diamond Rapids CPU with 64-bit extensions, MOVBE, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, CX16, SAHF, FXSR, AVX, XSAVE, PCLMUL, FSGSBASE, RDRND, F16C, AVX2, BMI, BMI2, LZCNT, FMA, MOVBE, HLE, RDSEED, ADCX, PREFETCHW, AES, CLFLUSHOPT, XSAVEC, XSAVES, SGX, AVX512F, AVX512VL, AVX512BW, AVX512DQ, AVX512CD, PKU, AVX512VBMI, AVX512IFMA, SHA, AVX512VNNI, GFNI, VAES, AVX512VBMI2, VPCLMULQDQ, AVX512BITALG, RDPID, AVX512VPOPCNTDQ, PCONFIG, WB- NOINVD, CLWB, MOVDIRI, MOVDIR64B, ENQCMD, CLDEMOTE, PTWRITE, WAIT- PKG, SERIALIZE, TSXLDTRK, UINTR, AMX-BF16, AMX-TILE, AMX-INT8, AVX-VNNI, AVX512FP16, AVX512BF16, AMX-FP16, PREFETCHI, AMX-COMPLEX, AVX10.1-512, AVX-IFMA, AVX-NE-CONVERT, AVX-VNNI-INT16, AVX-VNNI-INT8, CMPccXADD, SHA512, SM3, SM4, AVX10.2-512, APX_F, AMX-AVX512, AMX-FP8, AMX-TF32, MOVRS and AMX-MOVRS instruction set support. bonnell atomIntel Bonnell CPU with 64-bit extensions, MOVBE, MMX, SSE, SSE2, SSE3, SSSE3 and CX16 instruction set support. silvermont slm Intel Silvermont CPU with 64-bit extensions, MOVBE, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, CX16, SAHF, FXSR, PCLMUL, PREFETCHW and RDRND instruction set support. goldmont Intel Goldmont CPU with 64-bit extensions, MOVBE, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, CX16, SAHF, FXSR, PCLMUL, PREFETCHW, RDRND, AES, SHA, RDSEED, XSAVE, XSAVEC, XSAVES, XSAVEOPT, CLFLUSHOPT and FSGSBASE instruction set support. goldmont-plus Intel Goldmont Plus CPU with 64-bit extensions, MOVBE, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, CX16, SAHF, FXSR, PCLMUL, PREFETCHW, RDRND, AES, SHA, RDSEED, XSAVE, XSAVEC, XSAVES, XSAVEOPT, CLFLUSHOPT, FSGSBASE, PTWRITE, RDPID and SGX instruction set support. tremont Intel Tremont CPU with 64-bit extensions, MOVBE, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, CX16, SAHF, FXSR, PCLMUL, PREFETCHW, RDRND, AES, SHA, RDSEED, XSAVE, XSAVEC, XSAVES, XSAVEOPT, CLFLUSHOPT, FSGSBASE, PTWRITE, RDPID, SGX, CLWB, GFNI-SSE, MOVDIRI, MOVDIR64B, CLDEMOTE and WAITPKG instruction set support. sierraforest Intel Sierra Forest CPU with 64-bit extensions, MOVBE, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, CX16, AES, PREFETCHW, PCLMUL, RDRND, XSAVE, XSAVEC, XSAVES, XSAVEOPT, FSGSBASE, PTWRITE, RDPID, SGX, GFNI-SSE, CLWB, MOVDIRI, MOVDIR64B, CLDEMOTE, WAITPKG, ADCX, AVX, AVX2, BMI, BMI2, F16C, FMA, LZCNT, PCONFIG, PKU, VAES, VPCLMULQDQ, SERIALIZE, HRESET, KL, WIDEKL, AVX-VNNI, AVXIFMA, AVXVNNIINT8, AVXNECONVERT, CMPCCXADD, ENQCMD and UINTR instruction set support. grandridge Intel Grand Ridge CPU with 64-bit extensions, MOVBE, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, CX16, AES, PREFETCHW, PCLMUL, RDRND, XSAVE, XSAVEC, XSAVES, XSAVEOPT, FSGSBASE, PTWRITE, RDPID, SGX, GFNI-SSE, CLWB, MOVDIRI, MOVDIR64B, CLDEMOTE, WAITPKG, ADCX, AVX, AVX2, BMI, BMI2, F16C, FMA, LZCNT, PCONFIG, PKU, VAES, VPCLMULQDQ, SERIALIZE, HRESET, KL, WIDEKL, AVX-VNNI, AVXIFMA, AVXVNNIINT8, AVXNECONVERT, CMPCCXADD, ENQCMD and UINTR instruction set support. clearwaterforest Intel Clearwater Forest CPU with 64-bit extensions, MOVBE, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, CX16, AES, PREFETCHW, PCLMUL, RDRND, XSAVE, XSAVEC, XSAVES, XSAVEOPT, FSGS- BASE, PTWRITE, RDPID, SGX, GFNI-SSE, CLWB, MOVDIRI, MOVDIR64B, CLDEMOTE, WAITPKG, ADCX, AVX, AVX2, BMI, BMI2, F16C, FMA, LZCNT, PCONFIG, PKU, VAES, VPCLMULQDQ, SERIALIZE, HRESET, AVX-VNNI, EN- QCMD, UINTR, AVXIFMA, AVXVNNIINT8, AVXNECONVERT, CMPCCXADD, AVXVN- NIINT16, SHA512, SM3, SM4, USER_MSR and PREFETCHI instruction set support. k6 AMD K6 CPU with MMX instruction set support. k6-2 k6-3Improved versions of AMD K6 CPU with MMX and 3DNow! instruction set support. athlon athlon-tbird AMD Athlon CPU with MMX, 3dNOW!, enhanced 3DNow! and SSE prefetch instructions support. athlon-4 athlon-xp athlon-mp Improved AMD Athlon CPU with MMX, 3DNow!, enhanced 3DNow! and full SSE instruction set support. k8 opteron athlon64 athlon-fx Processors based on the AMD K8 core with x86-64 instruction set support, including the AMD Opteron, Athlon 64, and Athlon 64 FX processors. (This supersets MMX, SSE, SSE2, 3DNow!, enhanced 3DNow! and 64-bit instruction set extensions.) k8-sse3 opteron-sse3 athlon64-sse3 Improved versions of AMD K8 cores with SSE3 instruction set sup- port. amdfam10 barcelona CPUs based on AMD Family 10h cores with x86-64 instruction set sup- port. (This supersets CX16, MMX, SSE, SSE2, SSE3, SSE4A, 3DNow!, enhanced 3DNow!, ABM and 64-bit instruction set extensions.) bdver1 CPUs based on AMD Family 15h cores with x86-64 instruction set sup- port. (This supersets FMA4, AVX, XOP, LWP, AES, PCLMUL, CX16, MMX, SSE, SSE2, SSE3, SSE4A, SSSE3, SSE4.1, SSE4.2, ABM and 64-bit in- struction set extensions.) bdver2 AMD Family 15h core based CPUs with x86-64 instruction set support. (This supersets BMI, TBM, F16C, FMA, FMA4, AVX, XOP, LWP, AES, PCLMUL, CX16, MMX, SSE, SSE2, SSE3, SSE4A, SSSE3, SSE4.1, SSE4.2, ABM and 64-bit instruction set extensions.) bdver3 AMD Family 15h core based CPUs with x86-64 instruction set support. (This supersets BMI, TBM, F16C, FMA, FMA4, FSGSBASE, AVX, XOP, LWP, AES, PCLMUL, CX16, MMX, SSE, SSE2, SSE3, SSE4A, SSSE3, SSE4.1, SSE4.2, ABM and 64-bit instruction set extensions.) bdver4 AMD Family 15h core based CPUs with x86-64 instruction set support. (This supersets BMI, BMI2, TBM, F16C, FMA, FMA4, FSGSBASE, AVX, AVX2, XOP, LWP, AES, PCLMUL, CX16, MOVBE, MMX, SSE, SSE2, SSE3, SSE4A, SSSE3, SSE4.1, SSE4.2, ABM and 64-bit instruction set exten- sions.) znver1 AMD Family 17h core based CPUs with x86-64 instruction set support. (This supersets BMI, BMI2, F16C, FMA, FSGSBASE, AVX, AVX2, ADCX, RDSEED, MWAITX, SHA, CLZERO, AES, PCLMUL, CX16, MOVBE, MMX, SSE, SSE2, SSE3, SSE4A, SSSE3, SSE4.1, SSE4.2, ABM, XSAVEC, XSAVES, CLFLUSHOPT, POPCNT, and 64-bit instruction set extensions.) znver2 AMD Family 17h core based CPUs with x86-64 instruction set support. (This supersets BMI, BMI2, CLWB, F16C, FMA, FSGSBASE, AVX, AVX2, ADCX, RDSEED, MWAITX, SHA, CLZERO, AES, PCLMUL, CX16, MOVBE, MMX, SSE, SSE2, SSE3, SSE4A, SSSE3, SSE4.1, SSE4.2, ABM, XSAVEC, XSAVES, CLFLUSHOPT, POPCNT, RDPID, WBNOINVD, and 64-bit instruction set ex- tensions.) znver3 AMD Family 19h core based CPUs with x86-64 instruction set support. (This supersets BMI, BMI2, CLWB, F16C, FMA, FSGSBASE, AVX, AVX2, ADCX, RDSEED, MWAITX, SHA, CLZERO, AES, PCLMUL, CX16, MOVBE, MMX, SSE, SSE2, SSE3, SSE4A, SSSE3, SSE4.1, SSE4.2, ABM, XSAVEC, XSAVES, CLFLUSHOPT, POPCNT, RDPID, WBNOINVD, PKU, VPCLMULQDQ, VAES, and 64-bit instruction set extensions.) znver4 AMD Family 19h core based CPUs with x86-64 instruction set support. (This supersets BMI, BMI2, CLWB, F16C, FMA, FSGSBASE, AVX, AVX2, ADCX, RDSEED, MWAITX, SHA, CLZERO, AES, PCLMUL, CX16, MOVBE, MMX, SSE, SSE2, SSE3, SSE4A, SSSE3, SSE4.1, SSE4.2, ABM, XSAVEC, XSAVES, CLFLUSHOPT, POPCNT, RDPID, WBNOINVD, PKU, VPCLMULQDQ, VAES, AVX512F, AVX512DQ, AVX512IFMA, AVX512CD, AVX512BW, AVX512VL, AVX512BF16, AVX512VBMI, AVX512VBMI2, AVX512VNNI, AVX512BITALG, AVX512VPOPCNTDQ, GFNI and 64-bit instruction set extensions.) znver5 AMD Family 1ah core based CPUs with x86-64 instruction set support. (This supersets BMI, BMI2, CLWB, F16C, FMA, FSGSBASE, AVX, AVX2, ADCX, RDSEED, MWAITX, SHA, CLZERO, AES, PCLMUL, CX16, MOVBE, MMX, SSE, SSE2, SSE3, SSE4A, SSSE3, SSE4.1, SSE4.2, ABM, XSAVEC, XSAVES, CLFLUSHOPT, POPCNT, RDPID, WBNOINVD, PKU, VPCLMULQDQ, VAES, AVX512F, AVX512DQ, AVX512IFMA, AVX512CD, AVX512BW, AVX512VL, AVX512BF16, AVX512VBMI, AVX512VBMI2, AVX512VNNI, AVX512BITALG, AVX512VPOPCNTDQ, GFNI, AVXVNNI, MOVDIRI, MOVDIR64B, AVX512VP2INTER- SECT, PREFETCHI and 64-bit instruction set extensions.) znver6 AMD Family 1ah core based CPUs with x86-64 instruction set support. (This supersets BMI, BMI2, CLWB, F16C, FMA, FSGSBASE, AVX, AVX2, ADCX, RDSEED, MWAITX, SHA, CLZERO, AES, PCLMUL, CX16, MOVBE, MMX, SSE, SSE2, SSE3, SSE4A, SSSE3, SSE4.1, SSE4.2, ABM, XSAVEC, XSAVES, CLFLUSHOPT, POPCNT, RDPID, WBNOINVD, PKU, VPCLMULQDQ, VAES, AVX512F, AVX512DQ, AVX512IFMA, AVX512CD, AVX512BW, AVX512VL, AVX512BF16, AVX512VBMI, AVX512VBMI2, AVX512VNNI, AVX512BITALG, AVX512VPOPCNTDQ, GFNI, AVXVNNI, MOVDIRI, MOVDIR64B, AVX512VP2INTER- SECT, PREFETCHI, AVXVNNIINT8, AVXIFMA, AVX512FP16, AVXNECONVERT, AVX512BMM and 64-bit instruction set extensions.) btver1 CPUs based on AMD Family 14h cores with x86-64 instruction set sup- port. (This supersets MMX, SSE, SSE2, SSE3, SSSE3, SSE4A, CX16, ABM and 64-bit instruction set extensions.) btver2 CPUs based on AMD Family 16h cores with x86-64 instruction set sup- port. This includes MOVBE, F16C, BMI, AVX, PCLMUL, AES, SSE4.2, SSE4.1, CX16, ABM, SSE4A, SSSE3, SSE3, SSE2, SSE, MMX and 64-bit instruction set extensions. winchip-c6 IDT WinChip C6 CPU, dealt in same way as i486 with additional MMX instruction set support. winchip2 IDT WinChip 2 CPU, dealt in same way as i486 with additional MMX and 3DNow! instruction set support. c3 VIA C3 CPU with MMX and 3DNow! instruction set support. (No sched- uling is implemented for this chip.) c3-2VIA C3-2 (Nehemiah/C5XL) CPU with MMX and SSE instruction set sup- port. (No scheduling is implemented for this chip.) c7 VIA C7 (Esther) CPU with MMX, SSE, SSE2 and SSE3 instruction set support. (No scheduling is implemented for this chip.) samuel-2 VIA Eden Samuel 2 CPU with MMX and 3DNow! instruction set support. (No scheduling is implemented for this chip.) nehemiah VIA Eden Nehemiah CPU with MMX and SSE instruction set support. (No scheduling is implemented for this chip.) esther VIA Eden Esther CPU with MMX, SSE, SSE2 and SSE3 instruction set support. (No scheduling is implemented for this chip.) eden-x2 VIA Eden X2 CPU with x86-64, MMX, SSE, SSE2 and SSE3 instruction set support. (No scheduling is implemented for this chip.) eden-x4 VIA Eden X4 CPU with x86-64, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX and AVX2 instruction set support. (No scheduling is implemented for this chip.) nanoGeneric VIA Nano CPU with x86-64, MMX, SSE, SSE2, SSE3 and SSSE3 instruction set support. (No scheduling is implemented for this chip.) nano-1000 VIA Nano 1xxx CPU with x86-64, MMX, SSE, SSE2, SSE3 and SSSE3 in- struction set support. (No scheduling is implemented for this chip.) nano-2000 VIA Nano 2xxx CPU with x86-64, MMX, SSE, SSE2, SSE3 and SSSE3 in- struction set support. (No scheduling is implemented for this chip.) nano-3000 VIA Nano 3xxx CPU with x86-64, MMX, SSE, SSE2, SSE3, SSSE3 and SSE4.1 instruction set support. (No scheduling is implemented for this chip.) nano-x2 VIA Nano Dual Core CPU with x86-64, MMX, SSE, SSE2, SSE3, SSSE3 and SSE4.1 instruction set support. (No scheduling is implemented for this chip.) nano-x4 VIA Nano Quad Core CPU with x86-64, MMX, SSE, SSE2, SSE3, SSSE3 and SSE4.1 instruction set support. (No scheduling is implemented for this chip.) lujiazui ZHAOXIN lujiazui CPU with x86-64, MOVBE, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, AES, PCLMUL, RDRND, XSAVE, XSAVEOPT, FSGSBASE, CX16, ABM, BMI, BMI2, FXSR, RDSEED instruction set sup- port. While the CPUs do support AVX and F16C, these aren't enabled by "-march=lujiazui" for performance reasons. yongfeng ZHAOXIN yongfeng CPU with x86-64, MOVBE, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX, POPCNT, AES, PCLMUL, RDRND, XSAVE, XSAVEOPT, FSGSBASE, CX16, ABM, BMI, BMI2, F16C, FXSR, RDSEED, AVX2, FMA, SHA, LZCNT instruction set support. shijidadao ZHAOXIN shijidadao CPU with x86-64, MOVBE, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX, POPCNT, AES, PCLMUL, RDRND, XSAVE, XSAVEOPT, FSGSBASE, CX16, ABM, BMI, BMI2, F16C, FXSR, RDSEED, AVX2, FMA, SHA, LZCNT instruction set support. geode AMD Geode embedded processor with MMX and 3DNow! instruction set support. c86-4g-m4 HYGON c86-4g-m4 CPU with x86-64, MMX, SSE, SSE2, SSE3, SSE4A, CX16, ABM, SSSE3, SSE4.1, SSE4.2, AES, PCLMUL, AVX, AVX2, BMI, BMI2, F16C, FMA, PRFCHW, FXSR, SHA, XSAVE, XSAVEOPT, XSAVEC, FSGSBASE, RDRND, MOVBE, MWAITX, ADX, RDSEED, CLZERO, CLFLUSHOPT, XSAVES, LZCNT, POPCNT instruction set support. c86-4g-m6 HYGON c86-4g-m6 CPU with x86-64, MMX, SSE, SSE2, SSE3, SSE4A, CX16, ABM, SSSE3, SSE4.1, SSE4.2, AES, PCLMUL, AVX, AVX2, BMI, BMI2, F16C, FMA, PRFCHW, FXSR, SHA, XSAVE, XSAVEOPT, XSAVEC, FSGSBASE, RDRND, MOVBE, MWAITX, ADX, RDSEED, CLZERO, CLFLUSHOPT, XSAVES, LZCNT, POPCNT instruction set support. c86-4g-m7 HYGON c86-4g-m7 CPU with x86-64, MMX, SSE, SSE2, SSE3, SSE4A, CX16, ABM, SSSE3, SSE4.1, SSE4.2, AES, PCLMUL, AVX, AVX2, BMI, BMI2, F16C, FMA, PRFCHW, FXSR, SHA, XSAVE, XSAVEOPT, XSAVEC, FSGSBASE, RDRND, MOVBE, MWAITX, ADX, RDSEED, CLZERO, CLFLUSHOPT, XSAVES, LZCNT, POPCNT, AVX512F, AVX512DQ, AVX512IFMA, AVX512CD, AVX512BW, AVX512VL, AVX512BF16, AVX512VBMI, AVX512VBMI2, GFNI, AVX512VNNI, VAES, AVX512BITALG, AVX512VPOPCNTDQ, AVX512VP2INTERSECT, AVXVNNI, VPCLMULQDQ, WBNOINVD instruction set support. -mtune=cpu-type Tune to cpu-type everything applicable about the generated code, except for the ABI and the set of available instructions. While picking a specific cpu-type schedules things appropriately for that particular chip, the compiler does not generate any code that cannot run on the default machine type unless you use a -march=cpu-type option. For ex- ample, if GCC is configured for i686-pc-linux-gnu then -mtune=pentium4 generates code that is tuned for Pentium 4 but still runs on i686 ma- chines. The choices for cpu-type are the same as for -march. In addition, -mtune supports 2 extra choices for cpu-type: generic Produce code optimized for the most common IA32/AMD64/EM64T proces- sors. If you know the CPU on which your code will run, then you should use the corresponding -mtune or -march option instead of -mtune=generic. But, if you do not know exactly what CPU users of your application will have, then you should use this option. As new processors are deployed in the marketplace, the behavior of this option will change. Therefore, if you upgrade to a newer ver- sion of GCC, code generation controlled by this option will change to reflect the processors that are most common at the time that version of GCC is released. There is no -march=generic option because -march indicates the in- struction set the compiler can use, and there is no generic in- struction set applicable to all processors. In contrast, -mtune indicates the processor (or, in this case, collection of proces- sors) for which the code is optimized. intel Produce code optimized for the most current Intel processors, which are Haswell and Silvermont for this version of GCC. If you know the CPU on which your code will run, then you should use the corre- sponding -mtune or -march option instead of -mtune=intel. But, if you want your application performs better on both Diamond Rapids and Clearwater Forest, then you should use this option. As new Intel processors are deployed in the marketplace, the behav- ior of this option will change. Therefore, if you upgrade to a newer version of GCC, code generation controlled by this option will change to reflect the most current Intel processors at the time that version of GCC is released. There is no -march=intel option because -march indicates the in- struction set the compiler can use, and there is no common instruc- tion set applicable to all processors. In contrast, -mtune indi- cates the processor (or, in this case, collection of processors) for which the code is optimized. The following options allow more detailed control over which instruction set extensions are targeted by GCC. Each has a corresponding -mno- option to disable use of these instructions. These extensions are also available as built-in functions: see x86 Built-in Functions, for details of the functions enabled and disabled by these switches. These options enable GCC to use these extended instructions in generated code. Applications that perform run-time CPU detection must compile sepa- rate files for each supported architecture, using the appropriate flags. In particular, the file containing the CPU detection code should be com- piled without these options. To control whether 387 or SSE/AVX instructions are generated automatically for floating-point arithmetic, see -mfpmath=, below. -mmmx Support MMX built-in functions. -msse Support MMX and SSE built-in functions and code generation. -msse2 Support MMX, SSE and SSE2 built-in functions and code generation. -msse3 Support MMX, SSE, SSE2 and SSE3 built-in functions and code generation. -mssse3 Support MMX, SSE, SSE2, SSE3 and SSSE3 built-in functions and code gen- eration. -msse4.1 Support MMX, SSE, SSE2, SSE3, SSSE3 and SSE4.1 built-in functions and code generation. -msse4.2 Support MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1 and SSE4.2 built-in func- tions and code generation. -msse4 Support MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1 and SSE4.2 built-in func- tions and code generation. Note that -msse4 enables both SSE4.1 and SSE4.2 support, while -mno-sse4 turns off those features; neither form of the option affects SSE4A support, controlled separately by -msse4a. -msse4a Support MMX, SSE, SSE2, SSE3 and SSE4A built-in functions and code gen- eration. -mavx Support MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2 and AVX built-in functions and code generation. -mavx2 Support MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX and AVX2 built-in functions and code generation. -mavx512f Support MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX, AVX2 and AVX512F built-in functions and code generation. -mavx512cd Support MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX, AVX2, AVX512F and AVX512CD built-in functions and code generation. -mavx512vl Support MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX, AVX2, AVX512F and AVX512VL built-in functions and code generation. -mavx512bw Support MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX, AVX2, AVX512F and AVX512BW built-in functions and code generation. -mavx512dq Support MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX, AVX2, AVX512F and AVX512DQ built-in functions and code generation. -mavx512ifma Support MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX, AVX2, AVX512F and AVX512IFMA built-in functions and code generation. -mavx512vbmi Support MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX, AVX2, AVX512F and AVX512VBMI built-in functions and code generation. -mavx512vpopcntdq Support MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX, AVX2, AVX512F and AVX512VPOPCNTDQ built-in functions and code generation. -mavx512vp2intersect Support AVX512VP2INTERSECT built-in functions and code generation. -mavx512vnni Support AVX512VNNI built-in functions and code generation. -mavx512vbmi2 Support MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX, AVX2, AVX512F and AVX512VBMI2 built-in functions and code generation. -mavx512bf16 Support MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX, AVX2, AVX512F and AVX512BF16 built-in functions and code generation. -mavx512fp16 Support MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX, AVX2, AVX512F and AVX512-FP16 built-in functions and code generation. -mavx512bitalg Support MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX, AVX2, AVX512F and AVX512BITALG built-in functions and code generation. -mavx512bmm Support AVX512BMM built-in functions and code generation. -mavxvnni Support MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX, AVX2, and AVXVNNI built-in functions and code generation. -mavxifma Support MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX, AVX2, and AVXIFMA built-in functions and code generation. -mavxvnniint8 Support MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX, AVX2 and AVXVNNIINT8 built-in functions and code generation. -mavxneconvert Support MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX, AVX2, and AVXNECONVERT build-in functions and code generation. -mavxvnniint16 Support MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX, AVX2 and AVXVNNIINT16 built-in functions and code generation. -mavx10.1 Support MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX, AVX2, and AVX10.1 built-in functions and code generation. -mavx10.2 Support MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX, AVX2, AVX10.1 and AVX10.2 built-in functions and code generation. -msha Support SHA1 and SHA256 built-in functions and code generation. -maes Support AES built-in functions and code generation. -mpclmul Support PCLMUL built-in functions and code generation. -mclflushopt Support CLFLUSHOPT instructions. -mclwb Support CLWB instruction. -mfsgsbase Support FSGSBASE built-in functions and code generation. -mptwrite Support PTWRITE built-in functions and code generation. -mrdrnd Support RDRND built-in functions and code generation. -mf16c Support F16C built-in functions and code generation. -mfma Support MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX and FMA built-in functions and code generation. -mfma4 Support FMA4 built-in functions and code generation. -mpconfig Support PCONFIG built-in functions and code generation. -mwbnoinvd Support WBNOINVD built-in functions and code generation. -mprfchw Support PREFETCHW instruction. -mrdpid Support RDPID built-in functions and code generation. -mrdseed Support RDSEED instruction. -msgx Support SGX built-in functions and code generation. -mxop Support XOP built-in functions and code generation. -mlwp Support LWP built-in functions and code generation. -m3dnow Support 3DNow! built-in functions. -m3dnowa Support Athlon 3Dnow! built-in functions. -mpopcnt Support code generation of popcnt instruction. -mabm Support code generation of Advanced Bit Manipulation (ABM) instruc- tions. -madx Support flag-preserving add-carry instructions. -mbmi Support BMI built-in functions and code generation. -mbmi2 Support BMI2 built-in functions and code generation. -mlzcnt Support LZCNT built-in function and code generation. -mfxsr Support FXSAVE and FXRSTOR instructions. -mxsave Support XSAVE and XRSTOR instructions. -mxsaveopt Support XSAVEOPT instruction. -mxsavec Support XSAVEC instructions. -mxsaves Support XSAVES and XRSTORS instructions. -mrtm Support RTM built-in functions and code generation. -mhle Support Hardware Lock Elision prefixes. -mtbm Support TBM built-in functions and code generation. -mmwaitx Support MWAITX and MONITORX built-in functions and code generation. -mclzero Support CLZERO built-in functions and code generation. -mpku Support PKU built-in functions and code generation. -mgfni Support GFNI built-in functions and code generation. -mvaes Support VAES built-in functions and code generation. -mwaitpkg Support WAITPKG built-in functions and code generation. -mvpclmulqdq Support VPCLMULQDQ built-in functions and code generation. -mmovdiri Support MOVDIRI built-in functions and code generation. -mmovdir64b Support MOVDIR64B built-in functions and code generation. -menqcmd Support ENQCMD built-in functions and code generation. -muintr Support UINTR built-in functions and code generation. -mtsxldtrk Support TSXLDTRK built-in functions and code generation. -mcldemote Support CLDEMOTE built-in functions and code generation. -mserialize Support SERIALIZE built-in functions and code generation. -mamx-tile Support AMX-TILE built-in functions and code generation. -mamx-int8 Support AMX-INT8 built-in functions and code generation. -mamx-bf16 Support AMX-BF16 built-in functions and code generation. -mhreset Support HRESET built-in functions and code generation. -mklSupport KL built-in functions and code generation. -mwidekl Support WIDEKL built-in functions and code generation. -mcmpccxadd Support MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX, AVX2, and CM- PCCXADD build-in functions and code generation. -mamx-fp16 Support AMX-FP16 built-in functions and code generation. -mprefetchi Support PREFETCHI built-in functions and code generation. -mraoint Support RAOINT built-in functions and code generation. -mamx-complex Support AMX-COMPLEX built-in functions and code generation. -msm3 Support MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX and SM3 built-in functions and code generation. -msm4 Support MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX and SM4 built-in functions and code generation. -msha512 Support MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX and SHA512 built-in functions and code generation. -mapxf Support code generation for APX features, including EGPR, PUSH2POP2, NDD, PPX, NF, CCMP and ZU. -musermsr Support USER_MSR built-in functions and code generation. -mamx-avx512 Support MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX, AVX2, AVX10.1, AVX10.2 and AMX-AVX512 built-in functions and code generation. -mamx-tf32 Support AMX-TF32 built-in functions and code generation. -mamx-fp8 Support AMX-FP8 built-in functions and code generation. -mmovrs Support MOVRS built-in functions and code generation. -mamx-movrs Support AMX-MOVRS built-in functions and code generation. These additional options are available for the x86 processor family. -mfpmath=unit Generate floating-point arithmetic for selected unit unit. The choices for unit are: 387 Use the standard 387 floating-point coprocessor present on the ma- jority of chips and emulated otherwise. Code compiled with this option runs almost everywhere. The temporary results are computed in 80-bit precision instead of the precision specified by the type, resulting in slightly different results compared to most of other chips. See -ffloat-store for more detailed description. This is the default choice for non-Darwin x86-32 targets. sse Use scalar floating-point instructions present in the SSE instruc- tion set. This instruction set is supported by Pentium III and newer chips, and in the AMD line by Athlon-4, Athlon XP and Athlon MP chips. The earlier version of the SSE instruction set supports only single-precision arithmetic, thus the double and extended-pre- cision arithmetic are still done using 387. A later version, present only in Pentium 4 and AMD x86-64 chips, supports dou- ble-precision arithmetic too. For the x86-32 compiler, you must use -march=cpu-type, -msse or -msse2 switches to enable SSE extensions and make this option ef- fective. For the x86-64 compiler, these extensions are enabled by default. The resulting code should be considerably faster in the majority of cases and avoid the numerical instability problems of 387 code, but may break some existing code that expects temporaries to be 80 bits. This is the default choice for the x86-64 compiler, Darwin x86-32 targets, and the default choice for x86-32 targets with the SSE2 instruction set when -ffast-math is enabled. GCC depresses SSE instructions when -mavx (or another option en- abling AVX extensions) is used. Instead, it generates new AVX in- structions or AVX equivalents for all SSE instructions when needed. sse,387 sse+387 bothAttempt to utilize both instruction sets at once. This effectively doubles the amount of available registers, and on chips with sepa- rate execution units for 387 and SSE the execution resources too. Use this option with care, as it is still experimental, because the GCC register allocator does not model separate functional units well, resulting in unstable performance. -mieee-fp -mno-ieee-fp Control whether or not the compiler uses IEEE floating-point compar- isons. These correctly handle the case where the result of a compari- son is unordered. -m80387 -mhard-float Generate output containing 80387 instructions for floating point. -mno-80387 -msoft-float Generate output containing library calls for floating point. Warning: the requisite libraries are not part of GCC. Normally the fa- cilities of the machine's usual C compiler are used, but this cannot be done directly in cross-compilation. You must make your own arrange- ments to provide suitable library functions for cross-compilation. On machines where a function returns floating-point results in the 80387 register stack, some floating-point opcodes may be emitted even if -msoft-float is used. -mno-fp-ret-in-387 Do not use the FPU registers for return values of functions. The usual calling convention has functions return values of types "float" and "double" in an FPU register, even if there is no FPU. The idea is that the operating system should emulate an FPU. The option -mno-fp-ret-in-387 causes such values to be returned in or- dinary CPU registers instead. -mno-fancy-math-387 Some 387 emulators do not support the "sin", "cos" and "sqrt" instruc- tions for the 387. Specify this option to avoid generating those in- structions. This option is overridden when -march indicates that the target CPU always has an FPU and so the instruction does not need emu- lation. These instructions are not generated unless you also use the -funsafe-math-optimizations switch. -malign-double -mno-align-double Control whether GCC aligns "double", "long double", and "long long" variables on a two-word boundary or a one-word boundary. Aligning "double" variables on a two-word boundary produces code that runs some- what faster on a Pentium at the expense of more memory. On x86-64, -malign-double is enabled by default. Warning: if you use the -malign-double switch, structures containing the above types are aligned differently than the published application binary interface specifications for the x86-32 and are not binary com- patible with structures in code compiled without that switch. -m96bit-long-double -m128bit-long-double These switches control the size of "long double" type. The x86-32 ap- plication binary interface specifies the size to be 96 bits, so -m96bit-long-double is the default in 32-bit mode. Modern architectures (Pentium and newer) prefer "long double" to be aligned to an 8- or 16-byte boundary. In arrays or structures conform- ing to the ABI, this is not possible. So specifying -m128bit-long-dou- ble aligns "long double" to a 16-byte boundary by padding the "long double" with an additional 32-bit zero. In the x86-64 compiler, -m128bit-long-double is the default choice as its ABI specifies that "long double" is aligned on 16-byte boundary. Notice that neither of these options enable any extra precision over the x87 standard of 80 bits for a "long double". Warning: if you override the default value for your target ABI, this changes the size of structures and arrays containing "long double" variables, as well as modifying the function calling convention for functions taking "long double". Hence they are not binary-compatible with code compiled without that switch. -mlong-double-64 -mlong-double-80 -mlong-double-128 These switches control the size of "long double" type. A size of 64 bits makes the "long double" type equivalent to the "double" type. This is the default for 32-bit Bionic C library. A size of 128 bits makes the "long double" type equivalent to the "__float128" type. This is the default for 64-bit Bionic C library. Warning: if you override the default value for your target ABI, this changes the size of structures and arrays containing "long double" variables, as well as modifying the function calling convention for functions taking "long double". Hence they are not binary-compatible with code compiled without that switch. -malign-data=type Control how GCC aligns variables. Supported values for type are compat uses increased alignment value compatible uses GCC 4.8 and earlier, abi uses alignment value as specified by the psABI, and cacheline uses in- creased alignment value to match the cache line size. compat is the default. -mlarge-data-threshold=threshold When -mcmodel=medium or -mcmodel=large is specified, data objects larger than threshold are placed in large data sections. The default is 65535. -mrtd Use a different function-calling convention, in which functions that take a fixed number of arguments return with the "ret num" instruction, which pops their arguments while returning. This saves one instruction in the caller since there is no need to pop the arguments there. You can specify that an individual function is called with this calling sequence with the function attribute "stdcall". You can also override the -mrtd option by using the function attribute "cdecl". Warning: this calling convention is incompatible with the one normally used on Unix, so you cannot use it if you need to call libraries com- piled with the Unix compiler. Also, you must provide function prototypes for all functions that take variable numbers of arguments (including "printf"); otherwise incorrect code is generated for calls to those functions. In addition, seriously incorrect code results if you call a function with too many arguments. (Normally, extra arguments are harmlessly ig- nored.) -mregparm=num Control how many registers are used to pass integer arguments. By de- fault, 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 "regparm". Warning: if you use this switch, and num is nonzero, then you must build all modules with the same value, including any libraries. This includes the system libraries and startup modules. -msseregparm Use SSE register passing conventions for float and double arguments and return values. You can control this behavior for a specific function by using the function attribute "sseregparm". Warning: if you use this switch then you must build all modules with the same value, including any libraries. This includes the system li- braries and startup modules. -mvect8-ret-in-mem Return 8-byte vectors in memory instead of MMX registers. This is the default on VxWorks to match the ABI of the Sun Studio compilers until version 12. Only use this option if you need to remain compatible with existing code produced by those previous compiler versions or older versions of GCC. -mpc32 -mpc64 -mpc80 Set 80387 floating-point precision to 32, 64 or 80 bits. When -mpc32 is specified, the significands of results of floating-point operations are rounded to 24 bits (single precision); -mpc64 rounds the signifi- cands of results of floating-point operations to 53 bits (double preci- sion) and -mpc80 rounds the significands of results of floating-point operations to 64 bits (extended double precision), which is the de- fault. When this option is used, floating-point operations in higher precisions are not available to the programmer without setting the FPU control word explicitly. Setting the rounding of floating-point operations to less than the de- fault 80 bits can speed some programs by 2% or more. Note that some mathematical libraries assume that extended-precision (80-bit) float- ing-point operations are enabled by default; routines in such libraries could suffer significant loss of accuracy, typically through so-called "catastrophic cancellation", when this option is used to set the preci- sion to less than extended precision. -mdaz-ftz -mno-daz-ftz The flush-to-zero (FTZ) and denormals-are-zero (DAZ) flags in the MXCSR register are used to control floating-point calculations. The -Ofast, -ffast-math, or -funsafe-math-optimizations options normally link in startup code that sets these flags except when building a shared li- brary (-shared). You can use the -mdaz-ftz and -mno-daz-ftz options to explicitly enable or disable setting these flags, regardless of other options passed to GCC. -mstackrealign Realign the stack at entry. On the x86, the -mstackrealign option gen- erates an alternate prologue and epilogue that realigns the run-time stack if necessary. This supports mixing legacy codes that keep 4-byte stack alignment with modern codes that keep 16-byte stack alignment for SSE compatibility. See also the attribute "force_align_arg_pointer", applicable to individual functions. -mstack-arg-probe Emit stack probing code in the function prologue. -mpreferred-stack-boundary=num Attempt to keep the stack boundary aligned to a 2 raised to num byte boundary. If -mpreferred-stack-boundary is not specified, the default is 4 (16 bytes or 128 bits). Warning: When generating code for the x86-64 architecture with SSE ex- tensions disabled, -mpreferred-stack-boundary=3 can be used to keep the stack boundary aligned to 8 byte boundary. Since x86-64 ABI require 16 byte stack alignment, this is ABI incompatible and intended to be used in controlled environment where stack space is important limitation. This option leads to wrong code when functions compiled with 16 byte stack alignment (such as functions from a standard library) are called with misaligned stack. In this case, SSE instructions may lead to mis- aligned memory access traps. In addition, variable arguments are han- dled incorrectly for 16 byte aligned objects (including x87 long double and __int128), leading to wrong results. You must build all modules with -mpreferred-stack-boundary=3, including any libraries. This in- cludes the system libraries and startup modules. -mincoming-stack-boundary=num Assume the incoming stack is aligned to a 2 raised to num byte bound- ary. If -mincoming-stack-boundary is not specified, the one specified by -mpreferred-stack-boundary is used. On Pentium and Pentium Pro, "double" and "long double" values should be aligned to an 8-byte boundary (see -malign-double) or suffer signifi- cant run time performance penalties. On Pentium III, the Streaming SIMD Extension (SSE) data type "__m128" may not work properly if it is not 16-byte aligned. 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 pre- ferred stack boundary from a function compiled with a lower preferred stack boundary most likely misaligns the stack. It is recommended that libraries that use callbacks always use the default setting. This extra alignment does consume extra stack space, and generally in- creases 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 -mpreferred-stack-boundary=2. -mdump-tune-features This option instructs GCC to dump the names of the x86 performance tun- ing features and default settings. The names can be used in -mtune-ctrl=feature-list. -mtune-ctrl=feature-list This option is used to do fine-grain control of x86 code generation features. feature-list is a comma-separated list of feature names. See also -mdump-tune-features. When specified, the feature is turned on if it is not preceded with ^; otherwise, it is turned off. -mtune-ctrl=feature-list is intended to be used by GCC developers. Us- ing it may lead to code paths not covered by testing and can poten- tially result in compiler ICEs or runtime errors. -mno-default This option instructs GCC to turn off all tunable features. See also -mtune-ctrl=feature-list and -mdump-tune-features. -mcld This option instructs GCC to emit a "cld" instruction in the prologue of functions that use string instructions. String instructions depend on the DF flag to select between autoincrement or autodecrement mode. While the ABI specifies the DF flag to be cleared on function entry, some operating systems violate this specification by not clearing the DF flag in their exception dispatchers. The exception handler can be invoked with the DF flag set, which leads to wrong direction mode when string instructions are used. This option can be enabled by default on 32-bit x86 targets by configuring GCC with the --enable-cld configure option. Generation of "cld" instructions can be suppressed with the -mno-cld compiler option in this case. -mvzeroupper This option instructs GCC to emit a "vzeroupper" instruction before a transfer of control flow out of the function to minimize the AVX to SSE transition penalty as well as remove unnecessary "zeroupper" intrin- sics. -mstv -mno-stv Enable/disable Scalar to Vectorization pass transforming 64-bit integer computation into vector ones. This optimization is restricted to -O2 and higher. -mprefer-avx128 This option instructs GCC to use 128-bit AVX instructions instead of 256-bit AVX instructions in the auto-vectorizer. -mprefer-vector-width=opt This option instructs GCC to use opt-bit vector width in instructions instead of default on the selected platform. -mpartial-vector-fp-math -mno-partial-vector-fp-math This option enables GCC to generate floating-point operations that might affect the set of floating-point status flags on partial vectors, where vector elements reside in the low part of the 128-bit SSE regis- ter. Unless -fno-trapping-math is specified, the compiler guarantees correct behavior by sanitizing all input operands to have zeroes in the unused upper part of the vector register. Note that by using built-in functions or inline assembly with partial vector arguments, NaNs, de- normal or invalid values can leak into the upper part of the vector, causing possible performance issues when -fno-trapping-math is in ef- fect. These issues can be mitigated by manually sanitizing the upper part of the partial vector argument register or by using -mdaz-ftz to set denormals-are-zero (DAZ) flag in the MXCSR register. This option is enabled by default. -mmove-max=bits This option instructs GCC to set the maximum number of bits can be moved from memory to memory efficiently to bits. The valid bits are 128, 256 and 512. -mstore-max=bits This option instructs GCC to set the maximum number of bits can be stored to memory efficiently to bits. The valid bits are 128, 256 and 512. noneNo extra limitations applied to GCC other than defined by the se- lected platform. 128 Prefer 128-bit vector width for instructions. 256 Prefer 256-bit vector width for instructions. 512 Prefer 512-bit vector width for instructions. -mnoreturn-no-callee-saved-registers This option optimizes functions with "noreturn" attribute or "_Nore- turn" specifier by not saving in the function prologue callee-saved registers which are used in the function (except for the "BP" regis- ter). This option can interfere with debugging of the caller of the "noreturn" function or any function further up in the call stack, so it is not enabled by default. -mcx16 This option enables GCC to generate "CMPXCHG16B" instructions in 64-bit code to implement compare-and-exchange operations on 16-byte aligned 128-bit objects. This is useful for atomic updates of data structures exceeding one machine word in size. The compiler uses this instruction to implement __sync Builtins. However, for __atomic Builtins operating on 128-bit integers, a library call is always used. -msahf This option enables generation of "SAHF" instructions in 64-bit code. Early Intel Pentium 4 CPUs with Intel 64 support, prior to the intro- duction of Pentium 4 G1 step in December 2005, lacked the "LAHF" and "SAHF" instructions which are supported by AMD64. These are load and store instructions, respectively, for certain status flags. In 64-bit mode, the "SAHF" instruction is used to optimize "fmod", "drem", and "remainder" built-in functions; see Other Builtins for details. -mmovbe This option enables use of the "movbe" instruction to optimize byte swapping of four and eight byte entities. -mshstk The -mshstk option enables shadow stack built-in functions from x86 Control-flow Enforcement Technology (CET). -mcrc32 This option enables built-in functions "__builtin_ia32_crc32qi", "__builtin_ia32_crc32hi", "__builtin_ia32_crc32si" and "__builtin_ia32_crc32di" to generate the "crc32" machine instruction. -mmwait This option enables built-in functions "__builtin_ia32_monitor", and "__builtin_ia32_mwait" to generate the "monitor" and "mwait" machine instructions. -mrecip This option enables use of "RCPSS" and "RSQRTSS" instructions (and their vectorized variants "RCPPS" and "RSQRTPS") with an additional Newton-Raphson step to increase precision instead of "DIVSS" and "SQRTSS" (and their vectorized variants) for single-precision float- ing-point arguments. These instructions are generated only when -fun- safe-math-optimizations is enabled together with -ffinite-math-only and -fno-trapping-math. Note that while the throughput of the sequence is higher than the throughput of the non-reciprocal instruction, the pre- cision of the sequence can be decreased by up to 2 ulp (i.e. the in- verse of 1.0 equals 0.99999994). Note that GCC implements "1.0f/sqrtf(x)" in terms of "RSQRTSS" (or "RSQRTPS") already with -ffast-math (or the above option combination), and doesn't need -mrecip. Also note that GCC emits the above sequence with additional New- ton-Raphson step for vectorized single-float division and vectorized sqrtf(x) already with -ffast-math (or the above option combination), and doesn't need -mrecip. -mrecip=opt This option controls which reciprocal estimate instructions may be used. opt is a comma-separated list of options, which may be preceded by a ! to invert the option: all Enable all estimate instructions. default Enable the default instructions, equivalent to -mrecip. noneDisable all estimate instructions, equivalent to -mno-recip. div Enable the approximation for scalar division. vec-div Enable the approximation for vectorized division. sqrtEnable the approximation for scalar square root. vec-sqrt Enable the approximation for vectorized square root. So, for example, -mrecip=all,!sqrt enables all of the reciprocal ap- proximations, except for square root. -mveclibabi=type Specifies the ABI type to use for vectorizing intrinsics using an ex- ternal library. Supported values for type are svml for the Intel short vector math library, aocl for the math library (LibM) from AMD Optimiz- ing CPU Libraries (AOCL) and acml for the end-of-life AMD core math li- brary (to which AOCL-LibM is the successor). To use this option, both -ftree-vectorize and -funsafe-math-optimizations have to be enabled, and an SVML or ACML ABI-compatible library must be specified at link time. GCC currently emits calls to "vmldExp2", "vmldLn2", "vmldLog102", "vmldPow2", "vmldTanh2", "vmldTan2", "vmldAtan2", "vmldAtanh2", "vmld- Cbrt2", "vmldSinh2", "vmldSin2", "vmldAsinh2", "vmldAsin2", "vmld- Cosh2", "vmldCos2", "vmldAcosh2", "vmldAcos2", "vmlsExp4", "vmlsLn4", "vmlsLog104", "vmlsPow4", "vmlsTanh4", "vmlsTan4", "vmlsAtan4", "vmlsA- tanh4", "vmlsCbrt4", "vmlsSinh4", "vmlsSin4", "vmlsAsinh4", "vml- sAsin4", "vmlsCosh4", "vmlsCos4", "vmlsAcosh4" and "vmlsAcos4" for cor- responding function type when -mveclibabi=svml is used, "amd_vrs4_acosf", "amd_vrs16_acosf", "amd_vrd8_asin", "amd_vrs4_asinf", "amd_vrs8_asinf", "amd_vrs16_asinf", "amd_vrd2_atan", "amd_vrd8_atan", "amd_vrs4_atanf", "amd_vrs8_atanf", "amd_vrs16_atanf", "amd_vrd2_cos", "amd_vrd4_cos", "amd_vrd8_cos", "amd_vrs4_cosf", "amd_vrs8_cosf", "amd_vrs16_cosf", "amd_vrs4_coshf", "amd_vrs8_coshf", "amd_vrd2_erf", "amd_vrd4_erf", "amd_vrd8_erf", "amd_vrs4_erff", "amd_vrs8_erff", "amd_vrs16_erff", "amd_vrd2_exp", "amd_vrd4_exp", "amd_vrd8_exp", "amd_vrs4_expf", "amd_vrs8_expf", "amd_vrs16_expf", "amd_vrd2_exp10", "amd_vrs4_exp10f", "amd_vrd2_exp2", "amd_vrd4_exp2", "amd_vrd8_exp2", "amd_vrs4_exp2f", "amd_vrs8_exp2f", "amd_vrs16_exp2f", "amd_vrs4_expm1f", "amd_vrd2_log", "amd_vrd4_log", "amd_vrd8_log", "amd_vrs4_logf", "amd_vrs8_logf", "amd_vrs16_logf", "amd_vrd2_log10", "amd_vrs4_log10f", "amd_vrs8_log10f", "amd_vrs16_log10f", "amd_vrd2_log1p", "amd_vrs4_log1pf", "amd_vrd2_log2", "amd_vrd4_log2", "amd_vrd8_log2", "amd_vrs4_log2f", "amd_vrs8_log2f", "amd_vrs16_log2f", "amd_vrd2_pow", "amd_vrd4_pow", "amd_vrd8_pow", "amd_vrs4_powf", "amd_vrs8_powf", "amd_vrs16_powf", "amd_vrd2_sin", "amd_vrd4_sin", "amd_vrd8_sin", "amd_vrs4_sinf", "amd_vrs8_sinf", "amd_vrs16_sinf", "amd_vrd2_tan", "amd_vrd4_tan", "amd_vrd8_tan", "amd_vrs16_tanf", "amd_vrs4_tanhf", "amd_vrs8_tanhf", "amd_vrs16_tanhf" for the corre- sponding function type when -mveclibabi=aocl is used, and "__vrd2_sin", "__vrd2_cos", "__vrd2_exp", "__vrd2_log", "__vrd2_log2", "__vrd2_log10", "__vrs4_sinf", "__vrs4_cosf", "__vrs4_expf", "__vrs4_logf", "__vrs4_log2f", "__vrs4_log10f" and "__vrs4_powf" for the corresponding function type when -mveclibabi=acml is used. -mabi=name Generate code for the specified calling convention. Permissible values are sysv for the ABI used on GNU/Linux and other systems, and ms for the Microsoft ABI. The default is to use the Microsoft ABI when tar- geting Microsoft Windows and the SysV ABI on all other systems. You can control this behavior for specific functions by using the function attributes "ms_abi" and "sysv_abi". -masm=dialect Output assembly instructions using selected dialect. Also affects which dialect is used for basic "asm" and extended "asm". Supported choices (in dialect order) are att or intel. The default is att. Darwin does not support intel. -mforce-indirect-call Force all calls to functions to be indirect. This is useful when using Intel Processor Trace where it generates more precise timing informa- tion for function calls. -mmanual-endbr Insert ENDBR instruction at function entry only via the "cf_check" function attribute. This is useful when used with the option -fcf-pro- tection=branch to control ENDBR insertion at the function entry. -mcet-switch By default, CET instrumentation is turned off on switch statements that use a jump table and indirect branch track is disabled. Since jump ta- bles are stored in read-only memory, this does not result in a direct loss of hardening. But if the jump table index is attacker-controlled, the indirect jump may not be constrained by CET. This option turns on CET instrumentation to enable indirect branch track for switch state- ments with jump tables which leads to the jump targets reachable via any indirect jumps. -mcall-ms2sysv-xlogues Due to differences in 64-bit ABIs, any Microsoft ABI function that calls a System V ABI function must consider RSI, RDI and XMM6-15 as clobbered. By default, the code for saving and restoring these regis- ters is emitted inline, resulting in fairly lengthy prologues and epi- logues. Using -mcall-ms2sysv-xlogues emits prologues and epilogues that use stubs in the static portion of libgcc to perform these saves and restores, thus reducing function size at the cost of a few extra instructions. -mtls-dialect=type Generate code to access thread-local storage using the gnu or gnu2 con- ventions. gnu is the conservative default; gnu2 is more efficient, but it may add compile- and run-time requirements that cannot be satisfied on all systems. -mpush-args -mno-push-args Use PUSH operations to store outgoing parameters. This method is shorter and usually equally fast as method using SUB/MOV operations and is enabled by default. In some cases disabling it may improve perfor- mance because of improved scheduling and reduced dependencies. -maccumulate-outgoing-args If enabled, the maximum amount of space required for outgoing arguments is computed in the function prologue. This is faster on most modern CPUs because of reduced dependencies, improved scheduling and reduced stack usage when the preferred stack boundary is not equal to 2. The drawback is a notable increase in code size. This switch implies -mno-push-args. -mms-bitfields -mno-ms-bitfields Enable/disable bit-field layout compatible with the native Microsoft Windows compiler. If "packed" is used on a structure, or if bit-fields are used, it may be that the Microsoft ABI lays out the structure differently than the way GCC normally does. Particularly when moving packed data between functions compiled with GCC and the native Microsoft compiler (either via function call or as data in a file), it may be necessary to access either format. This option is enabled by default for Microsoft Windows targets. This behavior can also be controlled locally by use of variable or type at- tributes. For more information, see x86 Attributes. The Microsoft structure layout algorithm is fairly simple with the ex- ception of the bit-field packing. The padding and alignment of members of structures and whether a bit-field can straddle a storage-unit boundary are determine by these rules: 1. Structure members are stored sequentially in the order in which they are declared: the first member has the lowest memory address and the last member the highest. 2. Every data object has an alignment requirement. The alignment re- quirement for all data except structures, unions, and arrays is either the size of the object or the current packing size (specified with ei- ther the "aligned" attribute or the "pack" pragma), whichever is less. For structures, unions, and arrays, the alignment require- ment is the largest alignment requirement of its members. Every object is allocated an offset so that: offset % alignment_requirement == 0 3. Adjacent bit-fields are packed into the same 1-, 2-, or 4-byte allo- cation unit if the integral types are the same size and if the next bit-field fits into the current allocation unit without crossing the boundary imposed by the common alignment requirements of the bit-fields. MSVC interprets zero-length bit-fields in the following ways: 1. If a zero-length bit-field is inserted between two bit-fields that are normally coalesced, the bit-fields are not coalesced. For example: struct { unsigned long bf_1 : 12; unsigned long : 0; unsigned long bf_2 : 12; } t1; The size of "t1" is 8 bytes with the zero-length bit-field. If the zero-length bit-field were removed, "t1"'s size would be 4 bytes. 2. If a zero-length bit-field is inserted after a bit-field, "foo", and the alignment of the zero-length bit-field is greater than the member that follows it, "bar", "bar" is aligned as the type of the zero-length bit-field. For example: struct { char foo : 4; short : 0; char bar; } t2; struct { char foo : 4; short : 0; double bar; } t3; For "t2", "bar" is placed at offset 2, rather than offset 1. Ac- cordingly, the size of "t2" is 4. For "t3", the zero-length bit-field does not affect the alignment of "bar" or, as a result, the size of the structure. Taking this into account, it is important to note the following: 1. If a zero-length bit-field follows a normal bit-field, the type of the zero-length bit-field may affect the alignment of the structure as whole. For example, "t2" has a size of 4 bytes, since the zero-length bit-field follows a normal bit-field, and is of type short. 2. Even if a zero-length bit-field is not followed by a normal bit-field, it may still affect the alignment of the structure: struct { char foo : 6; long : 0; } t4; Here, "t4" takes up 4 bytes. 3. Zero-length bit-fields following non-bit-field members are ignored: struct { char foo; long : 0; char bar; } t5; Here, "t5" takes up 2 bytes. -mno-align-stringops Do not align the destination of inlined string operations. This switch reduces code size and improves performance in case the destination is already aligned, but GCC doesn't know about it. -minline-all-stringops By default GCC inlines string operations only when the destination is known to be aligned to least a 4-byte boundary. This enables more in- lining and increases code size, but may improve performance of code that depends on fast "memcpy" and "memset" for short lengths. The op- tion enables inline expansion of "strlen" for all pointer alignments. -minline-stringops-dynamically For string operations of unknown size, use run-time checks with inline code for small blocks and a library call for large blocks. -mstringop-strategy=alg Override the internal decision heuristic for the particular algorithm to use for inlining string operations. The allowed values for alg are: rep_byte rep_4byte rep_8byte Expand using i386 "rep" prefix of the specified size. byte_loop loop unrolled_loop Expand into an inline loop. libcall Always use a library call. -mmemcpy-strategy=strategy Override the internal decision heuristic to decide if "__builtin_mem- cpy" should be inlined and what inline algorithm to use when the ex- pected size of the copy operation is known. strategy is a comma-sepa- rated list of alg:max_size:dest_align triplets. alg is specified in -mstringop-strategy, max_size specifies the max byte size with which inline algorithm alg is allowed. For the last triplet, the max_size must be -1. The max_size of the triplets in the list must be specified in increasing order. The minimal byte size for alg is 0 for the first triplet and "max_size + 1" of the preceding range. -mmemset-strategy=strategy This option is similar to -mmemcpy-strategy= except that it controls the "__builtin_memset" expansion. -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 -momit-leaf-frame-pointer removes the frame pointer for leaf functions, which might make debugging harder. -mtls-direct-seg-refs -mno-tls-direct-seg-refs Controls whether TLS variables may be accessed with offsets from the TLS segment register (%gs for 32-bit, %fs for 64-bit), or whether the thread base pointer must be added. Whether or not this is valid de- pends on the operating system, and whether it maps the segment to cover the entire TLS area. For systems that use the GNU C Library, the default is on. -msse2avx -mno-sse2avx Specify that the assembler should encode SSE instructions with VEX pre- fix. The option -mavx turns this on by default. -mfentry -mno-fentry If profiling is active (-pg), put the profiling counter call before the prologue. Note: On x86 architectures the attribute "ms_hook_prologue" isn't possible at the moment for -mfentry and -pg. -mrecord-mcount -mno-record-mcount If profiling is active (-pg), generate a section that contains pointers to each profiling call; this is useful for automatically patching the calls. You can use the mfentry-section= option to set the name of the section; it defaults to __mcount_loc. -mnop-mcount -mno-nop-mcount If profiling is active (-pg), generate the calls to the profiling func- tions as NOPs. This is useful when they should be patched in later dy- namically. This is likely only useful together with -mrecord-mcount. -minstrument-return=type With -pg -mfentry, instrument function exits according to type, which may be one of none to not instrument, call to generate a call to "__re- turn__", or nop5 to generate a 5-byte nop sequence. This option only instruments true returns ending with a "ret", not sibling calls via a jump. -mrecord-return -mno-record-return Generate a "__return_loc" section pointing to all return instrumenta- tion code. -mfentry-name=name Set name of "__fentry__" symbol called at function entry for -pg -mfen- try functions. -mfentry-section=name Set name of section to record -mrecord-mcount calls. The default is __mcount_loc. -mskip-rax-setup -mno-skip-rax-setup When generating code for the x86-64 architecture with SSE extensions disabled, -mskip-rax-setup can be used to skip setting up RAX register when there are no variable arguments passed in vector registers. -m8bit-idiv -mno-8bit-idiv On some processors, like Intel Atom, 8-bit unsigned integer divide is much faster than 32-bit/64-bit integer divide. This option generates a run-time check. If both dividend and divisor are within range of 0 to 255, 8-bit unsigned integer divide is used instead of 32-bit/64-bit in- teger divide. -mavx256-split-unaligned-load -mavx256-split-unaligned-store Split 32-byte AVX unaligned load and store. -mstack-protector-guard=guard -mstack-protector-guard-reg=reg -mstack-protector-guard-offset=offset -mstack-protector-guard-symbol=symbol Generate stack protection code using canary at guard. Supported loca- tions are global for global canary or tls for per-thread canary in the TLS block (the default). This option has effect only when -fstack-pro- tector or -fstack-protector-all is specified. With the latter choice the options -mstack-protector-guard-reg=reg and -mstack-protector-guard-offset=offset furthermore specify which segment register (%fs or %gs) to use as base register for reading the canary, and from what offset from that base register. The default for those is as specified in the relevant ABI. -mstack-protector-guard-symbol=symbol overrides the offset with a sym- bol reference to a canary in the TLS block. -mgeneral-regs-only Generate code that uses only the general-purpose registers. This pre- vents the compiler from using floating-point, vector, mask and bound registers. -mrelax-cmpxchg-loop When emitting a compare-and-swap loop for __sync Builtins and __atomic Builtins lacking a native instruction, optimize for the highly con- tended case by issuing an atomic load before the "CMPXCHG" instruction, and using the "PAUSE" instruction to save CPU power when restarting the loop. -mindirect-branch=choice Convert indirect call and jump with choice. The default is keep, which keeps indirect call and jump unmodified. thunk converts indirect call and jump to call and return thunk. thunk-inline converts indirect call and jump to inlined call and return thunk. thunk-extern converts indi- rect call and jump to external call and return thunk provided in a sep- arate object file. You can control this behavior for a specific func- tion by using the function attribute "indirect_branch". Note that -mcmodel=large is incompatible with -mindirect-branch=thunk and -mindirect-branch=thunk-extern since the thunk function may not be reachable in the large code model. Note that -mindirect-branch=thunk-extern is compatible with -fcf-pro- tection=branch since the external thunk can be made to enable con- trol-flow check. -mfunction-return=choice Convert function return with choice. The default is keep, which keeps function return unmodified. thunk converts function return to call and return thunk. thunk-inline converts function return to inlined call and return thunk. thunk-extern converts function return to external call and return thunk provided in a separate object file. You can con- trol this behavior for a specific function by using the function at- tribute "function_return". Note that -mindirect-return=thunk-extern is compatible with -fcf-pro- tection=branch since the external thunk can be made to enable con- trol-flow check. Note that -mcmodel=large is incompatible with -mfunction-return=thunk and -mfunction-return=thunk-extern since the thunk function may not be reachable in the large code model. -mindirect-branch-register Force indirect call and jump via register. -mharden-sls=choice Generate code to mitigate against straight line speculation (SLS) with choice. The default is none which disables all SLS hardening. return enables SLS hardening for function returns. indirect-jmp enables SLS hardening for indirect jumps. all enables all SLS hardening. -mindirect-branch-cs-prefix Add CS prefix to call and jmp to indirect thunk with branch target in r8-r15 registers, so that the call and jmp instruction length is 6 bytes. This allows them to potentially be replaced with lfence; call *%r8-r15 or lfence; jmp *%r8-r15 at run time. -mapx-inline-asm-use-gpr32 By default, EGPR usage is disabled in inline asm constraints as GCC cannot be aware of whether the asm instructions support GP32 or not. If your inline asm can handle EGPR, use -mapx-inline-asm-use-gpr32. -mgather -mscatter Enable vectorization for gather and scatter instructions, respectively. These -m switches are supported in addition to the above on x86-64 proces- sors in 64-bit environments. -m32 -m64 -mx32 -m16Generate code for a 16-bit, 32-bit or 64-bit environment. The -m32 op- tion sets "int", "long", and pointer types to 32 bits, and generates code that runs in 32-bit mode. The -m64 option sets "int" to 32 bits and "long" and pointer types to 64 bits, and generates code for the x86-64 architecture. For Darwin only the -m64 option also turns off the -fno-pic and -mdynamic-no-pic options. The -mx32 option sets "int", "long", and pointer types to 32 bits, and generates code for the x86-64 architecture. The -m16 option is the same as -m32, except for that it outputs the ".code16gcc" assembly directive at the beginning of the assembly output so that the binary can run in 16-bit mode. -miamcu The -miamcu option generates code that conforms to Intel MCU psABI. It requires the -m32 option to be turned on. -mno-red-zone Do not use a so-called "red zone" for x86-64 code. The red zone is mandated by the x86-64 ABI; it is a 128-byte area beyond the location of the stack pointer that is not modified by signal or interrupt han- dlers and therefore can be used for temporary data without adjusting the stack pointer. The flag -mno-red-zone disables this red zone. -mcmodel=small Generate code for the small code model: the program and its symbols must be linked in the lower 2 GB of the address space. Pointers are 64 bits. Programs can be statically or dynamically linked. This is the default code model. -mcmodel=kernel Generate code for the kernel code model. The kernel runs in the nega- tive 2 GB of the address space. This model has to be used for Linux kernel code. -mcmodel=medium Generate code for the medium model: the program is linked in the lower 2 GB of the address space. Small symbols are also placed there. Sym- bols with sizes larger than -mlarge-data-threshold are put into large data or BSS sections and can be located above 2GB. Programs can be statically or dynamically linked. -mcmodel=large Generate code for the large model. This model makes no assumptions about addresses and sizes of sections. -maddress-mode=long Generate code for long address mode. This is only supported for 64-bit and x32 environments. It is the default address mode for 64-bit envi- ronments. -maddress-mode=short Generate code for short address mode. This is only supported for 32-bit and x32 environments. It is the default address mode for 32-bit and x32 environments. -mneeded -mno-needed Emit GNU_PROPERTY_X86_ISA_1_NEEDED GNU property for Linux target to in- dicate the micro-architecture ISA level required to execute the binary. -mno-direct-extern-access Without -fpic or -fPIC, always use the GOT pointer to access external symbols. With -fpic or -fPIC, treat access to protected symbols as lo- cal symbols. The default is -mdirect-extern-access. Warning: shared libraries compiled with -mno-direct-extern-access and executable compiled with -mdirect-extern-access may not be binary com- patible if protected symbols are used in shared libraries and exe- cutable. -munroll-only-small-loops -mno-unroll-only-small-loops Controls conservative small loop unrolling. It is enabled by default with -O2, and unrolls loops with less than 4 instructions by 1 time. This gives better utilization of the instruction decoding pipeline on modern processors. You can disable this with -mno-un- roll-only-small-loops, and it is also disabled if the more general op- tions -funroll-loops or -funroll-all-loops are either enabled or ex- plicitly disabled. -mdispatch-scheduler Enable instruction scheduling. This is only supported on bdver1, bd- ver2, bdver3, bdver4, and znver1 processors and additionally requires -fschedule-insns -fsched-pressure. -mlam=choice LAM(linear-address masking) allows special bits in the pointer to be used for metadata. The default is none. With u48, pointer bits in posi- tions 62:48 can be used for metadata; With u57, pointer bits in posi- tions 62:57 can be used for metadata. x86 Windows Options Xstormy16 Options These options are defined for Xstormy16: -msim Choose startup files and linker script suitable for the simulator. Xtensa Options These options are supported for Xtensa targets: -mconst16 -mno-const16 Enable or disable use of "CONST16" instructions for loading constant values. When enabled, "CONST16" instructions are always used in place of the standard "L32R" instructions. The use of "CONST16" is enabled by default only if the "L32R" instruction is not available. -mserialize-volatile -mno-serialize-volatile When this option is enabled, GCC inserts "MEMW" instructions before "volatile" memory references to guarantee sequential consistency. The default is -mserialize-volatile. Use -mno-serialize-volatile to omit the "MEMW" instructions. -mforce-no-pic -mno-force-no-pic For targets like GNU/Linux, where all user-mode Xtensa code must be po- sition-independent code (PIC), this option disables PIC for compiling kernel code. -mtext-section-literals -mno-text-section-literals These options control the treatment of literal pools. The default is -mno-text-section-literals, which places literals in a separate section in the output file. This allows the literal pool to be placed in a data RAM/ROM, and it also allows the linker to combine literal pools from separate object files to remove redundant literals and improve code size. With -mtext-section-literals, 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. Literals for each function are placed right before that function. -mauto-litpools -mno-auto-litpools These options control the treatment of literal pools. The default is -mno-auto-litpools, which places literals in a separate section in the output file unless -mtext-section-literals is used. With -mauto-lit- pools the literals are interspersed in the text section by the assem- bler. Compiler does not produce explicit ".literal" directives and loads literals into registers with "MOVI" instructions instead of "L32R" to let the assembler do relaxation and place literals as neces- sary. This option allows assembler to create several literal pools per function and assemble very big functions, which may not be possible with -mtext-section-literals. -mtarget-align -mno-target-align When this option is enabled, GCC instructs the assembler to automati- cally align instructions to reduce branch penalties at the expense of some code density. The assembler attempts to widen density instruc- tions to align branch targets and the instructions following call in- structions. If there are not enough preceding safe density instruc- tions to align a target, no widening is performed. The default is -mtarget-align. These options do not affect the treatment of auto-aligned instructions like "LOOP", which the assembler always aligns, either by widening density instructions or by inserting NOP in- structions. -mlongcalls -mno-longcalls When this option is enabled, GCC 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 "CALL" instruc- tion into an "L32R" followed by a "CALLX" instruction. The default is -mno-longcalls. 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 GCC still shows direct call instructions---look at the disassembled object code to see the actual instructions. Note that the assembler uses an indirect call for every cross-file call, not just those that really are out of range. -mabi=name Generate code for the specified ABI. Permissible values are: call0, windowed. Default ABI is chosen by the Xtensa core configuration. -mabi=call0 When this option is enabled function parameters are passed in registers "a2" through "a7", registers "a12" through "a15" are caller-saved, and register "a15" may be used as a frame pointer. When this version of the ABI is enabled the C preprocessor symbol "__XTENSA_CALL0_ABI__" is defined. -mabi=windowed When this option is enabled function parameters are passed in registers "a10" through "a15", and called function rotates register window by 8 registers on entry so that its arguments are found in registers "a2" through "a7". Register "a7" may be used as a frame pointer. Register window is rotated 8 registers back upon return. When this version of the ABI is enabled the C preprocessor symbol "__XTENSA_WINDOWED_ABI__" is defined. -mextra-l32r-costs=n Specify an extra cost of instruction RAM/ROM access for "L32R" instruc- tions, in clock cycles. This affects, when optimizing for speed, whether loading a constant from literal pool using "L32R" or synthesiz- ing the constant from a small one with a couple of arithmetic instruc- tions. The default value is 0. -mstrict-align -mno-strict-align Avoid or allow generating memory accesses that may not be aligned on a natural object boundary as described in the architecture specification. The default is -mno-strict-align for cores that support both unaligned loads and stores in hardware and -mstrict-align for all other cores. -mforce-l32 -mno-force-l32 When this option is enabled, GCC performs 1- or 2-byte loads in the generic address space (ie., default memory references) by bit-extract- ing the desired portion from the result of an aligned 4-byte load, in- stead of the instructions originally provided for those purposes. This option does not affect memory stores of such byte width, or the place- ment of those memory sections (see also "__force_l32" address spaces described in Xtensa Named Address Spaces, and "force_l32" attribute de- scribed in Xtensa Attributes). The default is -mno-force-l32. zSeries Options These are listed under ENVIRONMENT This section describes several environment variables that affect how GCC 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. Note that you can also specify places to search using options such as -B, -I and -L. These take precedence over places specified using environment variables, which in turn take precedence over those specified by the con- figuration of GCC. LANG LC_CTYPE LC_MESSAGES LC_ALL These environment variables control the way that GCC uses localization information that allows GCC to work with different national conventions for diagnostic and informational output. GCC inspects the locale cate- gories LC_CTYPE and LC_MESSAGES if it has been configured to do so. These locale categories can be set to any value supported by your in- stallation. A typical value is en_GB.UTF-8 for English in the United Kingdom encoded in UTF-8. If the LC_ALL environment variable is set, it overrides the value of LC_CTYPE and LC_MESSAGES; otherwise, LC_CTYPE and LC_MESSAGES default to the value of the LANG environment variable. If none of these vari- ables are set, GCC defaults to traditional C English behavior. These environment variables do not affect the encodings of input files and strings in output files produced by GCC, which are controlled by the -finput-charset and -fexec-charset options, respectively. TMPDIR If TMPDIR is set, it specifies the directory to use for temporary files. GCC uses temporary files to hold the output of one stage of compilation which is to be used as input to the next stage: for exam- ple, the output of the preprocessor, which is the input to the compiler proper. GCC_DIAGNOSTICS_LOG If GCC_DIAGNOSTICS_LOG is set, then additional information about the diagnostics subsystem will be emitted. If it is set to an empty value, then the information will be written to stderr; otherwise, GCC will at- tempt to open that file and write the information there. The precise content and format of the information is subject to change; it is intended for use by GCC developers, rather than end-users. GCC_COMPARE_DEBUG Setting GCC_COMPARE_DEBUG is nearly equivalent to passing -fcompare-de- bug to the compiler driver. See the documentation of this option for more details. GCC_EXEC_PREFIX If GCC_EXEC_PREFIX 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. If GCC_EXEC_PREFIX is not set, GCC attempts to figure out an appropri- ate prefix to use based on the pathname it is invoked with. If GCC cannot find the subprogram using the specified prefix, it tries looking in the usual places for the subprogram. The default value of GCC_EXEC_PREFIX is prefix/lib/gcc/ where prefix is the prefix to the installed compiler. In many cases prefix is the value of "prefix" when you ran the configure script. Other prefixes specified with -B take precedence over this prefix. This prefix is also used for finding files such as crt0.o that are used for linking. In addition, the prefix is used in an unusual way in finding the direc- tories to search for header files. For each of the standard directo- ries whose name normally begins with /usr/local/lib/gcc (more pre- cisely, with the value of GCC_INCLUDE_DIR), GCC tries replacing that beginning with the specified prefix to produce an alternate directory name. Thus, with -Bfoo/, GCC searches foo/bar just before it searches the standard directory /usr/local/lib/bar. If a standard directory be- gins with the configured prefix then the value of prefix is replaced by GCC_EXEC_PREFIX when looking for header files. COMPILER_PATH The value of COMPILER_PATH is a colon-separated list of directories, much like PATH. GCC tries the directories thus specified when search- ing for subprograms, if it cannot find the subprograms using GCC_EXEC_PREFIX. LIBRARY_PATH The value of LIBRARY_PATH is a colon-separated list of directories, much like PATH. When configured as a native compiler, GCC tries the directories thus specified when searching for special linker files, if it cannot find them using GCC_EXEC_PREFIX. Linking using GCC also uses these directories when searching for ordinary libraries for the -l op- tion (but directories specified with -L come first). GCC_EXTRA_DIAGNOSTIC_OUTPUT If GCC_EXTRA_DIAGNOSTIC_OUTPUT is set to one of the following values, then additional text will be emitted to stderr when fix-it hints are emitted. -fdiagnostics-parseable-fixits and -fno-diagnos- tics-parseable-fixits take precedence over this environment variable. fixits-v1 Emit parseable fix-it hints, equivalent to -fdiagnos- tics-parseable-fixits. In particular, columns are expressed as a count of bytes, starting at byte 1 for the initial column. fixits-v2 As "fixits-v1", but columns are expressed as display columns, as per -fdiagnostics-column-unit=display. EXPERIMENTAL_SARIF_SOCKET If EXPERIMENTAL_SARIF_SOCKET is set in the environment, then the com- piler will attempt to connect to a UNIX domain stream socket with that name, and send an "OnSarifResult" JSON-RPC 2.0 notification to it for each diagnostic that occurs, where the value of the notification is a SARIF "result" object. The compiler will fail immediately if EXPERIMENTAL_SARIF_SOCKET is set and it cannot connect to it. This feature is experimental and subject to change or removal without notice. COLLECT_GCC_OPTIONS Set by the driver and read by collect2, lto-wrapper, and the LTO linker plugin to pass the driver's option list. If the list is too long (over 1 KiB by default), the driver writes it to a temporary file and sets this variable to @path instead. Some additional environment variables affect the behavior of the preproces- sor. CPATH C_INCLUDE_PATH CPLUS_INCLUDE_PATH OBJC_INCLUDE_PATH Each variable's value is a list of directories separated by a special character, much like PATH, in which to look for header files. The spe- cial character, "PATH_SEPARATOR", is target-dependent and determined at GCC build time. For Microsoft Windows-based targets it is a semicolon, and for almost all other targets it is a colon. CPATH specifies a list of directories to be searched as if specified with -I, but after any paths given with -I options on the command line. This environment variable is used regardless of which language is being preprocessed. 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 -isystem, but after any paths given with -isystem options on the command line. In all these variables, an empty element instructs the compiler to search its current working directory. Empty elements can appear at the beginning or end of a path. For instance, if the value of CPATH is ":/special/include", that has the same effect as -I. -I/special/in- clude. DEPENDENCIES_OUTPUT If this variable is set, its value specifies how to output dependencies for Make based on the non-system header files processed by the com- piler. System header files are ignored in the dependency output. The value of DEPENDENCIES_OUTPUT 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 file target, in which case the rules are written to file file using target as the tar- get name. In other words, this environment variable is equivalent to combining the options -MM and -MF, with an optional -MT switch too. SUNPRO_DEPENDENCIES This variable is the same as DEPENDENCIES_OUTPUT (see above), except that system header files are not ignored, so it implies -M rather than -MM. However, the dependence on the main input file is omitted. SOURCE_DATE_EPOCH If this variable is set, its value specifies a UNIX timestamp to be used in replacement of the current date and time in the "__DATE__" and "__TIME__" macros, so that the embedded timestamps become reproducible. The value of SOURCE_DATE_EPOCH must be a UNIX timestamp, defined as the number of seconds (excluding leap seconds) since 01 Jan 1970 00:00:00 represented in ASCII; identical to the output of "date +%s" on GNU/Linux and other systems that support the %s extension in the "date" command. The value should be a known timestamp such as the last modification time of the source or package and it should be set by the build process. BUGS For instructions on reporting bugs, see <https://gcc.gnu.org/bugs/>. FOOTNOTES 1. On some systems, gcc -shared needs to build supplementary stub code for constructors to work. On multi-libbed systems, gcc -shared 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. -shared suppresses the ad- dition of startup code to alter the floating-point environment as done with -ffast-math, -Ofast or -funsafe-math-optimizations on some tar- gets. SEE ALSO gpl(7), gfdl(7), fsf-funding(7), cpp(1), gcov(1), as(1), ld(1), gdb(1) and the Info entries for gcc, cpp, as, ld, binutils and gdb. AUTHOR See the Info entry for gcc, or <https://gcc.gnu.org/onlinedocs/gcc/Contrib- utors.html>, for contributors to GCC. COPYRIGHT Copyright (c) 1988-2026 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.3 or any later version published by the Free Software Foundation; with the Invariant Sec- tions being "GNU General Public License" and "Funding Free Software", the Front-Cover texts being (a) (see below), and with the Back-Cover Texts be- ing (b) (see below). A copy of the license is included in the gfdl(7) man page. (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. gcc-17.0.0 2026-06-21 GCC(1)
NAME | SYNOPSIS | DESCRIPTION | OPTIONS | ENVIRONMENT | BUGS | FOOTNOTES | SEE ALSO | AUTHOR | COPYRIGHT
Want to link to this manual page? Use this URL:
<https://man.freebsd.org/cgi/man.cgi?query=gcc17&sektion=1&manpath=FreeBSD+Ports+15.1.quarterly>