>> This hasn't actually been tested on Win64 though.
>
> The 64-bit predefined macro is _WIN64.
Right; I also just discovered that xmm6 and xmm7 must be preserved,
which I wasn't doing.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://list
> -Original Message-
>
> Does mingw or cygwin support win64? I don't know if it's just MS that
> uses a new calling convention, or all win64 code, but if the former
> this should probably be conditionalized on _MSC_VER as well.
>
Cygwin is 32-bit. (It does run on 64-bit Windows though.)
> -Original Message-
>
> I just discovered that Microsoft wisely decided to use their own
> calling convention on Win64...
>
> This hasn't actually been tested on Win64 though.
The 64-bit predefined macro is _WIN64.
> ---
> src/gallium/auxiliary/rtasm/rtasm_x86sse.c | 15 +++
On Sun, 2010-08-15 at 09:22 -0700, tom fogal wrote:
> Luca Barbieri writes:
> > I just discovered that Microsoft wisely decided to use their own
> > calling convention on Win64...
Yep.
> > This hasn't actually been tested on Win64 though.
>
> Does mingw or cygwin support win64? I don't know if
Luca Barbieri writes:
> I just discovered that Microsoft wisely decided to use their own
> calling convention on Win64...
>
> This hasn't actually been tested on Win64 though.
Does mingw or cygwin support win64? I don't know if it's just MS that
uses a new calling convention, or all win64 code,
I just discovered that Microsoft wisely decided to use their own
calling convention on Win64...
This hasn't actually been tested on Win64 though.
---
src/gallium/auxiliary/rtasm/rtasm_x86sse.c | 15 +++
src/gallium/auxiliary/translate/translate_sse.c | 21 +---