3.18.51 Visium Options
- A program which performs file I/O and is destined to run on an MCM target
should be linked with this option. It causes the libraries libc.a and
libdebug.a to be linked. The program should be run on the target under
the control of the GDB remote debugging stub.
- A program which performs file I/O and is destined to run on the simulator
should be linked with option. This causes libraries libc.a and libsim.a to
- Generate code containing floating-point instructions. This is the
- Generate code containing library calls for floating-point.
-msoft-float changes the calling convention in the output file;
therefore, it is only useful if you compile all of a program with
this option. In particular, you need to compile libgcc.a, the
library that comes with GCC, with -msoft-float in order for
this to work.
- Set the instruction set, register set, and instruction scheduling parameters
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.
- Set the instruction scheduling parameters for machine type cpu_type,
but do not set the instruction set or register set that the option
- Generate code for the supervisor mode, where there are no restrictions on
the access to general registers. This is the default.
- Generate code for the user mode, where the access to some general registers
is forbidden: on the GR5, registers r24 to r31 cannot be accessed in this
mode; on the GR6, only registers r29 to r31 are affected.