https://community.intel.com/t5/Intel-Fortran-Compiler/Problem-calling-CVF-DLL-from-Intel-QuickWin/m-p/845628#M63597 <DIV></DIV> <DIV>Hi</DIV> <DIV></DIV> <DIV>I'm upgrading a program from CVF to Intel Fortran. I'm running into a problem calling a DLL that's written in CVF. </DIV> <DIV>An obvious solution is to upgrade the DLL to Intel Fortran too, but I don't want to do that right now as </DIV> <DIV>there are many otherprograms that call the DLL, some Fortran and some Visual Basic.</DIV> <DIV></DIV> <DIV>The call into the DLL works fine unless I use the compiler option /QZero. </DIV> <DIV>With/QZero I get an access violation. Looking in the debugger disassembly view, when the code tries to call the </DIV> <DIV>DLL it actually calls into address 000000. This causes an access violation (naturally enough). </DIV> <DIV>Looking at the module window, the DLL hasn't even been loaded. So it doesn't seem to be structure packing or</DIV> <DIV>calling conventions or any of the "usual suspects" for this stuff.</DIV> <DIV></DIV> <DIV>Without /QZero everything works fine (the module window shows the DLL has been loaded too).</DIV> <DIV>Again I think this rules out structure packing or calling conventions</DIV> <DIV></DIV> <DIV>So it seems to me/QZeromight beinterfering with the loading of the DLL?</DIV> <DIV></DIV> <DIV>The DLL is linked in using an import library and !DEC$IMPORT etc</DIV> <DIV></DIV> <DIV> <DIV>My full compiler options for the Intel program are below. It's a QuickWin</DIV> <DIV></DIV> <DIV>/nologo /include:"ReleaseNoHills/" /include:"Release/" /include:".Release/" /include:"incsub" /include:".incsub" /include:".UnifiedIncludes" /define:URBAN /define:NOHILLS /noaltparam /fpscomp:general /warn:declarations /Qsave /align:dcommons /assume:byterecl /Qzero /fpe:0 /fpconstant /iface:cvf /module:"$(INTDIR)/" /object:"$(INTDIR)/" /libs:qwin /c</DIV> <DIV></DIV></DIV> <DIV>Thanks in advance</DIV> <DIV>Mark</DIV> <DIV></DIV> Wed, 01 Feb 2006 00:16:51 GMT mark_jackson 2006-02-01T00:16:51Z https://community.intel.com/t5/Intel-Fortran-Compiler/Problem-calling-CVF-DLL-from-Intel-QuickWin/m-p/845628#M63597 <DIV></DIV> <DIV>Hi</DIV> <DIV></DIV> <DIV>I'm upgrading a program from CVF to Intel Fortran. I'm running into a problem calling a DLL that's written in CVF. </DIV> <DIV>An obvious solution is to upgrade the DLL to Intel Fortran too, but I don't want to do that right now as </DIV> <DIV>there are many otherprograms that call the DLL, some Fortran and some Visual Basic.</DIV> <DIV></DIV> <DIV>The call into the DLL works fine unless I use the compiler option /QZero. </DIV> <DIV>With/QZero I get an access violation. Looking in the debugger disassembly view, when the code tries to call the </DIV> <DIV>DLL it actually calls into address 000000. This causes an access violation (naturally enough). </DIV> <DIV>Looking at the module window, the DLL hasn't even been loaded. So it doesn't seem to be structure packing or</DIV> <DIV>calling conventions or any of the "usual suspects" for this stuff.</DIV> <DIV></DIV> <DIV>Without /QZero everything works fine (the module window shows the DLL has been loaded too).</DIV> <DIV>Again I think this rules out structure packing or calling conventions</DIV> <DIV></DIV> <DIV>So it seems to me/QZeromight beinterfering with the loading of the DLL?</DIV> <DIV></DIV> <DIV>The DLL is linked in using an import library and !DEC$IMPORT etc</DIV> <DIV></DIV> <DIV> <DIV>My full compiler options for the Intel program are below. It's a QuickWin</DIV> <DIV></DIV> <DIV>/nologo /include:"ReleaseNoHills/" /include:"Release/" /include:".Release/" /include:"incsub" /include:".incsub" /include:".UnifiedIncludes" /define:URBAN /define:NOHILLS /noaltparam /fpscomp:general /warn:declarations /Qsave /align:dcommons /assume:byterecl /Qzero /fpe:0 /fpconstant /iface:cvf /module:"$(INTDIR)/" /object:"$(INTDIR)/" /libs:qwin /c</DIV> <DIV></DIV></DIV> <DIV>Thanks in advance</DIV> <DIV>Mark</DIV> <DIV></DIV> Wed, 01 Feb 2006 00:16:51 GMT https://community.intel.com/t5/Intel-Fortran-Compiler/Problem-calling-CVF-DLL-from-Intel-QuickWin/m-p/845628#M63597 mark_jackson 2006-02-01T00:16:51Z https://community.intel.com/t5/Intel-Fortran-Compiler/Problem-calling-CVF-DLL-from-Intel-QuickWin/m-p/845629#M63598 Haven't seen this one before. Please send a test case to Intel Premier Support. Offhand, I can't think of what the cause could be. Wed, 01 Feb 2006 01:57:17 GMT https://community.intel.com/t5/Intel-Fortran-Compiler/Problem-calling-CVF-DLL-from-Intel-QuickWin/m-p/845629#M63598 Steven_L_Intel1 2006-02-01T01:57:17Z