Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Beginner
118 Views

another unable to start

Hi,

We've been having persistent 'unable to start' or can't find errors, even though the executable has been made and is correctly located.  The executable will not run stand alone; I suppose for wrong libraries??  Sometimes things are ok and then they switch back.  When not ok, debug version may run (incorrectly) but not release.  The forum seems to indicate this may be a PATH problem.  I'm using VS 15 & the latest Fortran 2019 update 1.  The software runs correctly on a laptop w/ very little on it.  I cannot seem to install Fortran on community VS 2017.  Don't really care.

Q1: Is there a tool in VS2015 to tell it where to look (like the one in Amplifier?)

Q2:  Here is my PATH; as far as I can tell, it seems benign and current.

Path=C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow;C:\Program Files (x86)\MSBuild\14.0\bin;C:\Program Files (x86)\MSBuild\14.0\bin;C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\;C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN\x86_amd64;C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN;C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Tools;C:\Windows\Microsoft.NET\Framework\v4.0.30319;C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\VCPackages;C:\Program Files (x86)\HTML Help Workshop;C:\Program Files (x86)\HTML Help Workshop;C:\Program Files (x86)\Microsoft Visual Studio 14.0\Team Tools\Performance Tools;C:\Program Files (x86)\Windows Kits\10\bin\x86;C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.6.1 Tools\;C:\Program Files (x86)\Intel\..\..\intel64\libfabric\bin\utils;C:\Program Files (x86)\Intel\..\..\intel64\libfabric\bin;C:\Program Files (x86)\Intel\..\..\intel64\bin\release;C:\Program Files (x86)\Intel\..\..\intel64\bin;C:\Program Files (x86)\IntelSWTools\Advisor 2019\bin32;C:\Program Files (x86)\IntelSWTools\VTune Amplifier 2019\bin32;C:\Program Files (x86)\IntelSWTools\Inspector 2019\bin32;C:\Program Files (x86)\IntelSWTools\compilers_and_libraries_2019.1.144\windows\mpi\intel64\bin;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Program Files (x86)\IntelSWTools\compilers_and_libraries_2018.2.185\windows\mpi\intel64\bin;C:\Program Files (x86)\IntelSWTools\compilers_and_libraries_2018.0.124\windows\mpi\intel64\bin;C:\Program Files (x86)\IntelSWTools\compilers_and_libraries_2017.4.210\windows\mpi\intel64\bin;C:\ProgramData\Oracle\Java\javapath;C:\Program Files (x86)\IntelSWTools\compilers_and_libraries_2018.0.065\windows\mpi\intel64\bin;C:\Program Files (x86)\IntelSWTools\compilers_and_libraries_2017.2.187\windows\mpi\intel64\bin;C:\Program Files (x86)\IntelSWTools\compilers_and_libraries_2017.0.109\windows\mpi\intel64\bin;C:\Program Files (x86)\Common Files\Intel\Shared Libraries\redist\intel64_win\mpirt;C:\Program Files (x86)\Common Files\Intel\Shared Libraries\redist\ia32_win\mpirt;C:\Program Files (x86)\Common Files\Intel\Shared Libraries\redist\intel64_win\compiler;C:\Program Files (x86)\Common Files\Intel\Shared Libraries\redist\ia32_win\compiler;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Windows\system32\config\systemprofile\.dnx\bin;C:\Program Files\Microsoft DNX\Dnvm\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files\SciTools\bin\pc-win64;d:\Program Files (x86)\IDM Computer Solutions\UEStudio;C:\Program Files (x86)\IDM Computer Solutions\UltraCompare;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;D:\Program Files\PuTTY\;C:\Program Files\dotnet\
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC

 

The main use of this computer is to compile & run my software in Fortran so I don't mind dumping anything that is causing a problem.

I just spent a week fooling with my code only to discover it is not the problem.  Most appreciative of any help in this regard.  thanks.

0 Kudos
90 Replies
Highlighted
Beginner
25 Views

mecej4:

I've started with NAG compiler testing.  It correctly finds the uninitialized variable of your test program during runtime.

0 Kudos
Highlighted
New Contributor II
25 Views

My old version of IVF (11.072) initialises x(:) to 0 in sub3(s), and therefore produces the intended answer.  gfortran does not initialise x(:) to 0, and therefore produces garbage.  It seems that Intel Fortran once did automatic initialisation, what is the current behaviour?

Neither compiler catches the uninitialised variables at runtime.  Tut tut.

0 Kudos
Highlighted
Beginner
25 Views

