CCminer(SP-MOD) Modded GPU kernels.

[AliMan]

Again, what's up with Qubit? Lots of fuss about it recently.

Yea I don't really see it being profitable at all, DGB was the best of it, but that stopped being profitable sometime back.

this one https://bitcointalk.org/index.php?topic=1006527.0

Just took notice of this today.

[1714904657]

1714904657

[1714904657]

1714904657

[1714904657]

1714904657

[scryptr]

SP_   bmw fix build error --

Attempted to build sp_ 's latest mod (v1.5.44+, just now) and received this error:

"In file included from /usr/include/c++/4.8/cstdint:35:0,
                 from qubit/qubit_luffa512.cu:21:
/usr/include/c++/4.8/bits/c++0x_warning.h:32:2: error: #error This file requires compiler and library support for the ISO C++ 2011 standard. This support is currently experimental, and must be enabled with the -std=c++11 or -std=gnu++11 compiler options.
 #error This file requires compiler and library support for the \
  ^
make[2]: *** [qubit/qubit_luffa512.o] Error 1
make[2]: *** Waiting for unfinished jobs...."

My build platform is Ubuntu 14.04.2, and it has built all sp_ mods up to 1.5.44 succesfully.  I built with the command
"bash build.sh" within the git build directory.       --scryptr

[chrysophylax]

SP_   bmw fix build error --

Attempted to build sp_ 's latest mod (v1.5.44+, just now) and received this error:

"In file included from /usr/include/c++/4.8/cstdint:35:0,
                 from qubit/qubit_luffa512.cu:21:
/usr/include/c++/4.8/bits/c++0x_warning.h:32:2: error: #error This file requires compiler and library support for the ISO C++ 2011 standard. This support is currently experimental, and must be enabled with the -std=c++11 or -std=gnu++11 compiler options.
 #error This file requires compiler and library support for the \
  ^
make[2]: *** [qubit/qubit_luffa512.o] Error 1
make[2]: *** Waiting for unfinished jobs...."

My build platform is Ubuntu 14.04.2, and it has built all sp_ mods up to 1.5.44 succesfully.  I built with the command
"bash build.sh" within the git build directory.       --scryptr

that is strange scrptr ...

ive built it with fedora 19 x64 and it runs beautifully ...

though i do have both stdc++ and gnuc++ installed in the systems ...

#crysx

[scryptr]

SP_   bmw fix build error --

Attempted to build sp_ 's latest mod (v1.5.44+, just now) and received this error:

"In file included from /usr/include/c++/4.8/cstdint:35:0,
                 from qubit/qubit_luffa512.cu:21:
/usr/include/c++/4.8/bits/c++0x_warning.h:32:2: error: #error This file requires compiler and library support for the ISO C++ 2011 standard. This support is currently experimental, and must be enabled with the -std=c++11 or -std=gnu++11 compiler options.
 #error This file requires compiler and library support for the \
  ^
make[2]: *** [qubit/qubit_luffa512.o] Error 1
make[2]: *** Waiting for unfinished jobs...."

My build platform is Ubuntu 14.04.2, and it has built all sp_ mods up to 1.5.44 succesfully.  I built with the command
"bash build.sh" within the git build directory.       --scryptr

that is strange scrptr ...

ive built it with fedora 19 x64 and it runs beautifully ...

though i do have both stdc++ and gnuc++ installed in the systems ...

#crysx

GNUC++11  --

With "sudo apt-get install gnuc++", I installed the gnuc++ compiler.  I still get the same compile error, however, just as I quoted it above.  Do I need to edit the build.sh file, or use a command line option when running "bash build.sh"?

--scryptr

[scryptr]

SP_   bmw fix build error --

Attempted to build sp_ 's latest mod (v1.5.44+, just now) and received this error:

"In file included from /usr/include/c++/4.8/cstdint:35:0,
                 from qubit/qubit_luffa512.cu:21:
