From: Simon South <simon@simonsouth.net>
To: 43802@debbugs.gnu.org
Subject: bug#43802: Knot: Linker runs very slowly and crashes during build
Date: Sun, 04 Oct 2020 19:01:06 -0400 [thread overview]
Message-ID: <87mu11egul.fsf@simonsouth.net> (raw)
In-Reply-To: <87a6x1g17f.fsf@simonsouth.net>
So naturally, as soon as I submit the bug report something occurs to me
that gets me unstuck.
The delay and crash are occuring while libtool is using gcc to compile
src/libzscanner/scanner.c, which appears to be generated at build time
from the file scanner.c.t0 in the same directory.
When I build Knot on my own, scanner.c has a size of 272 KB. When guix
builds it, scanner.c somehow balloons out to 1.9 MB! So naturally gcc is
going to need some time and space to make its way through all that code.
In fact the build process actually points out
NOTE: Compilation of scanner.c can take several minutes!
So perhaps all this is completely expected. Still... 1.9 MB. Of C
code. It's tempting to think something is going wrong here. (And anyway,
why the huge discrepancy in file size?)
I'm investigating.
--
Simon South
simon@simonsouth.net
next prev parent reply other threads:[~2020-10-05 12:49 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 [this message]
2020-10-05 0:09 ` Simon South
2020-10-05 15:26 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
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=87mu11egul.fsf@simonsouth.net \
--to=simon@simonsouth.net \
--cc=43802@debbugs.gnu.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).