AARRGHHH! Now I've lost the ability to create a debug exe again!   Here is the end of the build log:

SASi2.8a - 0 error(s), 0 warning(s)

compiler:

/nologo /debug:full /Od /QxHost /Qparallel /heap-arrays0 /Qopenmp /warn:interfaces /Qopt-report:5 /Qguide:2 /Qguide-file:"x64\Debug\SASi2.8a.gap" /module:"x64\Debug\\" /object:"x64\Debug\\" /Fd"x64\Debug\vc140.pdb" /traceback /check:all /libs:dll /threads /dbglibs /4Yportlib /Qmkl:parallel /c

linker:

/OUT:"x64\Debug\SASi2.8a.exe" /INCREMENTAL:NO /NOLOGO /MANIFEST /MANIFESTFILE:"x64\Debug\SASi2.8a.exe.intermediate.manifest" /MANIFESTUAC:"level='asInvoker' uiAccess='false'" /DEBUG /PDB:"Q:\SASi\SASi.2.8a\SASi2.8a\SASi2.8a\x64\Debug\SASi2.8a.pdb" /SUBSYSTEM:CONSOLE /STACK:100000000 /IMPLIB:"Q:\SASi\SASi.2.8a\SASi2.8a\SASi2.8a\x64\Debug\SASi2.8a.lib"

But no .exe in x64\Debug\ .  Works ok in release.  It is like the linker is never invoked.  After I build, when I go to execute, says it needs to recompile, then it immediately says it can't find the executable (of course, it doesn't exit in the debug directory).  It seems the linker is not invoked.  Again seems to work in older directories. 

 

0 Kudos
Highlighted
Black Belt Retired Employee
25 Views

The linker may not be invoked if VS thinks the project is up to date. Please attach a zip of buildlog.htm. I also suggest you check your antivirus software to see if it treated the EXE as a virus - many do that for newly created EXEs.

0 Kudos
Highlighted
Beginner
25 Views

Hi Steve: The build log is at the top of my last post.  note my last paragraph, it recompiles (or tries to) but doesn't link.

0 Kudos
Highlighted
Black Belt Retired Employee
25 Views

That's not the build log - maybe pieces of it. I want to see the whole thing.

0 Kudos
Highlighted
Beginner
25 Views

that's the whole thing.  Another clue to the problem but I don't know how to interpret it.

0 Kudos
Highlighted
Beginner
25 Views

here is the output window:

Q:\SASi\SASi.2.8a\SASi2.8a\SASi2.8a\mkl_vsl.f90 : warning: Module 'x64\Debug\mkl_vsl.mod' is created by both 'Q:\SASi\SASi.2.8a\SASi2.8a\SASi2.8a\mkl_vsl.f90' and 'Q:\SASi\SASi.2.8a\SASi2.8a\SASi2.8a\mkl_include_file.f90'.
Q:\SASi\SASi.2.8a\SASi2.8a\SASi2.8a\mkl_vsl.f90 : warning: Module 'x64\Debug\mkl_vsl_type.mod' is created by both 'Q:\SASi\SASi.2.8a\SASi2.8a\SASi2.8a\mkl_vsl.f90' and 'Q:\SASi\SASi.2.8a\SASi2.8a\SASi2.8a\mkl_include_file.f90'.
1>------ Build started: Project: SASi2.8a, Configuration: Debug x64 ------
1>Compiling with Intel(R) Visual Fortran Compiler 19.0.1.144 [Intel(R) 64]...
1>Tattles.f90
1>mkl_include_file.f90
1>ifort: remark #10397: optimization reports are generated in *.optrpt files in the output location
1>ifort: command line warning #10327: '/Qguide' requires an optimization level of '/O2' or higher; ignoring
1>SASiCommons_module_h.f90
1>ifort: remark #10397: optimization reports are generated in *.optrpt files in the output location
1>ifort: command line warning #10327: '/Qguide' requires an optimization level of '/O2' or higher; ignoring
1>H_module.f90
1>ifort: remark #10397: optimization reports are generated in *.optrpt files in the output location
1>ifort: command line warning #10327: '/Qguide' requires an optimization level of '/O2' or higher; ignoring
1>Star_atm_info_module_h.f90
1>ifort: remark #10397: optimization reports are generated in *.optrpt files in the output location
1>ifort: command line warning #10327: '/Qguide' requires an optimization level of '/O2' or higher; ignoring
1>Gaussian_module.f90
1>ifort: remark #10397: optimization reports are generated in *.optrpt files in the output location
1>ifort: command line warning #10327: '/Qguide' requires an optimization level of '/O2' or higher; ignoring
1>Randombw_module.f90
1>ifort: remark #10397: optimization reports are generated in *.optrpt files in the output location
1>ifort: command line warning #10327: '/Qguide' requires an optimization level of '/O2' or higher; ignoring
1>ConOpacity_module.f90
1>ifort: remark #10397: optimization reports are generated in *.optrpt files in the output location
1>ifort: command line warning #10327: '/Qguide' requires an optimization level of '/O2' or higher; ignoring
1>Star_ln_info_module_h.f90
1>ifort: remark #10397: optimization reports are generated in *.optrpt files in the output location
1>ifort: command line warning #10327: '/Qguide' requires an optimization level of '/O2' or higher; ignoring
1>Pst_module_h.f90
1>ifort: remark #10397: optimization reports are generated in *.optrpt files in the output location
1>ifort: command line warning #10327: '/Qguide' requires an optimization level of '/O2' or higher; ignoring
1>Collpho_module_h.f90
1>ifort: remark #10397: optimization reports are generated in *.optrpt files in the output location
1>ifort: command line warning #10327: '/Qguide' requires an optimization level of '/O2' or higher; ignoring
1>Q:\SASi\SASi.2.8a\SASi2.8a\SASi2.8a\Collpho_module_h.f90(383): warning #6843: A dummy argument with an explicit INTENT(OUT) declaration is not given an explicit value.   [THETA]
1>SASi.2.8.8.f90
1>ifort: remark #10397: optimization reports are generated in *.optrpt files in the output location
1>ifort: command line warning #10327: '/Qguide' requires an optimization level of '/O2' or higher; ignoring
1>
1>Build log written to  "file://Q:\SASi\SASi.2.8a\SASi2.8a\SASi2.8a\x64\Debug\BuildLog.htm"
1>SASi2.8a - 0 error(s), 12 warning(s)
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========

 

