mips-options.html

gcc手册

     <dd><dt><code>-mno-split-addresses</code>
     <dd>Generate code to load the high and low parts of address constants separately. 
This allows GCC to optimize away redundant loads of the high order
bits of addresses.  This optimization requires GNU as and GNU ld. 
This optimization is enabled by default for some embedded targets where
GNU as and GNU ld are standard.

     <br><dt><code>-mrnames</code>
     <dd><dt><code>-mno-rnames</code>
     <dd>The <code>-mrnames</code> switch says to output code using the MIPS software
names for the registers, instead of the hardware names (ie, <var>a0</var>
instead of <var>$4</var>).  The only known assembler that supports this option
is the Algorithmics assembler.

     <br><dt><code>-mgpopt</code>
     <dd><dt><code>-mno-gpopt</code>
     <dd>The <code>-mgpopt</code> switch says to write all of the data declarations
before the instructions in the text section, this allows the MIPS
assembler to generate one word memory references instead of using two
words for short global or static data items.  This is on by default if
optimization is selected.

     <br><dt><code>-mstats</code>
     <dd><dt><code>-mno-stats</code>
     <dd>For each non-inline function processed, the <code>-mstats</code> switch
causes the compiler to emit one line to the standard error file to
print statistics about the program (number of registers saved, stack
size, etc.).

     <br><dt><code>-mmemcpy</code>
     <dd><dt><code>-mno-memcpy</code>
     <dd>The <code>-mmemcpy</code> switch makes all block moves call the appropriate
string function (<code>memcpy</code> or <code>bcopy</code>) instead of possibly
generating inline code.

     <br><dt><code>-mmips-tfile</code>
     <dd><dt><code>-mno-mips-tfile</code>
     <dd>The <code>-mno-mips-tfile</code> switch causes the compiler not
postprocess the object file with the <code>mips-tfile</code> program,
after the MIPS assembler has generated it to add debug support.  If
<code>mips-tfile</code> is not run, then no local variables will be
available to the debugger.  In addition, <code>stage2</code> and
<code>stage3</code> objects will have the temporary file names passed to the
assembler embedded in the object file, which means the objects will
not compare the same.  The <code>-mno-mips-tfile</code> switch should only
be used when there are bugs in the <code>mips-tfile</code> program that
prevents compilation.

     <br><dt><code>-msoft-float</code>
     <dd>Generate output containing library calls for floating point. 
<strong>Warning:</strong> the requisite libraries are not part of GCC. 
Normally the facilities of the machine's usual C compiler are used, but
this can't be done directly in cross-compilation.  You must make your
own arrangements to provide suitable library functions for
cross-compilation.

     <br><dt><code>-mhard-float</code>
     <dd>Generate output containing floating point instructions.  This is the
default if you use the unmodified sources.

     <br><dt><code>-mabicalls</code>
     <dd><dt><code>-mno-abicalls</code>
     <dd>Emit (or do not emit) the pseudo operations <code>.abicalls</code>,
<code>.cpload</code>, and <code>.cprestore</code> that some System V.4 ports use for
position independent code.

     <br><dt><code>-mlong-calls</code>
     <dd><dt><code>-mno-long-calls</code>
     <dd>Do all calls with the <code>JALR</code> instruction, which requires
loading up a function's address into a register before the call. 
You need to use this switch, if you call outside of the current
512 megabyte segment to functions that are not through pointers.

     <br><dt><code>-mhalf-pic</code>
     <dd><dt><code>-mno-half-pic</code>
     <dd>Put pointers to extern references into the data section and load them
up, rather than put the references in the text section.

     <br><dt><code>-membedded-pic</code>
     <dd><dt><code>-mno-embedded-pic</code>
     <dd>Generate PIC code suitable for some embedded systems.  All calls are
made using PC relative address, and all data is addressed using the $gp
register.  No more than 65536 bytes of global data may be used.  This
requires GNU as and GNU ld which do most of the work.  This currently
only works on targets which use ECOFF; it does not work with ELF.

     <br><dt><code>-membedded-data</code>
     <dd><dt><code>-mno-embedded-data</code>
     <dd>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.

     <br><dt><code>-muninit-const-in-rodata</code>
     <dd><dt><code>-mno-uninit-const-in-rodata</code>
     <dd>When used together with <code>-membedded-data</code>, it will always store uninitialized
const variables in the read-only data section.

     <br><dt><code>-msingle-float</code>
     <dd><dt><code>-mdouble-float</code>
     <dd>The <code>-msingle-float</code> switch tells gcc to assume that the floating
point coprocessor only supports single precision operations, as on the
<code>r4650</code> chip.  The <code>-mdouble-float</code> switch permits gcc to use
double precision operations.  This is the default.

     <br><dt><code>-mmad</code>
     <dd><dt><code>-mno-mad</code>
     <dd>Permit use of the <code>mad</code>, <code>madu</code> and <code>mul</code> instructions,
as on the <code>r4650</code> chip.

     <br><dt><code>-m4650</code>
     <dd>Turns on <code>-msingle-float</code>, <code>-mmad</code>, and, at least for now,
<code>-mcpu=r4650</code>.

     <br><dt><code>-mips16</code>
     <dd><dt><code>-mno-mips16</code>
     <dd>Enable 16-bit instructions.

     <br><dt><code>-mentry</code>
     <dd>Use the entry and exit pseudo ops.  This option can only be used with
<code>-mips16</code>.

     <br><dt><code>-EL</code>
     <dd>Compile code for the processor in little endian mode. 
The requisite libraries are assumed to exist.

     <br><dt><code>-EB</code>
     <dd>Compile code for the processor in big endian mode. 
The requisite libraries are assumed to exist.

     <br><dt><code>-G </code><var>num</var><code></code>
     <dd>Put global and static items less than or equal to <var>num</var> bytes into
the small data or bss sections instead of the normal data or bss
section.  This allows the assembler to emit one word memory reference
instructions based on the global pointer (<var>gp</var> or <var>$28</var>),
instead of the normal two words used.  By default, <var>num</var> is 8 when
the MIPS assembler is used, and 0 when the GNU assembler is used.  The
<code>-G </code><var>num</var><code></code> switch is also passed to the assembler and linker. 
All modules should be compiled with the same <code>-G </code><var>num</var><code></code>
value.

     <br><dt><code>-nocpp</code>
     <dd>Tell the MIPS assembler to not run its preprocessor over user
assembler files (with a <code>.s</code> suffix) when assembling them.

     <br><dt><code>-mfix7000</code>
     <dd>Pass an option to gas which will cause nops to be inserted if
the read of the destination register of an mfhi or mflo instruction
occurs in the following two instructions.

     <br><dt><code>-no-crt0</code>
     <dd>Do not include the default crt0.

     <br><dt><code>-mflush-func=</code><var>func</var><code></code>
     <dd><dt><code>-mno-flush-func</code>
     <dd>Specifies the function to call to flush the I and D caches, or to not
call any such function.  If called, the function must take the same
arguments as the common <code>_flush_func()</code>, 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
<code>_flush_func</code> or <code>__cpu_flush</code>.

     <br><dt><code>-mbranch-likely</code>
     <dd><dt><code>-mno-branch-likely</code>
     <dd>Enable or disable use of Branch Likely instructions, regardless of the
default for the selected architecture.  By default, Branch Likely
instructions may be generated if they are supported by the selected
architecture.  An exception is for the MIPS32 and MIPS64 architectures
and processors which implement those architectures; for those, Branch
Likely instructions will not be generated by default because the MIPS32
and MIPS64 architectures specifically deprecate their use. 
</dl>

   </body></html>