Author: Andreas Guettinger
Date: 14:10:23 12/12/05
Go up one level in this thread
On December 12, 2005 at 13:59:30, Robert Hyatt wrote: >On December 11, 2005 at 10:29:31, Andreas Guettinger wrote: > >>On December 10, 2005 at 21:10:52, Robert Hyatt wrote: >> >>>On December 09, 2005 at 17:53:59, Andreas Guettinger wrote: >>> >>>>I compiled and tested Crafty 19.19 on a Dual Dual PowerMac G5 2.5 Ghz. The >>>>results are below. >>>>Unfortunately with the disappearance of Posix Threads fom Crafty sources since >>>>version 20 the SMP code of newer versions will not compile for ppc anymore. >>> >>>Doesn't OSX support fork()??? and the ATT shared memory libs??? >>> >> >>Yes, it does support fork. >>The problem is in lock.h, if it's not _WIN32 and _WIN64 and not ALPHA I end up >>in >>static void __inline__ LockX86(volatile int *lock) >>assembler code and my ppc hickups during compilation. >>:( >> >>Can you mail me if you have a fix for this? >> >>regards >>Andy > >I don't have one, but will fix one. The ideal solution would be for someone to >write a Lock() inline function that uses the G5 instruction set. I'll ask >around, but are there any PPC assembly experts floating around here? > >MUTEX stuff in posix threads is just not usable for how I am locking. The locks >are held for _very_ short periods of times, and there are not many conflicts as >well, so doing a lot of systems nonsense, ultimately blocking the requesting >process if the lock is already held by another process is just way too slow. Thanks. Unfortunately I know nothing about assembler. Maybe on a linux dev board that do ppc distro and kernel (Suse, gentoo) they could help. I only found this by googling a bit, maybe that is of use for someone that can read assembler: http://glide.stanford.edu/lxr/ident?v=linux-2.6.5;i=RW_LOCK_UNLOCKED regards Andy
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.