Re: [gnugo-devel] always init_board()

[Paul Pogonyshev]

> Here is a 3% speedup pretty much for free. When GNU Go reached a
> new_position(), it set the incremental board data uninitialized, and only
> initialized it when it was really needed. However, this meant that all
> low-level functions in board.c had to check for this. And the only time
> we really saved the call to init_board() was for add_stone(), e.g. for
> AB properties in .sgf-files.
>
> So instead we always call init_board() from new_position(). This makes
> board.o 1K smaller btw.
>
> Arend

interesting. i tried this some weeks ago and surprisingly got a slowdown by 
around 0.3 - 0.5%. i hadn't a clue of the reason, so i just buried the 
changes. maybe it was because of windows (i used it then)?

Paul