On Mon, Mar 23, 2009 at 5:52 PM, Andrew Haley wrote:
> Peter Leist wrote:
>>
>> I understand that, but at a given point in the program flow the assignment
>> of stack slot to a variable should be fixed.
>
> Should it? We do some very drastic transformations in gcc, sometimes
> coalescing variable
Peter Leist wrote:
> On Fri, Mar 20, 2009 at 4:54 PM, Ian Lance Taylor wrote:
>> Peter Leist writes:
>>
>>> How can I interpret the stack frame of the current_function? That
>>> means, how can
>>> I tell what is stored at the location FP+xxx. If that is not (easily)
>>> possible, it would
>>> hel
On Fri, Mar 20, 2009 at 4:54 PM, Ian Lance Taylor wrote:
> Peter Leist writes:
>
>> How can I interpret the stack frame of the current_function? That
>> means, how can
>> I tell what is stored at the location FP+xxx. If that is not (easily)
>> possible, it would
>> help if I can somehow determine
Peter Leist writes:
> How can I interpret the stack frame of the current_function? That
> means, how can
> I tell what is stored at the location FP+xxx. If that is not (easily)
> possible, it would
> help if I can somehow determine the type of data stored at that
> location (i.g is that
> a refer
Hello,
I just started hacking around with the gcc internals, so apologize if
this is a noob
question:
How can I interpret the stack frame of the current_function? That
means, how can
I tell what is stored at the location FP+xxx. If that is not (easily)
possible, it would
help if I can somehow det
