Re: [gnugo-devel] switching to multiple boards

[Dave Denholm]

Paul Pogonyshev <address@hidden> writes:

> I'm thinking of starting wrapping GNU Go board and related global
> variables into a structure so that we can have several boards in
> parallel.  I remember being hostile to this idea a few years ago,
> but maybe we will have to make GNU Go threaded eventually.  Are
> there any strong positive or negative opinions on this issue?
>

A potential benefit is that (the c compiler can generate code such that)
one register keeps a pointer to that structure. Then accesses to the
various globals can be accessed more efficiently.

Also, there could be cache benefits, since it can give more control
over the ordering of the globals in memory.

> If we go at it, we should probably create a CVS branch (or will
> that be a Subversion branch?), since the task seems to be _very_
> large and the multi-board version will be in non-working state for
> (very) long time.  For the start, it is absolutely necessary to
> make `libboard' compile and at this stage cooperation is hardly
> possible.  Later, it will be possible that several of us work on
> separate modules, converting them more or less independently.
>

Can it be done incrementaly by using #define to map an existing name
to an element in the global structure ?


dd
-- 
Dave Denholm              <address@hidden>       http://www.esmertec.com