From: Stefan Israelsson Tampe <stefan.itampe@gmail.com>
To: guile-devel <guile-devel@gnu.org>
Subject: Compiler Warning message ideas
Date: Sun, 22 Jan 2012 23:01:39 +0100 [thread overview]
Message-ID: <CAGua6m2DtPJfMPZHt1qH_kDa+or6U2j84uxD679e6TGi7rY7NA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 629 bytes --]
When compiling newest stable-2.0 I noticed,
wrote `ice-9/eval.go'
GUILEC ice-9/psyntax-pp.go
GC Warning: Repeated allocation of very large block (appr. size 69632):
May lead to memory leak and poor performance.
wrote `ice-9/psyntax-pp.go'
E.g. basically making a thread allocates a large block for the stack and
the bohem gc explicitly tells us
that doing this will probably lead to memory leak using their gc.
So, make sure to use "thread pools" or at least pools of stacks.
An idea is to hack on guile so that thread creation will allocate the
stacks from a pool and then see if the
memory leak is plugged.
/Stefan
[-- Attachment #2: Type: text/html, Size: 707 bytes --]
next reply other threads:[~2012-01-22 22:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-22 22:01 Stefan Israelsson Tampe [this message]
2012-01-23 15:48 ` Compiler Warning message ideas 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=CAGua6m2DtPJfMPZHt1qH_kDa+or6U2j84uxD679e6TGi7rY7NA@mail.gmail.com \
--to=stefan.itampe@gmail.com \
--cc=guile-devel@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.
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).