From: Richard Sandiford <rdsandiford@googlemail.com>
To: binutils@sourceware.org
Subject: Re: Release 2.21 - rough schedule
Date: Wed, 22 Sep 2010 19:31:00 -0000 [thread overview]
Message-ID: <87lj6tpocq.fsf@firetop.home> (raw)
In-Reply-To: <20100921003158.GL16874@bubble.grove.modra.org> (Alan Modra's message of "Tue, 21 Sep 2010 10:01:58 +0930")
Alan Modra <amodra@gmail.com> writes:
> On Mon, Sep 20, 2010 at 04:48:07PM +0100, Richard Earnshaw wrote:
>> On Sat, 2010-09-18 at 12:29 +0930, Alan Modra wrote:
>> > arm-aout arm-coff arm-epoc-pe arm-linux arm-netbsdelf arm-none-eabi arm-nto arm-pe arm-symbianelf arm-vxworks arm-wince-pe
>>
>> So arm-linux isn't very interesting these days, and nor is arm-aout
>> (which I'm surprised we still claim to support at all). But
>
> Deprecate it. If ARM maintainers aren't interested in a target it's
> likely that users are better served by staying with an older version
> of binutils.
Talking about deprecation, I wonder if anyone uses the non-ELF MIPS
ports with up-to-date binutils? mips-ecoff has had terrible testresults
for a while, but I've no idea whether the failures are benign.
Richard
next prev parent reply other threads:[~2010-09-22 19:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-02 14:09 Tristan Gingold
2010-09-07 16:38 ` Doug Kwan (關振德)
2010-09-18 2:59 ` Alan Modra
2010-09-20 15:48 ` Richard Earnshaw
2010-09-21 0:32 ` Alan Modra
2010-09-22 15:22 ` Tejas Belagod
2010-09-22 19:31 ` Richard Sandiford [this message]
2010-09-22 22:58 ` Maciej W. Rozycki
2010-09-23 7:17 ` Tristan Gingold
2010-09-23 12:19 ` Maciej W. Rozycki
2010-09-18 7:31 ` Matt Rice
2010-09-21 9:24 ` Mike Frysinger
2010-09-21 9:26 ` Tristan Gingold
2010-09-21 9:28 ` Kai Tietz
2010-09-21 9:31 ` Tristan Gingold
2010-09-21 9:44 ` Kai Tietz
2010-09-23 5:11 ` Dave Korn
2010-09-23 7:33 ` Tristan Gingold
2010-10-21 12:33 ` Release 2.21 - schedule Tristan Gingold
2010-11-03 14:12 ` Release 2.21 - branch on Friday ? Tristan Gingold
2010-11-04 2:40 ` Dave Korn
2010-11-04 8:11 ` Tristan Gingold
2010-11-05 9:24 ` Branch 2.21 created Tristan Gingold
2010-12-08 19:38 ` Andreas Schwab
2010-12-08 23:44 ` Alan Modra
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=87lj6tpocq.fsf@firetop.home \
--to=rdsandiford@googlemail.com \
--cc=binutils@sourceware.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).