From: Andrew Cagney <ac131313@cygnus.com>
To: Michael Elizabeth Chastain <chastain@cygnus.com>,
Daniel Berlin <dberlin@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: C++ FAIL counts and the effect of demangler fix
Date: Thu, 15 Feb 2001 10:27:00 -0000 [thread overview]
Message-ID: <3A8C1E5E.F4A2C5E2@cygnus.com> (raw)
In-Reply-To: <200102141649.IAA28922@bosch.cygnus.com>
Michael Elizabeth Chastain wrote:
> > It would be nice if the problems were resolved, however, they are _NOT_
> > a 5.1 release criteria so not especially high on my radar. 5.1 needs
> > to work with real compilers installed on real machines.
>
> I respectfully disagree. I think gdb 5.1 needs to be ready for gcc 3.0.
I can see why both of you might disagree, however my position stands.
Remember:
o I'm not stopping you trying to fix
all the bugs. I'm just stopping you
making that last critical bug/feature
(minus the next one) the reason to delay
the release of GDB 5.1.
o we're trying to move to a situtation where
there are more frequent releases of GDB
(and I'm failing dismally). Right now
5.1 is effectivly stuck because it
needs SPARC/Linux fixed.
o I don't want GDB's release schedule in
someway directly tided to GCC's release
schedule.
I also posted this decision to the discussion list and at the time I had
ZERO responses.
Andrew
next prev parent reply other threads:[~2001-02-15 10:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-14 8:49 Michael Elizabeth Chastain
2001-02-15 10:27 ` Andrew Cagney [this message]
2001-02-15 13:46 ` Per Bothner
2001-02-15 15:06 ` Andrew Cagney
2001-02-15 15:14 ` Per Bothner
2001-02-15 23:35 ` Eli Zaretskii
2001-02-16 0:58 ` Daniel Berlin
2001-02-16 2:32 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2001-02-14 10:24 Michael Elizabeth Chastain
2001-02-14 8:52 Michael Elizabeth Chastain
2001-02-14 10:06 ` Daniel Berlin
2001-02-14 0:06 Michael Elizabeth Chastain
2001-02-14 7:31 ` Andrew Cagney
2001-02-14 8:28 ` Daniel Berlin
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=3A8C1E5E.F4A2C5E2@cygnus.com \
--to=ac131313@cygnus.com \
--cc=chastain@cygnus.com \
--cc=dberlin@redhat.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