From: "Neil Jerram" <neiljerram@googlemail.com>
To: hanwen@xs4all.nl
Cc: guile-devel@gnu.org
Subject: Re: advice on reducing C stack frame size?
Date: Sun, 14 Sep 2008 18:46:04 +0200 [thread overview]
Message-ID: <49dd78620809140946i2f0ed4d9ubd9868d58b5f7a18@mail.gmail.com> (raw)
In-Reply-To: <gah20r$p48$1@ger.gmane.org>
2008/9/13 Han-Wen Nienhuys <hanwen@xs4all.nl>:
> Andy Wingo escreveu:
>>
>> My question is: what should I do about this? Wait for the runtime tuning
>> patches to land in master and then merge them? Assume that over time, I
>
> This looks like a bug or an oversight. - 14k is about 3500 SCM values; we surely
> don't have that many local variables, so it looks as if there might be some
> macro that expands into a local array. I'd have a look at the addresses of the
> different local variables to see where all that memory is going. Also, look at
> the preprocessed source and scan for array variables.
I agree. I would first try to find out if the apparent 20k/14k is
real, and if so what accounts for it all.
Neil
next prev parent reply other threads:[~2008-09-14 16:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-13 16:56 advice on reducing C stack frame size? Andy Wingo
2008-09-13 18:48 ` Han-Wen Nienhuys
2008-09-14 16:46 ` Neil Jerram [this message]
2008-09-16 5:27 ` Ken Raeburn
2008-09-16 17:57 ` Andy Wingo
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=49dd78620809140946i2f0ed4d9ubd9868d58b5f7a18@mail.gmail.com \
--to=neiljerram@googlemail.com \
--cc=guile-devel@gnu.org \
--cc=hanwen@xs4all.nl \
/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).