delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2005/01/10/16:38:17

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: Mon, 10 Jan 2005 21:35:02 -0000
MIME-Version: 1.0
In-Reply-To: <crurea$eg8$1@sea.gmane.org>
Message-ID: <NUTMEG6Tnhgz2Uogux400000e95@NUTMEG.CAM.ARTIMI.COM>
X-OriginalArrivalTime: 10 Jan 2005 21:35:02.0046 (UTC) FILETIME=[3DE18BE0:01C4F75C]

> -----Original Message-----
> From: cygwin-owner On Behalf Of Mark Hadfield
> Sent: 10 January 2005 21:18

> Is there a cure that would allow a simple-minded, grey-haired Fortran 
> programmer like me to rely on Cygwin g77 (or gfortran) for 
> moderate-sized computational tasks?

  LOL, I love the subtle sense of understatement you fortran guys use to
describe handling arrays of hundreds of millions of elements :)

  Anyway, the simple answer appears to be "Use g95 instead", doesn't it?

    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/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019