Questions in Respect to Code Release

Discussion of chess software programming and technical issues.

Moderators: bob, hgm, Harvey Williamson

Forum rules
This textbox is used to restore diagrams posted with the [d] tag before the upgrade.
jorose
Posts: 269
Joined: Thu Jan 22, 2015 2:21 pm
Location: Zurich, Switzerland
Full name: Jonathan Rosenthal

Questions in Respect to Code Release

Post by jorose » Thu Mar 05, 2015 7:57 pm

I am going to release my engine sometime this month. Unfortunately I have never released code and also didn't originally write my code with the intention of releasing it or having it run on any machine aside from my own. This leads me to a few questions. I also suspect I might have more questions before I release and in order not to clutter up the forum I will just reply to my own post here if I do end up with more questions.

So my first question is in respect to licensing. I want to release my code under GPL however I found out there are 3 versions of GPL, is there a reason not to use the newest version? On this same note as far I can remember there shouldn't be any code snippets I didn't write myself that is longer then just a few lines of code, however I use kogge stone fill algorithms which I at some point, back when my engine was still in Java took from the CPW page I just linked. Is it even possible for me to release my engine with this part of the code? Do I need to add people to the list of authors if I don't remove this part of the code?

Assuming I can release my code under some license, should I write the license information at the top of every single file or does it suffice to simply add it in the project directory together with a read me file?

Furthermore I wrote my code under Linux and I currently have the following 3 functions which I don't know if they are platform specific?

Code: Select all

/** return the number of trailing zeros */
inline int numberOfTrailingZeros(BitBoard x) {
	return __builtin_ctzll(x);
}

/** return the leading number of zeros */
inline int numberOfLeadingZeros(BitBoard x) {
	return __builtin_clzll(x);
}

/** return number of set 1 bits */
inline int popCount(BitBoard x) {
	return __builtin_popcountll(x);
}
Aside from again having the question if it is possible to release my code with these functions in them I also wanted to know if I would have to change something so the code will compile on Windows/OSX? My understanding is that functions that start with "__" are system specific...

The last question that comes to mind is in respect to makefiles. This is my first and so far only larger scale (more then a single file) project written in c++ and was in large part done in order to learn how to code c++ (for better or worse the majority of c++ code I have now seen outside of my own, is that of Stockfish). And while it was a great learning experience it was a serious uphill battle for me and as such I tried to avoid some things, specifically I haven't used pointers in my code yet and have absolutely no clue how to write my own makefile yet. Instead I opted for making a Managed Make C++ project using the Eclipse CDT. In essence what I am trying to say is my makefile is automatically generated and any other automatically or manually generated makefile should be as good or better then mine and I don't know how it actually works. My question is when I release the code should I release the makefile with it? Should I take the time to learn to write and proceed to write my own makefile before releasing the project? Will the makefile work on systems that are not Linux without changing it at all?

Angrim
Posts: 69
Joined: Mon Jun 25, 2012 8:16 pm
Location: Forks, WA
Full name: Ben Nye

Re: Questions in Respect to Code Release

Post by Angrim » Thu Mar 05, 2015 8:12 pm

the __builtin_popcountll and similar are gcc specific rather than linux specific, so as long as you use gcc they should be portable. You are more likely to have trouble with timing and i/o functions when porting to windows. I recommend borrowing a windows computer and trying to compile it, could be an interesting learning experience. MinGW is a decent gcc for windows package to start with.

kbhearn
Posts: 411
Joined: Thu Dec 30, 2010 3:48 am

Re: Questions in Respect to Code Release

Post by kbhearn » Thu Mar 05, 2015 8:49 pm

The last question that comes to mind is in respect to makefiles. This is my first and so far only larger scale (more then a single file) project written in c++ and was in large part done in order to learn how to code c++ (for better or worse the majority of c++ code I have now seen outside of my own, is that of Stockfish). And while it was a great learning experience it was a serious uphill battle for me and as such I tried to avoid some things, specifically I haven't used pointers in my code yet and have absolutely no clue how to write my own makefile yet. Instead I opted for making a Managed Make C++ project using the Eclipse CDT. In essence what I am trying to say is my makefile is automatically generated and any other automatically or manually generated makefile should be as good or better then mine and I don't know how it actually works. My question is when I release the code should I release the makefile with it? Should I take the time to learn to write and proceed to write my own makefile before releasing the project? Will the makefile work on systems that are not Linux without changing it at all?
Yes you should include a makefile, even if it's only a simple one so that a user can simply go to the directory and run make.

For windows, most potential users will not have a compiler and installing one may be more work than they're willing to do. You should provide an executable packaged with any required dlls.

syzygy
Posts: 4458
Joined: Tue Feb 28, 2012 10:56 pm

Re: Questions in Respect to Code Release

Post by syzygy » Thu Mar 05, 2015 8:52 pm

It's also possible to install a mingw-based crosscompiler on Linux. Then you can develop and compile for Windows having all the conveniences of Linux. Testing can be done using Wine.

User avatar
Evert
Posts: 2923
Joined: Fri Jan 21, 2011 11:42 pm
Location: NL
Contact:

Re: Questions in Respect to Code Release

Post by Evert » Thu Mar 05, 2015 9:06 pm

jorose wrote:I am going to release my engine sometime this month.
Congratulations!
So my first question is in respect to licensing. I want to release my code under GPL however I found out there are 3 versions of GPL, is there a reason not to use the newest version?
Maybe. There are people who are very hung up on the distinction between GPL 2 and GPL 3. See http://stackoverflow.com/questions/4146 ... 3-licenses for a list of bullet points.
Ultimately though, it is up to you to understand the terms under which you release the source code, in particular what other people can and cannot do with it. Also remember that even if you release the code under the GPL, the code is still yours: you can change the licence later (but you cannot retract versions that are already out there that are under the GPL).
On this same note as far I can remember there shouldn't be any code snippets I didn't write myself that is longer then just a few lines of code, however I use kogge stone fill algorithms which I at some point, back when my engine was still in Java took from the CPW page I just linked. Is it even possible for me to release my engine with this part of the code?
Yes. Worst possible case - you stick a separate licence on that bit of code.

There are a lot of technicalities that have to do with code that is released for educational or instructive purposes. Without any counter arguments, I would assume that code on CPW specifically falls under "fair use/public domain". Ask if you want to be certain.

