Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID:	<38D90755.CCBB8862@inbox.lv>
Date:	Wed, 22 Mar 2000 19:48:05 +0200
From:	Alex <alexx AT inbox DOT lv>
X-Mailer:	Mozilla 4.04 [en] (Win95; I)
MIME-Version:	1.0
To:	Mumit Khan <khan AT NanoTech DOT Wisc DOT EDU>
CC:	cygwin AT sourceware DOT cygnus DOT com
Subject:	Re: Memory management in Cygwin
References:	<Pine DOT HPP DOT 3 DOT 96 DOT 1000319161935 DOT 16154C-100000 AT hp2 DOT xraylith DOT wisc DOT edu>

Mumit Khan wrote:

> On Sun, 19 Mar 2000, Alex wrote:
>
> > I'm interested to know if C/C++ compilers in Cygwin somehow optimize
> > memory allocation/deallocation routines like getting large blocks from
> > OS and then redistributing small portions to the program.
> > Thanks for help!
>
> It's not the compilers, but rather the runtime that manage the memory
> pools, and yes, Cygwin's memory manager does do pool optimization just
> like every other `malloc' package out there.
>
> Cygwin's malloc is based on, as far as I can tell, Doug Lea's public
> domain implementation. See his homepage http://g.oswego.edu/index.html
> for the design document (go down to the "Software" section).
>
> Regards,
> Mumit

 Thanks for help, but it still isn't clear for me, how the memory management
is done in the programs compiled in Cygwin. How about executables build with
-mno-cygwin option? As I know they don't use any runtime libraries. Does the
linker put memory optimization code in them?



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -