RFC: Cygwin 64 bit?

[JonY]

On 6/27/2011 20:59, Corinna Vinschen wrote:
>>> I suspect we'll come out ahead in the end by following Linux and doing
>>> the translator -- the number of native windows apps compiled with
>>> cygwin-gcc (and which can't use mingw-gcc) seems a rather small fraction
>>> of the total, and posix apps could become a royal pain to compile on
>>> cygwin if sizeof(long) != sizeof(void*).
>>>
>>>
>>
>> So, some sort of thunk server/client thing in between the Cygwin DLL and
>> system DLL?
> 
> What is that good for?  Cygwin apps are POSIX apps, Cygwin DLLs are
> POSIX libs.  They only interact with the Cygwin DLL.  If they also
> use Win32 API, they are on their own and they better use Win32 types
> like DWORD, etc.  I don't see any need to make this even a bit more
> complicated than necessary.  Apart from that, the only non-POSIX
> DLL is the Cygwin DLL itself.  If it doesn't interact cleanly with
> the Win32 API it goes boom and we fix.
>

Yeah, I meant the Cygwin DLL itself, how does it communicate/thunk the
ABI difference when talking with win32/win64 API?

Like the other post mentioned one solution might be sizeof(LONG) !=
sizeof(long).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0xED74C077.asc
Type: application/pgp-keys
Size: 1685 bytes
Desc: not available
URL: <http://cygwin.com/pipermail/cygwin-developers/attachments/20110627/3dc95295/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 196 bytes
Desc: OpenPGP digital signature
URL: <http://cygwin.com/pipermail/cygwin-developers/attachments/20110627/3dc95295/attachment.sig>