This is the mail archive of the
mailing list for the binutils project.
Re: Release 2.23
- From: Richard Earnshaw <rearnsha at arm dot com>
- To: Tristan Gingold <gingold at adacore dot com>
- Cc: Matthias Klose <doko at ubuntu dot com>, "nickc at redhat dot com" <nickc at redhat dot com>, binutils Development <binutils at sourceware dot org>
- Date: Wed, 01 Aug 2012 15:02:45 +0100
- Subject: Re: Release 2.23
- References: <EFF1B4C0-3885-4580-8DA9-23540D588E9E@adacore.com> <50183FF0.firstname.lastname@example.org> <975FAACC-5CF5-4426-80A5-AB11F995A1F3@adacore.com>
On 01/08/12 14:58, Tristan Gingold wrote:
> On Jul 31, 2012, at 10:28 PM, Matthias Klose wrote:
>> On 23.07.2012 14:40, Tristan Gingold wrote:
>>> I was rather busy before the summer and hence I didn't take the time to create a 2.22.1 release.
>>> I can however schedule a release for this summer. So my plan is:
>>> * I will create the 2.23 branch this week and creating a pre-release just after.
>>> * I plan to do the 2.23 release at the end of August or at the beginning of September (unless there is a blocking issue).
>>> So, if you have big or large changes, it would be nice to wait a little bit. And as usual, do not hesitate to test your favourite platforms.
>> what are the chances to get the recently submitted aarch64 target backported to
>> the branch once it is accepted for the trunk?
> Looks like some of you would like to have aarch64 in 2.23.
> As it might change the schedule, I'd like to understand the reasons for having aarch64 in 2.23
Because binutils is a key enabler and rolling this out into various
distros is significantly harder if it isn't in a major release. In
particular we're targetting GCC-4.8 for the main compiler support and
that needs a binutils that supports it.
Why are we planning a binutils release so much earlier this year than we
have done for the previous 3 or 4 years (at least)?