In practical terms: don't worry about it.
Do I need to add people to the list of authors if I don't remove this part of the code?
Presumably you already credit the source in your readme file? That is probably good enough (and should be done even if not required, it's only polite).
Assuming I can release my code under some license, should I write the license information at the top of every single file or does it suffice to simply add it in the project directory together with a read me file?
I think the latter is sufficient (don't put the licence in the README though, put the licence blurb in the readme and stick the full licence text in a separate file).
Furthermore I wrote my code under Linux and I currently have the following 3 functions which I don't know if they are platform specific?

Code: Select all

/** return the number of trailing zeros */
inline int numberOfTrailingZeros(BitBoard x) {
	return __builtin_ctzll(x);
}

/** return the leading number of zeros */
inline int numberOfLeadingZeros(BitBoard x) {
	return __builtin_clzll(x);
}

/** return number of set 1 bits */
inline int popCount(BitBoard x) {
	return __builtin_popcountll(x);
}
Aside from again having the question if it is possible to release my code with these functions in them I also wanted to know if I would have to change something so the code will compile on Windows/OSX? My understanding is that functions that start with "__" are system specific...
These particular ones are compiler specific. They work with both GCC and Clang, so you should be good on both Linux and OS X. Windows is a different matter. GCC is still fine, but most people use different compilers on Windows. You can have a look at my program SjaakII (in particular the file include/bits64.h) to see one possible way of handling this.
Having said all that - if this is the only change you have to make to get things to compile under Windows, well done! That's better than I ever managed.
The last question that comes to mind is in respect to makefiles. This is my first and so far only larger scale (more then a single file) project written in c++ and was in large part done in order to learn how to code c++ (for better or worse the majority of c++ code I have now seen outside of my own, is that of Stockfish). And while it was a great learning experience it was a serious uphill battle for me and as such I tried to avoid some things, specifically I haven't used pointers in my code yet and have absolutely no clue how to write my own makefile yet. Instead I opted for making a Managed Make C++ project using the Eclipse CDT. In essence what I am trying to say is my makefile is automatically generated and any other automatically or manually generated makefile should be as good or better then mine and I don't know how it actually works. My question is when I release the code should I release the makefile with it?
If it's all you have, go for it. Chances are it'll be useless, but having a non-functional makefile is no worse than not having one at all. Some people include a simple shell script to build the code (which basically runs "gcc -O2 *.c -o myprogram").
Chances are someone here will send you an appropriate makefile.
Should I take the time to learn to write and proceed to write my own makefile before releasing the project?
Yes and no. It's good to learn how to write simple makefiles, so do that.
However, large and complicated makefiles are hard to maintain (by hand) once you need to worry about differences between compilers and platforms. Learn to use a configure/makefile generator instead. Autotools used to be the standard for UNIX based systems, but they're pretty complicated and not portable. Personally I'm a fan of CMake, but there are other options.
Will the makefile work on systems that are not Linux without changing it at all?
No.
In fact they probably won't work on anyone else's computer even if they run Linux.

User avatar
Evert
Posts: 2923
Joined: Fri Jan 21, 2011 11:42 pm
Location: NL
Contact:

Re: Questions in Respect to Code Release

Post by Evert » Thu Mar 05, 2015 9:10 pm

syzygy wrote:It's also possible to install a mingw-based crosscompiler on Linux. Then you can develop and compile for Windows having all the conveniences of Linux. Testing can be done using Wine.
I (used to) do this, it works well.

The downside, I found, was that I needed to distribute the C++ runtime along with my executable (I couldn't static-link it), which is rather large.

There are also many friendly Windows users around who may well offer to help you with compiling your code on Windows. Just ask.

Dann Corbit
Posts: 10188
Joined: Wed Mar 08, 2006 7:57 pm
Location: Redmond, WA USA
Contact:

Re: Questions in Respect to Code Release

Post by Dann Corbit » Thu Mar 05, 2015 9:18 pm

Angrim wrote:the __builtin_popcountll and similar are gcc specific rather than linux specific, so as long as you use gcc they should be portable. You are more likely to have trouble with timing and i/o functions when porting to windows. I recommend borrowing a windows computer and trying to compile it, could be an interesting learning experience. MinGW is a decent gcc for windows package to start with.
Speaking of Windows, here is why lots of engines lose games on time...

Did your engine ever have an inexplicable loss on time, that you could not reproduce?

This is a fragment of a log file where I had the time set to 5 minutes.
You will notice that the last entry has enormous time allocated to it and the previous entries had the correct 5 minute slot:

Code: Select all

Searching: 8/3P4/1B6/8/2b5/Kn3N2/1pk5/8 w - - 0 1
infinite: 1 ponder: 0 time: 0 increment: 0 moves to go: 0

 1   +0.74   00:00      98  Ne1+ Kc3 
 2   -0.31   00:00     247  Ne1+ Kc3 Ba5+ Nxa5 
 3   +0.68   00:00     322  Ne1+ Kc3 d8=Q b1=Q 
 4   +0.68   00:00     464  Ne1+ Kc3 d8=Q b1=Q Qf6+ Kd2 
 5   +6.86   00:00    1837  Ne1+ Kc1 Be3+ Kd1 d8=Q+ Ke2 Kxb2 Kxe3 Qe7+ Kf4 
 6   +7.80   00:00    3170  Ne1+ Kb1 d8=Q Ka1 Qd1+ Nc1 Qc2 b1=N+ Kb4 
 7   +7.45   00:00    5597  Ne1+ Kc3 d8=Q b1=N+ Ka4 Kb2 Qf6+ Ka2 Nc2 N1d2 
 8   +7.45   00:00    6453  Ne1+ Kc3 d8=Q b1=N+ Ka4 Kb2 Qf6+ Ka2 Nc2 N1d2 Nb4+ Kb1 
 9   +9.72   00:01   23449  Ne1+ Kc3 d8=Q b1=N+ Ka4 Kb2 Qf6+ Ka2 Nc2 N1d2 Nb4+ Kb1 Qg6+ Ka1 Qc2 Nc5+ Bxc5 
10  +11.03   00:02  107088  Ne1+ Kc3 d8=Q b1=N+ Ka2 N1d2 Qf6+ Nd4+ Ka3 Nb1+ Ka4 Bb5+ Ka5 Na3 Bxd4+ Kd2 Qf2+ Kc1 Qe3+ Kd1 Qxa3 
11  +11.03   00:02  108362  Ne1+ Kc3 d8=Q b1=N+ Ka2 N1d2 Qf6+ Nd4+ Ka3 Nb1+ Ka4 Bb5+ Ka5 Na3 Bxd4+ Kd2 Qf2+ Kc1 Qe3+ Kd1 
12  +52.09   00:05  209361  Ne1+ Kc3 d8=Q b1=N+ Ka2 N3d2+ Ka1 Nb3+ Kxb1 Nd2+ Kc1 Nb3+ Kd1 Kb2 Qh4 Bd5 Qf2+ Ka3 Nc2+ Ka4 Qe3 
13  +52.09   00:05  210146  Ne1+ Kc3 d8=Q b1=N+ Ka2 N3d2+ Ka1 Nb3+ Kxb1 Nd2+ Kc1 Nb3+ Kd1 Kb2 Qh4 Bd5 Qf2+ Ka3 Nc2+ Ka4 Qe3 
14  +52.09   00:05  217780  Ne1+ Kc3 d8=Q b1=N+ Ka2 N3d2+ Ka1 Nb3+ Kxb1 Nd2+ Kc1 Nb3+ Kd1 Kb2 Qh4 Bd5 Qf2+ Ka3 Nc2+ Ka4 Qe3 Na5 
15  +52.09   00:05  219127  Ne1+ Kc3 d8=Q b1=N+ Ka2 N3d2+ Ka1 Nb3+ Kxb1 Nd2+ Kc1 Nb3+ Kd1 Kb2 Qh4 Bd5 Qf2+ Ka3 Nc2+ Ka4 Qe3 Na5 Qa3+ Kb5 Qc5+ Ka6 Qxa5+ Kb7 Qxd5+ Kxb6 
16     #78   00:06  246112  Ne1+ Kc3 d8=Q b1=N+ Ka2 N3d2+ Ka1 Nb3+ Kxb1 Nd2+ Ka1 Nb3+ Ka2 Nd2+ Ka3 Nb1+ Ka4 Bb3+ Ka5 Kb2 Qd4+ Ka2 Qf2+ Ka1 Bd4+ Nc3 Bxc3+ 
17     #78   00:07  255093  Ne1+ Kc3 d8=Q b1=N+ Ka2 N3d2+ Ka1 Nb3+ Kxb1 Nd2+ Ka1 Nb3+ Ka2 Nd2+ Ka3 Nb1+ Ka4 Bb3+ Ka5 Kb2 Qd4+ Ka2 Qf2+ Ka1 Bd4+ Nc3 Bxc3+ 
18     #78   00:08  274249  Ne1+ Kc3 d8=Q b1=N+ Ka2 N3d2+ Ka1 Nb3+ Kxb1 Nd2+ Ka1 Nb3+ Ka2 Nd2+ Ka3 Nb1+ Ka4 Bb3+ Ka5 Kb2 Qd4+ Ka2 Qf2+ Ka1 Bd4+ Nc3 Bxc3+ 
19     #78   00:09  295876  Ne1+ Kc3 d8=Q b1=N+ Ka2 N3d2+ Ka1 Nb3+ Kxb1 Nd2+ Ka1 Nb3+ Ka2 Nd2+ Ka3 Nb1+ Ka4 Bb3+ Ka5 Kb2 Qd4+ Ka2 Qf2+ Ka1 Bd4+ Nc3 Bxc3+ 
20     #78   00:11  335240  Ne1+ Kc3 d8=Q b1=N+ Ka2 N3d2+ Ka1 Nb3+ Kxb1 Nd2+ Ka1 Nb3+ Ka2 Nd2+ Ka3 Nb1+ Ka4 Bb3+ Ka5 Kb2 Qd4+ Ka2 Qf2+ Ka1 Bd4+ Nc3 Bxc3+ 
21     #75   00:13  408233  Ne1+ Kc3 d8=Q b1=N+ Ka2 N3d2+ Ka1 Nb3+ Kxb1 Nd2+ Kc1 Nb3+ Kd1 Bb5 Qc7+ Bc4 Nc2 Nd2 Qe5+ Kb3 Kxd2 
22     #75   00:16  459498  Ne1+ Kc3 d8=Q b1=N+ Ka2 N3d2+ Ka1 Nb3+ Kxb1 Nd2+ Kc1 Nb3+ Kd1 Bb5 Qc7+ Bc4 Nc2 Nd2 Qe5+ Kb3 Kxd2 
23     #75   00:19  528159  Ne1+ Kc3 d8=Q b1=N+ Ka2 N3d2+ Ka1 Nb3+ Kxb1 Nd2+ Kc1 Nb3+ Kd1 Bb5 Qc7+ Bc4 Nc2 Nd2 Qe5+ Kb3 Kxd2 
24     #75   00:24  619868  Ne1+ Kc3 d8=Q b1=N+ Ka2 N3d2+ Ka1 Nb3+ Kxb1 Nd2+ Kc1 Nb3+ Kd1 Bb5 Qc7+ Bc4 Nc2 Nd2 Qe5+ Kb3 Kxd2 
25     #75   00:27  753910  Ne1+ Kc3 d8=Q b1=N+ Ka2 N3d2+ Ka1 Nb3+ Kxb1 Nd2+ Kc1 Nb3+ Kd1 Bb5 Qc7+ Kb4 Nc2+ Ka4 Qa7+ Na5 Qxa5+ 
26     #75   00:36   1002K  Ne1+ Kc3 d8=Q b1=N+ Ka2 N1d2 Qf6+ Kb4 Nc2+ Kb5 Na3+ Kb4 Nxc4 Nc1+ Kb2 Nd3+ Kc2 Ne4 Qe7+ Ndc5 Bxc5+ 
27     #75   00:41   1284K  Ne1+ Kc3 d8=Q b1=N+ Ka2 N1d2 Qf6+ Nd4+ Ka3 Nb1+ Ka4 Bb3+ Ka5 Bc4 Qxd4+ Kb3 Qd1+ Kb2 Qc2+ Ka1 Qxc4 
28     #75   00:46   1448K  Ne1+ Kc3 d8=Q b1=N+ Ka2 N1d2 Qf6+ Nd4+ Ka3 Nb1+ Ka4 Bb3+ Ka5 Bc4 Qxd4+ Kb3 Qd1+ Kb2 Qc2+ Ka1 Qxc4 
29     #73   00:54   2165K  Ne1+ Kc3 d8=Q b1=N+ Ka4 Kb2 Qf6+ Ka2 Qf5 Bg8 Qc2+ Ka1 Nd3 Nc5+ Bxc5 Bb3+ Qxb3 
30     #73   01:02   2411K  Ne1+ Kc3 d8=Q b1=N+ Ka4 Kb2 Qf6+ Ka2 Qf5 Bg8 Qc2+ Ka1 Nd3 Nc5+ Bxc5 Bb3+ Qxb3 
31     #73   01:08   2620K  Ne1+ Kc3 d8=Q b1=N+ Ka4 Kb2 Qf6+ Ka2 Qf5 Bg8 Qc2+ Ka1 Nd3 Nc5+ Bxc5 Bb3+ Qxb3 
32     #73   01:14   2882K  Ne1+ Kc3 d8=Q b1=N+ Ka4 Kb2 Qf6+ Ka2 Qf5 Bg8 Qc2+ Ka1 Nd3 Nc5+ Bxc5 Bb3+ Qxb3 
33     #73   01:22   3243K  Ne1+ Kc3 d8=Q b1=N+ Ka4 Kb2 Qf6+ Ka2 Qf5 Bg8 Qc2+ Ka1 Nd3 Nc5+ Bxc5 Bb3+ Qxb3 
34     #73   01:30   3656K  Ne1+ Kc3 d8=Q b1=N+ Ka4 Kb2 Qf6+ Ka2 Qf5 Bg8 Qc2+ Ka1 Nd3 Nc5+ Bxc5 Bb3+ Qxb3 
35     #73   01:38   4125K  Ne1+ Kc3 d8=Q b1=N+ Ka4 Kb2 Qf6+ Ka2 Qf5 Bg8 Qc2+ Ka1 Nd3 Nc5+ Bxc5 Bb3+ Qxb3 
36     #73   01:47   4662K  Ne1+ Kc3 d8=Q b1=N+ Ka4 Kb2 Qf6+ Ka2 Qf5 Bg8 Qc2+ Ka1 Nd3 Nc5+ Bxc5 Bb3+ Qxb3 
37     #73   02:00   5255K  Ne1+ Kc3 d8=Q b1=N+ Ka4 Kb2 Qf6+ Ka2 Qf5 Bg8 Qc2+ Ka1 Nd3 Nc5+ Bxc5 Bb3+ Qxb3 
38     #73   02:21   6939K  Ne1+ Kc3 d8=Q b1=N+ Ka4 Kb2 Qf6+ Ka2 Qf5 Bg8 Qc2+ Ka1 Nd3 Nc5+ Bxc5 Bb3+ Qxb3 
39     #73   02:42   8452K  Ne1+ Kc3 d8=Q b1=N+ Ka4 Kb2 Qf6+ Ka2 Qf5 Bg8 Qc2+ Ka1 Nd3 Nc5+ Bxc5 Bb3+ Qxb3 
40     #73   02:50   9436K  Ne1+ Kc3 d8=Q b1=N+ Ka4 Kb2 Qf6+ Ka2 Qf5 Bg8 Qc2+ Ka1 Nd3 Nc5+ Bxc5 Bb3+ Qxb3 
41     #73   02:59  10736K  Ne1+ Kc3 d8=Q b1=N+ Ka4 Kb2 Qf6+ Ka2 Qf5 Bg8 Qc2+ Ka1 Nd3 Nc5+ Bxc5 Bb3+ Qxb3 
42     #73   03:20  13449K  Ne1+ Kc3 d8=Q b1=N+ Ka4 Kb2 Qf6+ Ka2 Qf5 Bg8 Qc2+ Ka1 Nd3 Nc5+ Bxc5 Bb3+ Qxb3 
43     #73   03:38  15335K  Ne1+ Kc3 d8=Q b1=N+ Ka4 Kb2 Qf6+ Ka2 Qf5 Bg8 Qc2+ Ka1 Nd3 Nc5+ Bxc5 Bb3+ Qxb3 
44     #73   03:57  19207K  Ne1+ Kc3 d8=Q b1=N+ Ka4 Kb2 Qf6+ Ka2 Qf5 Bg8 Qc2+ Ka1 Nd3 Nc5+ Bxc5 Bb3+ Qxb3 
45     #73   04:12  22046K  Ne1+ Kc3 d8=Q b1=N+ Ka4 Kb2 Qf6+ Ka2 Qf5 Bg8 Qc2+ Ka1 Nd3 Nc5+ Bxc5 Bb3+ Qxb3 
46     #73   04:37  27651K  Ne1+ Kc3 d8=Q b1=N+ Ka4 Kb2 Qf6+ Ka2 Qf5 Bg8 Qc2+ Ka1 Nd3 Nc5+ Bxc5 Bb3+ Qxb3 
47     #73   04:53  34097K  Ne1+ Kc3 d8=Q b1=N+ Ka4 Kb2 Qf6+ Ka2 Qf5 Bg8 Qc2+ Ka1 Nd3 Nc5+ Bxc5 Bb3+ Qxb3 
48     #73   04:59  37839K  Ne1+ Kc3 d8=Q b1=N+ Ka4 Kb2 Qf6+ Ka2 Qf5 Bg8 Qc2+ Ka1 Nd3 Nc5+ Bxc5 Bb3+ Qxb3 
Nodes: 37839197
Nodes/second: 126148
Best move: Ne1+
Ponder move: Kc3

Searching: 8/8/2K5/8/4Pp2/2NpNk2/q4P2/4B3 w - - 0 1
infinite: 1 ponder: 0 time: 0 increment: 0 moves to go: 0

 1   +4.73   00:00     106  Nxa2 fxe3 fxe3 Kxe4 
 2   +4.73   00:00     140  Nxa2 fxe3 
 3   +4.73   00:00     175  Nxa2 fxe3 fxe3 
 4   +4.73   00:00     231  Nxa2 fxe3 fxe3 Kxe4 
 5   +4.66   00:00     389  Nxa2 fxe3 fxe3 Ke2 Nc1+ Kxe1 
 6   +5.69   00:00     675  Nxa2 fxe3 fxe3 Kg4 Nc3 Kf3 
 7   +5.76   00:00     867  Nxa2 fxe3 fxe3 Kg4 Bc3 Kf3 e5 Kxe3 
 8   +8.32   00:00    5366  Nxa2 Kxe4 Nc3+ Kd4 Nb5+ Ke4 Nc4 Kf3 Kc5 Kg2 
 9   +8.63   00:00   12423  Nxa2 Kxe4 Nc3+ Ke5 Ned5 f3 Bd2 Kf5 Kc5 Ke5 Bf4+ Kf5 
10   +9.67   00:00   27537  Nxa2 Kxe4 Nc4 Kd4 Nb2 d2 Bxd2 f3 Be3+ Ke5 Nc4+ Kf5 
11  +46.63   00:01   42652  Nxa2 Kxe4 Nc4 Kd4 Nb2 d2 Bxd2 f3 Be3+ Ke5 Nc4+ Kf5 Nd2 
12  +46.63   00:01   43338  Nxa2 Kxe4 Nc4 Kd4 Nb2 d2 Bxd2 f3 Be3+ Ke5 Nc4+ Kf5 Nd2 Kg4 
13  +50.76   00:01   48383  Nxa2 d2 Bxd2 Ke2 Nc4 f3 Be3 Kf1 Nd2+ Kg2 Nxf3 Kh3 Nc1 Kg4 
14     #70   00:02   55406  Nxa2 d2 Bxd2 Ke2 Nc1+ Kf3 Bc3 Kxf2 Nd3+ Ke2 Nxf4+ 
15     #70   00:02   58976  Nxa2 d2 Bxd2 Ke2 Nc1+ Kf3 Bc3 Kxf2 Nd3+ Ke2 Nxf4+ 
16     #70   00:03   63235  Nxa2 d2 Bxd2 Ke2 Nc1+ Kf3 Bc3 Kxf2 Nd3+ Ke2 Nxf4+ 
17     #70   00:03   69048  Nxa2 d2 Bxd2 Ke2 Nc1+ Kf3 Bc3 Kxf2 Nd3+ Ke2 Nxf4+ 
18     #70   00:03   77887  Nxa2 d2 Bxd2 Ke2 Nc1+ Kf3 Bc3 Kxf2 Nd3+ Ke2 Nxf4+ 
19     #70   00:04   92104  Nxa2 d2 Bxd2 Ke2 Nc1+ Kf3 Bc3 Kxf2 Nd3+ Ke2 Nxf4+ 
20     #70   00:04  114164  Nxa2 d2 Bxd2 Ke2 Nc1+ Kf3 Bc3 Kxf2 Nd3+ Ke2 Nxf4+ 
21     #70   00:05  141657  Nxa2 d2 Bxd2 Ke2 Nc1+ Kf3 Bc3 Kxf2 Nd3+ Ke2 Nxf4+ 
22     #70   00:06  182236  Nxa2 d2 Bxd2 Ke2 Nc1+ Kf3 Bc3 Kxf2 Nd3+ Ke2 Nxf4+ 
23     #70   00:07  221884  Nxa2 d2 Bxd2 Ke2 Nc1+ Kf3 Bc3 Kxf2 Nd3+ Ke2 Nxf4+ 
24     #70   00:09  292403  Nxa2 d2 Bxd2 Ke2 Nc1+ Kf3 Bc3 Kxf2 Nd3+ Ke2 Nxf4+ 
25     #70   00:10  390975  Nxa2 d2 Bxd2 Ke2 Nc1+ Kf3 Bc3 Kxf2 Nd3+ Ke2 Nxf4+ 
26     #70   00:13  553945  Nxa2 d2 Bxd2 Ke2 Nc1+ Kf3 Bc3 Kxf2 Nd3+ Ke2 Nxf4+ 
27     #70   00:16  822646  Nxa2 d2 Bxd2 Ke2 Nc1+ Kf3 Bc3 Kxf2 Nd3+ Ke2 Nxf4+ 
28     #70   00:18   1215K  Nxa2 d2 Bxd2 Ke2 Nc1+ Kf3 Bc3 Kxf2 Nd3+ Ke2 Nxf4+ 
29     #70   00:23   1592K  Nxa2 d2 Bxd2 Ke2 Nc1+ Kf3 Bc3 Kxf2 Nd3+ Ke2 Nxf4+ 
30     #70   00:29   2195K  Nxa2 d2 Bxd2 Ke2 Nc1+ Kf3 Bc3 Kxf2 Nd3+ Ke2 Nxf4+ 
31     #70   02:11   9400K  Nxa2 Kxe4 Nc4 f3 Nc1 Kf5 Nxd3 Ke6 Nce5 Ke7 Nxf3 
32     #70   02:31  14016K  Nxa2 Kxe4 Nc1 d2 Bxd2 f3 Nd3 Kd4 Ne5 Kxe5 
33     #70   03:04  19583K  Nxa2 Kxe4 Nc1 d2 Bxd2 f3 Nd3 Kd4 Ne5 Kxe5 
34     #70   03:15  22200K  Nxa2 Kxe4 Nc1 d2 Bxd2 f3 Nd3 Kd4 Ne5 Kxe5 
35     #70   03:32  27596K  Nxa2 Kxe4 Nc1 d2 Bxd2 f3 Nd3 Kd4 Ne5 Kxe5 
36     #69   04:59  49602K  Nxa2 Kxe4 Nc1 d2 Bxd2 Kd4 Ne2+ Ke5 Nxf4 
37     #69   05:00  50308K  Nxa2 Kxe4 Nc1 d2 Bxd2 Kd4 Ne2+ Ke5 Nxf4 
Nodes: 50308945
Nodes/second: 167650
Best move: Nxa2
Ponder move: Kxe4

Searching: 7K/4B3/2P5/4p2p/P1k1P3/3n4/2pP2P1/8 w - - 0 1
infinite: 1 ponder: 0 time: 0 increment: 0 moves to go: 0

 1   -2.05   00:00      25  c7 
 2   +1.90   00:00      61  c7 c1=Q 
 3   +1.90   00:00     122  c7 c1=Q c8=Q+ Kd4 
 4   +1.69   00:00     231  c7 c1=Q c8=Q+ Kd4 Qd7+ Kxe4 
 5   +1.61   00:00     465  c7 c1=Q c8=Q+ Kd4 Qd7+ Kxe4 Qb7+ Kd4 Qb6+ Kc4 
 6   +1.64   00:00     944  c7 c1=Q c8=Q+ Kd4 Qd7+ Kxe4 g4 hxg4 
 7   +1.84   00:00    2089  c7 c1=Q c8=Q+ Kd4 Qd7+ Kxe4 g4 hxg4 Qxg4+ Kd5 
 8   +1.69   00:00    4081  c7 c1=Q c8=Q+ Kd4 Qd7+ Kxe4 Qb7+ Kf5 Qf3+ Nf4 a5 Qxd2 
 9   +1.64   00:00    6780  c7 c1=Q c8=Q+ Kd4 Qd7+ Kxe4 g4 hxg4 Qxg4+ Nf4 Bb4 Kd4 Bc3+ Kd5 
10   +1.90   00:00   24676  c7 c1=Q c8=Q+ Kd4 Qd7+ Kxe4 Bg5 Qa3 Qh7+ Kd5 Qf7+ Kc6 Qe8+ Kd5 Qb5+ Kd6 
11   +1.96   00:00   47623  c7 c1=Q c8=Q+ Kd4 Qd7+ Kxe4 Bg5 Qa3 Qh7+ Kd4 Be3+ Kd5 Qg8+ Kc6 Qc8+ Kd5 Qa8+ Ke6 a5 
12   +5.89   00:00  110336  c7 c1=Q c8=Q+ Kb3 Qxc1 Nxc1 a5 h4 a6 Nd3 a7 h3 a8=Q h2 Qd5+ Kc2 
13   +8.00   00:00  209047  c7 c1=Q c8=Q+ Kd4 Qxc1 Nxc1 a5 h4 a6 h3 gxh3 Nd3 a7 Nf4 a8=Q Ng6+ Kg8 
14   +8.58   00:00  255208  c7 c1=Q c8=Q+ Kb3 Qxc1 Nxc1 a5 Ne2 a6 Nf4 a7 Ng6+ Kg7 Nxe7 a8=Q Kc2 Qa4+ Kxd2 Qb4+ Kd3 Qxe7 
15   +9.11   00:01  338335  c7 c1=Q c8=Q+ Kd4 Qxc1 Nxc1 a5 Kxe4 a6 Kf5 a7 Ke6 a8=Q Kxe7 Qa3+ Ke6 Qxc1 Kf5 Qc2+ Kf4 
16   +9.42   00:01  487215  c7 c1=Q c8=Q+ Kd4 Qxc1 Nxc1 a5 Kxe4 a6 Kd5 a7 Ke6 a8=Q Kxe7 Qa3+ Kf7 Qxc1 Ke6 Qc6+ Ke7 
17  +10.00   00:03  798892  c7 c1=Q c8=Q+ Kd4 Qxc1 Nxc1 a5 Kxe4 a6 Kf5 a7 Ke6 Ba3 Nd3 a8=Q Nf4 Qc6+ Kf5 Kg7 Ne6+ Kh6 Nf4 
18  +11.40   00:08   1960K  c7 c1=Q c8=Q+ Kd4 Qxc1 Nxc1 a5 Nb3 a6 Nxd2 a7 Nc4 a8=Q Ne3 Bg5 Ng4 Qd5+ Kc3 Kg7 Kc2 Qf7 Kc3 
19  +12.44   00:12   3581K  c7 c1=Q c8=Q+ Kd4 Qxc1 Nxc1 a5 Kc4 a6 Kd3 a7 Ke2 a8=Q Nd3 Qd5 Nf4 Qb5+ Kxd2 Kg7 Ne6+ Kf6 Nd4 Qd5 Ke3 Kxe5 Nc2 Qb3+ Kd2 
20  +12.50   00:13   3963K  c7 c1=Q c8=Q+ Kb3 Qxc1 Nxc1 a5 Kc2 a6 Nd3 a7 Kd1 a8=Q Ke1 Qa1+ Kf2 Kg7 Kxg2 Qc3 Ne1 Qxe5 Nf3 Qxh5 Kg3 
21  +12.76   00:15   4799K  c7 c1=Q c8=Q+ Kd4 Qxc1 Nxc1 a5 Nd3 a6 Nf4 a7 Kd3 a8=Q Ke2 Kg7 Kf2 Qa5 Nd3 Qc3 Ke2 Qc4 Kxd2 Bg5+ Nf4 g3 Ke3 gxf4 exf4 Qc1+ Kxe4 
22  +13.21   00:19   6570K  c7 c1=Q c8=Q+ Kb3 Qxc1 Nxc1 a5 Nd3 a6 Kb2 a7 Nf2 a8=Q Ng4 Qd5 Kb1 Kg7 Kc2 Bd6 Kd1 Bxe5 h4 Bc3 Ke2 e5 
23  +14.06   00:26   9459K  c7 c1=Q c8=Q+ Kd4 Qxc1 Nxc1 a5 Kd3 a6 Kc2 a7 Nd3 a8=Q h4 Qa5 Nf4 Kg7 Nh5+ Kf7 Nf4 Qxe5 Nxg2 Qc3+ Kb1 e5 h3 Qxh3 Ne1 
24  +14.76   00:30  11423K  c7 c1=Q c8=Q+ Kd4 Qxc1 Nxc1 a5 Nd3 a6 Nf2 a7 Ng4 a8=Q Kd3 Qd5+ Kc2 Kg7 Kd1 Qf7 Kc2 Qxh5 Nf2 Qxe5 Nd1 Qd4 Kb1 e5 Kc2 e6 
25  +16.81   00:36  13710K  c7 c1=Q c8=Q+ Kd4 Qxc1 Nxc1 a5 h4 a6 Nd3 a7 Nf4 a8=Q h3 gxh3 Kd3 Kg7 Ke2 Qa5 Nd3 Qd5 Nf2 Qxe5 Kf1 d4 Ke1 d5 Ke2 Qf5 Nd3 d6 Ke3 d7 
26  +17.15   00:41  14628K  c7 c1=Q c8=Q+ Kb3 Qxc1 Nxc1 a5 Nd3 a6 Kc2 a7 Nf2 a8=Q Ng4 Qd5 Kb2 Kg7 Kb1 Qf7 Kc2 Qxh5 Nf2 Qxe5 Nd1 Qd4 Kb1 e5 Kc2 
27  +20.38   00:50  17345K  c7 c1=Q c8=Q+ Kd4 Qxc1 Nxc1 a5 Nd3 a6 Nf4 a7 Kd3 a8=Q Ke2 Kg7 Kf2 Qa5 Ne6+ Kf6 Nd4 Qxe5 Nc2 Qc5+ Ke2 Qxc2 h4 d4+ Kf1 d5 Ke1 d6 Kf1 Qd1+ Kf2 d7 
28  +51.88   01:06  22863K  c7 c1=Q c8=Q+ Kd4 Qxc1 Nxc1 a5 Ne2 a6 Nf4 a7 Kd3 a8=Q Ke2 Kg7 Kf2 Qa5 Nd3 Qa3 Ke2 Qc3 Ne1 Qxe5 Kd3 Qb5+ Kc2 d4 Kc1 Qf1 Kd1 Bb4 Kc2 Bxe1 
29  +55.31   01:16  28882K  c7 c1=Q c8=Q+ Kd4 Qxc1 Nxc1 a5 Ne2 a6 Nf4 a7 Kd3 a8=Q Ke2 Kg7 Ne6+ Kf6 Nd4 Kxe5 Nc2 Qa2 Ne1 d4+ Kd1 Bg5 Nf3+ gxf3 Ke1 Qf7 Kf1 Qxh5 Ke2 Qh1 Kd3 Qf1+ Kc2 
30  +55.31   01:16  29049K  c7 c1=Q c8=Q+ Kd4 Qxc1 Nxc1 a5 Ne2 a6 Nf4 a7 Kd3 a8=Q Ke2 Kg7 Ne6+ Kf6 Nd4 Kxe5 Nc2 Qa2 Ne1 d4+ Kd1 Bg5 Nf3+ gxf3 Ke1 Qf7 Kf1 Qxh5 Ke2 Qh1 
31  +55.31   01:17  29264K  c7 c1=Q c8=Q+ Kd4 Qxc1 Nxc1 a5 Ne2 a6 Nf4 a7 Kd3 a8=Q Ke2 Kg7 Ne6+ Kf6 Nd4 Kxe5 Nc2 Qa2 Ne1 d4+ Kd1 Bg5 Nf3+ gxf3 Ke1 Qf7 Kf1 Qxh5 Ke2 Qh1 Kd3 
32  +55.31   01:24  31103K  c7 c1=Q c8=Q+ Kd4 Qxc1 Nxc1 a5 Ne2 a6 Nf4 a7 Kd3 a8=Q Ke2 Kg7 Ne6+ Kf6 Nd4 Kxe5 Nc2 Qa2 Ne1 d4+ Kd1 Bg5 Nf3+ gxf3 Ke1 Qf7 Kf1 Qxh5 Ke2 Qh1 Kd3 Qf1+ Kc2 
33     #86   02:39  51738K  c7 c1=Q c8=Q+ Kd4 Qxc1 Nxc1 a5 h4 a6 h3 gxh3 Nd3 a7 Nf4 a8=Q Kc4 Qa1 Kd3 Qa5 Kc2 Kg7 Nh5+ Kf7 Nf4 Qxe5 Ne2 Kg7 Kd1 Qa1+ Kc2 Qc3+ Kd1 Qf3 Kc1 Qxe2 Kc2 
34     #86   02:47  55396K  c7 c1=Q c8=Q+ Kb3 Qxc1 Nxc1 a5 h4 a6 h3 gxh3 Ne2 a7 Nf4 a8=Q Kc2 Qa4+ Kd3 Qa5 Kc2 Kg7 Ne6+ Kf6 Nf4 Qxe5 Ne2 Kg7 Kd1 Qa1+ Kc2 Qc3+ Kd1 Qf3 Kc1 Qxe2 Kc2 Qc4+ Kd1 Qf1+ Kc2 
35     #86   02:48  56212K  c7 c1=Q c8=Q+ Kb3 Qxc1 Nxc1 a5 h4 a6 h3 gxh3 Ne2 a7 Nf4 a8=Q Kc2 Qa4+ Kd3 Qa5 Kc2 Kg7 Ne6+ Kf6 Nf4 Qxe5 Ne2 Kg7 Kd1 Qa1+ Kc2 Qc3+ Kd1 Qf3 Kc1 Qxe2 Kc2 Qc4+ Kd1 Qf1+ Kc2 Qb1+ Kxb1 
36     #83   03:17  64457K  c7 c1=Q c8=Q+ Kb3 Qxc1 Nxc1 a5 h4 a6 h3 gxh3 Ne2 a7 Nf4 a8=Q Kc2 Qa5 Kc1 Kg7 Nh5+ Kf7 Nf4 Qxe5 Ne2 Qa1+ Kc2 Qa2+ Kd3 Qb1+ Kc4 Qb4+ Kd3 Qc3+ Kxe4 Qd3+ Kxd3 
37     #82   03:35  72445K  c7 c1=Q c8=Q+ Kb3 Qxc1 Nxc1 a5 h4 a6 h3 gxh3 Ne2 a7 Nf4 a8=Q Kc2 Qa5 Kc1 Kg7 Nh5+ Kf7 Nf4 Qxe5 Ne2 Qc5+ Kd1 Qh5 Kc2 Qxe2 Kc1 Qf1+ Kc2 Qb1+ Kxb1 
38     #82   03:40  75366K  c7 c1=Q c8=Q+ Kb3 Qxc1 Nxc1 a5 h4 a6 h3 gxh3 Ne2 a7 Nf4 a8=Q Kc2 Qa5 Kd1 Kg7 Nh5+ Kf7 Nf4 Qxe5 Nd3 Qc3 Nf4 Qf3+ Kc2 Qxf4 Kd1 Qf1+ Kc2 Qb1+ Kxb1 
39     #82   03:50  77989K  c7 c1=Q c8=Q+ Kb3 Qxc1 Nxc1 a5 h4 a6 h3 gxh3 Ne2 a7 Nf4 a8=Q Kc2 Qa5 Kd1 Kg7 Nh5+ Kf7 Nf4 Qxe5 Nd3 Qc3 Nf4 Qf3+ Kc2 Qxf4 Kd1 Qf1+ Kc2 Qb1+ Kxb1 
40     #82   03:59  82137K  c7 c1=Q c8=Q+ Kb3 Qxc1 Nxc1 a5 h4 a6 h3 gxh3 Ne2 a7 Nf4 a8=Q Kc2 Qa5 Kd1 Kg7 Nh5+ Kf7 Nf4 Qxe5 Nd3 Qc3 Nf4 Qf3+ Kc2 Qxf4 Kd1 Qf1+ Kc2 Qb1+ Kxb1 
41     #82   04:14  87254K  c7 c1=Q c8=Q+ Kb3 Qxc1 Nxc1 a5 h4 a6 h3 gxh3 Ne2 a7 Nf4 a8=Q Kc2 Qa5 Kd1 Kg7 Nh5+ Kf7 Nf4 Qxe5 Nd3 Qc3 Nf4 Qf3+ Kc2 Qxf4 Kd1 Qf1+ Kc2 Qb1+ Kxb1 
42     #82   04:32  94375K  c7 c1=Q c8=Q+ Kb3 Qxc1 Nxc1 a5 h4 a6 h3 gxh3 Ne2 a7 Nf4 a8=Q Kc2 Qa5 Kd1 Kg7 Nh5+ Kf7 Nf4 Qxe5 Nd3 Qc3 Nf4 Qf3+ Kc2 Qxf4 Kd1 Qf1+ Kc2 Qb1+ Kxb1 
43     #82   04:48 101348K  c7 c1=Q c8=Q+ Kb3 Qxc1 Nxc1 a5 h4 a6 h3 gxh3 Ne2 a7 Nf4 a8=Q Kc2 Qa5 Kd1 Kg7 Nh5+ Kf7 Nf4 Qxe5 Nd3 Qc3 Nf4 Qf3+ Kc2 Qxf4 Kd1 Qf1+ Kc2 Qb1+ Kxb1 
44     #80   06:12 130359K  c7 c1=Q c8=Q+ Kb3 Qxc1 Nxc1 a5 h4 a6 h3 gxh3 Ne2 a7 Nf4 a8=Q Kc2 Qa5 Kd1 Kg7 Ne6+ Kf7 Nd4 Qa1+ Kc2 Qxd4 exd4 d3 Kc1 Bf6 Kc2 Bxd4 
45     #80   07:04 143149K  c7 c1=Q c8=Q+ Kb3 Qxc1 Nxc1 a5 h4 a6 h3 gxh3 Ne2 a7 Nf4 a8=Q Kc2 Qa5 Kd1 Kg7 Ne6+ Kf7 Nd4 Qa1+ Kc2 Qxd4 exd4 d3 Kc1 Bf6 Kc2 Bxd4 
46     #79   10:28 201345K  c7 c1=Q c8=Q+ Kb3 Qxc1 Nxc1 a5 Kc2 a6 Nd3 a7 Nf4 a8=Q Kd1 Qa3 Ng6+ Kg7 Nf4 Qf3+ Kc1 Qxf4 exf4 Kg6 h4 Bxh4 Kd1 Bg3 f3 gxf3 
47     #79   11:07 214082K  c7 c1=Q c8=Q+ Kb3 Qxc1 Nxc1 a5 Kc2 a6 Nd3 a7 Nf4 a8=Q Kd1 Qa3 Ng6+ Kg7 Nf4 Qf3+ Kc1 Qxf4 exf4 Kg6 h4 Bxh4 Kd1 Bg3 f3 gxf3 
48     #78   20:13 387118K  c7 c1=Q c8=Q+ Kb3 Qxc1 Nxc1 a5 Kc2 a6 Nd3 a7 Nf4 a8=Q Nxg2 Qa4+ Kd3 Qb5+ Kc2 Qxe5 Kd1 Qxh5+ Kc2 Qh1 Nf4 Qb1+ Kxb1 
49     #77   25:28 525487K  c7 c1=Q c8=Q+ Kb3 Qxc1 Nxc1 a5 Kc2 a6 Nd3 a7 Nf4 a8=Q Ng6+ Kg7 Nxe7 Qe8 Kd1 Qxe7 Ke2 Qxe5 h4 Qh5+ Kd3 Qxh4 
50     #77   32:59 720044K  c7 c1=Q c8=Q+ Kb3 Qxc1 Nxc1 a5 Kc2 a6 Nd3 a7 Nf4 a8=Q Ng6+ Kg7 Nxe7 Qe8 Kd1 Qxe7 Ke2 Qxe5 h4 Qh5+ Kd3 Qxh4 
51     #77   35:50 832445K  c7 c1=Q c8=Q+ Kb3 Qxc1 Nxc1 a5 Kc2 a6 Nd3 a7 Nf4 a8=Q Ng6+ Kg7 Nxe7 Qe8 Kd1 Qxe7 Ke2 Qxe5 h4 Qh5+ Kd3 Qxh4 
52     #77   45:26   1084M  c7 c1=Q c8=Q+ Kb3 Qxc1 Nxc1 a5 Kc2 a6 Nd3 a7 Nf4 a8=Q Kd3 Qa3+ Kxe4 Qe3+ Kd5 Qxf4 exf4 Bg5 Ke4 Kg7 Kf5 Bxf4 
53     #77   55:30   1325M  c7 c1=Q c8=Q+ Kb3 Qxc1 Nxc1 a5 Kc2 a6 Nd3 a7 Nf4 a8=Q Kd3 Qa3+ Kxe4 Qe3+ Kd5 Qxf4 exf4 Bg5 Ke4 Kg7 Kf5 Bxf4 
54     #77 1:02:42   1515M  c7 c1=Q c8=Q+ Kb3 Qxc1 Nxc1 a5 Kc2 a6 Nd3 a7 Nf4 a8=Q Kd3 Qa3+ Kxe4 Qe3+ Kd5 Qxf4 exf4 Bg5 Ke4 Kg7 Kf5 Bxf4 
55     #77 1:14:26   1860M  c7 c1=Q c8=Q+ Kb3 Qxc1 Nxc1 a5 Kc2 a6 Nd3 a7 Nf4 a8=Q Kd3 Qa3+ Kxe4 Qe3+ Kf5 Qxf4+ Kxf4 Bd6 h4 Kg7 Kg4 Bxe5 
56     #77 1:30:12   2234M  c7 c1=Q c8=Q+ Kb3 Qxc1 Nxc1 a5 Kc2 a6 Nd3 a7 Nf4 a8=Q Kd3 Qa3+ Kxe4 Qe3+ Kf5 Qxf4+ Kxf4 Bd6 h4 Kg7 Kg4 Bxe5 
57     #77 4:07:14   6171M  c7 c1=Q c8=Q+ Kb3 Qxc1 Nxc1 a5 Kc2 a6 h4 a7 h3 gxh3 Ne2 a8=Q Nf4 Qa6 Kd1 Bg5 Ke1 Bxf4 exf4 Qf1+ Kxf1 
58     #77 7:30:34  11126M  c7 c1=Q c8=Q+ Kb3 Qxc1 Nxc1 a5 Kc2 a6 h4 a7 h3 gxh3 Ne2 a8=Q Nf4 Qa6 Kd1 Bg5 Ke1 Bxf4 exf4 Qf1+ Kxf1 
59     #7715:31:57  26416M  c7 c1=Q c8=Q+ Kb3 Qxc1 Nxc1 a5 Kc2 a6 h4 a7 h3 gxh3 Ne2 a8=Q Nf4 Qa6 Kd1 Bg5 Ke1 Bxf4 exf4 Qf1+ Kxf1 
60     #7720:04:24  34038M  c7 c1=Q c8=Q+ Kb3 Qxc1 Nxc1 a5 Kc2 a6 h4 a7 h3 gxh3 Ne2 a8=Q Nf4 Qa6 Kd1 Bg5 Ke1 Bxf4 exf4 Qf1+ Kxf1 
61     #7732:15:55  55181M  c7 c1=Q c8=Q+ Kd4 Qxc1 Nxc1 a5 h4 a6 h3 gxh3 Ne2 a7 Nf4 a8=Q Ng6+ Kg7 Nf4 Qa3 Kxe4 Qb4+ Kd5 Qxf4 exf4 
Here is the problem (GetTickCount() wraps around once every 50 days or so:
https://msdn.microsoft.com/en-us/librar ... 85%29.aspx

Sort of a solution (but it does not work on every platform):
https://msdn.microsoft.com/en-us/librar ... 85%29.aspx

You can use QueryPerformanceCounter and QueryPerformanceFrequency, but you are not guaranteed to get a high performance timer, since there are a limited number of them and they could be in use.

So a general Windows timing solution could be to inquire on the high performance counter, and use it if available.
Then query Kernel32.lib for the presence of GetTickCount64 to see if it exists. If it exists, use that, else use GetTickCount.

I always have many machines running around the clock doing chess analysis. So I run into this bug all the time.

Gerd Isenberg
Posts: 2128
Joined: Wed Mar 08, 2006 7:47 pm
Location: Hattingen, Germany

Re: Questions in Respect to Code Release

Post by Gerd Isenberg » Thu Mar 05, 2015 9:41 pm

jorose wrote:I am going to release my engine sometime this month. Unfortunately I have never released code and also didn't originally write my code with the intention of releasing it or having it run on any machine aside from my own. This leads me to a few questions. I also suspect I might have more questions before I release and in order not to clutter up the forum I will just reply to my own post here if I do end up with more questions.

So my first question is in respect to licensing. I want to release my code under GPL however I found out there are 3 versions of GPL, is there a reason not to use the newest version? On this same note as far I can remember there shouldn't be any code snippets I didn't write myself that is longer then just a few lines of code, however I use kogge stone fill algorithms which I at some point, back when my engine was still in Java took from the CPW page I just linked. Is it even possible for me to release my engine with this part of the code? Do I need to add people to the list of authors if I don't remove this part of the code?
Hi Jonathan,

code and text from cpw is formally under "Creative Commons Attribution Share-Alike 3.0 License", i.e. cpw-engine. As primary cpw editor and author of the bitboard pages, I consider these code snippets public domain. For a GPL program to mention a cpw page or url is great - for Kogge-Stone, you may mention Steffan Westcott and his post in a function header or similar, but in no way as author of your engine.

http://www.stmintz.com/ccc/index.php?id=252289

You may also write a small article about your engine in cpw ;-)

Good luck and fun,
Gerd

syzygy
Posts: 4458
Joined: Tue Feb 28, 2012 10:56 pm

Re: Questions in Respect to Code Release

Post by syzygy » Fri Mar 06, 2015 12:20 am

Evert wrote:
syzygy wrote:It's also possible to install a mingw-based crosscompiler on Linux. Then you can develop and compile for Windows having all the conveniences of Linux. Testing can be done using Wine.
I (used to) do this, it works well.

The downside, I found, was that I needed to distribute the C++ runtime along with my executable (I couldn't static-link it), which is rather large.
No need for that with C, but it seems the OP is indeed using C++.

As far as I can see, it is possible to link statically using -static-libstdc++, but I have never tried this.

Anyway, this is not specific to running mingw as a cross-compiler on Linux but also applies to running mingw on Windows (unless there is a bug in some mingw cross-compiler distribution).

jdart
Posts: 3835
Joined: Fri Mar 10, 2006 4:23 am
Location: http://www.arasanchess.org

Re: Questions in Respect to Code Release

Post by jdart » Fri Mar 06, 2015 2:39 pm

The bit-manipulation intrinsics are not portable but depend on the compiler.

To see how to do this portably, you can look at:

https://github.com/jdart1/arasan-chess/ ... bitboard.h.

(You can even use this code - it is MIT licensed, which is more permissive than GPL).

If you want to run on Mac you need to support their compiler (clang). Clang can be installed on Linux and you can test with it there. It is a good idea anyway to run with multiple compilers because they will generate different warnings.

Windows is a pain, especially if you want to support the native compiler (MSVC). However using Cygwin you can build using gcc on Windows.

--Jon

Post Reply