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:	<001d01c2d300$333b9a00$d16bd6d1@oemcomputer>
From:	"Charles D. Russell" <worwor AT bellsouth DOT net>
To:	"cygwin cygwin" <cygwin AT cygwin DOT com>
Subject:	Memory for large arrays in cygwin/g77
Date:	Wed, 12 Feb 2003 19:35:18 -0600
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2800.1106

Using cygwin/g77, I was happy with a memory limitation of something over 240
Mb when I was using a laptop with 64 Mb of physical memory. However, I
recently acquired a new PC with 512 Mb of physical memory and found that the
memory available for array allocation did not increase, remaining little
over 240 Mb. The same phenomenon occurs with f2c as with g77. I can do a
little better in straight C, with something over 600 Mb available on the new
computer, but only by declaring the arrays dynamically. What is going on? (I
am not a programmer, just a number cruncher.)

I have explored accessible memory by means of the subsequent test program,
edited in several obvious ways.

implicit double precision (a-h,o-z)
c ny=300 works (240 Mb), 400 doesnt (message about heap)
parameter(nx=100000,ny=300)
dimension a(nx,ny)
c dimension a1(nx,ny)
write(6,*) 'megabytes= ',nx*ny*8/1d6
a(1,1)=1d0
a(nx,ny)=1d0
write(6,*) 'extremes initialized'
end


--
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/

- Raw text -