Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
29280 Discussions

Problem calling CVF DLL from Intel QuickWin

mark_jackson
Beginner
460 Views
Hi
I'm upgrading a program from CVF to Intel Fortran. I'm running into a problem calling a DLL that's written in CVF.
An obvious solution is to upgrade the DLL to Intel Fortran too, but I don't want to do that right now as
there are many otherprograms that call the DLL, some Fortran and some Visual Basic.
The call into the DLL works fine unless I use the compiler option /QZero.
With/QZero I get an access violation. Looking in the debugger disassembly view, when the code tries to call the
DLL it actually calls into address 000000. This causes an access violation (naturally enough).
Looking at the module window, the DLL hasn't even been loaded. So it doesn't seem to be structure packing or
calling conventions or any of the "usual suspects" for this stuff.
Without /QZero everything works fine (the module window shows the DLL has been loaded too).
Again I think this rules out structure packing or calling conventions
So it seems to me/QZeromight beinterfering with the loading of the DLL?
The DLL is linked in using an import library and !DEC$IMPORT etc
My full compiler options for the Intel program are below. It's a QuickWin
/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
Thanks in advance
Mark
0 Kudos
1 Reply
Steven_L_Intel1
Employee
460 Views
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.
0 Kudos
Reply