Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <000701c2d602$8dab7d20$60c84cd8@oemcomputer>
From: "Charles D. Russell" <worwor AT bellsouth DOT net>
To: "cygwin cygwin" <cygwin AT cygwin DOT com>
Subject: size limit for static arrays in cygwin/gcc
Date: Sun, 16 Feb 2003 15:29:25 -0600
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106

:Danny Smith  wrote
By default stack reserve is set to 2MB by ld.exe.  Try setting stack reserve
higher, eg,
 -Wl,--stack=0x2000000
will get you 32MB stack reserve
-------------------------------------

Thanks.  That was a revelation.  I thought stack was for pointers and
automatic variables, and a big stack was needed only for deep recursion.  So
the trick of increasing the stack, which works for g77, does not simply
displace a bug to another part of memory.  f2c still doesn't work for large
arrays, even setting -Wl in CFLAGS, but maybe CFLAGS is not passed through
the shell script used with f2c to emulate f77.  I'll have to look at that
sometime, but g77 will serve for now.  I've had no problem using f2c for
large arrays on a unix system.

Running fortran used to be simpler.  You just had to remember to drop in the
compiler deck first, the data deck last.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/