HP aC++/HP C A.06.20 Release Notes

This option limits the number of instantiation contexts output by the compiler for
diagnostics involving template instantiations. At most num outermost contexts and
num innermost contexts are shown. If there are more than 2 * num relevant contexts,
the additional contexts are omitted. Omitted contexts are replaced by a single line
separating the outermost num contexts from the innermost num contexts, and indicating
the number of contexts omitted. The default value for num is 5. A value of 0 removes
the limit.
+wperfadvice Option (New)
+wperfadvice[={1|2|3|4}]
This option enables performance advisory messages. The optional level 1, 2, 3, or 4
controls how verbosely the performance advisory messages are emitted. The higher
the level, the more messages are generated. Level 1 emits only the most important
messages, while level 4 emits all the messages. If the optional level is not specified, it
defaults to 2.
+Wv Option (New)
+Wv[d1,d2,...,dn]
The new +Wvoption displays the description for diagnostic message numbers
d1,d2,...,dn.
Specifying this option causes HP Code Advisor to emit the descriptive text for the
specified diagnostics to stderr. This option must not be used with any other compiler
options.
If the description for a diagnostic is not available, HP Code Advisor emits only the
diagnostic with a note that the description is not available.
+wlock Option (New)
+wlock
This option enables compile-time diagnostic messages for potential errors in using
lock/unlock calls in programs that use pthread library based lock/unlock functions.
Warnings are emitted for acquiring an already acquired lock, releasing an already
released lock, and unconditionally releasing a lock that has been conditionally acquired.
This diagnostic checking is based on cross-module analysis performed by the compiler.
Therefore, the +wlockoption implicitly enables a limited form of cross-module analysis,
even if -ipo or+O4options are not specified. This can lead to a significant increase in
the compile time compared to a build without the +wlockoption. Using this option
could result in the compiler invoking optimizations other than those that are part of
the user-specified optimization level. If +wlockis used in addition to -ipoor +O4, the
generated code is not affected, and the compile time does not increase much.
New Features in Version A.06.15 19