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 f
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
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
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
f: 6a 0d push $0xd
111: e8 fc ff ff ff call 112
116: 83 c4 10add$0x10,%esp
119: c9 leave
11a: c3 ret
-----
--
Rodney M. Bates
