From: Joel Brobecker <brobecker@gnat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: cagney@gnu.org, ica2_ts@csv.ica.uni-stuttgart.de,
kettenis@chello.nl, gdb-patches@sources.redhat.com
Subject: Re: [RFA] MIPS_TEXT symbols should be associated to .text section?
Date: Fri, 30 Jul 2004 18:55:00 -0000 [thread overview]
Message-ID: <20040730185513.GT1167@gnat.com> (raw)
In-Reply-To: <1190-Fri30Jul2004214217+0300-eliz@gnu.org>
> What's to prevent us from holding 6.2 until this bug is resolved?
> What's the rush to put out a release with broken MIPS support?
Andrew probably has reasons for not delaying the release, and
I respect them.
I would be pleased if we delayed 6.2 for IRIX. But the fact of the
matter is that I discovered the fact while the first 6.2 tarball
was being made, and I also don't know how long we would need to delay it
before we could get IRIX back into a releasable shape. So I can't ask
for the delay, especially since IRIX support in 6.0 and 6.1 was broken
too.
Part of the problem with the unknown delay is with the fact that
one patch is out of our control (I am actively discussing with a BFD
mantainer, so hopefully we'll have a resolution soon), and the other
part of the problem is that the other 2 GDB patches apparently need
more work (On one of them, Andrew thinks we need some reorganization
to take place before my patch can go in, and on the other he wants
the patch to be more complete). I personally think that we are letting
the best be the enemy of good, as we could have a much better GDB right
now with a couple of adjustements left for later, but it's not my decision.
--
Joel
next prev parent reply other threads:[~2004-07-30 18:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-21 20:46 Joel Brobecker
2004-07-29 22:02 ` Joel Brobecker
2004-07-29 22:19 ` Thiemo Seufer
2004-07-29 23:15 ` Mark Kettenis
2004-07-30 0:31 ` Thiemo Seufer
2004-07-30 11:32 ` Eli Zaretskii
2004-07-30 13:37 ` Andrew Cagney
2004-07-30 18:04 ` Eli Zaretskii
2004-07-30 18:13 ` Joel Brobecker
2004-07-30 18:44 ` Eli Zaretskii
2004-07-30 18:55 ` Joel Brobecker [this message]
2004-07-30 19:36 ` Eli Zaretskii
2004-07-30 19:59 ` Andrew Cagney
2004-07-30 22:29 ` Michael Chastain
2004-07-30 18:08 ` Joel Brobecker
2004-07-30 18:57 ` Thiemo Seufer
2004-07-30 21:08 ` Mark Kettenis
2004-07-30 23:03 ` Joel Brobecker
2004-07-30 23:57 ` Thiemo Seufer
2004-07-30 18:19 ` Joel Brobecker
2004-07-30 0:17 ` Joel Brobecker
2004-07-22 15:47 David Anderson
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=20040730185513.GT1167@gnat.com \
--to=brobecker@gnat.com \
--cc=cagney@gnu.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=ica2_ts@csv.ica.uni-stuttgart.de \
--cc=kettenis@chello.nl \
/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