C/C++ Programmer's Guide (G06.27+, H06.08+, J06.03+)

Usage Guidelines
• On Guardian environment, the LINKFILE pragma must be entered on the compiler RUN
command line for native C and C++.
• LINKFILE invokes eld or ld rather than nld if you include SHARED or CALL_SHARED.
• Use the LINKFILE pragma to specify in a text file the names of the object files or linkfiles
(not source files) that make up a program for linking with a linker utility. An example of
LINKFILE appears in Examples (page 306).
• The C or C++ run-time libraries are linked to the program only if the RUNNABLE pragma is
also specified on Guardian environment. On OSS environment, you must specifically invoke
the linker.
• The compiler driver does not verify the existence or the readability of the command file specified
in the LINKFILE directive.
LIST
The LIST pragmas control the generation of compiler-listing text. The LIST pragma enables the
generation of compiler-listing text, and the NOLIST pragma disables it.
[NO]LIST
The pragma default settings are:
SYSTYPE OSSSYSTYPE GUARDIAN
LISTLISTTNS C compiler
LISTLISTG-series TNS c89 utility
LISTLISTTNS/R native C and C++ compilers
LISTLISTNative c89 and c99 utilities
LISTLISTTNS/E native C and C++ compilers
Usage Guideline
The LIST and NOLIST pragmas can be entered on the compiler RUN command line or in the
source text. You can also use the -W[no]list flag of the c89 or the c99 utility.
LMAP
The LMAP pragma controls the generation and presentation of load-map information in the compiler
listing. The LMAP pragma enables load-map generation and specifies how to present the load
maps. NOLMAP disables generation of load maps or disables one form of load-map presentation.
[NO]LMAP { lmap-type }
{ ( lmap-type [ , lmap-type ] ) }
{ * }
lmap-type:
{ ALPHA | LOC }
lmap-type
specifies the type of load-map presentation to enable or disable. The available presentation
types are:
ALPHA
specifies load maps of functions and data blocks sorted by name.
214 Compiler Pragmas