These options are defined specifically for the CRIS ports.
Generate code for the specified architecture. The choices for
v10for respectively ETRAX4, ETRAX100, and ETRAX100LX. Default is
architecture-typeeverything applicable about the generated code, except for the ABI and the set of available instructions. The choices for
architecture-typeare the same as for
Warn when the stack frame of a function exceeds
- -metrax4, -metrax100#
- -mmul-bug-workaround, -mno-mul-bug-workaround#
Work around a bug in the
muluinstructions for CPU models where it applies. This option is disabled by default.
Enable CRIS-specific verbose debug-related information in the assembly code. This option also has the effect of turning off the
#NO_APPformatted-code indicator to the assembler at the beginning of the assembly file.
Do not use condition-code results from previous instruction; always emit compare and test instructions before use of condition codes.
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 maximum 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 options 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#
-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 together with visual inspection of the compiled code: no warnings or errors are generated when call-saved registers must be saved, or storage for local variables needs to be allocated.
Legacy no-op option.
This option arranges to link with input-output functions from a simulator library. Code, initialized data and zero-initialized data are allocated consecutively.