From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Neil Jerram" Newsgroups: gmane.lisp.guile.devel Subject: Re: advice on reducing C stack frame size? Date: Sun, 14 Sep 2008 18:46:04 +0200 Message-ID: <49dd78620809140946i2f0ed4d9ubd9868d58b5f7a18@mail.gmail.com> References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1221410791 3264 80.91.229.12 (14 Sep 2008 16:46:31 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 14 Sep 2008 16:46:31 +0000 (UTC) Cc: guile-devel@gnu.org To: hanwen@xs4all.nl Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Sun Sep 14 18:47:27 2008 Return-path: Envelope-to: guile-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1Keukn-0000bf-9S for guile-devel@m.gmane.org; Sun, 14 Sep 2008 18:47:17 +0200 Original-Received: from localhost ([127.0.0.1]:56085 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Keujm-0003zZ-Ol for guile-devel@m.gmane.org; Sun, 14 Sep 2008 12:46:14 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Keujg-0003ye-Ag for guile-devel@gnu.org; Sun, 14 Sep 2008 12:46:08 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Keujd-0003xp-OI for guile-devel@gnu.org; Sun, 14 Sep 2008 12:46:06 -0400 Original-Received: from [199.232.76.173] (port=33290 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Keujd-0003xm-Lr for guile-devel@gnu.org; Sun, 14 Sep 2008 12:46:05 -0400 Original-Received: from rv-out-0708.google.com ([209.85.198.246]:62270) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Keujd-00017u-D1 for guile-devel@gnu.org; Sun, 14 Sep 2008 12:46:05 -0400 Original-Received: by rv-out-0708.google.com with SMTP id k29so1967362rvb.6 for ; Sun, 14 Sep 2008 09:46:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=ga/qHZVnFULh8SZyV6wjfC7afC0izVbb/XBjgEBcF5g=; b=rl5VKfbVvgJVSOGbvnEgNZorbOgAzYKoCkBgdLd4Lr4AR1m2FmCjPzBaZEaRgTCyR2 VaEFfmn4wPnJxzgkylQwxioPUndZqmrR5vmFjyCGtgV+ipC1Ks6eFf7SlVLmwcDKH8mT zO6tUQpBSVuA/ceeUXa+Vq3vH/fMlHnY2eBRw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=ZH+fWCtCvR7tBj/b9OJVuHaqTgyqsyBpyjOcnTfloyGXgcvspIalbf9A/EIZU4GPR6 3PkjGAJm9KXJGObHoQ+76v14G4Kgp27NFaDzWyEUVp9nfofuUsZMozUp/zN9zTSmBVC/ abMqIycHqrqr/lyYmLr6QDgN1f/rS5pud0U5I= Original-Received: by 10.141.142.15 with SMTP id u15mr4144254rvn.171.1221410764252; Sun, 14 Sep 2008 09:46:04 -0700 (PDT) Original-Received: by 10.141.177.4 with HTTP; Sun, 14 Sep 2008 09:46:04 -0700 (PDT) In-Reply-To: Content-Disposition: inline X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Developers list for Guile, the GNU extensibility library" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Errors-To: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.devel:7689 Archived-At: 2008/9/13 Han-Wen Nienhuys : > 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