> As for the documentation I can recommend
> - http://blogs.msdn.com/freik/archive/category/12430.aspx
> - MSDN
> - the PE-COFF v8 document recently updated by MS
> (http://www.microsoft.com/whdc/system/platform/firmware/PECOFF.mspx)
> - the ABI document that comes with some MSVC versions
Thank yo
- PŮVODNÍ ZPRÁVA -
Od: "Kuba Ober" <[EMAIL PROTECTED]>
Komu: wine-devel@winehq.org
Předmět: Re: Win64 status
Datum: 21.6.2006 - 13:01:23
> On Wednesday 21 June 2006 06:39, Filip Navara wrote:
> > Hello guys,
> >
> > I'm about to jump in the mi
On 21/06/06, Kuba Ober <[EMAIL PROTECTED]> wrote:
Is the MSVC x64 ABI documented somewhere? I didn't have time to wade through
MSDN in search of that yet . . .
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/Kernel_d/hh/Kernel_d/64bitAMD_6ec00b51-bf75-41bf-8635-caa8653c8bd9.xml.
On Wednesday 21 June 2006 06:39, Filip Navara wrote:
> Hello guys,
>
> I'm about to jump in the middle of discussion. The problem is not only
> with the calling convention, but with the whole ABI rather. I've had
> GCC patched to use the MSVC x64 calling convention (without a switch
> though) for a
Hello guys,
I'm about to jump in the middle of discussion. The problem is not only
with the calling convention, but with the whole ABI rather. I've had
GCC patched to use the MSVC x64 calling convention (without a switch
though) for about a year now, but it doesn't solve the problem. There
is much
"Ge van Geldorp" <[EMAIL PROTECTED]> writes:
> __attribute__ seems most logical to me. Perhaps __attribute__(__msvccall__)
> (in the __attribute__(__stdcall__) tradition? An alternative to -msvc could
> perhaps be -mrtd ("Alternate calling convention"). For i386 builds of gcc,
> -mrtd makes stdcal
> > I'd be submitting a patch to mingw32 people as soon as it's
> > done, in addition to posting it here. Note that the only way
> > for me to test it would be to inspect the assembly output, as
> > I'm not running 64 bit environment here (even though I'm on a
> > 64 bit AMD processor). So it'd nee
> From: Kuba Ober <[EMAIL PROTECTED]>
>
> I'm currently hacking on gcc for an embedded target (Z8
> Encore), but I wouldn't mind giving it a try while I'm
> digging in the gcc tree.
Cool!
> I'd like to hear any suggestions as to how to tell the
> compiler to use that calling convention (I'm n
On Monday 19 June 2006 14:17, Ge van Geldorp wrote:
> With the Win64 patches I just submitted to wine-patches, I'm able to
> successfully build Win64-enabled Wine and execute the following 64-bit
> winelib (winelib64? wine64lib?) application:
>
> #include "windows.h"
>
> int WINAPI WinMain(HINSTANC
With the Win64 patches I just submitted to wine-patches, I'm able to
successfully build Win64-enabled Wine and execute the following 64-bit
winelib (winelib64? wine64lib?) application:
#include "windows.h"
int WINAPI WinMain(HINSTANCE hinst, HINSTANCE hprev, LPSTR cmdline, int
cmdshow)
{
DWORD
10 matches
Mail list logo