It is the same as the build log:

Compiling with Intel(R) Visual Fortran Compiler 19.0.1.144 [Intel(R) 64]... ifort /nologo /debug:full /Od /QxHost /Qparallel /heap-arrays0 /Qopenmp /warn:interfaces /Qopt-report:5 /Qopt-report-file /Qguide:2 /Qguide-file /Qguide-file:"x64\Debug\SASi2.8a.gap" /module:"x64\Debug\\" /object:"x64\Debug\\" /Fd"x64\Debug\vc140.pdb" /traceback /check:all /libs:dll /threads /dbglibs /4Yportlib /Qmkl:parallel /c /Qopt-report-format:vs /Qlocation,link,"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\\bin\amd64" /Qm64 "Q:\SASi\SASi.2.8a\SASi2.8a\SASi2.8a\Tattles.f90" ifort /nologo /debug:full /Od /QxHost /Qparallel /heap-arrays0 /Qopenmp /warn:interfaces /Qopt-report:5 /Qguide:2 /Qguide-file:"x64\Debug\SASi2.8a.gap" /module:"x64\Debug\\" /object:"x64\Debug\\" /Fd"x64\Debug\vc140.pdb" /traceback /check:all /libs:dll /threads /dbglibs /4Yportlib /Qmkl:parallel /c /Qopt-report-format:vs /Qlocation,link,"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\\bin\amd64" /Qm64 "Q:\SASi\SASi.2.8a\SASi2.8a\SASi2.8a\mkl_include_file.f90" ifort: remark #10397: optimization reports are generated in *.optrpt files in the output location ifort: command line warning #10327: '/Qguide' requires an optimization level of '/O2' or higher; ignoring ifort /nologo /debug:full /Od /QxHost /Qparallel /heap-arrays0 /Qopenmp /warn:interfaces /Qopt-report:5 /Qguide:2 /Qguide-file:"x64\Debug\SASi2.8a.gap" /module:"x64\Debug\\" /object:"x64\Debug\\" /Fd"x64\Debug\vc140.pdb" /traceback /check:all /libs:dll /threads /dbglibs /4Yportlib /Qmkl:parallel /c /Qopt-report-format:vs /Qlocation,link,"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\\bin\amd64" /Qm64 "Q:\SASi\SASi.2.8a\SASi2.8a\SASi2.8a\SASiCommons_module_h.f90" ifort: remark #10397: optimization reports are generated in *.optrpt files in the output location ifort: command line warning #10327: '/Qguide' requires an optimization level of '/O2' or higher; ignoring ifort /nologo /debug:full /Od /QxHost /Qparallel /heap-arrays0 /Qopenmp /warn:interfaces /Qopt-report:5 /Qguide:2 /Qguide-file:"x64\Debug\SASi2.8a.gap" /module:"x64\Debug\\" /object:"x64\Debug\\" /Fd"x64\Debug\vc140.pdb" /traceback /check:all /libs:dll /threads /dbglibs /4Yportlib /Qmkl:parallel /c /Qopt-report-format:vs /Qlocation,link,"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\\bin\amd64" /Qm64 "Q:\SASi\SASi.2.8a\SASi2.8a\SASi2.8a\H_module.f90" ifort: remark #10397: optimization reports are generated in *.optrpt files in the output location ifort: command line warning #10327: '/Qguide' requires an optimization level of '/O2' or higher; ignoring ifort /nologo /debug:full /Od /QxHost /Qparallel /heap-arrays0 /Qopenmp /warn:interfaces /Qopt-report:5 /Qguide:2 /Qguide-file:"x64\Debug\SASi2.8a.gap" /module:"x64\Debug\\" /object:"x64\Debug\\" /Fd"x64\Debug\vc140.pdb" /traceback /check:all /libs:dll /threads /dbglibs /4Yportlib /Qmkl:parallel /c /Qopt-report-format:vs /Qlocation,link,"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\\bin\amd64" /Qm64 "Q:\SASi\SASi.2.8a\SASi2.8a\SASi2.8a\Star_atm_info_module_h.f90" ifort: remark #10397: optimization reports are generated in *.optrpt files in the output location ifort: command line warning #10327: '/Qguide' requires an optimization level of '/O2' or higher; ignoring ifort /nologo /debug:full /Od /QxHost /Qparallel /heap-arrays0 /Qopenmp /warn:interfaces /Qopt-report:5 /Qguide:2 /Qguide-file:"x64\Debug\SASi2.8a.gap" /module:"x64\Debug\\" /object:"x64\Debug\\" /Fd"x64\Debug\vc140.pdb" /traceback /check:all /libs:dll /threads /dbglibs /4Yportlib /Qmkl:parallel /c /Qopt-report-format:vs /Qlocation,link,"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\\bin\amd64" /Qm64 "Q:\SASi\SASi.2.8a\SASi2.8a\SASi2.8a\Gaussian_module.f90" ifort: remark #10397: optimization reports are generated in *.optrpt files in the output location ifort: command line warning #10327: '/Qguide' requires an optimization level of '/O2' or higher; ignoring ifort /nologo /debug:full /Od /QxHost /Qparallel /heap-arrays0 /Qopenmp /warn:interfaces /Qopt-report:5 /Qguide:2 /Qguide-file:"x64\Debug\SASi2.8a.gap" /module:"x64\Debug\\" /object:"x64\Debug\\" /Fd"x64\Debug\vc140.pdb" /traceback /check:all /libs:dll /threads /dbglibs /4Yportlib /Qmkl:parallel /c /Qopt-report-format:vs /Qlocation,link,"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\\bin\amd64" /Qm64 "Q:\SASi\SASi.2.8a\SASi2.8a\SASi2.8a\Randombw_module.f90" ifort: remark #10397: optimization reports are generated in *.optrpt files in the output location ifort: command line warning #10327: '/Qguide' requires an optimization level of '/O2' or higher; ignoring ifort /nologo /debug:full /Od /QxHost /Qparallel /heap-arrays0 /Qopenmp /warn:interfaces /Qopt-report:5 /Qguide:2 /Qguide-file:"x64\Debug\SASi2.8a.gap" /module:"x64\Debug\\" /object:"x64\Debug\\" /Fd"x64\Debug\vc140.pdb" /traceback /check:all /libs:dll /threads /dbglibs /4Yportlib /Qmkl:parallel /c /Qopt-report-format:vs /Qlocation,link,"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\\bin\amd64" /Qm64 "Q:\SASi\SASi.2.8a\SASi2.8a\SASi2.8a\ConOpacity_module.f90" ifort: remark #10397: optimization reports are generated in *.optrpt files in the output location ifort: command line warning #10327: '/Qguide' requires an optimization level of '/O2' or higher; ignoring ifort /nologo /debug:full /Od /QxHost /Qparallel /heap-arrays0 /Qopenmp /warn:interfaces /Qopt-report:5 /Qguide:2 /Qguide-file:"x64\Debug\SASi2.8a.gap" /module:"x64\Debug\\" /object:"x64\Debug\\" /Fd"x64\Debug\vc140.pdb" /traceback /check:all /libs:dll /threads /dbglibs /4Yportlib /Qmkl:parallel /c /Qopt-report-format:vs /Qlocation,link,"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\\bin\amd64" /Qm64 "Q:\SASi\SASi.2.8a\SASi2.8a\SASi2.8a\Star_ln_info_module_h.f90" ifort: remark #10397: optimization reports are generated in *.optrpt files in the output location ifort: command line warning #10327: '/Qguide' requires an optimization level of '/O2' or higher; ignoring ifort /nologo /debug:full /Od /QxHost /Qparallel /heap-arrays0 /Qopenmp /warn:interfaces /Qopt-report:5 /Qguide:2 /Qguide-file:"x64\Debug\SASi2.8a.gap" /module:"x64\Debug\\" /object:"x64\Debug\\" /Fd"x64\Debug\vc140.pdb" /traceback /check:all /libs:dll /threads /dbglibs /4Yportlib /Qmkl:parallel /c /Qopt-report-format:vs /Qlocation,link,"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\\bin\amd64" /Qm64 "Q:\SASi\SASi.2.8a\SASi2.8a\SASi2.8a\Pst_module_h.f90" ifort: remark #10397: optimization reports are generated in *.optrpt files in the output location ifort: command line warning #10327: '/Qguide' requires an optimization level of '/O2' or higher; ignoring ifort /nologo /debug:full /Od /QxHost /Qparallel /heap-arrays0 /Qopenmp /warn:interfaces /Qopt-report:5 /Qguide:2 /Qguide-file:"x64\Debug\SASi2.8a.gap" /module:"x64\Debug\\" /object:"x64\Debug\\" /Fd"x64\Debug\vc140.pdb" /traceback /check:all /libs:dll /threads /dbglibs /4Yportlib /Qmkl:parallel /c /Qopt-report-format:vs /Qlocation,link,"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\\bin\amd64" /Qm64 "Q:\SASi\SASi.2.8a\SASi2.8a\SASi2.8a\Collpho_module_h.f90" ifort: remark #10397: optimization reports are generated in *.optrpt files in the output location ifort: command line warning #10327: '/Qguide' requires an optimization level of '/O2' or higher; ignoring Q:\SASi\SASi.2.8a\SASi2.8a\SASi2.8a\Collpho_module_h.f90(383): warning #6843: A dummy argument with an explicit INTENT(OUT) declaration is not given an explicit value. [THETA] subroutine collpho2(ln,z,theta,lam,rng) -------------------------^ ifort /nologo /debug:full /Od /QxHost /Qparallel /heap-arrays0 /Qopenmp /warn:interfaces /Qopt-report:5 /Qguide:2 /Qguide-file:"x64\Debug\SASi2.8a.gap" /module:"x64\Debug\\" /object:"x64\Debug\\" /Fd"x64\Debug\vc140.pdb" /traceback /check:all /libs:dll /threads /dbglibs /4Yportlib /Qmkl:parallel /c /Qopt-report-format:vs /Qlocation,link,"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\\bin\amd64" /Qm64 "Q:\SASi\SASi.2.8a\SASi2.8a\SASi2.8a\SASi.2.8.8.f90" ifort: remark #10397: optimization reports are generated in *.optrpt files in the output location ifort: command line warning #10327: '/Qguide' requires an optimization level of '/O2' or higher; ignoring SASi2.8a - 0 error(s), 12 warning(s)

