public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Alex <alexx@inbox.lv>
To: Mumit Khan <khan@NanoTech.Wisc.EDU>
Cc: cygwin@sourceware.cygnus.com
Subject: Re: Memory management in Cygwin
Date: Wed, 22 Mar 2000 09:52:00 -0000	[thread overview]
Message-ID: <38D90755.CCBB8862@inbox.lv> (raw)
In-Reply-To: <Pine.HPP.3.96.1000319161935.16154C-100000@hp2.xraylith.wisc.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@sourceware.cygnus.com

  reply	other threads:[~2000-03-22  9:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-19 11:26 Alex
2000-03-19 14:27 ` Mumit Khan
2000-03-22  9:52   ` Alex [this message]
2000-03-22 15:24     ` Mumit Khan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=38D90755.CCBB8862@inbox.lv \
    --to=alexx@inbox.lv \
    --cc=cygwin@sourceware.cygnus.com \
    --cc=khan@NanoTech.Wisc.EDU \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).