Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.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 To: Alex cc: cygwin@sourceware.cygnus.com Subject: Re: Memory management in Cygwin In-Reply-To: <38D528C7.431B316E@inbox.lv> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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@sourceware.cygnus.com