[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Windows Server 2008 64 bit
From: |
Aharon Robbins |
Subject: |
Re: Windows Server 2008 64 bit |
Date: |
Fri, 20 Feb 2009 12:35:11 +0200 |
> Date: Thu, 19 Feb 2009 23:41:46 +0200
> From: Eli Zaretskii <address@hidden>
> Subject: Re: Windows Server 2008 64 bit
> To: Aharon Robbins <address@hidden>
> Cc: address@hidden, address@hidden
>
> > Date: Thu, 19 Feb 2009 21:56:42 +0200
> > From: Aharon Robbins <address@hidden>
> > Cc: address@hidden, address@hidden
> >
> > > One thing that should be kept in mind is that 64-bit Windows use a
> > > different model than 64-bit Unices (a long is still 32 bit wide on
> > > 64-bit Windows). Thus, code that compiles and works on 64-bit Unix
> > > machines will not necessarily do so on 64-bit Windows.
> >
> > Weird. Is the long long a 64 bit value, or only the _int64 (or whatever
> > it's called)?
>
> int64_t or (non-portable) DWORDLONG. I think "long long" is only
> supported on Windows by GCC.
>
> > Since long is 32 bits, I would think things would compile and run and
> > work ok; I don't think gawk has any dependencies on sizeof long, nor
> > does it use long long.
>
> Does it use size_t and assumes it's the same size as a long? or cast a
> pointer to a long? All these work on 64-bit Unix, but not on 64-bit
> Windows.
It shouldn't be doing any of those things.
I'm sure that one day someone will do a port. :-)
Thanks,
Arnold