[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ft-devel] multithreading and 64 bits
From: |
Hin-Tak Leung |
Subject: |
Re: [ft-devel] multithreading and 64 bits |
Date: |
Wed, 26 Apr 2006 18:03:46 +0100 (BST) |
Yes, I got bitten by it in ghostscript a few months ago in the freetype
dervied code. long on win64 is indeed 32-bit - one needs "long long" to get
a 64-bit wide integer type on win64, unlike the case on most 64-bit unices.
--- Tom Kacvinsky <address@hidden> wrote:
> The long integer type on Windows 64 is 4 bytes wide, not 8 bytes wide.
> Thank you, MS! You will have to use ptrdiff_t if you want a full 8 byte
> wide integer type. Werner, I have not looked at the code recently, but
> I assume FT_PtrDist is like ptrdiff_t.
>
> Tom
>
> Werner LEMBERG wrote:
> > Sorry for the late reply.
> >
> >> i am using FreeType library on Windows 64 bits OS Opteron, with a 64
> >> bits executable (FreeType Build in 64 bits). There is a lot of
> >> problems :
> >>
> >> On Windows 64 bits, a "FT_Long", or a "Long" ,it's 2 Giga.
> >>
> >> But when we do a "pointer difference", i can see that a FT_Long is
> >> too small...
> >
> > You are completely right.
> >
> >> Example :
> >>
> >> static void shift_elements( PS_Table table,FT_Byte* old_base )
> >
> > This particular function I've just fixed in the CVS, thanks (we use
> > `FT_PtrDist'). Does your compiler generate warnings for other such
> > situations? Can you send a compiler log file to this list (possibly
> > compressed in case it is big)?
> >
> >
> > Werner
> >
> >
> > _______________________________________________
> > Freetype-devel mailing list
> > address@hidden
> > http://lists.nongnu.org/mailman/listinfo/freetype-devel
> >
>
>
> _______________________________________________
> Freetype-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/freetype-devel
>
Send instant messages to your online friends http://uk.messenger.yahoo.com