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.
29280 Discussions

is ivf 9.1 a 64-bit app?

Intel_C_Intel
Employee
‎05-22-2007 08:19 PM
794 Views
I have several extraordinarily large programs that I would like to compile with IVF 9.1 on a 64-bit version of Windows. Is the compiler itself capable of addressing more than 2GB?
0 Kudos

Link Copied

3 Replies
Steven_L_Intel1
Employee
‎05-23-2007 06:11 AM
794 Views
The IA-64 (Itanium) compiler is a 64-bit app, but the Intel 64 (EM64T) compiler is 32-bit and would have similar memory constraints as on 32-bit Windows. Are these single source files that are very large? Note that no matter what you do, there is a hard limit of 2GB for all static code and data on Windows, even 64-bit.
0 Kudos
Copy link
matthewclay
Beginner
‎05-23-2007 06:57 AM
794 Views
It is a single large file. I don't think the data will often be larger than 2GB, but if so, I can change to allocatable arrays. But the program code might be and I actually have less control over that.

By "static code", do you mean all program code, code that is not exported (say via _declspec()), code that is explicitly declared static (like in C), or something else?

0 Kudos
Copy link
Steven_L_Intel1
Employee
‎05-23-2007 07:15 AM
794 Views
Sorry - should have said "code and static data". That is, anything that is placed by the linker. It excludes dynamic allocation. The 2GB is a Windows object code format limit and not a compiler limit.

I would strongly suggest trying to break up the program into separate files (and that means separate subroutines, not just pieces that you stick together with INCLUDE.)
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.