Installation guide

Table 7–2: Comparison of DIGITAL UNIX and ULTRIX Predefined Symbols
for the cc Command
Name for −std and
−std1 Modes
Name for −std0
Mode
Name for ULTRIX
on RISC Systems
Name for ULTRIX
on VAX Systems
String containing the host hardware name:
_ _alpha _ _alpha _ _host_mips_ _ vax
String containing the target hardware name:
_ _alpha _ _alpha mips vax
String containing the operating system name:
_ _osf_ _ _ _osf_ _ unix unix
_ _unix_ _ _ _unix_ _ ultrix ultrix
unix bsd4_2 bsd4_2
String indicating that the host is a BSD system:
_SYSTYPE_BSD _SYSTYPE_BSD SYSTYPE_BSD
Not applicable
SYSTYPE_BSD
String indicating that the application is written in C:
_ _LANGUAGE_C_ _ _ _LANGUAGE_C_ _ LANGUAGE_C
Not applicable
LANGUAGE_C
String indicating that double floating-point format is used:
Not applicable Not applicable Not applicable
GFLOAT
7.4.2 Differences Between DIGITAL UNIX C and ULTRIX C on RISC
Systems
_______________________ Note _______________________
This section describes the behavior of ULTRIX C on Versions 4.3
and earlier RISC ULTRIX systems, and not the behavior of
ULTRIX C on Versions 4.3A or later systems. The reason is that
Versions 4.3A and later systems employ the MIPS Version 3.0
compiler environment, which is more completely similar to the
DIGITAL UNIX C compiler environment than the MIPS Version
2.10 compiler environment on earlier ULTRIX RISC systems,
which is described here.
When you compile your ULTRIX application on a DIGITAL UNIX system,
you may notice some differences in how the compilers operate. For
7–22 Migrating Your ULTRIX Application to a DIGITAL UNIX System