hmmm interesting and thanks for the feedback i wondered before if that would be a problem eh
i didn't think it would since i have been building on MingW and MingW64,
it would be a little bit of work to get rid of the colors but i'll look into it and see what i can do..
i have tried to keep it Linux + Windows eh even though i am mostly into windows coding and don't have any Linux distribs running for testing at the moment.
i was just trying to get it running on visual studio 2010 but got almost done and got some old errors and got tired of doing it.. some other time lol
also x86 / 32bit is working but all optimization flags i try with MingW seem to be a hell of a lot slower than the 64bit counterpart builds for some odd reason.
in the last year i have started over making a cpu miner mod using chunks of hashing algo's from other mods
but i am getting tired of starting over again and hope to just stick with this one and port new coins to this one and only this one now.
got some good features planned and coming and already did some..
right now i am testing out having the average hash rate shown in the window title every 5 seconds
Note: currently as *always the colored hash lines in the console show the fastest (submitted good share) hash rate.
So i was thinking it would be good to see what the average hash rate is going on in the background if using the quiet cmd-line..
i always run in quiet mode eh..
Also detected new block messages are normally suppressed as well as debug reject reason in quiet mode but i enabled them for a good reason..
If someone is getting a lot of bad shares and the reason they see is because it says "Job Not Found"
people really may want to consider tuning their scan time (probably lower)
although i have considered adding a cmd-line option to hide the "new block" msg's..
i also added some color and fixed up the benchmark code a bit.. it should be a lot better soon.
and i also added a cmd-line to enable cheat mode testing so no more multiple builds needed..
i think i did a ton of other crap too i forget and will have to compare the files before i do a changelog update again lol
it's a lot of screwing around cleaning up the source code folder and putting together a new packages of builds eh
but of someone wants the build i am currently running for haswell or SSE2 or SSE4 just say so and i can upload just that one .exe pretty damn fast lol
so far the only way i know to build for x86 / 32bit windows is to re-compile the LibCurl install and that is a big time consuming pain the ass
i want to see later if there is some way i can have both compiled and installed setup so i just have to configure again in the mod folder only..
it means i am coding with x64 so i have to delete everything and rebuild for x86 then i have to rebuild it back to x64 again..
and even on a fast machine LibCurl takes time
i have a sick fast SSD (Samsung 840 EVO 256GB SSD Sata III) and my 4770k cpu only uses like 10% when compiling but it still takes a while lol
edit: i also am using G.SKILL Trident X Series 16GB (2 x 8GB) DDR3 2400 - Memory i paid good money for running with xmp profile at 2400mhz
a couple things i want to add..
- Multi pool fall back support (i can pretty much copy and past it from cudaminer)
- Diff modifier via cmd-line (same i can get it from cudaminer or an sgminer mod) so far i have been hard coding values for testing in the last year.
- more hash stats in console window.. i was thinking of maybe something like this... CMA v5.5.5.5 [current% kh/s] [avg% kh/s] [highest% kh/s]
currently i am seeing a 5 second polled avg but i wrote the code and never did that before and i am not sure what i am doing lol
i had gettimeofday() start in Main then in MinerThread at the end i had it check if time has been 5 seconds and if so update the console window
and then start a new timer basically..
but what i am not sure of is what i should use to average it out..
i have tried 2 or 3 variables combined..
avg = (lowest_hash + hashrate) /2;
or
avg = (lowest_hash + hashrate + highest_hashrate) /3;
edit:
i tried also,
avg = (lowest_hash + highest_hashrate) /2;
but that seemed the most out of whack out of the three averaging strategies i can think of..