freetype-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [ft-devel] multithreading and 64 bits


From: PILLET Céline
Subject: RE: [ft-devel] multithreading and 64 bits
Date: Wed, 26 Apr 2006 17:18:56 +0100

I use FT_PtrDist in this case since 2 weeks, it's work.
I will send a compiler log file to this list.
Thanks for reply.

Celine.

-----Message d'origine-----
De : Tom Kacvinsky [mailto:address@hidden
Envoyé : mercredi 26 avril 2006 16:12
À : address@hidden
Objet : Re: [ft-devel] multithreading and 64 bits


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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]