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

Intel fortran link problem

MXG
New Contributor I
568 Views

Hi,

 

When we try to link a FORTRAN program with the Intel linker - we get this:

 Compiling with Intel® Fortran Compiler 2023.1.0 [Intel(R) 64]... ifx /nologo /debug:full /Od /I"D:\work_area\ISIS\OneDrive_2023-05-03\ISIS may 2\fftpack\obj\x64\Release" /DDEBUG /D_LARGEFILE_SOURCE /D_FILE_OFFSET_BITS=64 /DTIMING /DMKL_FFT /DMKL_EXP /DMKL_SINCI /DASYNCH_IO /Qopenmp /standard-semantics /debug-parameters:all /module:"obj\x64\Debug\\" /object:"obj\x64\Debug\\" /Fd"obj\x64\Debug\dll_pgorm.pdb" /traceback /check:all /libs:static /threads /Qmkl:sequential /c /F80000000 /recursive /Qlocation,link,"C:\Program Files\Microsoft Visual Studio\2022\Enterprise\VC\Tools\MSVC\14.31.31103\bin\HostX64\x64" /Qm64 "D:\work_area\ISIS\OneDrive_2023-05-03\ISIS may 2\pgorm\outputCostFunction.f90" ifx /nologo /debug:full /Od /I"D:\work_area\ISIS\OneDrive_2023-05-03\ISIS may 2\fftpack\obj\x64\Release" /DDEBUG /D_LARGEFILE_SOURCE /D_FILE_OFFSET_BITS=64 /DTIMING /DMKL_FFT /DMKL_EXP /DMKL_SINCI /DASYNCH_IO /Qopenmp /standard-semantics /debug-parameters:all /module:"obj\x64\Debug\\" /object:"obj\x64\Debug\\" /Fd"obj\x64\Debug\dll_pgorm.pdb" /traceback /check:all /libs:static /threads /Qmkl:sequential /c /F80000000 /recursive /Qlocation,link,"C:\Program Files\Microsoft Visual Studio\2022\Enterprise\VC\Tools\MSVC\14.31.31103\bin\HostX64\x64" /Qm64 "D:\work_area\ISIS\OneDrive_2023-05-03\ISIS may 2\pgorm\runInversion.f90" Linking... Creating temporary file "RSP1.rsp" with contents [ /OUT:"bin\x64\Debug\dll_pgorm.dll" /NOLOGO /LIBPATH:"..\segyio\bin\x64\Release" /LIBPATH:"..\horizonio\bin\x64\Release" /LIBPATH:"..\fftpack\bin\x64\Release" /LIBPATH:"..\libPgormZgy\bin\x64\Release" /LIBPATH:"D:\work_area\ISIS\OneDrive_2023-05-03_nuget\ISIS packages\Salmon.Native.VS140.18.1.7101\build\native\lib\x64\Release\dynamic" /NODEFAULTLIB:"LIBC" /MANIFEST:NO /DEBUG /PDB:"D:\work_area\ISIS\OneDrive_2023-05-03\ISIS may 2\pgorm\bin\x64\Debug\dll_pgorm.pdb" /SUBSYSTEM:WINDOWS /IMPLIB:"D:\work_area\ISIS\OneDrive_2023-05-03\ISIS may 2\pgorm\bin\x64\Debug\dll_pgorm.lib" /DLL segyio.lib horizonio.lib fftpack.lib Slb.Salmon.Zgy.lib libPgormZgy.lib /STACK:80000000 -qnextgen -qm64 /qoffload-ldopts="-mkl=sequential" "obj\x64\Debug\dll_pgorm_launcher.obj" "obj\x64\Debug\linpack.obj" "obj\x64\Debug\buffer.obj" "obj\x64\Debug\coordinates.obj" "obj\x64\Debug\tempFileIO.obj" "obj\x64\Debug\datatype.obj" "obj\x64\Debug\fileLogger.obj" "obj\x64\Debug\timing.obj" "obj\x64\Debug\errorHandling.obj" "obj\x64\Debug\parameters.obj" "obj\x64\Debug\svertical.obj" "obj\x64\Debug\progress.obj" "obj\x64\Debug\fft.obj" "obj\x64\Debug\outputCostFunction.obj" "obj\x64\Debug\resourceEstimation.obj" "obj\x64\Debug\outputProperties.obj" "obj\x64\Debug\waveletParser.obj" "obj\x64\Debug\util.obj" "obj\x64\Debug\licensing.obj" "obj\x64\Debug\postprocessing.obj" "obj\x64\Debug\processing.obj" "obj\x64\Debug\seval.obj" "obj\x64\Debug\preprocessing.obj" "obj\x64\Debug\processTrace.obj" "obj\x64\Debug\processLine.obj" "obj\x64\Debug\sflattrace.obj" "obj\x64\Debug\pgorm.obj" "obj\x64\Debug\runInversion.obj" "obj\x64\Debug\soutput.obj" "obj\x64\Debug\inputOutputFileIO.obj" "obj\x64\Debug\outputminMax.obj" "obj\x64\Debug\sflattrace2.obj" "D:\work_area\ISIS\OneDrive_2023-05-03\ISIS may 2\fftpack\bin\x64\Release\fftpack.lib" "D:\work_area\ISIS\OneDrive_2023-05-03\ISIS may 2\libPgormZgy\bin\x64\Release\libPgormZgy.lib" "D:\work_area\ISIS\OneDrive_2023-05-03\ISIS may 2\horizonio\bin\x64\Release\horizonio.lib" "D:\work_area\ISIS\OneDrive_2023-05-03\ISIS may 2\segyio\bin\x64\Release\segyio.lib" ] Creating command line "Link @"D:\work_area\ISIS\OneDrive_2023-05-03\ISIS may 2\pgorm\obj\x64\Debug\RSP1.rsp"" lld-link: warning: MS /GL object found in the command line. lld-link: warning: Finalizing linking process with MS-LINK PLEASE submit a bug report to https://software.intel.com/en-us/support/priority-support and include the crash backtrace. Stack dump: 0. Program arguments: C:\\PROGRA~2\\Intel\\oneAPI\\compiler\\20231~1.0\\windows\\bin\\Intel64\\..\\..\\bin-llvm\\lld-link.exe @C:\\Users\\jtveiten\\AppData\\Local\\Temp\\3544812arg4 Exception Code: 0xC0000005 #0 0x00007ff7725e0a80 (C:\PROGRA~2\Intel\oneAPI\compiler\20231~1.0\windows\bin\Intel64\..\..\bin-llvm\lld-link.exe+0x2bf0a80) #1 0x00007ff76fa3757e (C:\PROGRA~2\Intel\oneAPI\compiler\20231~1.0\windows\bin\Intel64\..\..\bin-llvm\lld-link.exe+0x4757e) #2 0x00007ff76fa2ef8c (C:\PROGRA~2\Intel\oneAPI\compiler\20231~1.0\windows\bin\Intel64\..\..\bin-llvm\lld-link.exe+0x3ef8c) #3 0x00007ff76fa281f0 (C:\PROGRA~2\Intel\oneAPI\compiler\20231~1.0\windows\bin\Intel64\..\..\bin-llvm\lld-link.exe+0x381f0) #4 0x00007ff76f9f1b85 (C:\PROGRA~2\Intel\oneAPI\compiler\20231~1.0\windows\bin\Intel64\..\..\bin-llvm\lld-link.exe+0x1b85) #5 0x00007ff76f9f12e6 (C:\PROGRA~2\Intel\oneAPI\compiler\20231~1.0\windows\bin\Intel64\..\..\bin-llvm\lld-link.exe+0x12e6) #6 0x00007ff7725c8638 (C:\PROGRA~2\Intel\oneAPI\compiler\20231~1.0\windows\bin\Intel64\..\..\bin-llvm\lld-link.exe+0x2bd8638) #7 0x00007fffd57d7604 (C:\WINDOWS\System32\KERNEL32.DLL+0x17604) #8 0x00007fffd60426a1 (C:\WINDOWS\SYSTEM32\ntdll.dll+0x526a1) dll_pgorm - 0 error(s), 2 warning(s)

 

