What are you using clock_t for in y-cruncher? :o At least the clock in ctime.h is useless for anything precise.
What are you using clock_t for in y-cruncher? :o At least the clock in ctime.h is useless for anything precise.
It uses it as part of the timer-hack detection. For all other purposes, it uses the performance counter - which is more accurate than ctime.h.
EDIT:
The Sanity Check Error is just a flag that comes out if the program thinks the clock has been tampered with. It's only purpose is in competitive benchmarking - which is irrelevant to this run.
So in the case of the overflow after 24.8 days, it wraps around - which has the same effect of setting the clock back 24.8 days (several times within a 90 day period).
Last edited by poke349; 08-04-2010 at 09:17 AM.
Main Machine:
AMD FX8350 @ stock --- 16 GB DDR3 @ 1333 MHz --- Asus M5A99FX Pro R2.0 --- 2.0 TB Seagate
Miscellaneous Workstations for Code-Testing:
Intel Core i7 4770K @ 4.0 GHz --- 32 GB DDR3 @ 1866 MHz --- Asus Z87-Plus --- 1.5 TB (boot) --- 4 x 1 TB + 4 x 2 TB (swap)
Bookmarks