- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I have two VMS running Visual Studio 2012 Ultimate but they both have different versions of the Fortran compiler installed:
VM #1: Intel(R) Visual Fortran Compiler XE 14.0.6.241 [IA-32]
VM #2: Intel(R) Visual Fortran Compiler 17.0.4.210 [IA-32]
I have a simple Fortran test project on both VMs and I am testing an issue with preprocessor include files that was brought up to me. On VM #1 when you have a syntax error in the included header file and you try to double-click on the error in the Visual Studio error list window it does not take you to the exact line where the error is. However on VM #2 if you double-click on the error it does take you to the included file and the exact line where the syntax error is.
In what compiler version was this issue fixed? The only way I am able to get around it is to remove the preprocessor "#" in the include, build the project, and then you are able to double-click on the error. I have attached a screenshot with what I mean.
If you need more clarification let me know. Thank you!
JP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Intel releases complete new installs, not patches. There would have been one version or update with the fix, not something that is "applied" to older versions. My guess is that this sort of bug was fixed in a major new version, not one of the updates. Try version 16. Perhaps one of the Intel folk can query the internal bug report database to see if they can locate my escalation of this issue. I am pretty sure the fix was in the compiler, not in fpp.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Precompiled headers would be for c++. As it's possible to install either of your ifort versions with or without Microsoft (and possibly also Intel) c++, I don't see what answers you could expect.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Tim I apologize I meant preprocessor includes not pre-compiled. I edited the post
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I recall that there was a bug related to how preprocessor include files were identified by line number in the compiled source. It was fixed, but I don't remember in which version.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Try adding -P after -fpp (as additional command line option).
This removes the preprocessor annotations for #line-number file-name.
In older versions of IVF I had a similar problem with the line numbers in the debugger not lining up. This corrected the problem for me. It is easy enough for you to try.
Jim Dempsey
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Intel releases complete new installs, not patches. There would have been one version or update with the fix, not something that is "applied" to older versions. My guess is that this sort of bug was fixed in a major new version, not one of the updates. Try version 16. Perhaps one of the Intel folk can query the internal bug report database to see if they can locate my escalation of this issue. I am pretty sure the fix was in the compiler, not in fpp.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sounds good. I will contact support and see if they can query the bug report database and tell me the version where it got fixed. Thanks again for your help!
JP
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page