Quote from: Amph on July 05, 2016, 12:57:45 PM

Quote from: pallas on July 05, 2016, 12:17:47 PM

Quote from: Amph on July 05, 2016, 12:08:00 PM

yeah sp is mia, he said he don't want to continue this, you should make your own thread Pallas, from what i understood you are a coder also, or maybe you have one already

No, I don't have a thread for "ccminer", even though I worked on it for more than a year now.
I've submitted some improvements and made some private work.
I may fork sp's ccminer and continue from there BUT:

- the code base is outdated, we should start from latest tpruvot's; but then it would make more sense to submit to his own fork directly (I did that too).
- sp_ said he might eventually post his optimisations on a newer codebase so I didn't want to do a duplicate work.
- applying all sp_'s optimisations to tpruvot's is no easy nor quick task; it might take months.
- some of the optimisations are on dead or almost dead algos; it might be better to restart from scratch... don't know.

last time i checked some tpruvot algo were not running at the same optimized hash of sp last version(not talking about private) like qubit and akin

i think it's better to fork from sp(so you get all the boost already), but if he will do it later at some point, then maybe we can just wait, but not sure his last message leave much to be desired...

Hell no. I ported pool management from trupvot's in my private fork. And that wasn't an easy job.
From the other side: no matter what you will choose as main codebase, this will take a lot of time in both cases. Just in my opinion: port from sp to trupvot's will be easier.