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: "Menezes, Evandro" <evandro dot menezes at amd dot com>
- To: "Kai Tietz" <Kai dot Tietz at onevision dot com>, "gcc" <gcc at gcc dot gnu dot org>
- Date: Fri, 23 Feb 2007 14:31:03 -0600
- Subject: RE: I need some advice for x86_64-pc-mingw32 va_list calling convention (in i386.c)
- References: <OFC90D35E0.8D63D4E8-ONC125728B.0038B2F2-C125728B.0039F7AD@onevision.de>
See http://msdn2.microsoft.com/en-us/library/ms235286(VS.80).aspx.
HTH
--
_______________________________________________________
Evandro Menezes AMD Austin, TX
> -----Original Message-----
> From: gcc-owner@gcc.gnu.org [mailto:gcc-owner@gcc.gnu.org] On
> Behalf Of Kai Tietz
> Sent: Friday, February 23, 2007 04:33
> To: gcc
> Subject: I need some advice for x86_64-pc-mingw32 va_list
> calling convention (in i386.c)
>
> Hi,
>
> I am currently on a mingw32 port for x86_64. It is operatable
> and I am
> allready able to generate the crt-stuff and have some needed
> import-libraries.
> Executables are linkable and executeable, but wildcard
> methods are leading
> to wrong execution, as found out.
> 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.
> The current patch for supporting this x86_64-targer I
> allready posted to
> gcc-patch.
>
> I would be very pleased, if somebody could give me a hint
> about the patch
> needed.
>
> Thank you very much,
> i.A. Kai Tietz
>
>
>
>
>