Pages:
Author

Topic: VanitySearch (Yet another address prefix finder) - page 56. (Read 31159 times)

sr. member
Activity: 462
Merit: 696
At the end of the list you have the number of items found by the CPU if this number is equal to 549, that means that all are wrong.
legendary
Activity: 1914
Merit: 2071
Output of current version (vanitygensearch -check):
Code:
ComputeKeys() found 1563 items , CPU check...
Expected item not found fefebd83 328e08ab 3b17c5c2 1fdc223d e99919bf
Expected item not found fefe17af bdccaa14 b240f5d9 acf1b7a7 6d66f7d4
Expected item not found 34122cfd 49587610 4fbb18c9 be290471 8bbe55a8
Expected item not found fefe2e06 e7430d2e 8dd6b425 26ff1d5e 57c9a8d6
.................

The list of item not found has 549 elements. Does it mean that 549 over 1563 are wrong?

there are still errors:
Code:
~/VanitySearch$ ./VanitySearch -stop  -t 7 -gpu  1Want
Start Sat Mar 16 19:17:24 2019
Difficulty: 264104224
Search: 1Want
Base Key:4C521F50F3A619FB59ED594ABAD7243B7266F5A0E4ED1850306A4523CF18283C
Number of CPU thread: 7
GPU: GPU #0 Quadro M2200 (8x128 cores) Grid(64x128)

Pub Addr: 1WantmvzmXjLYrMbs7WccKgdus2FgWu66
Prv Addr: 5JadqmMLiBnwNW1w8i1xwEJ3WjRkmSTTsjA7jDWtDYsBqC34sEt
Prv Key : 0x64B3566DF6454B047C32CE2E665C23F6092B8CCD9A88E3E3877045CAAFC14EFD
Check   : 136kVCwRzYyBSfykqncpRsX378LxkCQ1Fd
Check   : 1JunfTKznR17uaRw5svvRy4a2XiB3DEbLR (comp)



Output of the working version (vanitygensearch -check):
Code:
~/VanitySearch_old2$ ./VanitySearch -check
...
ComputeKeys() found 539 items , CPU check...
GPU/CPU check OK
sr. member
Activity: 462
Merit: 696
They are not compile errors, it is the verbose ouput of nvcc, the _Z10CheckPointPjiiPtjS_S_ is a mangled name of the function CheckPoint in GPUCompute.h that I added in the last release.

legendary
Activity: 1914
Merit: 2071
The check works flawlessly on my configs, both linux and windows. It should work.
There is something wrong somewhere but where...


vanitygen -check works with a old version, this is the only compile error I got:
Code:
g++ -DWITHGPU -m64  -Wno-write-strings -O2 -I. -I/usr/local/cuda-8.0/include -o obj/hash/sha256_sse.o -c hash/sha256_sse.cpp
/usr/local/cuda-8.0/bin/nvcc -maxrregcount=0 --ptxas-options=-v --compile --compiler-options -fPIC -ccbin g++ -m64 -O2 -I/usr/local/cuda-8.0/include -gencode=arch=compute_50,code=sm_50 -o obj/GPU/GPUEngine.o -c GPU/GPUEngine.cu
ptxas info    : 0 bytes gmem, 16872 bytes cmem[3]
ptxas info    : Compiling entry function '_Z9comp_keysjPtPjPmS0_' for 'sm_50'
ptxas info    : Function properties for _Z9comp_keysjPtPjPmS0_
    16712 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
ptxas info    : Used 128 registers, 360 bytes cmem[0], 116 bytes cmem[2]
ptxas info    : Function properties for _Z11_GetHash160PmS_Ph
    0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
ptxas info    : Function properties for _Z15_GetHash160CompPmS_Ph
    0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
ptxas info    : Function properties for _Z7_ModInvPm
    0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
ptxas info    : Function properties for _Z9CheckHashjPtPmS0_ijPjS1_
    0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads



