CCminer(SP-MOD) Modded GPU kernels.

[induktor]

ccminer.cpp: In function ‘void* miner_thread(void*)’:
ccminer.cpp:1852:12: error: ‘Sleep’ was not declared in this scope
     Sleep(1);
            ^
Makefile:1836: recipe for target 'ccminer-ccminer.o' failed





linux not compile  on ubuntu

Replace Sleep with usleep
I made a pull request to fix this but for some reason sp didn't want to merge it.

Worked!, Thanks! 

[sp_]

fixed@git

[blackline]

linux still not compile not work

[sp_]

Whats the error message?

[blackline]

ccminer.cpp: In function ‘void* miner_thread(void*)’:
ccminer.cpp:1852:12: error: ‘Sleep’ was not declared in this scope
     Sleep(1);
            ^
Makefile:1836: recipe for target 'ccminer-ccminer.o' failed


saying that

[blackline]

ccminer.cpp: In function ‘void* miner_thread(void*)’:
ccminer.cpp:1852:12: error: ‘Sleep’ was not declared in this scope
     Sleep(1);
            ^
Makefile:1836: recipe for target 'ccminer-ccminer.o' failed
make[2]: *** [ccminer-ccminer.o] Error 1
make[2]: *** Waiting for unfinished jobs....
mv -f .deps/ccminer-pools.Tpo .deps/ccminer-pools.Po
mv -f .deps/ccminer-hefty1.Tpo .deps/ccminer-hefty1.Po
mv -f .deps/ccminer-util.Tpo .deps/ccminer-util.Po
make[2]: Leaving directory '/home/m1/miners/suprminer-spmod-git10'
Makefile:2262: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/m1/miners/suprminer-spmod-git10'
Makefile:680: recipe for target 'all' failed
make: *** [all] Error 2



not compline Error here all

[jugger1028]

Lol, you're so angry... That's some big madz.. Ok, I'll stop making fun of you, go put your nose back in his ass and close your eyes. It'll all go away...

PLEASE LEAVE THE THREAD--

Your obscene remarks are unwelcome.       --scryptr

Lol, dude, get a life..

[bensam1231]

I was wrong, Chinese miners are still jacking hashrate while price of crypto was declining. So even though we're at basically the same price as a month ago, we're making quite a bit less. It looks like we'll go negative at $.1kwh around 6k~. You can't compete with do or die attitudes. Chinese are too industrious and too stupid to know when to start dialing things back, so we get to ride this into the ground with them. That mixed with the dark hashrate is going to make this even worse as when BTC starts climbing again it wont matter as people will flip on their rigs so we'll be left in limbo for quite some time.

There is a inordinate amount of FPGAs floating around as well. From my experience with niche algos it seems any thing that can be mined with a FPGA is currently being. It's like the new ASIC. If coin makers care about their coin and GPU users they should consider hardening them against FPGAs. Ideally GPU mineable coins should be a moving target with algo adjustments on a regular basis as no one is doing this currently.

I've been in quite a few niche markets and they're all showing similar signs. It's like back in '14 when scrypt asics started showing up. I'm sure the Chinese are fucking things, but it's not just that, considering the decline in GPU shipments according to makers we shouldn't be seeing this much growth in GPU hashrate. It wouldn't be far fetched to assume custom ASICs similar to baikals that can mine multiple algos as well. GPUs are basically big ASICs. A couple of the coins I've mined have had legitimate operations show up and start advertising their 'cloud' mining service, which wasn't just one coin, and they weren't using GPUs.

That aside, the 2XXX series and Eth fork couldn't happen at a worse time.

Lol, you're so angry... That's some big madz.. Ok, I'll stop making fun of you, go put your nose back in his ass and close your eyes. It'll all go away...

PLEASE LEAVE THE THREAD--

Your obscene remarks are unwelcome.       --scryptr

Lol, dude, get a life..

Go take your bruised ego else where. Stop into your locally owned store and start talking shit there to kill time. No? Guess there are limitations to being spoiled.

[sp_]

Submitted a 10% faster fugue implementation @github. Using the same tricks as in my opensource echo implementation with 8 copies of the mixtab table in sharedmem to avoid bank conflicts.

[sp_]

submitted a 40% faster whirlpool80 @github / +6% whirlpool

[sp_]

X16r/X16s/C11/x17 Spmod-git #11 has been released

