Controls the display of diagnostic information.
Windows: Diagnostics > Disable Specific Diagnostics (/Qdiag-disable:id)
Diagnostics > Level of Static Security Analysis (/Qdiag-enable:sc{1|2|3} )
Linux: Compilation Diagnostics > Disable Specific Diagnostics (-diag-disable id)
Compilation Diagnostics > Level of Static Security Analysis (-diag-enable sc{1|2|3} or -diag-disable sv)
Mac OS X: Diagnostics > Disable Specific Diagnostics (-diag-disable id)
Diagnostics > Level of Static Security Analysis (-diag-enable [sc1,sc2,sc3])
IA-32, Intel® 64 architectures
Linux and Mac OS X: | -diag-type diag-list |
Windows: | /Qdiag-type:diag-list |
type |
Is an action to perform on diagnostics. Possible values are:
|
||||||||||||||||||||||||||||
diag-list |
Is a diagnostic group or ID value. Possible values are:
The diagnostic messages generated can be affected by certain options, such as /arch or /Qx (Windows) or -m or -x (Linux and Mac OS X). |
OFF |
The compiler issues certain diagnostic messages by default. |
This option controls the display of diagnostic information. Diagnostic messages are output to stderr unless compiler option -diag-file (Linux* and Mac OS* X) or /Qdiag-file (Windows*) is specified.
When diag-list value "warn" is used with static security analysis diagnostics, the following behavior occurs:
Option -diag-enable warn (Linux) and /Qdiag-enable:warn (Windows) enable all diagnostics except those that have an "error" severity level. They enable all static security analysis warnings, cautions, and remarks.
Option -diag-disable warn (Linux) and /Qdiag-disable:warn (Windows) disable all static security analysis diagnostics except those that have an "error" severity level. They suppress all static security analysis warnings, cautions, and remarks.
The following table shows more information on values you can specify for diag-list item sc.
diag-list Item |
Description |
|
---|---|---|
sc[n] |
The value of n for static security analysis messages can be any of the following: |
|
1 |
Produces the diagnostics with severity level set to all critical errors. | |
2 |
Produces the diagnostics with severity level set to all errors. This is the default if n is not specified. | |
3 |
Produces the diagnostics with severity level set to all errors and warnings. |
To disable static security analysis, specify /Qdiag-disable:sc (Windows) or option -diag-disable sc (Linux and Mac OS X).
To control the diagnostic information reported by the vectorizer, use the -vec-report (Linux and Mac OS X) or /Qvec-report (Windows) option.
To control the diagnostic information reported by the auto-parallelizer, use the -par-report (Linux and Mac OS X) or /Qpar-report (Windows) option.
enable vec |
Linux and Mac OS X: -vec-report Windows: /Qvec-report |
disable vec |
Linux and Mac OS X: -vec-report0 Windows: /Qvec-report0 |
enable par |
Linux and Mac OS X: -par-report Windows: /Qpar-report |
disable par |
Linux and Mac OS X: -par-report0 Windows: /Qpar-report0 |
The following example shows how to enable diagnostic IDs 117, 230 and 450:
-diag-enable 117,230,450 ! Linux and Mac OS X systems
/Qdiag-enable:117,230,450 ! Windows systems
The following example shows how to change vectorizer diagnostic messages to warnings:
-diag-enable vec -diag-warning vec ! Linux and Mac OS X systems
/Qdiag-enable:vec /Qdiag-warning:vec ! Windows systems
Note that you need to enable the vectorizer diagnostics before you can change them to warnings.
The following example shows how to disable all auto-parallelizer diagnostic messages:
-diag-disable par ! Linux and Mac OS X systems
/Qdiag-disable:par ! Windows systems
The following example shows how to produce static security analysis diagnostic messages for all critical errors:
-diag-enable sc1 ! Linux and Mac OS X systems
/Qdiag-enable:sc1 ! Windows system
The following example shows how to cause static security analysis diagnostics (and default diagnostics) to be sent to a file:
-diag-enable sc -diag-file=stat_ver_msg ! Linux and Mac OS X systems
/Qdiag-enable:sc /Qdiag-file:stat_ver_msg ! Windows systems
Note that you need to enable static security analysis diagnostics before you can send them to a file. In this case, the diagnostics are sent to file stat_ver_msg.diag. If a file name is not specified, the diagnostics are sent to name-of-the-first-source-file.diag.
The following example shows how to change all diagnostic warnings and remarks to errors:
-diag-error warn,remark ! Linux and Mac OS X systems
/Qdiag-error:warn,remark ! Windows systems
Copyright © 1996-2011, Intel Corporation. All rights reserved.