- 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
Hello Samuel,
I believe this is a known issue. Let me investigate a little, and I'll get back to you.
Patrick
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I can't reproduce your complaint with ifort-14.0.2.176 and default compilation switches, ie, 'ifort foo.f90'.
What compiler options are you using?
Patrick
- 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
Meanwhile, I tested with your 32-bit debug options and still can't reproduce this. Looks like we are both using Visual Studio 2012, but I doubt this has anything to do with VS2012. The other issue I had with "insufficient virtual memory" could be reproduced from the command line. But, I will check if that issue has a workaround.
C:\ISN_Forums\U507637>ifort /debug:full /Od /warn:interfaces /traceback /check:bounds /check:stack /libs:dll /threads /dbglibs test.f90
Intel(R) Visual Fortran Compiler XE for applications running on IA-32, Version 14.0.2.176 Build 20140130
Copyright (C) 1985-2014 Intel Corporation. All rights reserved.
Microsoft (R) Incremental Linker Version 11.00.61030.0
Copyright (C) Microsoft Corporation. All rights reserved.
-out:test.exe
-debug
-pdb:test.pdb
-subsystem:console
-incremental:no
test.obj
C:\ISN_Forums\U507637>test.exe
C:\ISN_Forums\U507637>
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
>>>I get a "severe (41): insufficient virtual memory" error when running the following code that use deferred-length character component, automatic allocation on assignment and a few other rather new Fortran features.
The faulty code line(162) is :
res = name // ' value is ' // str(foo)>>>
Could this message mean that some compiler allocated buffer is insufficient to hold the string.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
OK, I can reproduce this in VS2012 using a 32-bit Debug build (and with 64-bit Debug build as well). That's unusual -- it's rare to see an issue that can't be reproduced from a command prompt using the same compiler options VS defaults to for Debug builds.
I'll report this to the developers.
@iliyapolak -- presumably, but I don't know.
Patrick
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Tracking defect #DPD200254632. I'll keep this thread updated with the progress to repair.
Patrick
- 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
@Samuel
Completely agree with your explanation.It definitely makes sense.

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