Do you plan to release one for Cryptonight algorithm?
cpuminer already has cryptonight built in but I haven't looked at it yet. it's the code as tpruvot's version.
I wanted to get the first version out quickly to implement the available optimizations.
Give cryptonight it a try and let me know how it goes.
I did the original CN code - I kinda doubt it's getting much faster...
Open or private?
Both. It's open now.
Where can I get it? I've already given you credits in the startup header.
My github... I think. Let me look.
Yup:
https://github.com/wolf9466/cpuminer-multiLooks good based on the file name (aesni in it). I'll investigate and if faster and with your
permission I'll add it to my fork, with credit.
I don't have any wallets for this algo so I can mine to your adress while testing. It probaby
won't be a lot but I'll let it run for a bit.
I'm pretty tied up right now, more hash coming for the big 4 and I'm still trying to workaround
macros causing multiple def errors on link. I think I'm getting there, I converted them all to inline
functions, cloned them and gave the clones unique names. I can't help thinking there is a better
way because of my inexperience withc/c++.
I don't know if an inline function is as fast as a macro, it should be, all the work is at compile time.
Which leads me to a question. Using functions means I have to access the context struct members using
'->' instead of '.'. This says to me there is an added level of indirection. Does this also apply to inline
functions or is the compiler smart enough to optimize it out and code it like it was a ',' as it would be
if the code was truly inline?
It will be interesting to see if there is a penalty in converting to inliners as well as dealing with struct*
instead of struct. On the bright side splitting everything up into the standard init, update & close functions
allows me to take the init out of the loop.
Edit: I'm stumped about these multi defs. I must be missing something fundamental. I think I'll drop it for
now. I think I can get a little more out of aesni. After I release that I'll take a look at your cryptonight.
It looks like it's using some slower sub-algos so I should be able to improve on it.
Compiler errors with Groestl? Yeah, you're gonna kick yourself when you figure out why. I had to take a bit more than a cursory look at that optimized Groestl before I saw it.