For comparison, here is the release build log for exactly the same code:

Compiling with Intel(R) Visual Fortran Compiler 19.0.1.144 [Intel(R) 64]... ifort /nologo /debug:full /O2 /QxHost /Qparallel /heap-arrays0 /Qopenmp /Qopt-report:5 /align:rec16byte /align:zcommons /align:array256byte /module:"x64\Release\\" /object:"x64\Release\\" /Fd"x64\Release\vc140.pdb" /check:uninit /libs:dll /threads /4Yportlib /Qmkl:parallel /c /Qopt-report-format:vs /Qlocation,link,"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\\bin\amd64" /Qm64 "Q:\SASi\SASi.2.8a\SASi2.8a\SASi2.8a\Tattles.f90" ifort: remark #10397: optimization reports are generated in *.optrpt files in the output location ifort /nologo /debug:full /O2 /QxHost /Qparallel /heap-arrays0 /Qopenmp /Qopt-report:5 /align:rec16byte /align:zcommons /align:array256byte /module:"x64\Release\\" /object:"x64\Release\\" /Fd"x64\Release\vc140.pdb" /check:uninit /libs:dll /threads /4Yportlib /Qmkl:parallel /c /Qopt-report-format:vs /Qlocation,link,"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\\bin\amd64" /Qm64 "Q:\SASi\SASi.2.8a\SASi2.8a\SASi2.8a\mkl_include_file.f90" ifort: remark #10397: optimization reports are generated in *.optrpt files in the output location ifort /nologo /debug:full /O2 /QxHost /Qparallel /heap-arrays0 /Qopenmp /Qopt-report:5 /align:rec16byte /align:zcommons /align:array256byte /module:"x64\Release\\" /object:"x64\Release\\" /Fd"x64\Release\vc140.pdb" /check:uninit /libs:dll /threads /4Yportlib /Qmkl:parallel /c /Qopt-report-format:vs /Qlocation,link,"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\\bin\amd64" /Qm64 "Q:\SASi\SASi.2.8a\SASi2.8a\SASi2.8a\SASiCommons_module_h.f90" ifort: remark #10397: optimization reports are generated in *.optrpt files in the output location ifort /nologo /debug:full /O2 /QxHost /Qparallel /heap-arrays0 /Qopenmp /Qopt-report:5 /align:rec16byte /align:zcommons /align:array256byte /module:"x64\Release\\" /object:"x64\Release\\" /Fd"x64\Release\vc140.pdb" /check:uninit /libs:dll /threads /4Yportlib /Qmkl:parallel /c /Qopt-report-format:vs /Qlocation,link,"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\\bin\amd64" /Qm64 "Q:\SASi\SASi.2.8a\SASi2.8a\SASi2.8a\H_module.f90" ifort: remark #10397: optimization reports are generated in *.optrpt files in the output location ifort /nologo /debug:full /O2 /QxHost /Qparallel /heap-arrays0 /Qopenmp /Qopt-report:5 /align:rec16byte /align:zcommons /align:array256byte /module:"x64\Release\\" /object:"x64\Release\\" /Fd"x64\Release\vc140.pdb" /check:uninit /libs:dll /threads /4Yportlib /Qmkl:parallel /c /Qopt-report-format:vs /Qlocation,link,"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\\bin\amd64" /Qm64 "Q:\SASi\SASi.2.8a\SASi2.8a\SASi2.8a\Star_atm_info_module_h.f90" ifort: remark #10397: optimization reports are generated in *.optrpt files in the output location ifort /nologo /debug:full /O2 /QxHost /Qparallel /heap-arrays0 /Qopenmp /Qopt-report:5 /align:rec16byte /align:zcommons /align:array256byte /module:"x64\Release\\" /object:"x64\Release\\" /Fd"x64\Release\vc140.pdb" /check:uninit /libs:dll /threads /4Yportlib /Qmkl:parallel /c /Qopt-report-format:vs /Qlocation,link,"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\\bin\amd64" /Qm64 "Q:\SASi\SASi.2.8a\SASi2.8a\SASi2.8a\Gaussian_module.f90" ifort: remark #10397: optimization reports are generated in *.optrpt files in the output location ifort /nologo /debug:full /O2 /QxHost /Qparallel /heap-arrays0 /Qopenmp /Qopt-report:5 /align:rec16byte /align:zcommons /align:array256byte /module:"x64\Release\\" /object:"x64\Release\\" /Fd"x64\Release\vc140.pdb" /check:uninit /libs:dll /threads /4Yportlib /Qmkl:parallel /c /Qopt-report-format:vs /Qlocation,link,"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\\bin\amd64" /Qm64 "Q:\SASi\SASi.2.8a\SASi2.8a\SASi2.8a\Randombw_module.f90" ifort: remark #10397: optimization reports are generated in *.optrpt files in the output location ifort /nologo /debug:full /O2 /QxHost /Qparallel /heap-arrays0 /Qopenmp /Qopt-report:5 /align:rec16byte /align:zcommons /align:array256byte /module:"x64\Release\\" /object:"x64\Release\\" /Fd"x64\Release\vc140.pdb" /check:uninit /libs:dll /threads /4Yportlib /Qmkl:parallel /c /Qopt-report-format:vs /Qlocation,link,"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\\bin\amd64" /Qm64 "Q:\SASi\SASi.2.8a\SASi2.8a\SASi2.8a\ConOpacity_module.f90" ifort: remark #10397: optimization reports are generated in *.optrpt files in the output location ifort /nologo /debug:full /O2 /QxHost /Qparallel /heap-arrays0 /Qopenmp /Qopt-report:5 /align:rec16byte /align:zcommons /align:array256byte /module:"x64\Release\\" /object:"x64\Release\\" /Fd"x64\Release\vc140.pdb" /check:uninit /libs:dll /threads /4Yportlib /Qmkl:parallel /c /Qopt-report-format:vs /Qlocation,link,"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\\bin\amd64" /Qm64 "Q:\SASi\SASi.2.8a\SASi2.8a\SASi2.8a\Star_ln_info_module_h.f90" ifort: remark #10397: optimization reports are generated in *.optrpt files in the output location ifort /nologo /debug:full /O2 /QxHost /Qparallel /heap-arrays0 /Qopenmp /Qopt-report:5 /align:rec16byte /align:zcommons /align:array256byte /module:"x64\Release\\" /object:"x64\Release\\" /Fd"x64\Release\vc140.pdb" /check:uninit /libs:dll /threads /4Yportlib /Qmkl:parallel /c /Qopt-report-format:vs /Qlocation,link,"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\\bin\amd64" /Qm64 "Q:\SASi\SASi.2.8a\SASi2.8a\SASi2.8a\Pst_module_h.f90" ifort: remark #10397: optimization reports are generated in *.optrpt files in the output location ifort /nologo /debug:full /O2 /QxHost /Qparallel /heap-arrays0 /Qopenmp /Qopt-report:5 /align:rec16byte /align:zcommons /align:array256byte /module:"x64\Release\\" /object:"x64\Release\\" /Fd"x64\Release\vc140.pdb" /check:uninit /libs:dll /threads /4Yportlib /Qmkl:parallel /c /Qopt-report-format:vs /Qlocation,link,"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\\bin\amd64" /Qm64 "Q:\SASi\SASi.2.8a\SASi2.8a\SASi2.8a\Collpho_module_h.f90" ifort: remark #10397: optimization reports are generated in *.optrpt files in the output location Q:\SASi\SASi.2.8a\SASi2.8a\SASi2.8a\Collpho_module_h.f90(383): warning #6843: A dummy argument with an explicit INTENT(OUT) declaration is not given an explicit value. [THETA] subroutine collpho2(ln,z,theta,lam,rng) -------------------------^ ifort /nologo /debug:full /O2 /QxHost /Qparallel /heap-arrays0 /Qopenmp /Qopt-report:5 /align:rec16byte /align:zcommons /align:array256byte /module:"x64\Release\\" /object:"x64\Release\\" /Fd"x64\Release\vc140.pdb" /check:uninit /libs:dll /threads /4Yportlib /Qmkl:parallel /c /Qopt-report-format:vs /Qlocation,link,"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\\bin\amd64" /Qm64 "Q:\SASi\SASi.2.8a\SASi2.8a\SASi2.8a\SASi.2.8.8.f90" ifort: remark #10397: optimization reports are generated in *.optrpt files in the output location Linking... Link /OUT:"x64\Release\SASi2.8a.exe" /INCREMENTAL:NO /NOLOGO /MANIFEST /MANIFESTFILE:"x64\Release\SASi2.8a.exe.intermediate.manifest" /MANIFESTUAC:"level='asInvoker' uiAccess='false'" /SUBSYSTEM:CONSOLE /LARGEADDRESSAWARE /IMPLIB:"Q:\SASi\SASi.2.8a\SASi2.8a\SASi2.8a\x64\Release\SASi2.8a.lib" -qm64 /qoffload-ldopts="-mkl=parallel" "x64\Release\Tattles.obj" "x64\Release\mkl_include_file.obj" "x64\Release\SASiCommons_module_h.obj" "x64\Release\H_module.obj" "x64\Release\Star_atm_info_module_h.obj" "x64\Release\Gaussian_module.obj" "x64\Release\Randombw_module.obj" "x64\Release\ConOpacity_module.obj" "x64\Release\Star_ln_info_module_h.obj" "x64\Release\Pst_module_h.obj" "x64\Release\Collpho_module_h.obj" "x64\Release\SASi.2.8.8.obj" Embedding manifest... mt.exe /nologo /outputresource:"Q:\SASi\SASi.2.8a\SASi2.8a\SASi2.8a\x64\Release\SASi2.8a.exe;#1" /manifest "x64\Release\SASi2.8a.exe.intermediate.manifest" SASi2.8a - 0 error(s), 1 warning(s)

 

This is why I included the release and debug command lines.  I can only guess it has something to do with them.

0 Kudos
Highlighted
Black Belt Retired Employee
25 Views

Please ZIP the Debug buildlog.htm and attach it to a reply here. I am not interested in the contents of the output window.

0 Kudos
Highlighted
Beginner
25 Views

yeah, it is hard to read all run together.  I didn't know it would be easier in a zip file.

0 Kudos
Highlighted
Black Belt Retired Employee
25 Views

Ok, that helps. I see you are using /Qguide - that's no longer supported and you should remove that (and /Qguide-file) from your options.

Would you please attach the .vfproj file for this project?

0 Kudos
Highlighted
Beginner
25 Views

sure

0 Kudos
Highlighted
Black Belt Retired Employee
25 Views

It is indeed the setting for Guided Auto Parallel that is blocking linking. Now that I recall, if you had this enabled it would compile only, not linking. In the project properties, go to Diagnostics and set Guided Auto Parallelism to Disable.

I thought this feature was deleted but it's just "deprecated".

0 Kudos
Highlighted
Beginner
25 Views

Hi Steve: That solved that problem.  I'll check with the other fellow who is having similar problems & see if that is his problem, too.

0 Kudos
Highlighted
Beginner
25 Views

Hi to all who commented on my issues,

