unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Andy Wingo <wingo@igalia.com>,
	19180@debbugs.gnu.org, guile-devel@gnu.org
Subject: bug#19180: Weak tables harmful to GC?
Date: Thu, 26 Oct 2017 10:17:15 -0700	[thread overview]
Message-ID: <87o9othlr8.fsf__25131.0694883161$1509038298$gmane$org@gnu.org> (raw)
In-Reply-To: <87k1zimhmt.fsf@elephly.net> (Ricardo Wurmus's message of "Thu, 26 Oct 2017 10:35:06 +0200")

Hi Ricardo,

Ricardo Wurmus <rekado@elephly.net> skribis:

> I tried building Guile with the following Guix package definition:
>
> (define-public guile-2.2-awesome
>   (package (inherit guile-2.2)
>     (name "guile-awesome")
>     (source (origin (inherit (package-source guile-2.2))
>        (patches (list "/home/rwurmus/0001-Remove-weak-tables-and-revert-to-weak-hash-tables.patch"
>                       "/home/rwurmus/0002-Keep-weak-hash-table-item-count-consistent.patch"))))

[...]

>   BOOTSTRAP GUILEC system/foreign.go
> GC Warning: Repeated allocation of very large block (appr. size 230096896):
>         May lead to memory leak and poor performance
> GC Warning: Repeated allocation of very large block (appr. size 230096896):
>         May lead to memory leak and poor performance
> GC Warning: Repeated allocation of very large block (appr. size 230096896):
>         May lead to memory leak and poor performance
> GC Warning: Repeated allocation of very large block (appr. size 230096896):
>         May lead to memory leak and poor performance
> GC Warning: Repeated allocation of very large block (appr. size 230096896):
>         May lead to memory leak and poor performance
> GC Warning: Repeated allocation of very large block (appr. size 230096896):
>         May lead to memory leak and poor performance
> GC Warning: Repeated allocation of very large block (appr. size 230096896):
>         May lead to memory leak and poor performance
> Too many heap sections: Increase MAXHINCR or MAX_HEAP_SECTS
> /gnu/store/kpxi8h3669afr9r1bgvaf9ij3y4wdyyn-bash-minimal-4.4.12/bin/bash: line 6: 30796 Aborted                 GUILE_AUTO_COMPILE=0 ../meta/build-env guild compile --target="x86_64-unknown-linux-gnu" -O1 -L "/tmp/guix-build-guile-awesome-2.2.2.drv-0/guile-2.2.2/module" -L "/tmp/guix-build-guile-awesome-2.2.2.drv-0/guile-2.2.2/guile-readline" -o "language/scheme/compile-tree-il.go" "../module/language/scheme/compile-tree-il.scm"
> make[2]: *** [Makefile:1928: language/scheme/compile-tree-il.go] Error 134

Blech, that doesn’t sound like an improvement.

“make clean -C module && make” works for me, but now that I think of it
it might be reusing stuff from the prebuilt/ directory.

I’ll try again later.

Thanks for testing,
Ludo’.





  parent reply	other threads:[~2017-10-26 17:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87wp9gwz8m.fsf@gnu.org>
     [not found] ` <87fug4o8z2.fsf@pobox.com>
     [not found]   ` <87wp54z3p5.fsf@gnu.org>
     [not found]     ` <87zi9th1i6.fsf_-_@gnu.org>
     [not found]       ` <87y3o454pr.fsf@gnu.org>
     [not found]         ` <87r2tvncs5.fsf@dustycloud.org>
     [not found]           ` <87wp3mwwef.fsf@gnu.org>
     [not found]             ` <87po9c88rx.fsf@dustycloud.org>
     [not found]               ` <87o9owm9v1.fsf@gnu.org>
2017-10-25  0:50                 ` bug#19180: Weak tables harmful to GC? Christopher Allan Webber
     [not found]                 ` <87o9ow830m.fsf@dustycloud.org>
2017-10-25 17:11                   ` Ludovic Courtès
     [not found]             ` <87mv4gd0ik.fsf@elephly.net>
2017-10-25  6:38               ` Ricardo Wurmus
2017-10-26  7:03               ` Ludovic Courtès
     [not found]               ` <87a80eie63.fsf@gnu.org>
2017-10-26  8:35                 ` Ricardo Wurmus
     [not found]                 ` <87k1zimhmt.fsf@elephly.net>
2017-10-26 16:52                   ` Ricardo Wurmus
2017-10-26 17:17                   ` Ludovic Courtès [this message]
     [not found]                   ` <87bmktn96e.fsf@elephly.net>
2017-10-27  5:28                     ` Ludovic Courtès
     [not found]                     ` <87tvyl9n22.fsf@gnu.org>
2017-10-28  9:56                       ` Ricardo Wurmus
     [not found]                       ` <87r2tnlhno.fsf@elephly.net>
2017-10-30 12:35                         ` Ludovic Courtès
     [not found]                         ` <87a8087qz7.fsf@gnu.org>
2017-10-30 14:48                           ` Ricardo Wurmus
     [not found]                           ` <87d154lmio.fsf@mdc-berlin.de>
2017-10-30 17:20                             ` Ricardo Wurmus
     [not found]                             ` <878tfslfgl.fsf@mdc-berlin.de>
2017-10-30 22:18                               ` Ludovic Courtès
2017-10-30 17:29                           ` Andy Wingo
2017-10-30 23:13                             ` Ludovic Courtès
     [not found]                             ` <87zi88ut3k.fsf@gnu.org>
2017-10-31  8:25                               ` Andy Wingo
     [not found]                               ` <877evbiuzy.fsf@igalia.com>
2017-10-31 16:56                                 ` 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://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='87o9othlr8.fsf__25131.0694883161$1509038298$gmane$org@gnu.org' \
    --to=ludo@gnu.org \
    --cc=19180@debbugs.gnu.org \
    --cc=guile-devel@gnu.org \
    --cc=rekado@elephly.net \
    --cc=wingo@igalia.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).