From: Fangrui Song <i@maskray.me>
To: "Maciej W. Rozycki" <macro@wdc.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>,
"binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: Release 2.35 on Friday 24th ?
Date: Fri, 24 Jul 2020 16:34:25 -0700 [thread overview]
Message-ID: <20200724233425.q7iuvxwfd7bryflk@gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.21.2007241232470.24175@redsun52.ssa.fujisawa.hgst.com>
On 2020-07-24, Maciej W. Rozycki via Binutils wrote:
>On Fri, 24 Jul 2020, H.J. Lu wrote:
>
>> > Is it time to deprecate gold ?
>>
>> Yes, we should. I think lld is a good replacement for gold.
>
> It is not free software however.
>
> Maciej
https://www.gnu.org/licenses/license-list.en.html#apache2
> This is a free software license, compatible with version 3 of the GNU GPL.
http://www.apache.org/licenses/GPL-compatibility.html
> Apache 2 software can therefore be included in GPLv3 projects, because
> the GPLv3 license accepts our software into GPLv3 works.
If an lld executable is 90MiB, 87MiB is due to LLVM LTO. If you drop
those stuff, the executable is just 3MiB. If someone wants an
LLVM-library free linker, grab https://github.com/MaskRay/picolld/ ,
reimplement some LLVM support libraries (llvm/ADT/ llvm/Support). The
simplest is to use C++ std::, it is likely doable in a few thousand
lines of code. You will get a linker with
ARM/AArch64/PowerPC32/PowerPC64/RISC-V/x86 support with ~30000 lines of
code.
next prev parent reply other threads:[~2020-07-24 23:34 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
2020-07-24 11:42 ` Maciej W. Rozycki
2020-07-24 23:34 ` Fangrui Song [this message]
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=20200724233425.q7iuvxwfd7bryflk@gmail.com \
--to=i@maskray.me \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=macro@wdc.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).