HP aC++/HP C Programmer's Guide (B3901-90036; A.06.26; September 2011)
+Wwargs
+Wwarg1[,arg2,..,argn]
The +Wwargs option selectively treats compiler remarks or discretionary errors as
warnings. arg1 through argn are valid compiler message numbers. Conflicts between
+W, +Ww, and +We are resolved based on their severity. +We is the highest and +W is the
lowest.
+wlint
This option enables several warnings in the compiler that provide lint like functionality.
Checks are made for memory leaks, out-of-scope memory access, null pointer dereference,
and out-of-bounds access. These compile time diagnostics can be very useful in detecting
potential problems in the source code. To disable a specific warning introduced by
+wlint, a +Wargs option can be used after the +wlint option.
NOTE: The +wlint option is only supported on Itanium-based systems.
+Wmacro
+Wmacro:MACRONAME:d1,d2,...,dn
The +Wmacro option disables warning diagnostics d1,d2,...,dn in the expansion of
macro MACRONAME. If -1 is given as the warning number, then all warnings are
suppressed. This option is not applicable to warning numbers greater than 20000.
+Wmacro gets higher priority than the other diagnostic-control command-line options
that are applicable to the whole source. Diagnostic control pragmas take priority based
on where they are placed.
+wperfadvice
+wperfadvice[={1|2|3|4}]
The +wperfadvice 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 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.
+wsecurity
The +wsecurity option enables compile-time diagnostics for potential security violations.
Warnings are emitted for cases where untrusted (tainted) data may reach a critical
reference point in the program. This is based on cross-module analysis performed by the
compiler. Hence the +wsecurity option implicitly enables a limited form of cross-module
analysis, even if -ipo or +O4 options are not specified. This may lead to a significant
increase in the compile time compared to a build without the +wsecurity option. Using
this option may result in the compiler invoking optimizations other than those that are
46 Command-Line Options