Visible to Intel only — GUID: GUID-B4596977-3872-4FA2-80E8-28C01AF299FD
Visible to Intel only — GUID: GUID-B4596977-3872-4FA2-80E8-28C01AF299FD
diag-file, Qdiag-file
Causes the results of diagnostic analysis to be output to a file.
Syntax
Linux: |
-diag-file[=filename] |
macOS: |
None |
Windows: |
/Qdiag-file[:filename] |
Arguments
filename |
Is the name of the file for output. |
Default
OFF |
Diagnostic messages are output to stderr. |
Description
This option causes the results of diagnostic analysis to be output to a file. The file is placed in the current working directory.
You can include a file extension in filename. For example, if file.txt is specified, the name of the output file is file.txt. If you do not provide a file extension, the name of the file is filename.diag.
If filename is not specified, the name of the file is name-of-the-first-source-file.diag. This is also the name of the file if the name specified for file conflicts with a source file name provided in the command line.
If you specify the [Q]diag-file option and you also specify the [Q]diag-file-append option, the last option specified on the command line takes precedence.
IDE Equivalent
Visual Studio: Diagnostics > Diagnostics File
Diagnostics > Emit Diagnostics to File
Eclipse: Compilation Diagnostics > Diagnostics File
Xcode: Diagnostics > Diagnostics File, Diagnostics > Emit Diagnostics to File
Alternate Options
None
Example
The following example shows how to cause diagnostic analysis to be output to a file named my_diagnostics.diag:
-diag-file=my_diagnostics ! Linux systems /Qdiag-file:my_diagnostics ! Windows systems