There are two things I would like help with:
1) Does it work for you? In particular I am curious if the Windows version works, because I don't have Windows anywhere and I compiled it from Linux.
Thanks!
Thanks for releasing it. The plain 64bit compile runs on my no popcount Win7 quadcore w/o problems so far.
I guess you'll add some uci options in the future?
Will you also add an internal version numbering scheme?
I have currently added it to my chronology with the generic hex number of the master release.
There are two things I would like help with:
1) Does it work for you? In particular I am curious if the Windows version works, because I don't have Windows anywhere and I compiled it from Linux.
Thanks!
Thanks for releasing it. The plain 64bit compile runs on my no popcount Win7 quadcore w/o problems so far.
I guess you'll add some uci options in the future?
Will you also add an internal version numbering scheme?
I have currently added it to my chronology with the generic hex number of the master release.
Those are both very reasonable steps. I'll get to them. I've been lazy about figuring out how UCI options work, but it can't be that hard. At the very least I need to be able to adjust the hash size, I guess.
There are two things I would like help with:
1) Does it work for you? In particular I am curious if the Windows version works, because I don't have Windows anywhere and I compiled it from Linux.
Thanks!
Thanks for releasing it. The plain 64bit compile runs on my no popcount Win7 quadcore w/o problems so far.
I guess you'll add some uci options in the future?
Will you also add an internal version numbering scheme?
I have currently added it to my chronology with the generic hex number of the master release.
Those are both very reasonable steps. I'll get to them. I've been lazy about figuring out how UCI options work, but it can't be that hard. At the very least I need to be able to adjust the hash size, I guess.
Thanks!
Look at how Stockfish does UCI.
It's beautiful and brilliant.
Even a peanut-head like me can add new options at a whim.
Taking ideas is not a vice, it is a virtue. We have another word for this. It is called learning.
But sharing ideas is an even greater virtue. We have another word for this. It is called teaching.
NOTE: The memset is not quite right, because it clears `size' bytes, not `size' entries. But I can just call `TranspositionsTable::clear()' there. After that change valgrind only complains about the same things as it does if you run it on a hello world.
CppCheck has a couple of comments on the source code, maybe there are serious issues among them.
Since your make options allow for optimisations relying on strict pointer aliasing, it might be a good idea to test that with the GCC sanitiser options enabled. Works only under Linux.
Ras wrote:CppCheck has a couple of comments on the source code, maybe there are serious issues among them.
With --enable=warning it complains about several constructors that don't initialize things that don't need to be initialized.
Since your make options allow for optimisations relying on strict pointer aliasing, it might be a good idea to test that with the GCC sanitiser options enabled. Works only under Linux.
Oh, I didn't know about the -fsanitize options. I found an out-of-bounds array access in my SEE code. Thanks!
gets the annotation that the first term is always true. But if you had intended it to be that way, you would not have put a condition around the following block?