HP aC++/HP ANSI C Release Notes (B3901-90037; A.06.26; September 2011)

+O[no]dynopt (HP-UX 11.31 only) (New)
On HP-UX 11.31 systems, the +O[no]dynopt option enables [disables] dynamic
optimization for the output file. Both forms of this option change the default setting, which
allows the run-time environment to enable or disable dynamic optimization according
to a system-wide default. This option applies only to executable files and shared libraries,
if the run-time environment supports this feature. chatr(1) can be used to change this
setting, including restoration of the default setting, after the output file has been created.
+inline_level num (Enhanced)
The format for num is now N[.n], where num is either an integral value from 0 to 9 or a
value with a single decimal place from 0.0 to 9.0, as follows:
• 0 No inlining is done (same effect as the +d option).
• 1 Only functions marked with the inline keyword or implied by the language to be
inlined are considered for inlining.
• 1.0 < num < 2.0 Increasingly make inliner more aggressive below 2.0.
• 2 More inlining than level 1. This is the default level at optimization levels +O2,
+O3, and +O4.
• 2.0 < num < 9.0 Increasing levels of inliner aggressiveness.
• 9 Attempt to inline all functions other than recursive functions or those with a variable
number of arguments.
-dumpversion (New)
The -dumpversion option displays the simple version number of the compiler, such as
A.06.20. Compare with the -V option, which displays more verbose version information.
#include_next (New)
The #include_next preprocessor directive is similar to the #include directive, but
tells the preprocessor to continue the include-file search beyond the current directory,
and include the subsequent instance found in the file-search path.
#pragma diag_push (New)
This scoped pragma saves the current severity state of all diagnostics. Subsequent uses
of pragmas that modify the severity of a given diagnostic will be in effect within the scope
of the diag_push pragma. The effective scope ends with a corresponding #pragma
diag_pop. You can specify a #pragma diag_push within the scope of another
#pragma diag_push, which results in a new saved severity state and a new effective
scope. A compilation unit should have an equal number of #pragma diag_push and
#pragma diag_pop uses.
30 Product changes in earlier versions