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

POP
The POP pragma directs the native compilers to restore the value of certain pragmas that were
stored earlier by a PUSH pragma.
POP pragma-name
pragma-name:
{ EXTERN_DATA | FIELDALIGN | LIST | OVERFLOW_TRAPS |
REFALIGNED | WARN }
There is no default setting for this pragma.
Usage Guidelines
• The POP pragma can be entered only in the source text.
• Only the values EXTERN_DATA, FIELDALIGN, LIST, OVERFLOW_TRAPS, REFALIGNED, and
WARN can be used as arguments to the POP pragma. The use of any other pragma as an
operand is flagged as an error.
• Each POP pragma has a separate stack that holds up to 32 values.
PROFDIR
The PROFDIR option specifies where an instrumented process will create the raw data file.
PROFDIR "pathname"
The default settings are:
SYSTYPE OSSSYSTYPE GUARDIAN
N.A.N.A.TNS C compiler
N.A.N.A.G-series TNS c89 utility
N.A.N.A.TNS/R native C and C++ compilers
Current working directoryN.A.Native c89 and c99 utilities
N.A.Default subvolumeTNS/E native C and C++ compilers
When PROFDIR is specified, either PROFGEN or CODECOV must also be specified; otherwise,
PROFDIR is ignored. The specified path name is used exactly as specified. If the application will
run in the Guardian environment, specify a Guardian subvolume. If the application will run in the
OSS environment, specify an OSS directory.
Usage Guidelines
• The PROFDIR option can be entered only on the compiler RUN command. It can also be
specified with the -Wprofdir flag of the c89 or the c99 command in the OSS and Windows
environments.
• The PROFDIR option is intended to be used for code profiling; it is ignored unless the PROFGEN
or CODECOV option is also specified.
• If a program consists of more than one compilation module, you must either use the default
default pathname for each module or specify the same pathname for each module.
228 Compiler Pragmas