From: Daniel Jacobowitz <drow@false.org>
To: Doug Evans <dje@google.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [RFA] remove free_contents
Date: Thu, 03 Apr 2008 18:58:00 -0000 [thread overview]
Message-ID: <20080403181244.GA7857@caradoc.them.org> (raw)
In-Reply-To: <e394668d0804031054x10bfe737u5b915356f16f0c95@mail.gmail.com>
On Thu, Apr 03, 2008 at 10:54:48AM -0700, Doug Evans wrote:
> Either the comment is incomplete (i.e. some names are not allocated
> on an objfile_obstack), or the code is wrong (or in this case, outdated).
Both possible, I think, as long as the name has lifetime at least as
long as the objfile_obstack. It could come from mmaped dwarf
sections, for instance (if we get around to making that work... I see
that conversation on a patch to do this trailed off).
> 2008-04-03 Doug Evans <dje@sebabeach.org>
>
> * symtab.h (enum free_code): Delete free_contents, unused.
> * symmisc.c (free_symtab_block): Delete.
> (free_symtab, case free_code): Delete.
OK, thanks.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2008-04-03 18:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 18:13 Doug Evans
2008-04-03 18:58 ` Daniel Jacobowitz [this message]
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=20080403181244.GA7857@caradoc.them.org \
--to=drow@false.org \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
/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