Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
29276 Discussions

Missing executable and other build files

Glenn1
Beginner
889 Views

I'm using Intel Visual Fortran Compiler XE 12.0.2.154 [IA-32] to build a test solution called Parallel_Test on a Windows 7 64-bit system.I've set up a very simple program to start playing around with OpenMp commands.I can build the solution in Debug & Release, 32-bit and 64-bit modes (compile, link, and create the executable) successfully. The build files (BuildLog.htm, Parallel_Test.exe, Parallel_Test.intermediate.manifest, and Parallel_Test.obj) are present in the appropriate folders such as "Release"for 32-bit asI expected them to be.

However, if I go to the Project Properties, Fortran, Diagnosticsand change the "Guided Auto Parallelism Analysis" from "Disable" to "Simple (/Qguide:1)" and "Emit Guided Auto Parallelism Diagnostics to File" from "No" to "Yes (/Qguide-file) and then rebuild the solution, it rebuildssuccessfully butonly the updated "BuildLog.htm" file and the "Parallel_Test.gap" files are present. All of the other build filesdisappear (manifest, .obj, & .exe). I performed a search of the disk to see if they were created elsewhere in an unknown location but they do not exist. If I set the switch back to "Disable" and rebuild the solution then all of the files reappear. It seems that only the "Guided Auto Parallelism Analysis" switch is affecting the outcome.

I've experienced this behavior one other time unrelated to parallel commands/switches but did not pursue it to determine what property may have caused it to occur. I've added the project file.

Any thoughts?

Thanks!
Glenn.

0 Kudos
1 Solution
IanH
Honored Contributor III
889 Views
I believe this is by design. When /Qguide and friends are present on the command line no executable files are generated. The output of the compilation process is the diagnostic report.

View solution in original post

0 Kudos
3 Replies
IanH
Honored Contributor III
890 Views
I believe this is by design. When /Qguide and friends are present on the command line no executable files are generated. The output of the compilation process is the diagnostic report.
0 Kudos
Steven_L_Intel1
Employee
889 Views
Ian is correct. /Qguide and /Qdiag-enable:sc are like this.
0 Kudos
Glenn1
Beginner
889 Views
Thanks Ian & Steve. I had overlooked that point as I was reading the documentation.
0 Kudos
Reply