From: Kevin Buettner <kevinb@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>,
David Carlton <carlton@math.stanford.edu>
Cc: gdb <gdb@sources.redhat.com>
Subject: Re: xmmalloc?
Date: Fri, 20 Sep 2002 16:36:00 -0000 [thread overview]
Message-ID: <1020920233340.ZM27766@localhost.localdomain> (raw)
In-Reply-To: Daniel Jacobowitz <drow@mvista.com> "Re: xmmalloc?" (Sep 20, 7:16pm)
On Sep 20, 7:16pm, Daniel Jacobowitz wrote:
> I get the distinct impression that uses of mmalloc have started to
> rot...
>
> If this is not the case, could someone please summarize the advantages?
Yes, I'd like to see this too.
> Otherwise, should we just remove it entirely?
If no one makes a convincing case for it, I think it should be removed.
It'd make the code in utils.c simpler...
Kevin
next prev parent reply other threads:[~2002-09-20 23:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-20 15:55 xmmalloc? David Carlton
2002-09-20 16:16 ` xmmalloc? Daniel Jacobowitz
2002-09-20 16:36 ` Kevin Buettner [this message]
2002-09-20 16:48 ` xmmalloc? David Carlton
2002-09-20 17:16 ` xmmalloc? Andrew Cagney
2002-09-20 17:55 ` xmmalloc? Daniel Berlin
2002-09-20 16:17 ` xmmalloc? Kevin Buettner
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=1020920233340.ZM27766@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=carlton@math.stanford.edu \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
/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