CCminer(SP-MOD) Modded GPU kernels.

[scryptr]

SP_ v32 WILL NOT BUILD ON LINUX--

I tried building it and got dozens of ""t2" set but not used" errors.  I have no executable left on exit.

I checked "ccminer.cpp" for the correction that flipclip mentioned earlier.  The correction is in place in the git-code.

I am curently running tpruvot's 1.5.2-git release, it has been very stable.  A loss of 5mh/s for the rig, compared to sp_'s best, is painfully evident.       --scryptr

latest git pull sphash not build on linux:


./cuda_helper.h(73): Error: Cannot store to pointer that points to constant memory space

make[2]: *** [x15/cuda_x15_whirlpool.o] Error 1
make[2]: *** Waiting for unfinished jobs....

This is a different fix then before.  Unfortunately this is getting out of my realm here but when I made the below fixes, it compiled (Ubuntu 14.04) and quark ran fine (not sure about x15):
In Cudahelper.h (line 68):
FROM:
__device__ __forceinline__ uint64_t REPLACE_HIWORD(const uint64_t &x, const uint32_t y)
TO:
__device__ __forceinline__ uint64_t REPLACE_HIWORD(const uint64_t x, const uint32_t y)

(line 78):
FROM:
__device__ __forceinline__ uint64_t REPLACE_LOWORD(const uint64_t &x, const uint32_t y)
TO:
__device__ __forceinline__ uint64_t REPLACE_LOWORD(const uint64_t x, const uint32_t y)

Compiled and seems to be running fine.

cuda_helper.h ERRORS --

On lines 68, 78 (mentioned in your post) and lines 70, 80, and 84, there appear to be errors/typos.  I am not familiar enough with the code to fix it, but the "t2"variable is there, and it kicks up dozens of warnings at compilation time.  I have been able to compile the code with your fix, but the "t2" variable still produces warnings by the dozen.       --scryptr

[1714659790]

1714659790

[1714659790]

1714659790

[1714659790]

1714659790

[1714659790]

1714659790

[1714659790]

1714659790

[djm34]

SP_ v32 WILL NOT BUILD ON LINUX--

I tried building it and got dozens of ""t2" set but not used" errors.  I have no executable left on exit.

I checked "ccminer.cpp" for the correction that flipclip mentioned earlier.  The correction is in place in the git-code.

I am curently running tpruvot's 1.5.2-git release, it has been very stable.  A loss of 5mh/s for the rig, compared to sp_'s best, is painfully evident.       --scryptr

latest git pull sphash not build on linux:


./cuda_helper.h(73): Error: Cannot store to pointer that points to constant memory space

make[2]: *** [x15/cuda_x15_whirlpool.o] Error 1
make[2]: *** Waiting for unfinished jobs....

This is a different fix then before.  Unfortunately this is getting out of my realm here but when I made the below fixes, it compiled (Ubuntu 14.04) and quark ran fine (not sure about x15):
In Cudahelper.h (line 68):
FROM:
__device__ __forceinline__ uint64_t REPLACE_HIWORD(const uint64_t &x, const uint32_t y)
TO:
__device__ __forceinline__ uint64_t REPLACE_HIWORD(const uint64_t x, const uint32_t y)

(line 78):
FROM:
__device__ __forceinline__ uint64_t REPLACE_LOWORD(const uint64_t &x, const uint32_t y)
TO:
__device__ __forceinline__ uint64_t REPLACE_LOWORD(const uint64_t x, const uint32_t y)

Compiled and seems to be running fine.

cuda_helper.h ERRORS --

On lines 68, 78 (mentioned in your post) and lines 70, 80, and 84, there appear to be errors/typos.  I am not familiar enough with the code to fix it, but the "t2"variable is there, and it kicks up dozens of warnings at compilation time.  I have been able to compile the code with your fix, but the "t2" variable still produces warnings by the dozen.       --scryptr

what kind of warning ?
(in the first line 68, not sure t2=0 makes sense.)

[scryptr]

SP_ v32 WILL NOT BUILD ON LINUX--

I tried building it and got dozens of ""t2" set but not used" errors.  I have no executable left on exit.

I checked "ccminer.cpp" for the correction that flipclip mentioned earlier.  The correction is in place in the git-code.

I am curently running tpruvot's 1.5.2-git release, it has been very stable.  A loss of 5mh/s for the rig, compared to sp_'s best, is painfully evident.       --scryptr

latest git pull sphash not build on linux:


./cuda_helper.h(73): Error: Cannot store to pointer that points to constant memory space

make[2]: *** [x15/cuda_x15_whirlpool.o] Error 1
make[2]: *** Waiting for unfinished jobs....

