@SolidStateSurvivor
i suck at c/c++ even though i have been at over 10+ years.. prob is i am bad at math
anyway, i have done a lot and the more i do the more bugs i find etc etc
i fixed a bug that caused a race condition outputting the date/time..
it would get put out twice in a row before the log line.. i thought i fixed that issue last year lol
to fix it, the thread mutex lock should be started and stopped once.. not twice
i also thought i'd like the idea of another cmd-line to not show the date/time, i tried it (by accident) and it was ok.. i'd used it.
i'm really thinking that no matter what i do to the hashing algo it's just making things worse, as in some kind of cheat crap (based on pool data)
so i will leave in my last and best revision of it and advise people use the non cheat one..
USE the normal one preferably people unless you want to TEST.
i do think i will put scanhash() back and do separate functions for them based on the cheat cmd-line that should be faster code.
i've found some miner tweaks here and there too (in the hashing code)
i have added a lot more window data updated every 5 seconds and tweaked the averaging code
and i also think an alternative hashing speed log line showing the combined hash speed vs the per thread way it is now would be cool.
still didn't do multi-pool support yet or the 32bit windows VS2010 profiles/configs.. they are almost done lol
but i was just testing the final hashing now and it's fast and good as i can get it unless i go with UncleBob's style of algo's (which is faster)
but if i do that Visual Studio and x64 won't compile it doesn't support asm for 64bit so i think it's good enough (and unlce bob used asm)
i just tested both VS2010 and MingW x64 builds normal hashing algo and i get average i think* 490kh/s (VS2010) and 500kh/s (gcc) using 6 threads on my i7 4770k (75% usage)
So since both are so close in speed i don't see any reason to break Visual studio support now that i added it and got it going perfect with no warnings
It's nice to be able to code and build / test in VS2010, then do a MingW build later when the code is final for that extra bit of speed..
so far i got the window title looking like this BELOW (updated every 5 seconds with average hash rate speeds) not sure how well that will work out on Linux though lol
CMA | v5.1.0.5 | t=6 | a=Jackpot | s=5 | z=false [500 kh/s]
oh yeah and i added resource data to the windows build when compiling with VS2010 for viewing properties on Windows ..and prob more stuff i can't remember hahaa
