From: David Gordon Hogan <dhog@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 8c -v- gcc
Date: Thu, 28 Feb 2002 00:42:50 -0500 [thread overview]
Message-ID: <26a3aed2aad68bfadb70177d927faef9@plan9.bell-labs.com> (raw)
> free(malloc(8)) 1.1386 1.1170 0.1159
I just thought that this line needed to be highlighted.
We may not have the world's best code generation,
but our memory allocator's an order of magnitude
faster!
C:/cygwin/usr/src/cygwin-1.3.2-1/newlib/libc/stdlib/mallocr.c:
* Why use this malloc?
This is not the fastest, most space-conserving, most portable, or
most tunable malloc ever written. However it is among the fastest
while also being among the most space-conserving, portable and tunable.
next reply other threads:[~2002-02-28 5:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-28 5:42 David Gordon Hogan [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-27 12:28 steve.simon
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=26a3aed2aad68bfadb70177d927faef9@plan9.bell-labs.com \
--to=dhog@plan9.bell-labs.com \
--cc=9fans@cse.psu.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 NNTP newsgroup(s).