From: Adrian Bunk <bunk@stusta.de>
To: Roland Dreier <roland@topspin.com>
Cc: "Jörn Engel" <joern@wohnheim.fh-wedel.de>,
"Yum Rayan" <yum.rayan@gmail.com>,
linux-kernel@vger.kernel.org, mvw@planets.elm.net
Subject: Re: Stack usage tasks
Date: Thu, 31 Mar 2005 23:19:41 +0200 [thread overview]
Message-ID: <20050331211941.GJ3185@stusta.de> (raw)
In-Reply-To: <52ll83mtqd.fsf@topspin.com>
On Thu, Mar 31, 2005 at 12:43:38PM -0800, Roland Dreier wrote:
> > The task I'm suggesting was therefore:
> > - remove the -fno-unit-at-a-time in arch/i386/Makefile in your private
> > kernel sources
> > - use gcc 3.4
> > - reduce the stack usages in call paths > 3kB
>
> This is a good idea. However, I might suggest using gcc 4.0 (you'll
> have to use a snapshot now, but the release should only be a few weeks
> away). A patch went into gcc 4.0 that makes gcc more intelligent
> about sharing stack for variables that cannot be alive at the same
> time, and therefore it may be more feasible to make unit-at-a-time
> work for the i386 kernels.
That's one option.
Jörn, can you send a list of call paths with a stack usage > 3kB when
compiling with gcc 3.4 and unit-at-a-time (or tell me how to generate
these lists)?
If fixing a handful of places was sufficient, it was IMHO worth it for
enabling unit-at-a-time with gcc 3.4 .
> - R.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2005-03-31 21:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-31 7:39 [PATCH] Reduce stack usage in acct.c Yum Rayan
2005-03-31 15:05 ` Jörn Engel
2005-03-31 20:09 ` Randy.Dunlap
2005-03-31 20:40 ` Adrian Bunk
2005-03-31 20:30 ` Stack usage tasks Adrian Bunk
2005-03-31 20:43 ` Roland Dreier
2005-03-31 21:19 ` Adrian Bunk [this message]
2005-04-01 10:17 ` Jörn Engel
2005-04-01 11:16 ` Jörn Engel
2005-04-03 11:35 ` [PATCH] Reduce stack usage in acct.c Olaf Dietsche
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050331211941.GJ3185@stusta.de \
--to=bunk@stusta.de \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mvw@planets.elm.net \
--cc=roland@topspin.com \
--cc=yum.rayan@gmail.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