- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello, I am contemplating migrating my development platform and runtime environmentfrom WinXP Pro to WinXP Pro X64. The development platform runs MS VS .NET 2003 and IVF W_FC_C_9.0.024.
What are the growing pains in doing so. Should I leave the development system running WinXP and then cross compile and perform the debug sessions in WinXP x64?
I have a very compute intensive application that will, in the near future, require more than 4GB of RAM.
Your advice from your experiences would be welcome.
Jim Dempsey
Link Copied
3 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
VS.NET 2003 is an IA-32 system. While it will run on XP x64, it is still IA-32, so our EM64T compiler does not integrate with it. VS2005 will support native development on x64 with a future version of Intel Visual Fortran.
You can fudge VS.NET 2003 to use the Intel EM64T compiler and the PSDK to do your compiles and links. You'll have to use the Intel Debugger (idb) to debug there.
I've done some work porting Win32 apps there, and found a lot of them make assumptions about the 32-bit environment. Handles, for example, are 64-bit on x64. Also, some legacy APIs that you may be using are not supported on x64 (CreateWindow is one - use CreateWindowEx instead.)
Most of what I needed to do was to use kinds to specify the "appropriate" kind for variables that were handles and integer pointers.
If your code is "straight Fortran", you should have little trouble.
You can fudge VS.NET 2003 to use the Intel EM64T compiler and the PSDK to do your compiles and links. You'll have to use the Intel Debugger (idb) to debug there.
I've done some work porting Win32 apps there, and found a lot of them make assumptions about the 32-bit environment. Handles, for example, are 64-bit on x64. Also, some legacy APIs that you may be using are not supported on x64 (CreateWindow is one - use CreateWindowEx instead.)
Most of what I needed to do was to use kinds to specify the "appropriate" kind for variables that were handles and integer pointers.
If your code is "straight Fortran", you should have little trouble.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is there an ETA for full intigration if IVF into VS 2005. There is no need for me to upgrade VS until then. I can live with 2-3GB of virtual memory space for several months yet. Just doing some future planning for the day when my app needs more RAM.
I also use the Array Visualizer from the IVF distribution. Is there a problem with using AV on EM64T system?
Jim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We will be in beta test with a version that supports VS2005 before the end of the year. If you want to be included in the beta test, send an e-mail to me at steve.lionel at intel.com. We had wanted to begin the beta earlier, with the beta of VS2005, but MS kept making incompatible changes in each new beta release, so we decided to wait for the retail release before starting.
Array Visualizer currently (9.0) supports EM64T.
Array Visualizer currently (9.0) supports EM64T.

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