- Added support for X17 (+10-15% faster than the ccminer alexis 1.0 opensource fork) (24-25MHASH on the 1080ti)
- Faster x16r/x16s +3-5% more than sp-mod #10 (Optimalizations added to Fugue, whirlpool)

this miner is free, opensource, and have no fee

cuda 9.2 builds:

https://github.com/sp-hash/suprminer/releases

sourcecode:

https://github.com/sp-hash/suprminer/commits/master

[Dr_Victor]

X16r/X16s/C11/x17 Spmod-git #11 has been released

- Added support for X17 (+10-15% faster than the ccminer alexis 1.0 opensource fork) (24-25MHASH on the 1080ti)
- Faster x16r/x16s +3-5% more than sp-mod #10 (Optimalizations added to Fugue, whirlpool)

this miner is free, opensource, and have no fee

cuda 9.2 builds:

https://github.com/sp-hash/suprminer/releases

sourcecode:

https://github.com/sp-hash/suprminer/commits/master

Your free product will not allow t-rex, Cryptodredge and Enemy sleep. Definitely we will see their new versions in a few days.

[Mr.Spider703]

X16r/X16s/C11/x17 Spmod-git #11 has been released

- Added support for X17 (+10-15% faster than the ccminer alexis 1.0 opensource fork) (24-25MHASH on the 1080ti)
- Faster x16r/x16s +3-5% more than sp-mod #10 (Optimalizations added to Fugue, whirlpool)

this miner is free, opensource, and have no fee

cuda 9.2 builds:

https://github.com/sp-hash/suprminer/releases

sourcecode:

https://github.com/sp-hash/suprminer/commits/master

Your free product will not allow t-rex, Cryptodredge and Enemy sleep. Definitely we will see their new versions in a few days.

If see for time, SP_ late with the release of the new miner, z-enemy first, T-Rex second

[sp_]

If see for time, SP_ late with the release of the new miner, z-enemy first, T-Rex second

My miner is not new, and my miner is the fastest opensource by far in the following algos. C11/X16R/X16S/X17

[Mr.Spider703]

If see for time, SP_ late with the release of the new miner, z-enemy first, T-Rex second

My miner is not new, and my miner is the fastest opensource by far in the following algos. C11/X16R/X16S/X17

If you compare the income by coins, z-enemy wins 10-12% Net income of z-enemy miner
if see on pool your miner almost no one uses it

[Amph]

any speed test for the 2080?

[sp_]

z-enemy wins 10-12% Net income of z-enemy miner

My opensource is improving and is now running at the same speed as the enemy miner did a few weeks ago.
Every algo has a limit, and the competition can't add 10-15% a week forever.

[jmumich]

z-enemy wins 10-12% Net income of z-enemy miner

My opensource is improving and is now running at the same speed as the enemy miner did a few weeks ago.
Every algo has a limit, and the competition can't add 10-15% a week forever.

Thanks - your contributions have made it easier for even a relative novice to make further modifications to the code and come out (slightly) ahead of enemy and trex, even before their fees.

I've bought a couple mods from you - and been rejected when I asked for a discount on multiple, oh well, but I do have to say that your contributions have been very valuable, and make me more willing to pay full price in the future if it makes sense.

[jugger1028]

z-enemy wins 10-12% Net income of z-enemy miner

My opensource is improving and is now running at the same speed as the enemy miner did a few weeks ago.
Every algo has a limit, and the competition can't add 10-15% a week forever.

Thanks - your contributions have made it easier for even a relative novice to make further modifications to the code and come out (slightly) ahead of enemy and trex, even before their fees.

I've bought a couple mods from you - and been rejected when I asked for a discount on multiple, oh well, but I do have to say that your contributions have been very valuable, and make me more willing to pay full price in the future if it makes sense.

Are you saying you've taken SP's x16r free miner and have modified it to make it faster than Z-enemy's miner? As for his contribution, I agree, he has contributed a lot towards the development of good miners, regardless of whether I agree with his fee schedule or not.

[sp_]

Pushed a 20% faster shavite_final implementation to github. Another #include "cuda_x11_aes_sp.cuh" modification...

The sp-modded Optimized AES has been applied to the following hashing functions.

echo  (done)
fugue (done)
shavite (only the final function / if shavite is the last algo in the chain)
whirlpool(not done)
streborg(not done)