* stack frames
@ 2000-12-29 7:40 Roland Silver
2000-12-29 12:35 ` Alexandre Oliva
0 siblings, 1 reply; 2+ messages in thread
From: Roland Silver @ 2000-12-29 7:40 UTC (permalink / raw)
To: help-gcc
I have some questions about stack frames -- or rather, the stack on
which stack frames are allocated -- call it the "F-stack".
1. How many bytes are allocated to the F-stack when an app is launched?
2. How can I specify that allocation?
3. What happens if that stack is overpushed?
4. Is there protection against overpushing the F-stack?
I'd greatly appreciate anyone answering some or all of these
questions, with a Cc to me at <rollo@kitcarson.net>.
--
--Roland Silver <rollo@kitcarson.net>
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: stack frames
2000-12-29 7:40 stack frames Roland Silver
@ 2000-12-29 12:35 ` Alexandre Oliva
0 siblings, 0 replies; 2+ messages in thread
From: Alexandre Oliva @ 2000-12-29 12:35 UTC (permalink / raw)
To: Roland Silver; +Cc: help-gcc
On Dec 29, 2000, Roland Silver <rollo@kitcarson.net> wrote:
> 1. How many bytes are allocated to the F-stack when an app is launched?
It depends on the operating system.
> 2. How can I specify that allocation?
It depends on the operating system.
> 3. What happens if that stack is overpushed?
Undefined behavior.
> 4. Is there protection against overpushing the F-stack?
Only in functions compiled with -fstack-check.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2000-12-29 12:35 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-12-29 7:40 stack frames Roland Silver
2000-12-29 12:35 ` Alexandre Oliva
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).