public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jmfriedman7 at alum dot mit.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/53569] New: mac-OSX idle memory
Date: Mon, 04 Jun 2012 02:38:00 -0000	[thread overview]
Message-ID: <bug-53569-4@http.gcc.gnu.org/bugzilla/> (raw)

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: unassigned@gcc.gnu.org
        ReportedBy: jmfriedman7@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.


             reply	other threads:[~2012-06-04  2:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-04  2:38 jmfriedman7 at alum dot mit.edu [this message]
2012-06-04  2:47 ` [Bug target/53569] " pinskia at gcc dot gnu.org
2012-06-04  3:11 ` jmfriedman7 at gmail dot com
2012-06-04  3:34 ` kargl at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-53569-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).