- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I followed up on a suggestion in a previous thread, and tried out the evaluation version of Intel Fortran 7.1 on a mixed Fortran / C# project.
By far the hardest part was managing to get the installation file from the Intel website. Finally, someone at Intel (not from the compiler team) volunteered to call me on the phone and discuss the problem. Tthen, magically, I soon had the file.
I integrated the product into Visual Studio 2003. Using the ?Enable Unmanaged Debugging? option, I am able to compile, and debug simultaneously, an unmanaged Fortran DLL and the managed code that calls into it via P/Invoke. Intel Fortran recognizes the few basic !DEC$ directives I tried. The debugger recognizes and properly handles Fortran arrays. It also properly handles variables in a subroutine that are passed from the calling program. I could step thru and set breakpoints in both the Fortran and the managed code. Development of combined managed code and unmanaged Fortran should be quite seamless.
The product is somewhat buggy but it does seem to work, based on just a short amount of use.
I couldn't find the equivalent of the Post-Build step in CVF 6.6. This is useful for copying the DLL and PDB files for the Fortran DLL into the Debug folder of the C# project.
Dynamic Help and IntelliSense do not work with Fortran code, unfortunately.
The debugger does not recognize variables whose names begin with "$."
QUESTION: We have two copies of CVF 6.6 that we bought last year, plus two more copies in unopened boxes that we bought about a month ago. How much is it going to cost to upgrade to the new product, when it is released?
By far the hardest part was managing to get the installation file from the Intel website. Finally, someone at Intel (not from the compiler team) volunteered to call me on the phone and discuss the problem. Tthen, magically, I soon had the file.
I integrated the product into Visual Studio 2003. Using the ?Enable Unmanaged Debugging? option, I am able to compile, and debug simultaneously, an unmanaged Fortran DLL and the managed code that calls into it via P/Invoke. Intel Fortran recognizes the few basic !DEC$ directives I tried. The debugger recognizes and properly handles Fortran arrays. It also properly handles variables in a subroutine that are passed from the calling program. I could step thru and set breakpoints in both the Fortran and the managed code. Development of combined managed code and unmanaged Fortran should be quite seamless.
The product is somewhat buggy but it does seem to work, based on just a short amount of use.
I couldn't find the equivalent of the Post-Build step in CVF 6.6. This is useful for copying the DLL and PDB files for the Fortran DLL into the Debug folder of the C# project.
Dynamic Help and IntelliSense do not work with Fortran code, unfortunately.
The debugger does not recognize variables whose names begin with "$."
QUESTION: We have two copies of CVF 6.6 that we bought last year, plus two more copies in unopened boxes that we bought about a month ago. How much is it going to cost to upgrade to the new product, when it is released?
Link Copied
2 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Upgrade pricing is not yet set.
Steve
Steve
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Any idea when it will be set?
I hope Intel is not going to gouge us.
I hope Intel is not going to gouge us.

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page