From: "Maciej W. Rozycki" <macro@imgtec.com>
To: Tristan Gingold <gingold@adacore.com>
Cc: binutils <binutils@sourceware.org>
Subject: Re: Binutils release 2.28 - soon
Date: Wed, 01 Feb 2017 23:33:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1702012303110.26999@tp.orcam.me.uk> (raw)
In-Reply-To: <alpine.DEB.2.00.1612231852180.6743@tp.orcam.me.uk>
On Fri, 23 Dec 2016, Maciej W. Rozycki wrote:
> FYI, I'll be automatically pushing all changes I've intended to make as
> a part of the current MIPS development effort to this branch then, until
> a further notice.
>
> I'll be away from tomorrow until Jan 8th, and I will have further stuff
> to push when I am back, as I won't be able to complete the documentation
> and test suite updates tonight for the upcoming MIPS feature I intend to
> publish.
I have decided to withdraw from pushing the feature originally intended
for 2.28 and keep it to the master branch only.
Firstly, the delay incurred by all the work related to recent bug fixes,
and PR ld/20828 in particular, means that any further work on the 2.28
branch would potentially continue blocking the release without a good
justification. Secondly, the extra time bought will let me update the
feature with some enhancements recently envisaged, making it more complete
right from the beginning. It does not mean I expect any significant delay
with that code though -- it's just that it'll happen on the master branch
only.
I think there may yet be some further fallout from PR ld/20828 affecting
2.28, but otherwise, with the final tweaks to the test suite just applied,
I consider myself done with MIPS target changes intended for 2.28.
There are still:
FAIL: objcopy -shared -z relro (tbss1)
FAIL: objcopy -shared -z relro (tbss2)
FAIL: objcopy -shared -z relro (tbss3)
uninvestigated MIPS regressions remaining, which I regret, however they
are long-standing and not necessarily an actual linker issue. I will
strive to resolve them on master soon.
However if anyone has anything they consider important to resolve for
2.28 and the MIPS target, then please do let me know and I'll see what I
can do.
And last but not least thanks for your patience, Tristan, and your effort
with release management!
Maciej
next prev parent reply other threads:[~2017-02-01 23:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-12 9:49 Tristan Gingold
2016-12-12 13:58 ` Jiong Wang
2016-12-13 11:13 ` Nick Clifton
2016-12-13 13:00 ` Jiong Wang
2016-12-12 23:57 ` Alan Modra
2016-12-13 0:08 ` Andrew Pinski
2016-12-13 5:20 ` Yury Norov
2016-12-13 11:01 ` Maciej W. Rozycki
2016-12-15 4:54 ` Palmer Dabbelt
2016-12-23 4:26 ` Cary Coutant
2016-12-23 9:13 ` Tristan Gingold
2016-12-23 19:08 ` Maciej W. Rozycki
2016-12-24 3:26 ` Alan Modra
2017-02-01 23:33 ` Maciej W. Rozycki [this message]
2017-02-02 16:52 ` Tristan Gingold
2017-02-15 1:46 ` Alan Modra
2017-02-15 19:42 ` H.J. Lu
2017-02-19 0:38 ` Palmer Dabbelt
2016-12-29 3:47 ` Matthias Klose
2016-12-29 4:44 ` Joel Brobecker
2016-12-29 13:58 ` Matthias Klose
2016-12-29 14:33 ` Maciej W. Rozycki
2016-12-30 5:49 ` Joel Brobecker
2016-12-30 6:18 ` Matthias Klose
2016-12-30 6:42 ` Joel Brobecker
2016-12-30 9:15 ` Andreas Schwab
2016-12-31 3:43 ` Joel Brobecker
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=alpine.DEB.2.00.1702012303110.26999@tp.orcam.me.uk \
--to=macro@imgtec.com \
--cc=binutils@sourceware.org \
--cc=gingold@adacore.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).