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
X-Authentication-Warning:	hp2.xraylith.wisc.edu: khan owned process doing -bs
Date:	Sun, 19 Mar 2000 16:27:04 -0600 (CST)
From:	Mumit Khan <khan AT NanoTech DOT Wisc DOT EDU>
To:	Alex <alexx AT inbox DOT lv>
cc:	cygwin AT sourceware DOT cygnus DOT com
Subject:	Re: Memory management in Cygwin
In-Reply-To:	<38D528C7.431B316E@inbox.lv>
Message-ID:	<Pine.HPP.3.96.1000319161935.16154C-100000@hp2.xraylith.wisc.edu>
MIME-Version:	1.0

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



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

- Raw text -