This is a different fix then before.  Unfortunately this is getting out of my realm here but when I made the below fixes, it compiled (Ubuntu 14.04) and quark ran fine (not sure about x15):
In Cudahelper.h (line 68):
FROM:
__device__ __forceinline__ uint64_t REPLACE_HIWORD(const uint64_t &x, const uint32_t y)
TO:
__device__ __forceinline__ uint64_t REPLACE_HIWORD(const uint64_t x, const uint32_t y)

(line 78):
FROM:
__device__ __forceinline__ uint64_t REPLACE_LOWORD(const uint64_t &x, const uint32_t y)
TO:
__device__ __forceinline__ uint64_t REPLACE_LOWORD(const uint64_t x, const uint32_t y)

Compiled and seems to be running fine.

cuda_helper.h ERRORS --

On lines 68, 78 (mentioned in your post) and lines 70, 80, and 84, there appear to be errors/typos.  I am not familiar enough with the code to fix it, but the "t2"variable is there, and it kicks up dozens of warnings at compilation time.  I have been able to compile the code with your fix, but the "t2" variable still produces warnings by the dozen.       --scryptr

what kind of warning ?
(in the first line 68, not sure t2=0 makes sense.)

DJM34--

I didn't think so, either!  In fact, I deleted "=0" and compiled again.  It compiled, as before, with dozens of ""t2" set but not used" errors.  In my first post, I used the word "defined", instead of "set", but these are continual warnings during compilation.         --scryptr

[chrysophylax]

SP_ v32 WILL NOT BUILD ON LINUX--

I tried building it and got dozens of ""t2" set but not used" errors.  I have no executable left on exit.

I checked "ccminer.cpp" for the correction that flipclip mentioned earlier.  The correction is in place in the git-code.

I am curently running tpruvot's 1.5.2-git release, it has been very stable.  A loss of 5mh/s for the rig, compared to sp_'s best, is painfully evident.       --scryptr

latest git pull sphash not build on linux:


./cuda_helper.h(73): Error: Cannot store to pointer that points to constant memory space

make[2]: *** [x15/cuda_x15_whirlpool.o] Error 1
make[2]: *** Waiting for unfinished jobs....

This is a different fix then before.  Unfortunately this is getting out of my realm here but when I made the below fixes, it compiled (Ubuntu 14.04) and quark ran fine (not sure about x15):
In Cudahelper.h (line 68):
FROM:
__device__ __forceinline__ uint64_t REPLACE_HIWORD(const uint64_t &x, const uint32_t y)
TO:
__device__ __forceinline__ uint64_t REPLACE_HIWORD(const uint64_t x, const uint32_t y)

(line 78):
FROM:
__device__ __forceinline__ uint64_t REPLACE_LOWORD(const uint64_t &x, const uint32_t y)
TO:
__device__ __forceinline__ uint64_t REPLACE_LOWORD(const uint64_t x, const uint32_t y)

Compiled and seems to be running fine.

cuda_helper.h ERRORS --

On lines 68, 78 (mentioned in your post) and lines 70, 80, and 84, there appear to be errors/typos.  I am not familiar enough with the code to fix it, but the "t2"variable is there, and it kicks up dozens of warnings at compilation time.  I have been able to compile the code with your fix, but the "t2" variable still produces warnings by the dozen.       --scryptr

what kind of warning ?
(in the first line 68, not sure t2=0 makes sense.)

DJM34--

I didn't think so, either!  In fact, I deleted "=0" and compiled again.  It compiled, as before, with dozens of ""t2" set but not used" errors.  In my first post, I used the word "defined", instead of "set", but these are continual warnings during compilation.         --scryptr

same here ... continual t2 warnings and a error at the end ... so no compile ...

t2 ... does that mean terminator 2 is coming back for revenge - and thats why its not working?

ok ok - so im not funny ... bite me ...



#crysx

[sp_]

I have fixed the build now.

[chrysophylax]

I have fixed the build now.

pull - compile - test ... doing that now mate ...

#crysx

[sp_]

I added another fix,  you might need. @ github.

later today I wil release the first version of the spreadminer to the ppl who have donated 0.1 BTC. The miner is not
finished, but it works, and a little faster than the old one.

[chrysophylax]

I added another fix,  you might need. @ github.

later today I wil release the first version of the spreadminer to the ppl who have donated 0.1 BTC. The miner is not
finished, but it works, and a little faster than the old one.

tanx sp ...

downloading the git pull now ...

how will you distribute the spreadx11 miner to the donors? ...

id like to donate some more also - which algo would you prefer to have this time round?

