http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53569
Bug #: 53569
Summary: mac-OSX idle memory
Classification: Unclassified
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: minor
Priority: P3
Component: fortran
AssignedTo: unassig...@gcc.gnu.org
ReportedBy: jmfriedm...@alum.mit.edu
Calls to fortran subroutines that use large temporary arrays fill up 'idle
memory' on the MAC-OSX, as can be seen with 'top' or the Mac 'activity
monitor'. I found that I can get around this by using:
call system('purge')
to evoke the command line 'purge' from within the program before the 'return'
statement for such subroutines to free the idle memory; but I was wondering
whether something could be done more fundamentally at the compiler level to
avoid this problem.
Without such clearing of idle memory I used to hear lots of disk access being
done to get around the small amount of free 'core' memory. Massive arrays
would eat up many Gb of core memory by turning it to 'idle memory'.
Maybe there is a compile time option that I do not know about.
