This is the mail archive of the gcc@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: Some small optimization issues with gcc 4.0 20050418

From: James E Wilson <wilson at specifixinc dot com>
To: Sebastian Biallas <sb at biallas dot net>
Cc: gcc at gcc dot gnu dot org
Date: Mon, 25 Apr 2005 13:28:05 -0700
Subject: Re: Some small optimization issues with gcc 4.0 20050418
References: <4267B9FD.6090900@biallas.net> <426958E1.6030706@specifixinc.com> <426C1B5A.4010704@biallas.net>

Sebastian Biallas wrote:

You don't need to reserve a stack slot for the return address on x86.
The stack slot will be allocated implicitly by the "call" instruction.

OK, then this must be a similar issue to the register saves in the prologue. There is confusion between calculating the frame size, and calculating the amount to subtract from the stack pointer. These are not the same on x86 because some values are being pushed on the stack. -- Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com

Follow-Ups:
- Re: Some small optimization issues with gcc 4.0 20050418
  - From: Sebastian Biallas

References:
- Some small optimization issues with gcc 4.0 20050418
  - From: Sebastian Biallas
- Re: Some small optimization issues with gcc 4.0 20050418
  - From: James E Wilson
- Re: Some small optimization issues with gcc 4.0 20050418
  - From: Sebastian Biallas

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