/usr/include/c++/4.8/bits/c++0x_warning.h:32:2: error: #error This file requires compiler and library support for the ISO C++ 2011 standard. This support is currently experimental, and must be enabled with the -std=c++11 or -std=gnu++11 compiler options.
 #error This file requires compiler and library support for the \
  ^
make[2]: *** [qubit/qubit_luffa512.o] Error 1
make[2]: *** Waiting for unfinished jobs...."

My build platform is Ubuntu 14.04.2, and it has built all sp_ mods up to 1.5.44 succesfully.  I built with the command
"bash build.sh" within the git build directory.       --scryptr

that is strange scrptr ...

ive built it with fedora 19 x64 and it runs beautifully ...

though i do have both stdc++ and gnuc++ installed in the systems ...

#crysx

GNUC++11  --

With "sudo apt-get install gnuc++", I installed the gnuc++ compiler.  I still get the same compile error, however, just as I quoted it above.  Do I need to edit the build.sh file, or use a command line option when running "bash build.sh"?

--scryptr

First, nuke the entire downloaded directory and use git to clone again. Edit Makefile.am, adding -std=gnu++11 to the line that reads "ccminer_CPPFLAGS = ..." - just put it anywhere after the equals sign. Then do this:

Code:

./autogen.sh
./configure --with-cuda=/path/to/cuda
make

WOLF0 --

THANKS!  But apparently, sp_ modified his "build.sh" file and re-committed to Github while we were typing here.  I re-cloned his Git and it compiled without error.  I am running his latest commit on Quark right now, it is a shade slower on my rig, about 150kh/s overall for 6x750ti FTW cards.

I will note this for later use.  Thanks again!       -scryptr

[sp_]

THANKS!  But apparently, sp_ modified his "build.sh" file and re-committed to Github while we were typing here.  I re-cloned his Git and it compiled without error.  I am running his latest commit on Quark right now, it is a shade slower on my rig, about 150kh/s overall for 6x750ti FTW cards.
I will note this for later use.  Thanks again!       -scryptr

Builds from the head of git are experimental.

Try qubit. What do you get.

Wich version are you comparing with. (44) ?

[scryptr]

THANKS!  But apparently, sp_ modified his "build.sh" file and re-committed to Github while we were typing here.  I re-cloned his Git and it compiled without error.  I am running his latest commit on Quark right now, it is a shade slower on my rig, about 150kh/s overall for 6x750ti FTW cards.
I will note this for later use.  Thanks again!       -scryptr

Builds from the head of git are experimental.

Try qubit. What do you get.

Wich version are you comparing with. (44) ?

SP_  --

I was using a post-release compilation of v44 (v44a).  This latest build runs Quark at 36500kh/s for 6x750ti FTW.  The older release ran at 36520kh/s.  After allowing the rig to run a few hours, it stabilized at the 36500kh/s speed.  I'll try Qubit again soon.       --scryptr

[sp_]

Here are the results from cryptomining-blog difference between 43 and 44 (quark /qubit) standard clocks

GTX 750 Ti
– Quark .43 – 5395 KHS
– Quark .44 – 5420 KHS
– Qubit .43 – 4319 KHS
– Qubit .44 – 4440 KHS

GTX 980
– Quark .43 – 15338 KHS
– Quark .44 – 15558 KHS
– Qubit .43 – 13771 KHS
– Qubit .44 – 14115 KHS

