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

an interesting/strange thing

yjyincj
Beginner
‎09-17-2009 03:59 AM
508 Views
I wrote a code that runns a variaty of allocate-deallocate arrays. When I run it in Win XP professional, it stops after it has run a while, saying insufficient virtual memory. However, it runs very well on Fedora 11 (x86). Is that because of the different memory management algorithm between two OS? Both computers have 2G ram.
0 Kudos

Link Copied

3 Replies
jimdempseyatthecove
Honored Contributor III
‎09-17-2009 12:02 PM
508 Views

Look in MSDN under Low Fragmentation Heap (or LFH). You may need to set the option to enable LFH.

Jim Dempsey
0 Kudos
Copy link
nahid5692001
Beginner
‎09-17-2009 12:29 PM
508 Views

Look in MSDN under Low Fragmentation Heap (or LFH). You may need to set the option to enable LFH.

Jim Dempsey

This is an LFH issue, try to enable it and run it with both systems. should work
0 Kudos
Copy link
yjyincj
Beginner
‎09-18-2009 01:52 PM
508 Views
Quoting - nahid5692001

This is an LFH issue, try to enable it and run it with both systems. should work
Great! I have been wondering this for a long while. Yeah it should help with LFH. I found from msdn that LFH is enabled from windows vista. So there will be no problem to run on vista or Win7. Thanks.
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.