search

guagua-pamcn / a-dda

Automatically exported from code.google.com/p/a-dda
0 stars 0 forks source link

Overflow of clock #43

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Try to avoid overflow of 'clock' function when run in a sequential mode.

Original issue reported on code.google.com by yurkin on 24 Dec 2008 at 7:24

GoogleCodeExporter commented 8 years ago 
Most probably, this should not be a problem in 64-bit environment, since then 
upper
limit for clock_t is practically unreachable. At least in many implementations,
clock_t is defined as long, so LP64 data model should help.

For 32-bit the problem still persists (more than 2 hours run times are wrong), 
but it
is only low-priority to fix this.

Original comment by yurkin on 9 Apr 2009 at 4:10

GoogleCodeExporter commented 8 years ago 
Since 32-bit systems become obsolete, I am closing this issues. Anyway ADDA 
always produces accurate wall time for the whole run, which is sufficient for 
most applications.

Original comment by yurkin on 16 Apr 2012 at 9:29

GoogleCodeExporter commented 8 years ago 
Moreover, r1308 added a test, which will produce a warning if overflow has 
(probably) occurred.

Original comment by yurkin on 16 Feb 2014 at 4:45