From: Jim Blandy <jimb@redhat.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb@sources.redhat.com, mec.gnu@mindspring.com
Subject: Re: Technical criteria for retaining symbol readers
Date: Wed, 23 Jun 2004 18:44:00 -0000 [thread overview]
Message-ID: <vt2fz8mm7x3.fsf@zenia.home> (raw)
In-Reply-To: <40D70123.9060308@gnu.org>
Andrew Cagney <cagney@gnu.org> writes:
> I'd like to see us establish clear technical criteria against which
> symtab readers are measured. Those that don't meet the criteria, either
> being fixed or removed.
>
> As an example, should it be a requirement that all symbol-readers use
> the build-symtab framework?
That would be good.
I'd also like to have some kind of requirement for testability. For
example, I have no way (that I know of) to evaluate changes to
nlmread.c, but that shouldn't mean that I mustn't change anything it
depends on. Perhaps we should require that, in order to be retained,
symbol readers have a contact person who can give GDB developers
access to a machine that actually uses that format. (A complete sim
toolchain being available would be an easy way to satisfy this
requirement.)
next prev parent reply other threads:[~2004-06-23 18:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-21 15:39 Andrew Cagney
2004-06-23 18:44 ` Jim Blandy [this message]
2004-06-23 19:50 Michael Elizabeth Chastain
2004-06-23 20:14 ` Andrew Cagney
2004-06-28 23:59 ` Jim Blandy
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=vt2fz8mm7x3.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=mec.gnu@mindspring.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