From: ng0 <ng0@infotropique.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>,
Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Subject: Re: Compilation failure on very large module
Date: Tue, 13 Jun 2017 12:27:44 +0000 [thread overview]
Message-ID: <20170613122744.u5p66es7adtycu7y@abyayala> (raw)
In-Reply-To: <87fuf42i8j.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1144 bytes --]
Ludovic Courtès transcribed 0.9K bytes:
> Hello,
>
> Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> skribis:
>
> > Here’s the crash with Guile 2.2. I’ve added the module to the list of
> > modules that should be compiled and ran “make”. You can see that there
> > are a couple of undefined variables, but I don’t think this should lead
> > to a crash.
>
> Looks like the same problem as outlined here:
> <https://lists.gnu.org/archive/html/guile-devel/2017-05/msg00033.html>.
>
> Basically the compiler’s memory consumption seems to be proportional to
> the size of the input file, when I think it should be proportional to
> the complexity of the most complex top-level expression given that Guile
> doesn’t do inter-procedural analysis.
>
> (The failure you get on 2.0 seems to be another story: apparently we’re
> hitting a limitation somewhere in the object format.)
>
> Ludo’.
>
>
It is no longterm fix, but how about splitting up the largest
modules we have in several reasonable sized modules?
--
ng0
OpenPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
https://krosos.org/~/ng0/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-06-13 12:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 8:41 Compilation failure on very large module Ricardo Wurmus
2017-06-13 9:11 ` Ricardo Wurmus
2017-06-13 12:18 ` Ludovic Courtès
2017-06-13 12:27 ` ng0 [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=20170613122744.u5p66es7adtycu7y@abyayala \
--to=ng0@infotropique.org \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=ricardo.wurmus@mdc-berlin.de \
/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).