On 2/27/07, Kai Tietz <[EMAIL PROTECTED]> wrote:
Thank you,
I allready adjusted my code. But by the reason of the need to define
OUTGOING_REG_PARM_STACK_SPACE for this target, I had to change the general
definition of it to be target specific.
This is why the uses of OUTGOING_REG_PARM_STACK_SP
i Tietz <[EMAIL PROTECTED]>
cc
"Menezes, Evandro" <[EMAIL PROTECTED]>, gcc
Subject
Re: I need some advice for x86_64-pc-mingw32 va_list calling convention
(in i386.c)
On Mon, Feb 26, 2007 at 09:40:59AM +0100, Kai Tietz wrote:
> So is there allready a mechanism in gcc,
Kai Tietz writes:
>But I still have a problem about va-argument-passing. The MS compiler
>reserves stack space for all may va-callable methods register arguments.
Passing arguments to functions with variable arguments isn't a special
case here. According to Microsoft's documentation, you always n
On Mon, Feb 26, 2007 at 09:40:59AM +0100, Kai Tietz wrote:
> So is there allready a mechanism in gcc, by whom I can reserve for all
> methods simple space on stack for the 4 used register parameters, even if
> they are not used for argument passing ?
See sparc.h.
r~
Thanx,
this paper is helpful and shows what I expected. But I still have a
problem about va-argument-passing. The MS compiler reserves stack space
for all may va-callable methods register arguments. So far, good. This
means for GCC setting up REG_PARM_STACK_SPACE to the value of a stack
argum
See http://msdn2.microsoft.com/en-us/library/ms235286(VS.80).aspx.
HTH
--
___
Evandro Menezes AMDAustin, TX
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
> Behalf Of Kai Tietz
Kai Tietz writes:
>I detected, that the MS-ABI does not support SSE or MMX argument passing
>(as gcc does for x86_64). Therefore I search some advice about the
>enforcement of passing (sse,mmx) registers passing via the standard
>integer registers (for MS they are ecx,edx,r9) and via stack.
I t
