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 X-Originating-IP: [130.102.97.48] From: "K" To: Subject: RE: cygwin, g77 & 3-D arrays Date: Thu, 13 Feb 2003 11:46:30 +1000 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 Message-ID: X-OriginalArrivalTime: 13 Feb 2003 01:46:37.0793 (UTC) FILETIME=[BF503D10:01C2D301] Thanks for your replies, they helped me to figure out the problem. Basically it seems the declared dimensions of my 3-D arrays were too large for cygwin, making the parameters smaller allowed the program to run. So a new question for you, what is the largest that cygwin can handle? I don't know if it will make any difference to your replies but my code was along these lines: PARAMETER(MOBS=5000) PARAMETER(MC=10) PARAMETER(MB=1000) PARAMETER(MCV=100) INTEGER MOBS,MC,MB,MCV DOUBLE PRECISION fp(MB,MC,MOBS),fw(MB,MC,MCV+1),fa(MB,MC-1,MCV+1) With the numbers given above the program would not run in cygwin (it ran in Linux), making these much, much smaller (500,5,100,10 respectively) allowed it to run. Sometimes, however (depending on the data) I may need these numbers to be bigger again (particularly MOBS), so it would be good to know what is the largest cygwin can handle? Thanks again! -- 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/