From: Maxime Devos <maximedevos@telenet.be>
To: "(" <paren@disroot.org>, Julien Lepiller <julien@lepiller.eu>,
56030@debbugs.gnu.org
Subject: bug#56030: The guix pull profile is too big
Date: Thu, 21 Jul 2022 18:35:48 +0200 [thread overview]
Message-ID: <c749a063-4a9e-b885-063a-93f941a5572f@telenet.be> (raw)
In-Reply-To: <CLLH69CDKUHW.3HK1NCV0BEFFT@guix-aspire>
[-- Attachment #1.1.1.1: Type: text/plain, Size: 925 bytes --]
On 21-07-2022 18:29, ( wrote:
>> Not all linkers support linker scripts, e.g. mold doesn't from what I've
>> read because they make the linker slower.
> Would we really need to support anything other than ld, gold, and lld,
> though?
>
> -- (
We can choose to not package mold of course, but I think it would be a
good idea to support mold, because it appears to be much faster than the
others. Furthermore, I'd like to eventually switch to mold by default,
because it's much faster. From the README:
mold is so fast that it is only 2x /slower/ than |cp| on the same
machine. Feel free to file a bug <https://github.com/rui314/mold/issues>
if you find mold is not faster than other linkers.
Program (linker output size) GNU gold LLVM lld mold
Chrome 96 (1.89 GiB) 53.86s 11.74s 2.21s
Clang 13 (3.18 GiB) 64.12s 5.82s 2.90s
Firefox 89 libxul (1.64 GiB) 32.95s 6.80s 1.42s
[-- Attachment #1.1.1.2: Type: text/html, Size: 2030 bytes --]
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
prev parent reply other threads:[~2022-07-21 16:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 5:48 bug#56030: The guix pull profile is too big Julien Lepiller
2022-06-26 21:20 ` Ludovic Courtès
2022-08-30 10:04 ` zimoun
2022-07-21 14:52 ` Maxime Devos
2022-07-21 15:03 ` paren--- via Bug reports for GNU Guix
2022-07-21 15:38 ` paren--- via Bug reports for GNU Guix
2022-08-06 23:37 ` bug#56030: rfc2822 permits that left paren, but why do it? -- was " bokr
2022-07-21 15:11 ` paren--- via Bug reports for GNU Guix
2022-07-21 15:42 ` Julien Lepiller
2022-07-21 15:48 ` paren--- via Bug reports for GNU Guix
2022-07-21 15:52 ` paren--- via Bug reports for GNU Guix
2022-07-21 15:46 ` Maxime Devos
2022-07-21 15:49 ` paren--- via Bug reports for GNU Guix
2022-07-21 15:52 ` Julien Lepiller
2022-07-21 15:53 ` Maxime Devos
2022-07-21 16:13 ` paren--- via Bug reports for GNU Guix
2022-07-21 16:22 ` Maxime Devos
2022-07-21 16:29 ` paren--- via Bug reports for GNU Guix
2022-07-21 16:35 ` Maxime Devos [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c749a063-4a9e-b885-063a-93f941a5572f@telenet.be \
--to=maximedevos@telenet.be \
--cc=56030@debbugs.gnu.org \
--cc=julien@lepiller.eu \
--cc=paren@disroot.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).