Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Fri, 29 Apr 2005 10:27:49 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: I: G77 160 MB memory allocation limit Message-ID: <20050429082749.GM2572@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <45C1A052D4EE624FA64275E179096BAA26E806 AT ALRMMX01 DOT rm DOT aleniaspazio DOT it> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <45C1A052D4EE624FA64275E179096BAA26E806@ALRMMX01.rm.aleniaspazio.it> User-Agent: Mutt/1.4.2i On Apr 27 17:19, Impagnatiello Fabrizio wrote: > again >   > -----Messaggio originale----- > Da: Impagnatiello Fabrizio > Inviato: mercoledė 27 aprile 2005 17.15 > A: 'cygwin AT cygwin DOT com' > Oggetto: G77 160 MB memory allocation limit >   > Starting from 1.5.13 (14 and 15 subversions are the same) I experienced all FOTRAN written programs using large arrays to crash. >   > No error message, just exit. >   > After investigation (WEB/mailing list) and testing programs I discovered and verified that a new near 160 MByte allocation limit is induced by cygwin1.dll >   > Simple programs compiled with -mno-cygwin flag may allocate up to 1920 MByte. >   > With the old 1.5.12 the usable size (2BG RAM machine) was 1536 MByte. Please try the latest Cygwin snapshot from http://cygwin.com/snapshots/. I tested it with a large array of 1500 Megs in a pretty small application. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/