vanitygen -check deosn't works with the current version, this is the  compile error I got:
Code:
/usr/local/cuda-8.0/bin/nvcc -maxrregcount=0 --ptxas-options=-v --compile --compiler-options -fPIC -ccbin g++ -m64 -O2 -I/usr/local/cuda-8.0/include -gencode=arch=compute_50,code=sm_50 -o obj/GPU/GPUEngine.o -c GPU/GPUEngine.cu
ptxas info    : 0 bytes gmem, 33320 bytes cmem[3]
ptxas info    : Compiling entry function '_Z9comp_keysjPtPjPmS0_' for 'sm_50'
ptxas info    : Function properties for _Z9comp_keysjPtPjPmS0_
    32936 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
ptxas info    : Used 126 registers, 360 bytes cmem[0], 116 bytes cmem[2]
ptxas info    : Function properties for _Z10CheckPointPjiiPtjS_S_
    0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
ptxas info    : Function properties for _Z11_GetHash160PmS_Ph
    0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
ptxas info    : Function properties for _Z13CheckHashCompPtPmS0_ijPjS1_
    0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
ptxas info    : Function properties for _Z15CheckHashUncompPtPmS0_ijPjS1_
    0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
ptxas info    : Function properties for _Z15_GetHash160CompPmS_Ph
    0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
ptxas info    : Function properties for _Z7_ModInvPm
    0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
ptxas info    : Function properties for _Z9CheckHashjPtPmS0_ijPjS1_
    0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads

As you can see, in the last there is a different error:  Function properties for _Z10CheckPointPjiiPtjS_S_

sr. member
Activity: 462
Merit: 696
The check works flawlessly on my configs, both linux and windows. It should work.
There is something wrong somewhere but where...
legendary
Activity: 1914
Merit: 2071
I found out an illegal memory access.
I committed a fix on git source.
Thanks to test if it is better or not...


The error remains.

EDIT:
to be precise, now it seems that the results are correct (I made 10 tries) but vanitysearch -check produces the same error: maybe there is something wrong with -check function?

Code:
~/VanitySearch$ ./VanitySearch -check
GetBase10() Results OK
Add() Results OK : 125.000 MegaAdd/sec
Mult() Results OK : 24.272 MegaMult/sec
Div() Results OK : 4.566 MegaDiv/sec
ModInv()/ModExp() Results OK
ModInv() : 342.807 KiloInv/sec
IntGroup.ModInv() : 8.920 MegaInv/sec
ModMulK1() : 12.700 MegaMult/sec
ModSqrt() OK !
Check Generator :OK
Check Double :OK
Check Add :OK
Check GenKey :OK
Adress : 15t3Nt1zyMETkHbjJTTshxLnqPzQvAtdCe OK!
Adress : 1BoatSLRHtKNngkdXEeobR76b53LETtpyT OK!
Adress : 1JeanLucgidKHxfY5gkqGmoVjo1yaU4EDt OK(comp)!
Adress : 1Test6BNjSJC5qwYXsjwKVLvz7DpfLehy OK!
Adress : 1BitcoinP7vnLpsUHWbzDALyJKnNo16Qms OK(comp)!
Check Calc PubKey (full) 1ViViGLEawN27xRzGrEhhYPQrZiTKvKLo :OK
Check Calc PubKey (even) 1Gp7rQ4GdooysEAEJAS2o4Ktjvf1tZCihp:OK
Check Calc PubKey (odd) 18aPiLmTow7Xgu96msrDYvSSWweCvB9oBA:OK
GPU: GPU #0 Quadro M2200 (8x128 cores) Grid(64x128)
Seed: 902291
143.116 MegaKey/sec
ComputeKeys() found 1514 items , CPU check...
Expected item not found 3412af62 86300235 849853ea d298b73d d56bb672
Expected item not found 3412bc7b f1296ba0 afb84655 82130792 85bd7f54
Expected item not found 341232ca dd9bc221 4a9664ea 50c352fd 44addb30
Expected item not found 3412366e b3b688bc 7fe3a7bc 967677f8 6ac14eb9
Expected item not found 34128851 1ec60338 7c2f3643 fd5f4e86 0034f632
Expected item not found 34126703 5f43f06a d3b47d48 d70219e9 f208ba14
Expected item not found 3412d097 91788b71 ad6b2e75 308fdaf9 5a992844
Expected item not found fefedc03 fffe2da5 f492467d 154c8931 256f1442
Expected item not found fefe8106 2b806056 b0a46a1f d3969aea 5fb333bd
Expected item not found 341241b9 59581e9f ba6e39f4 f510d1a9 db8901d4
Expected item not found fefec45f 234faf04 cf53b66e 27307904 ffe364f3
Expected item not found 34120d3f 6c2613f4 71dbd886 c88e267a 586fc692
Expected item not found 3412780f a040e2a5 a16a1705 38480789 316b57af
Expected item not found fefe9a98 be3ac140 c7c35aef b088b405 42ee825a
Expected item not found 341253c0 29f92e0f 4b1f60f5 05363c5a 7c1972d2
Expected item not found 34129ee6 10e0641e c1b79be2 512466be 675e2b3a
sr. member
Activity: 462
Merit: 696
I found out an illegal memory access.
I committed a fix on git source.
Thanks to test if it is better or not...
sr. member
Activity: 462
Merit: 696
Good news.
But restoring the group size, and get back in my linux git repo the problem appears.
I will try to debug this.
sr. member
Activity: 462
Merit: 696
The 1111 is not a problem difficult to solve.
But the other concerning the GPU, f...ing hell !

