Skip to content
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

compile error with gcc 13.2 #22

Open
yssaya opened this issue Jun 22, 2024 · 3 comments
Open

compile error with gcc 13.2 #22

yssaya opened this issue Jun 22, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@yssaya
Copy link

yssaya commented Jun 22, 2024

I tried to build on Ubuntu 24.04 LTS, RTX 4090, CUDA 12.4, cuDNN 8.9.7.

$ git submodule update --init --recursive
$ mkdir build && cd build
$ cmake .. -DBLAS_BACKEND=CUDNN
$ make -j 4
...
In file included from /home/yss/go/sayuri/src/utils/parse_float.cc:1:
/home/yss/go/sayuri/src/utils/parse_float.h:8:33: error: 'std::uint32_t' has not been declared
8 | bool MatchFloat32(float f, std::uint32_t n);

$ gcc --version
gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0

Add this one line to these two files seems ok.
#include <cstdint>
src/utils/parse_float.h
src/utils/filesystem.h

@CGLemon
Copy link
Owner

CGLemon commented Jun 22, 2024

Thanks! I miss the header file.

I notice the weird result for this version, http://www.yss-aya.com/cgos/19x19/cross/sayuri321_2285_p1k.html . Seem the engine uses around 100 threads. I guess you still use same setting as sayuri321_1975_p1k. Did you use gcc13 to compile this engine?

@yssaya
Copy link
Author

yssaya commented Jun 22, 2024

oops, yes, I used gcc13 and used following option, and it was not same as sayuri321_1975_p1k.

../build/sayuri20240622 -t 0 -b 0 -p 1000 -w ../network/20240321zero-swa-2285k.bin.txt --capture-all-dead
sayuri321_1975_p1k's setting was
../build/sayuri20240603 -t 4 -p 1000 -w ../network/20240321zero-swa-1975k.bin.txt --capture-all-dead

I have started new sayuri321_2285_1k with " -t 4 -p 1000".

@CGLemon
Copy link
Owner

CGLemon commented Jun 22, 2024

I see. Engine will will select as many as possible threads number when we set the -t as 0. In this condition, we assume playouts number limit is high and have enough thinking time. I think we should set a threads number limit based on certain information to fix this bug.

@CGLemon CGLemon added the bug Something isn't working label Jun 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants