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

You can set the HIGHPIN flag of a native object file either:
◦ During compilation by using the HIGHPIN pragma, if an executable file is produced by
the compilation
◦ After compilation and linking of an executable object file by using an eld, ld, or nld
command
• For more details on using high PINs and converting a C program to run at a high PIN, see
the Guardian Programmer’s Guide.
HIGHREQUESTERS
The HIGHREQUESTERS pragma specifies that the object file supports high PIN requesters if the
object file includes the main function.
[NO]HIGHREQUESTERS
The pragma default settings are:
SYSTYPE OSSSYSTYPE GUARDIAN
Not setNot setTNS C compiler
HIGHREQUESTERSHIGHREQUESTERSG-series TNS c89 utility
HIGHREQUESTERSHIGHREQUESTERSTNS/R native C and C++ compilers
HIGHREQUESTERSHIGHREQUESTERSNative c89 and c99 utilities
HIGHREQUESTERSHIGHREQUESTERSTNS/E native C and C++ compilers
Usage Guidelines
• For the TNS C compiler, Cfront, and the TNS c89 utility, the HIGHREQUESTERS pragma can
be placed in the source text or in the RUN command that executes the compiler.
When you bind several object files together, Binder sets the HIGHREQUESTERS attribute in
the target object file if, and only if, the object file with the main function has the
HIGHREQUESTERS attribute.
• For the native C and C++ compilers, the HIGHREQUESTERS pragma can be entered on the
compiler RUN command line (not in the source file) or be specified with the
-Whighrequesters flag of the c89 or the c99 utility.
The HIGHREQUESTERS attribute is set for native C and C++ programs only if an executable
object file is the output of the compilation. (Process attributes cannot be set for native relinkable
object files.)
• You can set the HIGHREQUESTERS object-file attribute either during compilation using the
HIGHREQUESTERS pragma or after compilation using the Binder SET command (for TNS
programs) or the eld, ld, or nld utility (for native programs).
• For more details on setting the HIGHREQUESTERS object-file attribute, see the Guardian
Programmer’s Guide.
ICODE
The ICODE pragma controls whether the compiler listing includes the instruction-code mnemonics
generated for each function immediately following the source text of the function. The ICODE
pragma directs the compiler to list these mnemonics, and NOICODE directs it to not list them.
[NO]ICODE
202 Compiler Pragmas