Author: Frank Phillips
Date: 12:02:10 08/20/03
Go up one level in this thread
On August 19, 2003 at 20:06:58, Mathieu Pagé wrote: >Hi, > >The fact: > >I have this question i read at some place that it is faster to unmake a move >than to save the state of the game before moving then restoring it when we want >to unmake the move. > >For the moment my engines did not implement unmake() (it is still buggy). > >My thougth: > >Since bitboard computation are slow (on 32 hardware) i think that it can be >slower to unmake the move than to save the state. I friend of me that is lot >better than me at optimizing code also think that. > >My questions: > >Are you all using unmake() function or there is some of you that found that >saving the state is better ? > >In the case that unmake is better. by wich factor ? > >Thanks for your help. > >Mathieu Pagé It is useful to include the memcpy() approach in your program, anyway, to test your make/unmake code is working properly. Having done that you can then see which is better for you. Frank
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.