Very Slow Compilation under VS 2013 plus PSXE 2016

[Aboulghasem_K_]

Hi Steve,

I have to machines one with VS 2008 and Intel Parallel Studio XE 2013 and the other one with VS 2013 and Intel Parallel Studio XE 2016. When I compile identical Fortran codes in these two machines it takes about 4-5 minutes to be compiled in the first machine (i.e., with the old versions for both VS and Intel Fortran Compiler) whereas it takes about 5-6 hours in the second machine! I have checked the Intel Fortran compiler options in the two machines and it appears to me they are identical. I would appreciate it if you could help me to resolve this issue.

Thanks very much,

Aboulghasem

[Kevin_D_Intel]

Hi Aboulghasem - I separated your post from the earlier post to help us work your issue separately. Your issue also occurs on Windows not Linux so I relocated it to our Visual Fortran forum also.

As a first step, on the slow system can you please open a pre-initialized Visual Fortran command-prompt window using the VS2013 specific short-cut installed by our product. I do not know your OS, but those should be under an area like:

C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Intel Parallel Studio XE 2016\Compiler and Performance Libraries\Command Prompt with Intel Compiler 16.0

Under this command-prompt window, please set the environment variable INTEL_LMD_DEBUG to a file name. You can include a path component to say place it into a subfolder like C:\temp for example. Then just invoke ifort with no options. For example:

C:\temp> set INTEL_LMD_DEBUG=C:\temp\lmdout.txt
 
C:\temp> ifort
Intel(R) Visual Fortran Intel(R) 64 Compiler for applications running on Intel(R) 64, Version 16.0.0.110 Build 20150815
Copyright (C) 1985-2015 Intel Corporation.  All rights reserved.
 
ifort: command line error: no files specified; for help type "ifort /help"
 
C:\> dir  C:\temp\lmdout.txt
 Volume in drive C has no label.
 
 Directory of C:\temp
 
09/21/2015  02:51 AM             6,788 lmdout.txt
               1 File(s)          6,788 bytes

Please attach this file to a *private* reply to me only (using Send Author A Message). This file will contain sensitive information about your license that we do not want expose in the public forum.

Thank you.