From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "Simon South" <simon@simonsouth.net>, "Ludovic Courtès" <ludo@gnu.org>
Cc: 43802@debbugs.gnu.org
Subject: bug#43802: Knot: Linker runs very slowly and crashes during build
Date: Mon, 05 Oct 2020 17:26:08 +0200 [thread overview]
Message-ID: <875z7oae3z.fsf@nckx> (raw)
In-Reply-To: <878scledol.fsf@simonsouth.net>
[-- Attachment #1: Type: text/plain, Size: 876 bytes --]
Simon,
Would it make sense to provide a faster-building slower-starting
Knot variant alongside the main package?
Ludovic Courtès 写道：
> I this an LTO build (with ‘-flto’ in the compile and link
> flags)? That
> could explain the memory requirements.
No, but good guess.
Simon South 写道：
> Turns out this is not a bug.
The fast parser is written in Ragel[0], which compiles down to
almost 2 MiB of ‘C’, which is then thrown at GCC to sort out. I
know to put the kettle on before hacking on Knot locally.
What I didn't know was that these generated C files were included
in the release tarball. We have the Ragel, we can rebuild them,
and we now do so in commit
2b73e50c31a61b5dcef35a1e4b9484d9dbcb0fbc. Thanks for bringing it
to my attention.
Kind regards,
T G-R
[0]: http://www.colm.net/open-source/ragel/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2020-10-05 15:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-04 20:56 bug#43802: Knot: Linker runs very slowly and crashes during build Simon South
2020-10-04 23:01 ` Simon South
2020-10-05 0:09 ` Simon South
2020-10-05 15:26 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2020-10-05 15:44 ` Simon South
2020-10-07 22:06 ` Ludovic Courtès
2020-10-05 14:15 ` Ludovic Courtès
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=875z7oae3z.fsf@nckx \
--to=bug-guix@gnu.org \
--cc=43802@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=me@tobias.gr \
--cc=simon@simonsouth.net \
/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).