From: Mark Kettenis <kettenis@chello.nl>
To: carlton@kealia.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC/RFA] Per-objfile data mechanism
Date: Sun, 10 Aug 2003 19:03:00 -0000 [thread overview]
Message-ID: <200308101903.h7AJ32Bx079942@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <yf24r1nn3c0.fsf@hawaii.kealia.com> (message from David Carlton on Tue, 15 Jul 2003 09:48:31 -0700)
From: David Carlton <carlton@kealia.com>
Date: Tue, 15 Jul 2003 09:48:31 -0700
On Tue, 15 Jul 2003 12:17:29 -0400, Daniel Jacobowitz
<drow@mvista.com> said:
> The concept is nice, but I share David's concern.
I was also going to write, based on a cursory misreading of Mark's
patch, that it simplified memory management in some circumstances, but
now that I look at it more closely, I think I just misread the patch.
(I may still be misreading the patch; my head is spinning with other
things.) Would it be possible/beneficial to modify the mechanism to
provide an optional per-datum cleanup function as well?
I quite deliberately left per-datum initializers and destructors out
to encourage the use of the per-objfile obstacks. But they can always
be added if they're needed.
So what's the final verdict. Should my patch go in, or do people have
concrete ideas about necessary improvements or alternative
implementations?
Mark
next prev parent reply other threads:[~2003-08-10 19:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-13 17:17 Mark Kettenis
2003-07-15 15:55 ` David Carlton
2003-07-15 16:17 ` Daniel Jacobowitz
2003-07-15 16:48 ` David Carlton
2003-07-15 17:27 ` Daniel Jacobowitz
2003-08-10 19:03 ` Mark Kettenis [this message]
2003-08-11 15:45 ` David Carlton
2003-08-12 20:08 ` Andrew Cagney
2003-08-12 20:51 ` David Carlton
2003-08-21 22:42 ` Mark Kettenis
2003-09-07 4:26 ` Daniel Jacobowitz
2003-08-13 20:54 ` Daniel Jacobowitz
2003-07-15 17:14 ` Andrew Cagney
2003-07-15 20:00 ` Elena Zannoni
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=200308101903.h7AJ32Bx079942@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=carlton@kealia.com \
--cc=gdb-patches@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