- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The same program runs correctlywith the 3D array of (32,32,512) (double) by thevs2005 plus intel visual fortran complier 10.1 (Intel 64 ). When the array is extended to (512, 512, 512) (double), however, if compiling,it shows that ---- Severe: Variable ... too large for NTCOFF. Bigger than 2GB. Use heap instead.
The computer has 8G physical memory. I have read these introductions in the document ---- On Intel 64 based systems running a 64-bit operating system, the maximum array size is limited by the size of the physical memory on the system plus any additional paging or swap space.
There must be some errors in setting. How could I deal with it?
Thanks!
Link Copied
- 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
On Linux there are three memory model choices where you can optionally have more than 2GB of static code and data, but not on Windows (nor MacOS).
- 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
The program runs well when Imake the large arrays using ALLOCATABLE and ALLOCATE functionson Windows. Many thanks for all of your suggestions. :-)
Other questions---
1. For the same size data, if it is possible, does static code and data run faster thanALLOCATABLE arrays, that is whythe staticdataareadoptedmore often?
2.Whether on Linux choosingmore than2GB of static code and datais more beneficial than applying ALLOCATABLE arrays?
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I would recommend using ALLOCATABLE for large arrays regardless.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I got this message, and some by memory limits windows and I resolved by applying the following:
array-heap: 0
I apply dynamic blocks:
-Dynamic common blocks: blocks name
and also increase the memory in the linker
-heap reserve size: Bytes
-heap commit size: Bytes
-stack reserve size: Bytes
-stack commit size: Bytes
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page