Closed hackmod closed 5 years ago
My dev system is Win 10 + x86_64 build + CUDA 10.0 + VS 2017 (no -Tv140).
This is what was used to generate the test vector, which passes against geth (with the required patches): https://github.com/ifdefelse/ProgPOW/blob/master/test/result.log
Can you try CUDA 10.0 instead of 9.0?
for linux, CUDA 9.0 works nicely (ubuntu 16.04 + CUDA 9.0)
and the compiled kernel.ptx
almost the same. (few register numbering changed)
personally, I will try to test CUDA 9.1, 9.2, and 10.0 in next week
CUDA 10.0 (with -Tv140
toolset) works nicely~
I guess, I have some installation problem with the CUDA-9.0. (maybe some outdated preview release?) After forcing update my old CUDA-9.0, it works nicely with no problem.
I can confirm that CUDA-9.0, CUDA-9.2 and CUDA-10.0 works! (CUDA-9.1 simply not tried)
so I can say that the minimal required CUDA version is 9.0 (Win 10 + Visual Studio 2017 (with v104 toolset)) 👍👍
I'm not sure why this happens.
linux binary works nicely, but Win x86_64 (Windows 10) + CUDA 9.0 + Visual Studio 2017 build (with
-Tv140
tool set) does not work correctly, (GTX1080-8GB)so I've dig into the source code and found that the
c_dag
generation part atprogpow_search()
seems odd.for normal case under linux, it print out
c_dag[0] = 2922db22466c51cc860021d27e41abf182c3d10b6acc5e7c3fa3d3f72b33ae8d
- epoch 0but Win x86_64 build case, it print some random output like as
c_dag[0] = 277c371ef7acd87123f6476e5d3b88f9be8e87ce7e544ebd5479c6a1b9db7b5c
- epoch 0and it results
GPU mix != CPU mix
any suggestion?