Page 6 of 7
Re: The most stupid idea by the Stockfish Team
Posted: Mon Aug 31, 2020 1:02 pm
by Gabor Szots
AndrewGrant wrote: ↑Mon Aug 31, 2020 12:42 pm
Gabor Szots wrote: ↑Mon Aug 31, 2020 12:17 pm
AndrewGrant wrote: ↑Sun Aug 30, 2020 12:04 pm
There is utility in packaging them together. The vast majority of Stockfish users are not people who frequent any forums like this.
If you really want to be ahead of the curve, just compile your own Stockfishs yourself.
There is a glitch in that, at least for me: the dev compile is 4 times as fast as mine. OK, I admit am totally new to compiling.
That would be because you selected a suboptimal make target. It is far more complex now that there are a dozen different targets to account for the vector maths that some processors have. If you told me your CPU, I could probably look at the makefile and tell you the right one, but I've not followed all the changes
Thanks Andrew. I did not use a makefile but this command line:
g++ -std=c++17 -DNDEBUG -DNNUE_EMBEDDING_OFF *.cpp syzygy/tbprobe.cpp nnue/evaluate_nnue.cpp nnue/features/half_kp.cpp -O3 -march=native -oStockfish_20_8_30-x64-SzG.exe
I have a somewhat old Haswell CPU (i5-4690K). But don't bother, I do this only for fun, I'm OK with the official builds.
Re: The most stupid idea by the Stockfish Team
Posted: Mon Aug 31, 2020 1:29 pm
by mmt
I had to double-check that I was not reading a thread started 20 years ago. That's when 21 MB was a sizable download. Right now, a medium web page size is 2 MB.
Re: The most stupid idea by the Stockfish Team
Posted: Mon Aug 31, 2020 6:21 pm
by Dann Corbit
Do you know how long it takes barracuda to check a 20MB zip file for viruses?
Now imagine that there are 3 or more binaries in the zip file.
Now imagine that you want to send the file to 30 different places.
Yes, I know this is only my problem.
You see no pain in it because there is no pain for you, but there is pain for other people.
It is true that these people are on the fringe so it is not important to worry about them according to the 80/20 rule.
Re: The most stupid idea by the Stockfish Team
Posted: Mon Aug 31, 2020 11:08 pm
by syzygy
Gabor Szots wrote: ↑Mon Aug 31, 2020 12:17 pm
AndrewGrant wrote: ↑Sun Aug 30, 2020 12:04 pm
There is utility in packaging them together. The vast majority of Stockfish users are not people who frequent any forums like this.
If you really want to be ahead of the curve, just compile your own Stockfishs yourself.
There is a glitch in that, at least for me: the dev compile is 4 times as fast as mine. OK, I admit am totally new to compiling.
You could try Cfish and just type "make pgo". The Makefile will then figure out the best settings for your system itself.
Re: The most stupid idea by the Stockfish Team
Posted: Tue Sep 01, 2020 12:48 am
by maxdeg
syzygy wrote: ↑Mon Aug 31, 2020 11:08 pm
Gabor Szots wrote: ↑Mon Aug 31, 2020 12:17 pm
AndrewGrant wrote: ↑Sun Aug 30, 2020 12:04 pm
There is utility in packaging them together. The vast majority of Stockfish users are not people who frequent any forums like this.
If you really want to be ahead of the curve, just compile your own Stockfishs yourself.
There is a glitch in that, at least for me: the dev compile is 4 times as fast as mine. OK, I admit am totally new to compiling.
You could try Cfish and just type "make pgo". The Makefile will then figure out the best settings for your system itself.
+3
Thank you very much RDM - worked perfectly.
One question if I may - how do I uniquely identify 'my' Cfish compile much as Gabor did with Stockfish.
Re: The most stupid idea by the Stockfish Team
Posted: Tue Sep 01, 2020 1:00 am
by syzygy
maxdeg wrote: ↑Tue Sep 01, 2020 12:48 am
One question if I may - how do I uniquely identify 'my' Cfish compile much as Gabor did with Stockfish.
What do you mean by identifying your Cfish compile?
If you want know what options were used to compile your Cfish, you can look at the output of "make" or you can start cfish.exe from the command line and type "compiler".
Re: The most stupid idea by the Stockfish Team
Posted: Tue Sep 01, 2020 1:05 am
by maxdeg
syzygy wrote: ↑Tue Sep 01, 2020 1:00 am
maxdeg wrote: ↑Tue Sep 01, 2020 12:48 am
One question if I may - how do I uniquely identify 'my' Cfish compile much as Gabor did with Stockfish.
What do you mean by identifying your Cfish compile?
If you want know what options were used to compile your Cfish, you can look at the output of "make" or you can start cfish.exe from the command line and type "compiler".
Thank you.
Re: The most stupid idea by the Stockfish Team
Posted: Tue Sep 01, 2020 7:52 am
by Gabor Szots
syzygy wrote: ↑Mon Aug 31, 2020 11:08 pm
You could try Cfish and just type "make pgo". The Makefile will then figure out the best settings for your system itself.
I did (using the master) but got these messages:
process_begin: CreateProcess(NULL, uname -s, ...) failed.
Makefile:26: pipe: No error
process_begin: CreateProcess(NULL, uname -s, ...) failed.
Makefile:386: pipe: Bad file descriptor
process_begin: CreateProcess(NULL, uname -s, ...) failed.
Makefile:390: pipe: Bad file descriptor
process_begin: CreateProcess(NULL, uname -s, ...) failed.
Makefile:390: pipe: Bad file descriptor
process_begin: CreateProcess(NULL, uname -s, ...) failed.
Makefile:449: pipe: Bad file descriptor
process_begin: CreateProcess(NULL, uname -s, ...) failed.
Makefile:449: pipe: Bad file descriptor
process_begin: CreateProcess(NULL, uname -s, ...) failed.
Makefile:465: pipe: Bad file descriptor
process_begin: CreateProcess(NULL, uname -s, ...) failed.
Makefile:499: pipe: Bad file descriptor
process_begin: CreateProcess(NULL, uname -s, ...) failed.
Makefile:533: pipe: Bad file descriptor
process_begin: CreateProcess(NULL, uname -s, ...) failed.
Makefile:643: pipe: Bad file descriptor
'grep' is not recognized as an internal or external command,
operable program or batch file.
curl was unexpected at this time.
shasum was unexpected at this time.
-f was unexpected at this time.
mingw32-make: *** [Makefile:814: net] Error 255
Thanks anyway.
Re: The most stupid idea by the Stockfish Team
Posted: Tue Sep 01, 2020 10:22 am
by syzygy
Gabor Szots wrote: ↑Tue Sep 01, 2020 7:52 am
syzygy wrote: ↑Mon Aug 31, 2020 11:08 pm
You could try Cfish and just type "make pgo". The Makefile will then figure out the best settings for your system itself.
I did (using the master) but got these messages:
process_begin: CreateProcess(NULL, uname -s, ...) failed.
Makefile:26: pipe: No error
process_begin: CreateProcess(NULL, uname -s, ...) failed.
Makefile:386: pipe: Bad file descriptor
process_begin: CreateProcess(NULL, uname -s, ...) failed.
Makefile:390: pipe: Bad file descriptor
process_begin: CreateProcess(NULL, uname -s, ...) failed.
Makefile:390: pipe: Bad file descriptor
process_begin: CreateProcess(NULL, uname -s, ...) failed.
Makefile:449: pipe: Bad file descriptor
process_begin: CreateProcess(NULL, uname -s, ...) failed.
Makefile:449: pipe: Bad file descriptor
process_begin: CreateProcess(NULL, uname -s, ...) failed.
Makefile:465: pipe: Bad file descriptor
process_begin: CreateProcess(NULL, uname -s, ...) failed.
Makefile:499: pipe: Bad file descriptor
process_begin: CreateProcess(NULL, uname -s, ...) failed.
Makefile:533: pipe: Bad file descriptor
process_begin: CreateProcess(NULL, uname -s, ...) failed.
Makefile:643: pipe: Bad file descriptor
'grep' is not recognized as an internal or external command,
operable program or batch file.
curl was unexpected at this time.
shasum was unexpected at this time.
-f was unexpected at this time.
mingw32-make: *** [Makefile:814: net] Error 255
Thanks anyway.
Looks like your MSYS2 installation is not how it is expected.
Perhaps you are compiling from a regular command prompt where you should open a terminal window with bash prompt? I'm not using MSYS2 myself, perhaps someone else here can explain what is wrong.
Re: The most stupid idea by the Stockfish Team
Posted: Tue Sep 01, 2020 11:25 am
by Guenther
syzygy wrote: ↑Tue Sep 01, 2020 10:22 am
Gabor Szots wrote: ↑Tue Sep 01, 2020 7:52 am
syzygy wrote: ↑Mon Aug 31, 2020 11:08 pm
You could try Cfish and just type "make pgo". The Makefile will then figure out the best settings for your system itself.
I did (using the master) but got these messages:
process_begin: CreateProcess(NULL, uname -s, ...) failed.
Makefile:26: pipe: No error
process_begin: CreateProcess(NULL, uname -s, ...) failed.
...
'grep' is not recognized as an internal or external command,
operable program or batch file.
curl was unexpected at this time.
shasum was unexpected at this time.
-f was unexpected at this time.
mingw32-make: *** [Makefile:814: net] Error 255
Thanks anyway.
Looks like your MSYS2 installation is not how it is expected.
Perhaps you are compiling from a regular command prompt where you should open a terminal window with bash prompt? I'm not using MSYS2 myself, perhaps someone else here can explain what is wrong.
Thanks it works like a charm here (also msys2 - completely fresh install, after a dumb antivirus update killed
first curl, then pacman and then even more, w/o any possibility of restoring the false positives, uahhh.
I changed my whole antivirus environment after this unhappy 'accident')
I guess Gabors toolchain is incomplete and grep seems lacking at all.
Is CFish now at the same commit level again as SF dev currently?
It seems it is faster than my SFdev compile w/o nnue included. Need to check this more precisely.
@Gabor
It seems your msys2 installation never was really complete, as grep is already in the 'base' group.
https://packages.msys2.org/group/
I suggest running all those commands again one by one, it will only load, what is missing or otherwise update.
Code: Select all
pacman -Syu
pacman -S mingw-w64-x86_64-gcc
pacman -S mingw-w64-x86_64-make
pacman -S mingw-w64-x86_64-toolchain
pacman -S libraries
If you ever want to compile e.g. cutechess you need this too
Code: Select all
pacman -S mingw-w64-x86_64-qt5-static