Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
From: "Dave Korn" <dave DOT korn AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: Memory for large arrays in cygwin/g77
Date: Thu, 6 Jan 2005 10:47:04 -0000
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <cri2e3$mmo$1@sea.gmane.org>
Message-ID: <NUTMEG8GhLxaYAeNbGC00000cd3@NUTMEG.CAM.ARTIMI.COM>
X-OriginalArrivalTime: 06 Jan 2005 10:47:04.0562 (UTC) FILETIME=[0F714520:01C4F3DD]

> -----Original Message-----
> From: cygwin-owner On Behalf Of Mark Hadfield
> Sent: 06 January 2005 00:58

> Dante Chialvo wrote:
> > I have similar problem than the one posted a while ago in
> > 
> > http://www.cygwin.com/ml/cygwin/2003-02/msg00842.html
> > 
> > Using cygwin/g77, in a PC with 1024 Mb of physical memory. 
> > After compiling and running the following test program 
> > the limit of 160 Mb cannot be surpassed. 

> > error message after running
> > C:\cygwin\home\dchialvo\test.exe (1972): *** 
> MapViewOfFileEx(0x71C, in_h 
> > 0x71C) failed, Win32 error 6

> Just to provide another data point, I have the same problem. 
> I have g77, 
> g95 and grfortran (gfc) installed (see below). With 
> heap_chunk_in_mb set 
> to 1024, on a machine with 1024 MiB RAM< I can run a simple Fortran 
> program with an array of up to ~ 1023 MiB. With g77 & gfc the 
> limit is 
> 156 MiB and beyond that it fails with something like
> 
>    gfctest.exe (844): *** MapViewOfFileEx(0x224, in_h 0x224)
>    failed, Win32 error 6

>  > Any suggestions will be appreciatted
> 
> Use g95

  It may also be possible to workaround the problem by fooling around with the
default stack allocation size; this can have knock-on effects which clear up the
reserved area of the process' memory map that error message is complaining
about.  

See 
http://www.cygwin.com/ml/cygwin/2004-10/msg01188.html
or 
http://www.cygwin.com/ml/cygwin/2004-07/msg00646.html for the full gory details,
and look up the "-Wl,--stack=XXXX" option.  You might need to play around with
values for the stack size until you find one that helps!


    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....


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