Hi, > > I was the one trying to implement multi-threaded branch [1]. With all due > > respect, I doubt it is doable without good knowledge how the engine is > > implemented internally. E.g. you need to synchronize or split to one per > > thread several caches that exist etc. The branch never reached working > > state as I abandoned it, as far as I remember after unpromising timing > > results. > > > > [1] cvs -d:pserver:[EMAIL PROTECTED]:/sources/gnugo -r multi-board co gnugo > > See the list archives around April 2005. > > http://lists.gnu.org/archive/html/gnugo-devel/2005-04/
That's too bad. :-( Multi-threading would be a great enhancement for GNU go. I suppose I'll have to find something else for the students. Any ideas for alternatives will be appreciated a lot. Are there any plans to reconsider that decision, given the fact that the two major chip producers will stop producing single-core processors this year? As Darren pointed out: > the future is multi-core not higher clock speeds. Unfortunately. - Chris _______________________________________________ gnugo-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnugo-devel
