This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Inlining vs the stack
- From: Daniel Berlin <dberlin at dberlin dot org>
- To: Bernd Jendrissek <berndj at prism dot co dot za>
- Cc: Ian Lance Taylor <ian at airs dot com>, Mike Stump <mrs at apple dot com>, Paul Koning <pkoning at equallogic dot com>, dalej at apple dot com, gcc at gcc dot gnu dot org, jh at suse dot cz
- Date: Sun, 14 Aug 2005 12:13:28 -0400
- Subject: Re: Inlining vs the stack
- References: <m3slxeg8js.fsf@gossamer.airs.com> <20050814160152.GA5090@prism.co.za>
> You'd expect the attempt to grow the stack to be made only *after*
> keep_going hits zero.
Only if you thought you knew better than the compiler :)
> I'd rather not have the compiler presume
> certainty of a 10GB stack allocation, especially not if it's actually
> pretty unlikely.
It could still be done, even if we inline.
There is nothing that prevents us from adding space to the stack
allocation only at that point, it's just not coded in gcc to do that.