-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: UCI960 Support? #3
Comments
Something else: I changed "char" to "short" , and then this link error happening: arm-linux-gnueabihf-gcc -O3 -flto -o laser bbinit.o board.o common.o eval.o evalhash.o hash.o search.o moveorder.o syzygy/tbprobe.o uci.o -lpthread Im using a cross compiler from x86_64 to arm (ubuntu) but my friend on a Rasp (=directly) has similar problems. |
Hi, For the compilation error, I have never tried compiling with anything other than MinGW, but the error probably comes from the inline assembly in common.cpp. Perhaps changing this to gcc intrinsics or setting USE_INLINE_ASM = false in common.h would help, at the cost of some NPS. |
Hi Jeff, for ubuntu (& its gcc), it works ...but not when i tried it on a raspberrypi. What about this "char => short" change from me (see above)? Jürgen |
The offdiag array is actually from Ronald de Man's Syzygy code, but there should be no harm in changing char to short (or int). I can't really explain the warnings, as KNOWN_WIN is used in eval.cpp and TB_WIN is used in search.cpp. Do the unused warnings stay even when all other warnings and errors are gone? Sometimes gcc gives unused warnings for const variables that are derived from other const variables (in this case both are derived from PIECE_VALUES[EG][PAWNS]) when it cannot complete the compilation. |
This is on a RaspberryPi3 (your files - not changed): make |
when i fix the "tbcore.c" (short) these errors vanish..the others stay. You can simply ignore it, if y want..I just mentioned its not everywhere perfect. |
Hi Jeff, Thanks for #6 ! I'll include yr engine in my next picochess release. for compile your newest code on raspPi (arm) i need to change this inline flag, and this tbcore stuff. Jürgen |
As a heads up, the current TCEC 960 competition made me try adding 960 support to laser. I don't think this code is ready for a PR yet, (may be buggy/reduce normal chess elo too much) but it appears to be "ok" at 960: c960b |
Hello,
im looking around for different uci engines for the project "picochess", which is also part of these DGT Pi chess clocks.
Mainly, im searching for engines with UCI960 support and/or Levels.
Now: Your side saying "todo uci960" ...can y tell me if that's planed in near future, and if yes when this can be expected? Also what about level support (similar to SF).
Jürgen
The text was updated successfully, but these errors were encountered: