Displaying 2 results from an estimated 2 matches for "utils_dostatefulop1_entry".
2010 Feb 12
3
[LLVMdev] Problems with custom calling convention on Mac OS X
...issue is that the generated code has a strong tendency to
manipulate the stack pointer when its not required. For a large amount
of functions, the generated code will start and finish with sp
manipulation to give the function some space despite the function not
otherwise using the stack.
e.g
Utils_doStatefulOp1_entry:
subl $4, %esp
movl 4(%ebp), %eax
movl 8(%ebp), %ecx
movl (%ebp), %esi
movl %eax, 8(%ebp)
movl %ecx, 4(%ebp)
addl $4, %ebp
addl $4, %esp
jmp stg_ap_pp_fast
It would be nice to fix this up as well.
Cheers,
David
2010 Feb 12
0
[LLVMdev] Problems with custom calling convention on Mac OS X
...strong tendency to
> manipulate the stack pointer when its not required. For a large amount
> of functions, the generated code will start and finish with sp
> manipulation to give the function some space despite the function not
> otherwise using the stack.
>
> e.g
>
> Utils_doStatefulOp1_entry:
> subl $4, %esp
> movl 4(%ebp), %eax
> movl 8(%ebp), %ecx
> movl (%ebp), %esi
> movl %eax, 8(%ebp)
> movl %ecx, 4(%ebp)
> addl $4, %ebp
> addl $4, %esp
> jmp stg_ap_pp_fast
>
> It would be nice to fix this up as well.
That's normal....