This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: I need some advice for x86_64-pc-mingw32 va_list calling convention (in i386.c)
- From: Kai Tietz <Kai dot Tietz at onevision dot com>
- To: Richard Henderson <rth at redhat dot com>
- Cc: "Menezes, Evandro" <evandro dot menezes at amd dot com>, gcc <gcc at gcc dot gnu dot org>
- Date: Tue, 27 Feb 2007 09:51:39 +0100
- Subject: Re: I need some advice for x86_64-pc-mingw32 va_list calling convention (in i386.c)
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. In front is was defined or -not-.
Now it is getting defined to the default value of 0 for targets not
defining it, one for targets allready using this define, and for
i386-target specific to the MS x86_64-mingw32 target. Otherwise, it
wouldn't be possible to have the x86_64 and the i386 compiler in one
executable anymore.
Regards,
i.A. Kai Tietz
----------------------------------------
Kai Tietz - Software engineering
OneVision Software Entwicklungs GmbH & Co KG
Dr.-Leo-Ritter-Str. 9, 93049 Regensburg, Germany
Phone: +49-941-78004-0
FAX: +49-941-78004-489
WWW: http://www.OneVision.com
Richard Henderson <rth@redhat.com>
26.02.2007 19:12
To
Kai Tietz <Kai.Tietz@onevision.com>
cc
"Menezes, Evandro" <evandro.menezes@amd.com>, gcc <gcc@gcc.gnu.org>
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, 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~