"Rodney M. Bates" <[EMAIL PROTECTED]> writes:
> OK, Thanks for the information. Just in case, does anybody already
> have it in their head roughly where in gcc code this decision is made?
tree-nested.c
Ian
OK, Thanks for the information. Just in case, does anybody already
have it in their head roughly where in gcc code this decision is made?
Ian Lance Taylor wrote:
"Rodney M. Bates" <[EMAIL PROTECTED]> writes:
When executing in foo, the frame pointer will point to a fixed spot in the
activatio
"Rodney M. Bates" <[EMAIL PROTECTED]> writes:
> When executing in foo, the frame pointer will point to a fixed spot in the
> activation record of foo. On i386, the FP is %ebx and it points to the
> dynamic link field. From there, loc is at displacement -4. Code in the
> body of foo will referen
http://earth.google.com/download-earth.html
On 7/13/06, DebianTux23 <[EMAIL PROTECTED]> wrote:
http://earth.google.com/download-earth.html
On 07 Jul 2006 10:11:01 -0700, Ian Lance Taylor < [EMAIL PROTECTED]> wrote:
> "Rodney M. Bates" < [EMAIL PROTECTED]> writes:
>
> > The following example
This is repost of my slightly earlier post, with a critical and
confusing misstatement corrected.
Well, I agree with what you said about your example, but it's not what
I am meaning. See below.
Ian Lance Taylor wrote:
"Rodney M. Bates" <[EMAIL PROTECTED]> writes:
I don't understand this.
Well, I agree with what you said about your example, but it's not what
I am meaning. See below.
Ian Lance Taylor wrote:
"Rodney M. Bates" <[EMAIL PROTECTED]> writes:
I don't understand this. A pointer to anywhere in an activation record
(or even outside it, if outside by a fixed offset) all
"Rodney M. Bates" <[EMAIL PROTECTED]> writes:
> I don't understand this. A pointer to anywhere in an activation record
> (or even outside it, if outside by a fixed offset) allows access to
> exactly the same set of things as any other, including the value the base
> register holds when the activa
Ian Lance Taylor wrote:
"Rodney M. Bates" <[EMAIL PROTECTED]> writes:
The following example C code and disassembly is compiled by gcc 3.4.3,
for i686. It uses two different invariants for what the value of
a static link is. Everywhere inside P, static link values are consistently
the same
"Rodney M. Bates" <[EMAIL PROTECTED]> writes:
> The following example C code and disassembly is compiled by gcc 3.4.3,
> for i686. It uses two different invariants for what the value of
> a static link is. Everywhere inside P, static link values are consistently
> the same as base pointer (%ebp
The following example C code and disassembly is compiled by gcc 3.4.3,
for i686. It uses two different invariants for what the value of
a static link is. Everywhere inside P, static link values are consistently
the same as base pointer (%ebp) register values for the same activation
record. A s
10 matches
Mail list logo
