📄 00000010.htm
字号:
<BR> -mno-fp-in-toc <BR> Control whether or not floating-point constants go <BR> in the Table of Contents (TOC), a table of all <BR> global variable and function addresses. By default <BR> GCC puts floating-point constants there; if the TOC <BR> overflows, `-mno-fp-in-toc' will reduce the size of <BR> the TOC, which may avoid the overflow. <BR> <BR> These `-m' options are defined for the IBM RT PC: <BR> <BR> -min-line-mul <BR> Use an in-line code sequence for integer multi- <BR> plies. This is the default. <BR> <BR> -mcall-lib-mul <BR> Call lmul$$ for integer multiples. <BR> <BR> -mfull-fp-blocks <BR> Generate full-size floating point data blocks, in- <BR> cluding the minimum amount of scratch space recom- <BR> mended by IBM. This is the default. <BR> <BR> -mminimum-fp-blocks <BR> Do not include extra scratch space in floating <BR> point data blocks. This results in smaller code, <BR> but slower execution, since scratch space must be <BR> allocated dynamically. <BR> <BR> -mfp-arg-in-fpregs <BR> Use a calling sequence incompatible with the IBM <BR> calling convention in which floating point argu- <BR> ments are passed in floating point registers. Note <BR> that varargs.h and stdargs.h will not work with <BR> floating point operands if this option is speci- <BR> fied. <BR> <BR> -mfp-arg-in-gregs <BR> Use the normal calling convention for floating <BR> point arguments. This is the default. <BR> <BR> -mhc-struct-return <BR> Return structures of more than one word in memory, <BR> rather than in a register. This provides compati- <BR> bility with the MetaWare HighC (hc) compiler. Use <BR> `-fpcc-struct-return' for compatibility with the <BR> Portable C Compiler (pcc). <BR> <BR> -mnohc-struct-return <BR> Return some structures of more than one word in <BR> registers, when convenient. This is the default. <BR> For compatibility with the IBM-supplied compilers, <BR> use either `-fpcc-struct-return' or <BR> `-mhc-struct-return'. <BR> <BR> These `-m' options are defined for the MIPS family of com- <BR> puters: <BR> <BR> -mcpu=cpu-type <BR> Assume the defaults for the machine type cpu-type <BR> when scheduling instructions. The default cpu-type <BR> is default, which picks the longest cycles times <BR> for any of the machines, in order that the code run <BR> at reasonable rates on all MIPS cpu's. Other <BR> choices for cpu-type are r2000, r3000, r4000, and <BR> r6000. While picking a specific cpu-type will <BR> schedule things appropriately for that particular <BR> chip, the compiler will not generate any code that <BR> does not meet level 1 of the MIPS ISA (instruction <BR> set architecture) without the -mips2 or -mips3 <BR> switches being used. <BR> <BR> -mips2 Issue instructions from level 2 of the MIPS ISA <BR> (branch likely, square root instructions). The <BR> -mcpu=r4000 or -mcpu=r6000 switch must be used in <BR> conjunction with -mips2. <BR> <BR> -mips3 Issue instructions from level 3 of the MIPS ISA (64 <BR> bit instructions). The -mcpu=r4000 switch must be <BR> used in conjunction with -mips2. <BR> <BR> -mint64 <BR> <BR> -mlong64 <BR> <BR> -mlonglong128 <BR> These options don't work at present. <BR> <BR> -mmips-as <BR> Generate code for the MIPS assembler, and invoke <BR> mips-tfile to add normal debug information. This <BR> is the default for all platforms except for the <BR> OSF/1 reference platform, using the OSF/rose object <BR> format. If any of the -ggdb, -gstabs, or -gstabs+ <BR> switches are used, the mips-tfile program will en- <BR> capsulate the stabs within MIPS ECOFF. <BR> <BR> -mgas Generate code for the GNU assembler. This is the <BR> default on the OSF/1 reference platform, using the <BR> OSF/rose object format. <BR> <BR> -mrnames <BR> <BR> -mno-rnames <BR> The -mrnames switch says to output code using the <BR> MIPS software names for the registers, in
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -