From: matt smith <infinite_south@yahoo.com>
To: gcc-help@gcc.gnu.org
Subject: stack allocation
Date: Sun, 12 Dec 2004 19:21:00 -0000 [thread overview]
Message-ID: <20041212192105.94719.qmail@web50706.mail.yahoo.com> (raw)
This issue has been discussed in a few threads that I
have found on google but there was no conclusive
answer given for the phenomenon.
example1.c
void function(int a, int b, int c) {
char buffer1[5];
char buffer2[10];
}
void main() {
function(1,2,3);
}
When you issue the "gcc -S -o example1.s example1.c"
command and view the function prolog you see that the
compiler reserves 40 bytes for these two arrays.
subl $40, %esp
To me the expected behavior should be subl $24, %esp
or in other words reserving 24 bytes of stack space.
Why the discrepancy? Thanks
Josh
__________________________________
Do you Yahoo!?
Meet the all-new My Yahoo! - Try it today!
http://my.yahoo.com
next reply other threads:[~2004-12-12 19:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-12 19:21 matt smith [this message]
2004-12-16 19:08 ` jlh
[not found] <CAPhGq=bY8hS0DF2rf7_5E8ycYS52uJR8UH=Yjb0NiDBdaSR+6Q@mail.gmail.com>
2011-11-18 17:57 ` Stack allocation Alexandru Juncu
2011-11-18 19:35 ` Andrew Haley
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=20041212192105.94719.qmail@web50706.mail.yahoo.com \
--to=infinite_south@yahoo.com \
--cc=gcc-help@gcc.gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).