- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Have you tried with the current release?
A minimum compilable source constructed from what you've posted works for me.
Note that your use of the period as a structure component selector (i.e. the dot in "item.values(i,j)") is not standard fortran. The standard language uses a percent sign "item%values(i,j)". Because dots are used to delimit operators I have come across instances where the parsing phase of the compiler gets rather confused if you use this dot structure component selector extension. I haven't personally experienced ICE's from this - but I guess it is a possibility.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Did you try a more recent compiler ( 13.1, 14.0) ? I quickly created a test based on your code lines above including the original WRITE statement - it compiles without issues using the 14.0 compiler (64bit however).
In case the newer compiler still shows the ICE, can you attach a small, complete ( compilable ) test case ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Did you try a more recent compiler ( 13.1, 14.0) ? I quickly created a test based on your code lines above including the original WRITE statement - it compiles without issues using the 14.0 compiler (64bit however).
In case the newer compiler still shows the ICE, can you attach a small, complete ( compilable ) test case ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi HeinzB, thanks for your comments. I had tried the "%" instead of "." but it made no difference
I'd love to try a more recent (less buggy?) compiler version but unfortunately my license has expired.
I'll try to isolate a compilable source for you to test, but it will take me some time. I have a feeling though that this test code would work, and it is something else in the full code that is the problem. For instance I have noticed that when adding a "<n>" type FORMAT descriptor, my working code then had a fatal compiler error. It seems that something is making the compiler "on the edge".
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I will send you a temporary license to try the latest compiler. This will clarify then at least, whether the issue is gone.

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