From: Marc Espie <espie@quatramaran.ens.fr>
To: gcc@gcc.gnu.org
Subject: Re: [Proposed binutils PATCH] Re: Diagnosing an intricate C++ problem
Date: Sun, 03 Sep 2000 12:10:00 -0000 [thread overview]
Message-ID: <200009031910.VAA16344@quatramaran.ens.fr> (raw)
In-Reply-To: <20000903111111.A8315@lucon.org>
In article < 20000903111111.A8315@lucon.org > you write:
>On Sun, Sep 03, 2000 at 05:31:09PM +0100, Philip Blundell wrote:
>> >>FWIW, as far as I know, binutils 2.10 is too old and so many bugs
>> >>have been fixed since then.
>> >Here's hoping that binutils next release won't have to wait for another
>> >three years...
>> My plan is to make 2.10.1 in a few weeks, and 2.11 at the end of the year.
>> If H.J can be more specific about which bugs he is having trouble
>with, we can
>> consider including the fixes in 2.10.1.
>All ELF and Linux related bug fixes are important to Linux. On the
>other hand, it takes me much less time to fix the current CVS than
>backport all those patches to 2.10. Please don't do it for Linux. We
>have to use the one based on the current sourceware.
Please do it for other platforms. Not every system has an over-eager
H.J.Lu churning bug-fixed after bug-fixed release of binutils...
next prev parent reply other threads:[~2000-09-03 12:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200007250811.DAA35595@latour.rsch.comm.mot.com>
[not found] ` <Pine.BSF.4.21.0009021957530.89194-100000@taygeta.dbai.tuwien.ac.at>
[not found] ` <20000902113513.A1131@lucon.org>
2000-09-03 8:33 ` Marc Espie
2000-09-03 9:42 ` Philip Blundell
2000-09-03 11:11 ` H . J . Lu
2000-09-03 12:10 ` Marc Espie [this message]
2000-09-03 12:59 ` Zack Weinberg
2000-09-04 8:55 ` H . J . Lu
2000-09-04 15:07 Mark Kettenis
2000-09-04 17:01 ` H . J . Lu
2000-09-05 18:32 ` Joe Buck
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=200009031910.VAA16344@quatramaran.ens.fr \
--to=espie@quatramaran.ens.fr \
--cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).