public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andreas Bauer <baueran@in.tum.de>
To: gcc@gcc.gnu.org
Subject: Alignment on x86
Date: Sun, 01 Sep 2002 20:37:00 -0000	[thread overview]
Message-ID: <20020902133712.I19469@royal.anu.edu.au> (raw)

Hi,

I'm in the process of adding a new call sequence to GCC 3.2 at the
moment, implementing a more general sibcall optimisation on Intel
platforms (and later others, too).  However, I'm wondering where I can
find the right documentation on byte alignment for the stack.

What are the boundaries GCC tries to allocate for each stack frame?  I've
always thought it was 16 byte alignment, and if a function has a few bytes
for locals and args, then the rest are aligned as padding.  But now I've
run into a few examples where I can't grasp the rationale anymore, behind
the amount of bytes allocated on the stack.

Any comments, links, hints to literature, etc. would be appreciated.

Thanks in advance,
Andi.

             reply	other threads:[~2002-09-02  3:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-01 20:37 Andreas Bauer [this message]
2002-09-02  2:57 ` Jan Hubicka

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=20020902133712.I19469@royal.anu.edu.au \
    --to=baueran@in.tum.de \
    --cc=gcc@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).