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.
29286 Discussions

DLL 32 bit vs 64 bit on Mobile Platforms

vikrantca
Beginner
‎04-01-2010 07:38 AM
514 Views
Hello,

I am using the following to build a fortran DLL.

Platform: 32 bit, Windows Server 2008, Intel Fortran (most recent version, downloaded yesterday) with VS 2008 Pro.

The compiler options for debug and release are as follows:

DEBUG Fortran Command Line:

/nologo /debug:full /Od /gen-interfaces /warn:interfaces /module:"Debug\\\\" /object:"Debug\\\\" /traceback /check:bounds /libs:static /threads /dbglibs /c

RELEASE Fortran

/nologo /module:"ReleaseOpt\\\\" /object:"ReleaseOpt\\\\" /libs:static /threads /c
Additional: /QaxSSE4.2,SSE4.1,SSSE3,SSE3,SSE2


My Applications - Using managed C++ to load the dll dynamically (using LoadLibrary) and using some of the functions in the DLL.

My problem: The DLL works just fine on Windows 32 bit (desktops and laptops). BUT, it does not work (LoadLibrary call hangs) on 64-bit Laptops. It DOES work on 64-bit (Windows 7) desktops.
I tried a fresh install of Win 7 x64 on 1 laptop and 1 desktop. The application/DLL runs fine on the desktop but not on the Laptop. Both the release and the debug versions dont work.

Any help is very much appreciated.

Thank you very much.

VA
0 Kudos

Link Copied

1 Reply
Steven_L_Intel1
Employee
‎04-01-2010 11:13 AM
514 Views
I have not heard of this behavior before. I suggest you download Dependency Walker (the x64 version), run it on the laptop and then "open" your DLL with it, to see if it reports any errors.

I will comment that your /Qax option should be simplified - only two specific and one generic code path is supported, and SSE2 is the default anyway.
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.