#crysx

[sp_]

By email.

[djm34]

SP_ v32 WILL NOT BUILD ON LINUX--

I tried building it and got dozens of ""t2" set but not used" errors.  I have no executable left on exit.

I checked "ccminer.cpp" for the correction that flipclip mentioned earlier.  The correction is in place in the git-code.

I am curently running tpruvot's 1.5.2-git release, it has been very stable.  A loss of 5mh/s for the rig, compared to sp_'s best, is painfully evident.       --scryptr

latest git pull sphash not build on linux:


./cuda_helper.h(73): Error: Cannot store to pointer that points to constant memory space

make[2]: *** [x15/cuda_x15_whirlpool.o] Error 1
make[2]: *** Waiting for unfinished jobs....

This is a different fix then before.  Unfortunately this is getting out of my realm here but when I made the below fixes, it compiled (Ubuntu 14.04) and quark ran fine (not sure about x15):
In Cudahelper.h (line 68):
FROM:
__device__ __forceinline__ uint64_t REPLACE_HIWORD(const uint64_t &x, const uint32_t y)
TO:
__device__ __forceinline__ uint64_t REPLACE_HIWORD(const uint64_t x, const uint32_t y)

(line 78):
FROM:
__device__ __forceinline__ uint64_t REPLACE_LOWORD(const uint64_t &x, const uint32_t y)
TO:
__device__ __forceinline__ uint64_t REPLACE_LOWORD(const uint64_t x, const uint32_t y)

Compiled and seems to be running fine.

cuda_helper.h ERRORS --

On lines 68, 78 (mentioned in your post) and lines 70, 80, and 84, there appear to be errors/typos.  I am not familiar enough with the code to fix it, but the "t2"variable is there, and it kicks up dozens of warnings at compilation time.  I have been able to compile the code with your fix, but the "t2" variable still produces warnings by the dozen.       --scryptr

what kind of warning ?
(in the first line 68, not sure t2=0 makes sense.)

DJM34--

I didn't think so, either!  In fact, I deleted "=0" and compiled again.  It compiled, as before, with dozens of ""t2" set but not used" errors.  In my first post, I used the word "defined", instead of "set", but these are continual warnings during compilation.         --scryptr

it is the compiler who is a bit confused about the asm command, because t2 initialized or not gets overwritten...
Actually I would be curious to know why the 2 lines asm has been replaced by 2 asm statement...
Same number of registers are allocated...

[sp_]

it is the compiler who is a bit confused about the asm command, because t2 initialized or not gets overwritten...
Actually I would be curious to know why the 2 lines asm has been replaced by 2 asm statement...
Same number of registers are allocated...

I have removed the warning, and everything should compile.

[chrysophylax]

it is the compiler who is a bit confused about the asm command, because t2 initialized or not gets overwritten...
Actually I would be curious to know why the 2 lines asm has been replaced by 2 asm statement...
Same number of registers are allocated...

I have removed the warning, and everything should compile.

the latest git compiles and runs well ... tanx sp ...

admittedly - i have only tested with x11 for now ... but will get quark running in the next few days after i finish a few of the rebuilds ...

#crysx

[sp_]

My 4card testrig(2x 750ti, 1x980, 1x970) is up 1MHASH with my new spreadcoin miner(standard clocks). The 750ti cards are not doing so well. Most improvements on 970 and 980 cards.

[chrysophylax]

My 4card testrig(2x 750ti, 1x980, 1x970) is up 1MHASH with my new spreadcoin miner(standard clocks). The 750ti cards are not doing so well. Most improvements on 970 and 980 cards.

thats a pity - most of my farm is 750ti oc ...

will see how it all goes anyway mate ... will be a good thing to see ...



#crysx

[jpouza]

My 4card testrig(2x 750ti, 1x980, 1x970) is up 1MHASH with my new spreadcoin miner(standard clocks). The 750ti cards are not doing so well. Most improvements on 970 and 980 cards.

That's nice,  I just loose 2x750ti and installed one 970 
The miner is up today?

[sp_]

Sending out the spreadminer v1.0 now.

I am missing 3 email adresses. If you have donated 0.1. Send me a pm with your email adress.

[sp_]

I am not finished. More exe files will follow.

[jpouza]

Sending out the spreadminer v1.0 now.

I am missing 3 email adresses. If you have donated 0.1. Send me a pm with your email adress.

I didn't receive nothing....

Sent you PM again with e-mail adress...

[jpouza]

Send me the file please, my cards are Oced and in the Water.

Cheers

[sp_]

Gmail removed the attachment. Rename the file to spreadminer1.7z and decrunch it with 7zip.