-EB
-EL
-march=
arch
Native Linux/GNU and IRIX toolchains also support 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' will set `_MIPS_ARCH' to `"r2000"' and define the macro `_MIPS_ARCH_R2000'.
Note that the `_MIPS_ARCH' macro uses the processor names given above. In other words, it will have the full prefix and will 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
When this option is not used, GCC will optimize for the processor specified by -march. By using -march and -mtune together, it is possible to generate code that will run 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
-mips2
-mips3
-mips4
-mips32
-mips32r2
-mips64
-mips64r2
-mips16
-mno-mips16
MIPS16 code generation can also be controlled on a per-function basis by means of mips16
and nomips16
attributes. See Function Attributes, for more information.
-mflip-mips16
-minterlink-mips16
-mno-interlink-mips16
For example, non-MIPS16 code cannot jump directly to MIPS16 code; it must either use a call or an indirect jump. -minterlink-mips16 therefore disables direct jumps unless GCC knows that the target of the jump is not MIPS16.
-mabi=32
-mabi=o64
-mabi=n32
-mabi=64
-mabi=eabi
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 http://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' instructions and is therefore only supported for MIPS32R2 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 floating-point values are returned in `$f0' only, not a `$f0'/`$f1' pair. The set of call-saved registers also remains the same, but all 64 bits are saved.
-mabicalls
-mno-abicalls
-mshared
-mno-shared
All -mabicalls code has traditionally been position-independent, regardless of options like -fPIC and -fpic. However, as an extension, the GNU toolchain allows executables to use absolute accesses for locally-binding symbols. It can also use shorter GP initialization sequences 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 will generally make executables both smaller and quicker.
-mshared is the default.
-mplt
-mno-plt
You can make -mplt the default by configuring GCC with --with-mips-plt. The default is -mno-plt otherwise.
-mxgot
-mno-xgot
GCC normally uses a single instruction to load values from the GOT. While this is relatively efficient, it will only work if the GOT is smaller than about 64k. Anything larger will cause 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. It should then work with very large GOTs, although it will also be less efficient, since it will take three instructions to fetch the value of a global symbol.
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 independent code.
-mgp32
-mgp64
-mfp32
-mfp64
-mhard-float
-msoft-float
-msingle-float
-mdouble-float
-mllsc
-mno-llsc
-mllsc is useful if the runtime environment can emulate the instructions 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 default for some configurations; see the installation documentation for details.
-mdsp
-mno-dsp
-mdspr2
-mno-dspr2
-msmartmips
-mno-smartmips
-mpaired-single
-mno-paired-single
-mdmx
-mno-mdmx
-mips3d
-mno-mips3d
-mmt
-mno-mt
-mlong64
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
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 registers, whichever is smaller.
-msym32
-mno-sym32
-G
num
The default -G option depends on the configuration.
-mlocal-sdata
-mno-local-sdata
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 libraries with -mno-local-sdata, so that the libraries leave more room for the main program.
-mextern-sdata
-mno-extern-sdata
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 defined by another module, you must either compile that module with a high-enough -G setting or attach a section
attribute to Var's definition. 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
-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 routines will pass an unknown value in $gp
. (In such situations, the boot monitor itself would usually be compiled with -G0.)
-mno-gpopt implies -mno-local-sdata and -mno-extern-sdata.
-membedded-data
-mno-embedded-data
-muninit-const-in-rodata
-mno-uninit-const-in-rodata
const
variables in the read-only data section. This option is only meaningful in conjunction with
-membedded-data.
-mcode-readable=
setting
-mcode-readable=yes
-mcode-readable=pcrel
-mcode-readable=no
-msplit-addresses
-mno-split-addresses
%hi()
and
%lo()
assembler relocation operators. This option has been superseded by
-mexplicit-relocs but is retained for backwards compatibility.
-mexplicit-relocs
-mno-explicit-relocs
-mexplicit-relocs is the default if GCC was configured to use an assembler that supports relocation operators.
-mcheck-zero-division
-mno-check-zero-division
The default is -mcheck-zero-division.
-mdivide-traps
-mdivide-breaks
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.
-mmemcpy
-mno-memcpy
memcpy()
for non-trivial block moves. The default is
-mno-memcpy, which allows GCC to inline most constant-sized copies.
-mlong-calls
-mno-long-calls
jal
instruction. Calling functions 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
mad
,
madu
and
mul
instructions, as provided by the R4650 ISA.
-mfused-madd
-mno-fused-madd
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.
-nocpp
-mfix-24k
-mno-fix-24k
-mfix-r4000
-mno-fix-r4000
-mfix-r4400
-mno-fix-r4400
-mfix-r10000
-mno-fix-r10000
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-vr4120
-mno-fix-vr4120
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.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
mflo
/
mfhi
errata. The workarounds are implemented by the assembler rather than by GCC, although GCC will avoid using
mflo
and
mfhi
if the VR4130
macc
,
macchi
,
dmacc
and
dmacchi
instructions are available instead.
-mfix-sb1
-mno-fix-sb1
-mr10k-cache-barrier=
setting
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 predicted outcome was wrong. However, on the R10K, even aborted instructions 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 will overwrite 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 accesses to any byte in the following regions will not have side effects:
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
-mr10k-cache-barrier=store
-mr10k-cache-barrier=none
-mflush-func=
func
-mno-flush-func
_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
-mbranch-likely
-mno-branch-likely
-mfp-exceptions
-mno-fp-exceptions
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
This option only has an effect when optimizing for the VR4130. It normally makes code faster, but at the expense of making it bigger. It is enabled by default at optimization level -O3.
-msynci
-mno-synci
synci
instructions on architectures that support it. The
synci
instructions (if enabled) will be generated when
__builtin___clear_cache()
is compiled.
This option defaults to -mno-synci
, but the default can be overridden by configuring 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 will not invalidate the instruction caches on all cores and may lead to undefined behavior.
-mrelax-pic-calls
-mno-relax-pic-calls
$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 assembler and a linker that supports the .reloc
assembly directive and -mexplicit-relocs
is in effect. With -mno-explicit-relocs
, this optimization can be performed by the assembler and the linker alone without help from the compiler.
-mmcount-ra-address
-mno-mcount-ra-address
_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:
$31
.*
ra-address, if ra-address is nonnull.The default is -mno-mcount-ra-address.