Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
29285 Discussions

Fortran limit on array size on Linux?

James_S_
Beginner
‎11-03-2009 10:58 AM
805 Views
I'm helping a researcher who's trying to creat a 4-dimensional array of double precision numbers, with a total of ~200 million elements.

dimension vstore(1:4,0:4,5000000,2),fstore(0:4,5000000,2)

When he tries to compile this code with 'ifort adaptnew2.for', he gets this error:

compilation aborted for adaptnew2.for (code 1)

He's using ifort 11.0.074. This same error occurs on ia32 and intel64 systems, running on rebuild of RHEL 5.4.

Is this a limitation of the Intel Fortran compiler or a bug? When we decrease the dimensions of the array so that it's less than ~200 million, the code compiles.

--
Prentice


0 Kudos

Link Copied

2 Replies
TimP
Honored Contributor III
‎11-03-2009 11:20 AM
805 Views
The limit for statically allocated data with default memory model is 2GB, as you found. ALLOCATABLE arrays for Intel64 may be much larger.
0 Kudos
Copy link
rreis
New Contributor I
‎11-04-2009 12:19 AM
805 Views
Check the option "-mcmodel" of the compiler (man ifort?)
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.