And all work fine on my 8 years old quadro 600 !
legendary
Activity: 1914
Merit: 2071
I confirm that there is a problem with difficulty calculation when searching prefix like 1111something...

For this prefix vanitygen
vanitygen.exe 11111
Difficulty: 4294967296
[353.08 Kkey/s][total 20853248][Prob 0.5%][50% in 2.8h]

and for

vanitygen.exe 111111
Difficulty: 1099511627776
[326.68 Kkey/s][total 987648][Prob 0.0%][50% in 27.0d]


256**4 = 4294967296

256**5 = 1099511627776
member
Activity: 117
Merit: 32
I confirm that there is a problem with difficulty calculation when searching prefix like 1111something...

For this prefix vanitygen
vanitygen.exe 11111
Difficulty: 4294967296
[353.08 Kkey/s][total 20853248][Prob 0.5%][50% in 2.8h]

and for

vanitygen.exe 111111
Difficulty: 1099511627776
[326.68 Kkey/s][total 987648][Prob 0.0%][50% in 27.0d]
legendary
Activity: 1914
Merit: 2071
I confirm that there is a problem with difficulty calculation when searching prefix like 1111something...


Case 11111.. should be simple:

difficulty = 256^(# of 1 - 1)

Example:
1 --> difficulty 1
11 --> difficulty = 256^1
111 --> difficulty = 256^2



Same error for GPU. Now it's a little slower too.

Code:
./VanitySearch -stop  -t 7 -gpu  111111
Start Sat Mar 16 15:44:37 2019
Difficulty: 1961676049784709488574464
Search: 111111
Base Key:BB62B2E3C2AB0474AC27C72F337D14BB6679B66AB0D82FEC2592FF91C87E6F2F
Number of CPU thread: 7
GPU: GPU #0 Quadro M2200 (8x128 cores) Grid(64x128)
145.164 MK/s (GPU 128.957 MK/s) (2^32.37) [P 0.00%][50.00% in 2.97021e+08y][0]
Pub Addr: 111111KYoXqxKvZFofwTHWBoUydR9PvT
Prv Addr: 5KEp6PQmPqDjS4yzsouLGS7KC5kMNoBnQdGEh9KHscGHXFG7wuE
Prv Key : 0xBB62B2E3C2AB0474AC27C72F337D14BB66F9B66AB23E2FEC2592FF91C88005B9
Check   : 1EUCkw1FJmgH3SqvnimVhZv6X213hsXCX9
Check   : 17wrT4K44bsuVSPvbm3wGncoCz129SAH6m (comp)

EDIT:

the last version that works for me is the one without endomorhism (with speed 130 MKeys/s):

Code:
./VanitySearch -check
GetBase10() Results OK
Add() Results OK : 204.082 MegaAdd/sec
Mult() Results OK : 27.174 MegaMult/sec
Div() Results OK : 5.076 MegaDiv/sec
ModInv()/ModExp() Results OK
ModInv() : 340.947 KiloInv/sec
IntGroup.ModInv() : 9.077 MegaInv/sec
ModMulK1() : 12.966 MegaMult/sec
ModSqrt() OK !
Check Generator :OK
Check Double :OK
Check Add :OK
Check GenKey :OK
Adress : 15t3Nt1zyMETkHbjJTTshxLnqPzQvAtdCe OK!
Adress : 1BoatSLRHtKNngkdXEeobR76b53LETtpyT OK!
Adress : 1JeanLucgidKHxfY5gkqGmoVjo1yaU4EDt OK(comp)!
Adress : 1Test6BNjSJC5qwYXsjwKVLvz7DpfLehy OK!
Adress : 1BitcoinP7vnLpsUHWbzDALyJKnNo16Qms OK(comp)!
Check Calc PubKey (full) 1ViViGLEawN27xRzGrEhhYPQrZiTKvKLo :OK
Check Calc PubKey (even) 1Gp7rQ4GdooysEAEJAS2o4Ktjvf1tZCihp:OK
Check Calc PubKey (odd) 18aPiLmTow7Xgu96msrDYvSSWweCvB9oBA:OK
GPU: GPU #0 Quadro M2200 (8x128 cores) Grid(64x128)
Seed: 632257
103.313 MegaKey/sec
ComputeKeys() found 504 items , CPU check...
GPU/CPU check OK
sr. member
Activity: 462
Merit: 696
I confirm that there is a problem with difficulty calculation when searching prefix like 1111something...
sr. member
Activity: 462
Merit: 696
Yes 11111 is quite difficult (leading 0).
May be there is also a bug with this particular case. I'll check that.

I restored the old group size.
Could try to update your git repo
And try again.
Many thank for your help.
legendary
Activity: 1914
Merit: 2071
Ok

Could you try to noiline to 2 ModMult, also in GPU/GPUEngine.cu:

Code:
Line 510: __device__ __noinline__ void _ModMult(uint64_t *r, uint64_t *a, uint64_t *b) {
Line 560: __device__ __noinline__ void _ModMult(uint64_t *r, uint64_t *a) {

It seems that I reached a limit with CUDA....
I had similar problem with the last release...

Same error again...

Very strange, look at the time:  5.00779e+06y to get the 50% ...
Code:
:~/VanitySearch$ ./VanitySearch -stop  -t 7 -gpu  11111
Start Sat Mar 16 15:26:49 2019
Difficulty: 33822000858357062172672
Search: 11111
Base Key:F2A543066C493024B85715EFFE2486460C80009A931F6D8B1614FC20573DC40B
Number of CPU thread: 7
GPU: GPU #0 Quadro M2200 (8x128 cores) Grid(64x128)
148.447 MK/s (GPU 130.846 MK/s) (2^30.47) [P 0.00%][50.00% in 5.00779e+06y][0]
Pub Addr: 111113auryoueJApjac3VvMcmPcL1W5Co
Prv Addr: 5KKbZb2q6ds9MKJ7RP5pdx7bFmazSU7arhkBetsUYBEJyNKHRQj
Prv Key : 0xC63F8239D2073D242F6263099770C17426D95822647B78C56E5A72AC6542C113
Check   : 1MRXFX8Vmw6n4GLSWVr6Jp8WGjLm74Cuj4
Check   : 1DJ7SW3Tp6wkFvUGhAfLNcrCy5pNSQTEtp (comp)
sr. member
Activity: 462
Merit: 696
Ok

Could you try to noiline to 2 ModMult, also in GPU/GPUEngine.cu:

Code:
Line 510: __device__ __noinline__ void _ModMult(uint64_t *r, uint64_t *a, uint64_t *b) {
Line 560: __device__ __noinline__ void _ModMult(uint64_t *r, uint64_t *a) {

It seems that I reached a limit with CUDA....
I had similar problem with the last release...
And no warning at all !
legendary
Activity: 1914
Merit: 2071
Ok
Could you try to edit GPUEngine.cu and to change the stackSize to 49152 line (48K) line 1371.
I doubled the group size and I missed this.
Does it improves something ?

Code:
  size_t stackSize = 49152;
  err = cudaDeviceSetLimit(cudaLimitStackSize, stackSize);
  if (err != cudaSuccess) {




Same error:

Code:
/usr/local/cuda-8.0/bin/nvcc -maxrregcount=0 --ptxas-options=-v --compile --compiler-options -fPIC -ccbin g++ -m64 -O2 -I/usr/local/cuda-8.0/include -gencode=arch=compute_50,code=sm_50 -o obj/GPU/GPUEngine.o -c GPU/GPUEngine.cu
ptxas info    : 0 bytes gmem, 33320 bytes cmem[3]
ptxas info    : Compiling entry function '_Z9comp_keysjPtPjPmS0_' for 'sm_50'
ptxas info    : Function properties for _Z9comp_keysjPtPjPmS0_
    32936 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
ptxas info    : Used 126 registers, 360 bytes cmem[0], 116 bytes cmem[2]
ptxas info    : Function properties for _Z10CheckPointPjiiPtjS_S_
    0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
ptxas info    : Function properties for _Z11_GetHash160PmS_Ph
    0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
ptxas info    : Function properties for _Z13CheckHashCompPtPmS0_ijPjS1_
    0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
ptxas info    : Function properties for _Z15CheckHashUncompPtPmS0_ijPjS1_
    0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
ptxas info    : Function properties for _Z15_GetHash160CompPmS_Ph
    0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
ptxas info    : Function properties for _Z7_ModInvPm
    0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
ptxas info    : Function properties for _Z9CheckHashjPtPmS0_ijPjS1_
    0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
Making VanitySearch...
g++ obj/Base58.o obj/IntGroup.o obj/main.o obj/Random.o obj/Timer.o obj/Int.o obj/IntMod.o obj/Point.o obj/SECP256K1.o obj/Vanity.o obj/GPU/GPUGenerate.o obj/hash/ripemd160.o obj/hash/sha256.o obj/hash/sha512.o obj/hash/ripemd160_sse.o obj/hash/sha256_sse.o obj/GPU/GPUEngine.o -lpthread -L/usr/local/cuda-8.0/lib64 -lcudart -o VanitySearch
sr. member
Activity: 462
Merit: 696
Ok
Could you try to edit GPUEngine.cu and to change the stackSize to 49152 line (48K) line 1371.
I doubled the group size and I missed this.
Does it improves something ?

Code:
  size_t stackSize = 49152;
  err = cudaDeviceSetLimit(cudaLimitStackSize, stackSize);
  if (err != cudaSuccess) {

legendary
Activity: 1914
Merit: 2071
Your git clone is up do date ?
git pull

Did you clean before making ?
make clean
and make gpu=1 all

On my config the -check is ok.
It looks like the problem I had last time when the GPU code was wrongly generated.


Code:
~$ git clone https://github.com/JeanLucPons/VanitySearch.git
Cloning into 'VanitySearch'...
remote: Enumerating objects: 147, done.
remote: Counting objects: 100% (147/147), done.
remote: Compressing objects: 100% (89/89), done.
remote: Total 472 (delta 90), reused 101 (delta 58), pack-reused 325
Ricezione degli oggetti: 100% (472/472), 287.95 KiB | 299.00 KiB/s, done.
Risoluzione dei delta: 100% (301/301), done.
~$ cd VanitySearch
~/VanitySearch$ git pull
Already up-to-date.


Code:
~/VanitySearch$ make clean
Cleaning...
~/VanitySearch$ make gpu=1 all
g++ -DWITHGPU -m64  -Wno-write-strings -O2 -I. -I/usr/local/cuda-8.0/include -o obj/Base58.o -c Base58.cpp
g++ -DWITHGPU -m64  -Wno-write-strings -O2 -I. -I/usr/local/cuda-8.0/include -o obj/IntGroup.o -c IntGroup.cpp
g++ -DWITHGPU -m64  -Wno-write-strings -O2 -I. -I/usr/local/cuda-8.0/include -o obj/main.o -c main.cpp
g++ -DWITHGPU -m64  -Wno-write-strings -O2 -I. -I/usr/local/cuda-8.0/include -o obj/Random.o -c Random.cpp
g++ -DWITHGPU -m64  -Wno-write-strings -O2 -I. -I/usr/local/cuda-8.0/include -o obj/Timer.o -c Timer.cpp
g++ -DWITHGPU -m64  -Wno-write-strings -O2 -I. -I/usr/local/cuda-8.0/include -o obj/Int.o -c Int.cpp
g++ -DWITHGPU -m64  -Wno-write-strings -O2 -I. -I/usr/local/cuda-8.0/include -o obj/IntMod.o -c IntMod.cpp
g++ -DWITHGPU -m64  -Wno-write-strings -O2 -I. -I/usr/local/cuda-8.0/include -o obj/Point.o -c Point.cpp
g++ -DWITHGPU -m64  -Wno-write-strings -O2 -I. -I/usr/local/cuda-8.0/include -o obj/SECP256K1.o -c SECP256K1.cpp
g++ -DWITHGPU -m64  -Wno-write-strings -O2 -I. -I/usr/local/cuda-8.0/include -o obj/Vanity.o -c Vanity.cpp
g++ -DWITHGPU -m64  -Wno-write-strings -O2 -I. -I/usr/local/cuda-8.0/include -o obj/GPU/GPUGenerate.o -c GPU/GPUGenerate.cpp
g++ -DWITHGPU -m64  -Wno-write-strings -O2 -I. -I/usr/local/cuda-8.0/include -o obj/hash/ripemd160.o -c hash/ripemd160.cpp
g++ -DWITHGPU -m64  -Wno-write-strings -O2 -I. -I/usr/local/cuda-8.0/include -o obj/hash/sha256.o -c hash/sha256.cpp
g++ -DWITHGPU -m64  -Wno-write-strings -O2 -I. -I/usr/local/cuda-8.0/include -o obj/hash/sha512.o -c hash/sha512.cpp
g++ -DWITHGPU -m64  -Wno-write-strings -O2 -I. -I/usr/local/cuda-8.0/include -o obj/hash/ripemd160_sse.o -c hash/ripemd160_sse.cpp
g++ -DWITHGPU -m64  -Wno-write-strings -O2 -I. -I/usr/local/cuda-8.0/include -o obj/hash/sha256_sse.o -c hash/sha256_sse.cpp
/usr/local/cuda-8.0/bin/nvcc -maxrregcount=0 --ptxas-options=-v --compile --compiler-options -fPIC -ccbin g++ -m64 -O2 -I/usr/local/cuda-8.0/include -gencode=arch=compute_50,code=sm_50 -o obj/GPU/GPUEngine.o -c GPU/GPUEngine.cu
ptxas info    : 0 bytes gmem, 33320 bytes cmem[3]
ptxas info    : Compiling entry function '_Z9comp_keysjPtPjPmS0_' for 'sm_50'
ptxas info    : Function properties for _Z9comp_keysjPtPjPmS0_
    32936 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
ptxas info    : Used 126 registers, 360 bytes cmem[0], 116 bytes cmem[2]
ptxas info    : Function properties for _Z10CheckPointPjiiPtjS_S_
    0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
ptxas info    : Function properties for _Z11_GetHash160PmS_Ph
    0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
ptxas info    : Function properties for _Z13CheckHashCompPtPmS0_ijPjS1_
    0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
ptxas info    : Function properties for _Z15CheckHashUncompPtPmS0_ijPjS1_
    0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
ptxas info    : Function properties for _Z15_GetHash160CompPmS_Ph
    0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
ptxas info    : Function properties for _Z7_ModInvPm
    0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
ptxas info    : Function properties for _Z9CheckHashjPtPmS0_ijPjS1_
    0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
Making VanitySearch...
g++ obj/Base58.o obj/IntGroup.o obj/main.o obj/Random.o obj/Timer.o obj/Int.o obj/IntMod.o obj/Point.o obj/SECP256K1.o obj/Vanity.o obj/GPU/GPUGenerate.o obj/hash/ripemd160.o obj/hash/sha256.o obj/hash/sha512.o obj/hash/ripemd160_sse.o obj/hash/sha256_sse.o obj/GPU/GPUEngine.o -lpthread -L/usr/local/cuda-8.0/lib64 -lcudart -o VanitySearch


Code:
~/VanitySearch$ ./VanitySearch -check
GetBase10() Results OK
Add() Results OK : 158.730 MegaAdd/sec
Mult() Results OK : 25.063 MegaMult/sec
Div() Results OK : 4.566 MegaDiv/sec
ModInv()/ModExp() Results OK
ModInv() : 337.671 KiloInv/sec
IntGroup.ModInv() : 9.041 MegaInv/sec
ModMulK1() : 12.934 MegaMult/sec
ModSqrt() OK !
Check Generator :OK
Check Double :OK
Check Add :OK
Check GenKey :OK
Adress : 15t3Nt1zyMETkHbjJTTshxLnqPzQvAtdCe OK!
Adress : 1BoatSLRHtKNngkdXEeobR76b53LETtpyT OK!
Adress : 1JeanLucgidKHxfY5gkqGmoVjo1yaU4EDt OK(comp)!
Adress : 1Test6BNjSJC5qwYXsjwKVLvz7DpfLehy OK!
Adress : 1BitcoinP7vnLpsUHWbzDALyJKnNo16Qms OK(comp)!
Check Calc PubKey (full) 1ViViGLEawN27xRzGrEhhYPQrZiTKvKLo :OK
Check Calc PubKey (even) 1Gp7rQ4GdooysEAEJAS2o4Ktjvf1tZCihp:OK
Check Calc PubKey (odd) 18aPiLmTow7Xgu96msrDYvSSWweCvB9oBA:OK
GPU: GPU #0 Quadro M2200 (8x128 cores) Grid(64x128)
Seed: 543374
107.806 MegaKey/sec
ComputeKeys() found 1499 items , CPU check...
Expected item not found fefe44b8 49f68f1f 096013ff e41e6d50 08263cf2
Expected item not found 3412f45b 16a98f1d bb7ee0f4 0278da41 07cb3ee6
Expected item not found fefe8197 02abccb1 39fcfe5c 7aa3a90a 33963bf2
Expected item not found fefedadb ac585a72 40bd3909 ecb1d075 e20484b9
Expected item not found 341249c5 f84bed21 07fb6121 631ee85d e5ef57c8
Expected item not found fefefa4a 23595a11 852a65fb 50ce146e 4540d8e8
Expected item not found fefe9430 b605f7f4 89981d6d 7b7a5088 a66b1f00
Expected item not found fefe9c16 400e3e2a 48c89b5a 3e52f969 918b7959
Expected item not found fefe5d8a 6d85d7df 48167af2 d4fc3a4d efa938e8
Expected item not found 3412485f e021867b f1397c5f ca679dba 77534406
Expected item not found 3412c6cd aecad837 247d170b f2eb91f4 81651450
Expected item not found 3412f092 9a76aa08 cb118f9e d0a04cc4 d03f89b6
Expected item not found 341299c8 ee36c5d2 17302781 6f96b5ab 71866549
Expected item not found 3412f7f1 1ce0cb01 8f52536b 55c48bbb 2f3b72f2
Expected item not found 3412b56c 3002219b bcce9cde 5e06bb74 5bd598c4
Expected item not found fefe8771 ac005e51 7cb4b3c4 f9a61416 e2e836bf
Expected item not found fefe8615 7ed9f4aa f16a2ceb ad9ffe89 5354f3f9
Expected item not found fefe25e1 afd03d00 c0c479c6 cd713bae b2e5cfa7
Expected item not found fefe334e 61a2a96e 0af5f876 357dab48 f67f214b
Expected item not found fefec35a 2ef5d92a b92dbe26 3c797bc6 5f35b539
Expected item not found fefe9221 f20eb58f 8a6f69c1 785431a7 d0730d12
Expected item not found 3412f913 ab809651 91539b93 232da11a ef41b61c
........
sr. member
Activity: 462
Merit: 696
@arulbero

Your git clone is up do date ?
git pull

Did you clean before making ?
make clean
and make gpu=1 all

On my config the -check is ok.
It looks like the problem I had last time when the GPU code was wrongly generated.

mmm....
Pages:
Jump to: