From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: jimb@redhat.com, gdb@sources.redhat.com
Subject: Re: Delay the branch for E500 native support
Date: Sun, 04 Jul 2004 06:14:00 -0000 [thread overview]
Message-ID: <20040704061351.GA25802@nevyn.them.org> (raw)
In-Reply-To: <7137-Sat03Jul2004122237+0300-eliz@gnu.org>
On Sat, Jul 03, 2004 at 12:22:37PM +0200, Eli Zaretskii wrote:
> > Date: Fri, 2 Jul 2004 18:40:47 -0400
> > From: Daniel Jacobowitz <drow@false.org>
> >
> > I would really have liked for GDB 6.1 to contain inter-compilation-unit
> > reference support too. If the timing doesn't work out, it doesn't work
> > out - if the schedule holds there may even be another release this
> > year.
>
> The intercu example is not a good analogy, IMHO: it was a new feature
> that was totally absent from the codebase.
>
> Jim's situation is somewhat different: there's a half-baked port
> already in the CVS. To me, it doesn't make sense to release a new
> version with incomplete support for some platform, where work is under
> way to make it complete in a week or so.
First of all, the e500 port has been in CVS as a target port, and
continuously evolving, for a long time - since before the release of
GDB 6.1. Secondly, it will require a DWARF feature which is
genericly used by GCC on all platforms, that we currently throw up our
hands at just like we do for inter-cu referenes.
But I was not trying to compare the two; I simply picked an example out
of my mailbox. Perhaps it was a bad choice of example.
We've chosen to release GDB according to a schedule, or at least to
make an effort in that direction. I think it's a reasonable choice,
but if you don't agree then we can discuss that. But pushing dates
back for one feature at a time is not a good way to finish anything;
either we're trying for a date or we aren't.
My two cents.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-07-04 6:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-02 22:27 Jim Blandy
2004-07-02 22:40 ` Daniel Jacobowitz
2004-07-03 9:28 ` Eli Zaretskii
2004-07-04 6:14 ` Daniel Jacobowitz [this message]
2004-07-04 19:20 ` Eli Zaretskii
2004-07-03 11:45 Michael Elizabeth Chastain
2004-07-03 21:16 ` Eli Zaretskii
2004-07-06 17:22 ` 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=20040704061351.GA25802@nevyn.them.org \
--to=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=jimb@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