public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Charles Wilson <cygwin@cwilson.fastmail.fm>
To: cygwin@cygwin.com
Subject: Re: enabling /largeaddressaware for cygwin in windows 7 64-bit
Date: Thu, 04 Aug 2011 17:37:00 -0000	[thread overview]
Message-ID: <4E3AD8D5.1060008@cwilson.fastmail.fm> (raw)
In-Reply-To: <20110804155355.GE21692@calimero.vinschen.de>

On 8/4/2011 11:53 AM, Corinna Vinschen wrote:
> On Aug  4 15:19, Amidon, William H. wrote:
>> The fortran 90 code I am running keeps running out of memory (virtual
>> memory or stack overflow errors) on jobs that the computer should
> 
> The main thread has a 2 Megs stack by default (Windows default).
> If you're running out of stack space, there's not much we can do.
> There's some way to define the default stacksize in the executable
> header but off the top of my head I don't know how to change it.

The linker options:

`--stack RESERVE'
`--stack RESERVE,COMMIT'
     Specify the number of bytes of memory to reserve (and optionally
     commit) to be used as stack for this program.  The default is 2Mb
     reserved, 4K committed.  [This option is specific to the i386 PE
     targeted port of the linker]

Obviously, the OP would need to pass these 'thru' the gfortran compiler
using
	-Wl,--stack,RESERVE
or	-Wl,--stack,"RESERVE,COMMIT" (may not work; there's a problem with
both ld and gcc using ',' as a delimiter)

--
Chuck

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2011-08-04 17:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-04 15:20 Amidon, William H.
2011-08-04 15:54 ` Corinna Vinschen
2011-08-04 17:37   ` Charles Wilson [this message]
2011-08-04 18:17     ` Corinna Vinschen
2011-08-04 22:17       ` Charles Wilson
2011-08-05  6:33         ` Corinna Vinschen

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=4E3AD8D5.1060008@cwilson.fastmail.fm \
    --to=cygwin@cwilson.fastmail.fm \
    --cc=cygwin@cygwin.com \
    /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).