Re: Extra 8 bytes on stack in gcc 4.3 (64-bit)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Bob Plantz <plantz@xxxxxxxx>
Subject: Re: Extra 8 bytes on stack in gcc 4.3 (64-bit)
From: Ian Lance Taylor <iant@xxxxxxxxxx>
Date: Fri, 10 Apr 2009 14:36:49 -0700
Cc: "John \(Eljay\) Love-Jensen" <eljay@xxxxxxxxx>, gcc-help <gcc-help@xxxxxxxxxxx>
In-reply-to: <1239378766.6110.25.camel@xxxxxxxxxxxxxxxxx> (Bob Plantz's message of "Fri\, 10 Apr 2009 08\:52\:46 -0700")
References: <1239335765.6150.50.camel@xxxxxxxxxxxxxxxxx> <204DEA5423F3BF47A6EE88C4E2979EC66BE84EDAEA@xxxxxxxxxxxxxxxxxxxxxx> <1239378766.6110.25.camel@xxxxxxxxxxxxxxxxx>
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (gnu/linux)

Bob Plantz <plantz@xxxxxxxx> writes:

> It was non-optimized. But I still expected the compiler not to allocate
> 16 bytes on the local stack frame for no reason.

You unfortunately can not make any such assumptions about the
unoptimized compiler.

Ian

References:
- Extra 8 bytes on stack in gcc 4.3 (64-bit)
  - From: Bob Plantz
- RE: Extra 8 bytes on stack in gcc 4.3 (64-bit)
  - From: John (Eljay) Love-Jensen
- RE: Extra 8 bytes on stack in gcc 4.3 (64-bit)
  - From: Bob Plantz

Prev by Date: Fwd: Re: fma operation::Result
Next by Date: Questions about the SSA reversion for formal parameters
Previous by thread: RE: Extra 8 bytes on stack in gcc 4.3 (64-bit)
Next by thread: fma operation
Index(es):
- Date
- Thread

[Index of Archives] [Linux C Programming] [Linux Kernel] [eCos] [Fedora Development] [Fedora Announce] [Autoconf] [The DWARVES Debugging Tools] [Yosemite Campsites] [Yosemite News] [Linux GCC]

Powered by Linux