"Vincent R." writes:
> No you are right, prologue definition in my context is :
> Typically, a prolog segment contains separate sequences of instructions
> that perform the following tasks:
>
> * Allocate a stack frame.
> * Save incoming argument registers.
> * Set up the frame pointe
On Fri, 16 Jan 2009 14:13:58 -0800, Ian Lance Taylor
wrote:
> "Vincent R." writes:
>
>> To locate appropriate handlers when an exception occurs in Win32
>> environments other than x86,
>
> Note that as far as I know, gcc only supports win32 for ARM and x86
> (and x86_64, I guess, or maybe that
"Vincent R." writes:
> To locate appropriate handlers when an exception occurs in Win32
> environments other than x86,
Note that as far as I know, gcc only supports win32 for ARM and x86
(and x86_64, I guess, or maybe that is win64). So I assume you are
talking about ARM.
> The portion of th
On Fri, 16 Jan 2009 08:37:20 -0800, Ian Lance Taylor
wrote:
> "Vincent R." writes:
>
>> I am working on a gcc-4.1.2 and I would like to know how the prologue
>> length from a function can be calculated.
>
> The question is not well formed. The instruction
"Vincent R." writes:
> I am working on a gcc-4.1.2 and I would like to know how the prologue
> length from a function can be calculated.
The question is not well formed. The instructions which are part of
the prologue (e.g., saving callee-saved registers onto the stack) can
Hi,
I am working on a gcc-4.1.2 and I would like to know how the prologue
length from a function can be calculated.
Indeed I am trying to evaluate what needs to be done to implement SEH and
one requirement is to be able to
fill a structure holding information like function length and prologue
