From: "H.J. Lu" <hjl.tools@gmail.com>
To: Nick Clifton <nickc@redhat.com>
Cc: Alan Modra <amodra@gmail.com>,
"Maciej W. Rozycki" <macro@wdc.com>,
"binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: Release 2.35 on Friday 24th ?
Date: Fri, 24 Jul 2020 04:29:08 -0700 [thread overview]
Message-ID: <CAMe9rOrrRzfBsbQ-DZ6u_UEjZo36emNp6JKcjHGRXSYaBe=uGw@mail.gmail.com> (raw)
In-Reply-To: <8fe29f99-4ddd-0467-ee16-03228a430e0d@redhat.com>
On Fri, Jul 24, 2020 at 4:23 AM Nick Clifton <nickc@redhat.com> wrote:
>
> Hi Guys,
>
> > On 2020-07-24 03:13, Alan Modra wrote:
>
> > Gold isn't in good shape when using modern gcc and glibc.
>
> I have been wondering if gold has started to bit-rot. I mean no
> insult to Cary or anyone else, but it seems to me that development
> work on gold has come to a halt, and bug fixes and new features are
> only being added when they are ported from the BFD linker.
>
> Is it time to deprecate gold ?
Yes, we should. I think lld is a good replacement for gold.
--
H.J.
next prev parent reply other threads:[~2020-07-24 11:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 15:05 Proposal: Earlier 2.35 release Nick Clifton
2020-06-02 15:16 ` H.J. Lu
2020-06-02 15:52 ` Michael Matz
2020-06-02 16:07 ` Matthias Klose
2020-06-02 16:11 ` Jose E. Marchesi
[not found] ` <alpine.LFD.2.21.2007221518200.24175@redsun52.ssa.fujisawa.hgst.com>
[not found] ` <7d209c63-c3e8-c22b-ce90-0bdfca4aa3f0@redhat.com>
[not found] ` <alpine.LFD.2.21.2007221712320.24175@redsun52.ssa.fujisawa.hgst.com>
2020-07-23 14:51 ` Release 2.35 on Friday 24th ? Nick Clifton
2020-07-23 15:24 ` H.J. Lu
2020-07-23 19:31 ` Maciej W. Rozycki
2020-07-24 2:13 ` Alan Modra
2020-07-24 3:09 ` H.J. Lu
2020-07-24 6:20 ` Alan Modra
2020-07-24 11:23 ` Nick Clifton
2020-07-24 11:29 ` H.J. Lu [this message]
2020-07-24 11:42 ` Maciej W. Rozycki
2020-07-24 23:34 ` Fangrui Song
2020-07-24 23:55 ` Maciej W. Rozycki
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='CAMe9rOrrRzfBsbQ-DZ6u_UEjZo36emNp6JKcjHGRXSYaBe=uGw@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=macro@wdc.com \
--cc=nickc@redhat.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).