This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] New -fstack-check implementation (1/n)

On Tue, 2006-11-28 at 18:13 +0100, Eric Botcazou wrote:
> > It's certainly of great interest to Java.  Is the design of this
> > documented somewhere?
> There are a few bits in the manual of the GCC internals, in the section
> "14.9.3 Specifying How Stack Checking is Done"
> Otherwise (no MMU or no guard pages, e.g. x86{-64}/Linux), we keep track in 
> the runtime of the stack usage for every thread (of course the primary thread 
> is special) and the compiler emits explicit calls to the runtime before any 
> stack allocations.  It's then up to the runtime to raise the exception 
> directly (gcc/ada/[sb]).

I am also interested in this because right now the SPU target uses it
too.  Maybe I am more interested in not breaking the use for the SPU
target rather than in the implementation.  The reason why people use
-fstack-check on the SPU is because memory is tight (256k) so they would
like to know while developing if they run out of stack space.

Andrew Pinski

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]