My tests show that the unreleased 45(working sourcecode on github) will add another 100KHASH to qubit on the 750ti. (after klaus-t's commit) (win32 windows build)

[sp_]

Yesterday I found out that the hefty 1 algo (mjolnir,heavycoin,securecoin?) is producing wrong results.
Are there any other coins that are using this algo?

If not, I will remove the support in my fork

[chrysophylax]

Yesterday I found out that the hefty 1 algo (mjolnir,heavycoin,securecoin?) is producing wrong results.
Are there any other coins that are using this algo?

If not, I will remove the support in my fork

unfortunately i do not know of any others ...

but i do have a question ... are you going to implement the spreadcoinx11 algo ( amongst some others ) in this fork as you previously mentioned? ...

tanx sp ...

#crysx

[sp_]

Yesterday I found out that the hefty 1 algo (mjolnir,heavycoin,securecoin?) is producing wrong results.
Are there any other coins that are using this algo?
If not, I will remove the support in my fork

unfortunately i do not know of any others ...
but i do have a question ... are you going to implement the spreadcoinx11 algo ( amongst some others ) in this fork as you previously mentioned? ...
tanx sp ...
#crysx

I might add scrypt-n..

Just checked, not many profitable scrypt-n coins out there..

Spreadcoin is still only for the donators. New version is coming soon with more hash.

[antonio8]

Yesterday I found out that the hefty 1 algo (mjolnir,heavycoin,securecoin?) is producing wrong results.
Are there any other coins that are using this algo?
If not, I will remove the support in my fork

unfortunately i do not know of any others ...
but i do have a question ... are you going to implement the spreadcoinx11 algo ( amongst some others ) in this fork as you previously mentioned? ...
tanx sp ...
#crysx

I might add scrypt-n..

Just checked, not many profitable scrypt-n coins out there..

Spreadcoin is still only for the donators. New version is coming soon with more hash.

So are you still vacationing is the big question.

[chrysophylax]

Yesterday I found out that the hefty 1 algo (mjolnir,heavycoin,securecoin?) is producing wrong results.
Are there any other coins that are using this algo?
If not, I will remove the support in my fork

unfortunately i do not know of any others ...
but i do have a question ... are you going to implement the spreadcoinx11 algo ( amongst some others ) in this fork as you previously mentioned? ...
tanx sp ...
#crysx

I might add scrypt-n..

Just checked, not many profitable scrypt-n coins out there..

Spreadcoin is still only for the donators. New version is coming soon with more hash.

tanx sp ...

we are one of the donors ...

but i thought i would ask due to it being a pain in the backside to continue changing miners on EVERY worker in the farm when we want to mine sprx11 ...

would be so much easier if it was within the one miner ...

tanx again ...

#crysx

[sp_]

So are you still vacationing is the big question.

No I am back. But busy at work.

I have some hours every evening and the weekends when the wheater is bad.

I think I will add Skein. Mining digibyte(skein) seems to be profitable.

[rednoW]

sp_

I confirm that built from your github source pre-release 45 gives 4540khs instead of the best previous 4418khs of r43.
R44 was no good for me except whirpool and x15.
Quark seems to be very close to R43 record 5717khs but R43 still better for quark

oced 750non-ti 1gb,

comparing v43 vs. v44 for my gtx750(non-ti) (windows binaries from github)
x15: 1966 vs 1976
x13: 2272 vs 2270
x11: 2886 vs 2883
quark: 5700 vs 5660
qubit: 4418 vs 4419 (with drops)
lyra: 882 vs 881

So, only x15 gain for me

[Grim]

I might add scrypt-n..

Just checked, not many profitable scrypt-n coins out there..

If scrypt-n can be optimized by you to run faster on higher vram cards I'll donate 0.3 btc right away 

[totoy]

Yesterday I found out that the hefty 1 algo (mjolnir,heavycoin,securecoin?) is producing wrong results.
Are there any other coins that are using this algo?

If not, I will remove the support in my fork

I only know one using hefty1, few miners though https://bitcointalk.org/index.php?topic=1006784.0

[sp_]

Added skeincoin from the tpruvot branch.

Didn't do many changes yet, so the speed should be around the same. (50-52MHASH on the standard 750ti)

[sp_]

Submitted a 10% increase in skeincoin.

The change was done in the sha-256 implementation

-Reduced register usage by moving constants from constmem to the instruction   cache
-bether launch configuration
-bether default intensity

[sp_]

I might add scrypt-n..
Just checked, not many profitable scrypt-n coins out there..

If scrypt-n can be optimized by you to run faster on higher vram cards I'll donate 0.3 btc right away 

I have managed to optimize all the hashing functions available in ccminer (20 algorithms?) 
Some of the algos just a few percent, and some of them more


I belive I can do scrypt-n as well.