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:	<5.1.0.14.0.20020325133529.00b0ca50@mail.unisa.it>
X-Sender:	gspagnuo AT mail DOT unisa DOT it
X-Mailer:	QUALCOMM Windows Eudora Version 5.1
Date:	Mon, 25 Mar 2002 14:54:22 +0100
To:	cygwin AT cygwin DOT com
From:	"G.Spagnuolo" <spanish AT ieee DOT org>
Subject:	Cygwin/DJGPP and memory
Mime-Version:	1.0

Dear all,
I'm browsing the mailing list archive about the limits on memory allocation 
under cygwin, but I've not yet a complete picture.
What is the real limit when I use new[] in a C++ program? The one I set in 
windows2000 register heap_chunk_in_mb?
What are the differences in memory limits between cygwin and DJGPP, besides 
the DJGPP need for DPMI?
Please clarify this point for a "medium level" programmer as me.
I am migrating from DJGPP to cygwin to benefit from a non-dos GCC 
interface, but I need to work with large sparse matrices and my programs 
are greedy for memory!

Thanks a lot for you time.

Regards

Giovanni


--
Dr. Giovanni Spagnuolo, Ph.D.
Assistant Professor
University of Salerno
Dipartimento di Ingegneria dell'Informazione ed Ingegneria Elettrica 
(D.I.I.I.E.)
Via Ponte Don Melillo
84084 Fisciano - Salerno - Italy
phone: +39 089 964258
fax: +39 089 964218
e-mail: spanish AT ieee DOT org

"You can tell whether a man is clever by his answers.
You can tell whether a man is wise by his questions."
Naguib Mahfouz


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