Nagy Ferenc László

I use this tool daily, but I don't really want to maintain it, sorry.

Any idea why gcc7 thinks that b is between 0 and 2147483647? It's unsigned char.

Let's hope the gcc developers will fix this. IMO this is the same bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81483

My ccminer was crashing on a vmovdqa instruction. I've fixed it by changing the neoscrypt_xor function inside sph/neoscrypt.cpp: ``` --- neoscrypt.cpp.old 2017-11-21 17:43:36.000000000 +0100 +++ neoscrypt.cpp 2017-12-15 19:19:37.550565124 +0100 @@...

As far as I understand this code runs on the CPU, so it shouldn't be related to the GPU. I was thinking that the issue is related to my compiler,...

Compilation of the current git version dies on my linux: ``` nvcc -gencode=arch=compute_61,code=sm_61 -gencode=arch=compute_52,code=sm_52 -gencode=arch=compute_50,code=sm_50 -gencode=arch=compute_37,code=sm_37 -gencode=arch=compute_35,code=sm_35 -gencode=arch=compute_30,code=sm_30 -I/usr/local/cuda/include -I. -O3 -std=c++11 -Xcompiler -fno-strict-aliasing -Wall -D_FORCE_INLINES --ptxas-options="-v" --maxrregcount=128 -o cuda_groestlcoin.o...