After a few months of thrashing (with some interruptions), I now have what appears to be stable code that I can proceed to develop with.  The last piece was an error in understanding/remembering a result in my regression testing.  It was a mishmash of issues, none of which turned out to be the highly suspect uninitialized variable error.  NAG identified a couple but they were inconsequential.  The regression error was not properly testing across different machines.  While the code, after Steve pointed out some of the really annoying aspects of the compiler configuration and path issues, works correctly on my Intel E5 machine, it does not on my i7-6950X, on which I was doing my development.  Fortran 2019 v3 on the I7 machine fails on the identical source and configuration parameters that works on the older E5 machine.  I thought I had tested that but apparently I was wrong.

This was complicated by the Heap arrays compilation parameter default being blank rather than zero, the stack size that cannot be set within 5% or so of the maximum, the failure of the install to set the path for the mkl libraries, and the Guided Auto Parallel issue -- all discussed by Steve above.  There were some more as well.  I think these issues should be addressed with warnings, at least, probably where possible in the notes that appear at the bottom of the properties pages when an option is highlighted.  At least in the compiler manual, where many of the descriptions are so barebones all you can fathom is that invoking it will cause the compiler to do it whatever it is.  These compiler option bugs should just plain be fixed.  Although I've written a couple of simple interpreters, I don't know anything about the internals of serious compilers but I've never before (since the 1960s) used a compiler with so many bugs/traps in the options. (with the possible exception of a GE 605 which was weird in many possible ways). 

Converting to NAG was harder than expected as several Intel non-standard capabilities had crept in, in particular conditional compilation meta-commands and the statistical package of the MKL which we used because the code is very sensitive to the quality of the random number generator(s).  Basically, I want to write fairly complicated astrophysics code, not become an expert in the idiosyncrasies of the compiler and its options.  It is hard enough to get my physics right; it is much harder if I don't trust the compiler!

Anyway, thanks to all that chimed in, especially Steve; I'm sure I'll be back

--Bruce

 

0 Kudos
Highlighted
25 Views

Bruce,

I wish to thank you for taking the time to write your final feedback. Too often is the case that once a problem is solve, we get no response back, or too little feedback, from the person having the problem. Thank you.

BTW if you need someone to review and/or comment on your astrophysics code, I'd be willing to help. You can send me a private message to get contact information. The simulation package I've developed, which was based on an excellent but old F77 model, now is more modern F90, fully parallelized (OpenMP), visualization package, and has integrated the JPL SPICE mission data files which are used to populate the initial data for planetary/satellites/asteroids. The simulation from that point advances the states of the planetary bodies as well as the things I am modeling. My research area wasn't specifically about planetary bodies, but rather about the dynamics of tethers. Think of Space Elevator and the issues of how to deploy them. This model, is capable of factoring in the light speed travel time of gravitational influences (assuming gravity waves/flux propagate at light speed). While I am not suggesting you use this model, I may have some insight as to how you can implement equivalent functionality in your code.

Jim Dempsey

0 Kudos
Highlighted
Black Belt Retired Employee
25 Views

Jim, Bruce can't send you a private message unless you send him one first. As a "Black Belt", you have that privilege, but Bruce does not.

0 Kudos
Highlighted
25 Views

Thanks Steve, I now notice that I cannot sent private message either. That appears to have changed.

Jim

0 Kudos
Highlighted
25 Views

Bruce,

Are you William Bruce Weaver at Monterey?

Jim Dempsey

0 Kudos
Highlighted
Beginner
25 Views

yes

0 Kudos