This is the mail archive of the gcc-help@gcc.gnu.org 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: Memory Allocation On Stack

From: "Pankaj Kohli" <pankaj208 at gmail dot com>
To: "John (Eljay) Love-Jensen" <eljay at adobe dot com>
Cc: "Andrew Haley" <aph-gcc at littlepinkcloud dot com>, tstdenis at ellipticsemi dot com, kanishk dot 85 at gmail dot com, gcc-help at gcc dot gnu dot org
Date: Sun, 22 Jul 2007 08:52:50 +0530
Subject: Re: Memory Allocation On Stack
References: <4ae360740707211202y6d2e34acw21562f1fb04e96f6@mail.gmail.com> <EDC8DDD212FEB34C884CBB0EE8EC2D9103B25C6E@namailgen.corp.adobe.com>

No, PUSHL pushes 4 bytes on stack.

On 7/22/07, John (Eljay) Love-Jensen <eljay@adobe.com> wrote:

>What about this one ? Three PUSHes + sub 0x10,%esp. That makes 28 bytes. Stack is not aligned on 16-byte boundary in this case.

Isn't that Two PUSHes (= 2 x 4 = 8), One PUSHL (= 8), and sub 0x10 (= 16), making 32 bytes?

--
- Pankaj

----------------------------------------------------------------------------------------------------------------------
There are only 10 kind of people in the world, those who can count in
binary, and those who cannot.

References:
- Re: Memory Allocation On Stack
  - From: Pankaj Kohli
- RE: Memory Allocation On Stack
  - From: John (Eljay) Love-Jensen

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