- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
I have just upgraded to parallel studio 2015 from the latest version of 2013 and my main Fortran code no longer compiles. The compilation fails for just one of many files with the error message:
fortcom: Fatal: There has been an internal compiler error (C0000005).
ifort: error #10298: problem during post processing of parallel object compilation
I first tried experimenting with different compiler settings to find a work-around for the problem and I found that disabling openmp resolves the issue. My code relies heavily on openmp, however, so I tried digging further. I started out by removing all openmp directives from the file, but that had no effect. I then tried to iteratively uncomment more and more of the source file until I could get it to compile. The difference between compilation and error in the first instance turned out to be uncommenting a simple go to statement. I then thought I was home free and tried rolling back to the original source file uncommenting only the problematic "go to" statement - but that wouldn't compile either. I then proceeded with trimming the source file once again and now the code started to compile by uncommenting a line with a simple function call. I followed this iterative approach for a while, but I could not identify any set lines of code as the root of the problem.
I then turned to the command line and ran the exact compile line used within the IDE (copied from the html build log) and it it worked! Any suggestions as to what is causing this?
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If you are able to then you should submit the offending code to Premier Support along with your project settings. (It will be kept confidential if necessary) All ICE's are compiler errors which I presume Intel would prefer to fix.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I cannot say from the description of what you have done/tried what might be leading to this. If we can get the original source and project settings we should be able to identify the cause and maybe find a usable work around.
If you feel comfortable sharing your code via the Forum and a private communication with me then you can also do that or proceed as Les suggested.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Something set or not set in the environment comparing VS to cmdline perhaps?

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