Any idea what the problem is?

 

Regards,

Morten Gaupaas

0 Kudos
4 Replies
andrew_4619
Honored Contributor II
538 Views

/DDEBUG /D_LARGEFILE_SOURCE /D_FILE_OFFSET_BITS=64 /DTIMING /DMKL_FFT /DMKL_EXP /DMKL_SINCI /DASYNCH_IO

None of those are Intel Fortran compiler options that I recognise. NumPy???  I would start by removing those and try agian to see what you get.

0 Kudos
James_T_Intel
Moderator
537 Views

Are you seeing this on every build attempt, or is it inconsistent?


Are you able to trim this down to a small reproducer?


0 Kudos
Ron_Green
Moderator
506 Views

@andrew_4619  I think the /D 's are defines for the preprocessor.

 

Can you add option -# or -dryrun to the ifx options?  this will print out more detailed information on the compile and link.

The linker is complaining about find /GL objects.  Are any of the libraries or objects you are linking in from VC++ and from an earlier version if Visual Studio - compiled with an older Visual Studio?  I found this of interest:

https://learn.microsoft.com/en-us/cpp/build/reference/gl-whole-program-optimization?view=msvc-170

 

/GL is global object optimization, or what we call IPO.  Were any of the objects compiled with -ipo or interprocedural optimization?  

 

0 Kudos
James_T_Intel
Moderator
318 Views

Due to lack of reply, I am closing this from an Intel support perspective. Any further replies will be considered community only.


0 Kudos
Reply