The New Asm's mhz.ex
- Posted by xerox_irs at lvcm.com May 23, 2003
- 383 views
This is a multi-part message in MIME format. ------=_NextPart_000_0005_01C320A7.0979A460 charset="iso-8859-1" Well this is actually an old problem, and I just never reported = it(sorry) because I could fix it in a half-second. In the mhz.ex, the = reading is inaccurate, it reports 167ish for my 700mhz, thats because = over the course of 5 seconds, it generate about 3.5 billion ticks, and = if it is just a slite tad faster, say generating 4.167 billion tick, = well it drops off the '4' (cause 4billion is bigger than 32bit) or the = amount (cyclemark2-cyclemark1) may be negetive leading me to believe it = generates 4bill - 167mill. Either way it either needs the full 64bit number,(which you can do as = there are mmx instructions on most comps with rdtsc) or shorten the time = of five seconds, so it doen't overflow, but yes this does decrease the = accuracy. This is a little tiny problem, not worth mentioning though, so its not a = huge priority. But it may take a massive amount of effort to correct = this(ie changing the 5 to a 1 or 2 in one place). Thanks for the library Daniel Kluss ------=_NextPart_000_0005_01C320A7.0979A460 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Diso-8859-1"> <META content=3D"MSHTML 6.00.2800.1170" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT face=3DArial size=3D2>Well this is actually an old problem, = and I just=20 never reported it(sorry) because I could fix it in a half-second. In the = mhz.ex,=20 the reading is inaccurate, it reports 167ish for my 700mhz, thats = because over=20 the course of 5 seconds, it generate about 3.5 billion ticks, and if it = is just=20 a slite tad faster, say generating 4.167 billion tick, well it = drops off=20 the '4' (cause 4billion is bigger than 32bit) or the amount=20 (cyclemark2-cyclemark1) may be negetive leading me to believe it = generates 4bill=20 - 167mill.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Either way it either needs the full = 64bit=20 number,(which you can do as there are mmx instructions on most comps = with rdtsc)=20 or shorten the time of five seconds, so it doen't overflow, but yes this = does=20 decrease the accuracy.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>This is a little tiny problem, not = worth mentioning=20 though, so its not a huge priority. But it may take a massive amount of = effort=20 to correct this(ie changing the 5 to a 1 or 2 in one = place).</FONT></DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2>Thanks for the library</FONT></DIV> ------=_NextPart_000_0005_01C320A7.0979A460--