invoke ticcount
invoke wsprintf, ADDR buftime, ADDR szformat, eax
invoke MessageBox,0,ADDR buftime, ADDR mytitle,MB_OK
invoke ExitProcess, 0


I ran across this RDSTC opcode would it be better to use it instead of the above &
which would save processor time. Want to use it for timing the speed of graphics movements from start to finish. Or is there a faster way to time it

your thoughts are greatly appriecated thanks in advance:alright:
Posted on 2003-07-12 22:16:43 by Tweak
I think RDTSC can be used only in ring0
Posted on 2003-07-13 02:26:50 by greenant
that's not true. i wrote an app using rdtsc causing no faults.

save processor time with a messagebox?

use it like this:


rdtsc
mov [tmpval],eax

;your code to test

rdtsc
sub eax,[tmpval]

;print the value eax somewhere
Posted on 2003-07-13 03:41:04 by hartyl
You are right. The old msdos with emm386 created problem but win2k is ok
Posted on 2003-07-13 07:11:36 by greenant
Posted on 2003-07-13 09:07:58 by Ratch
Check this link for informations, if is possible to use RDTSC without generating #UD (undefined opcode) under all of Windows:

http://spasm.servehttp.com/SpAsm/viewtopic.php?t=480

In a short cut, resume is there is possible to use RDTSC without problems. The best would be set up your own SEH for trap fault #UD.
Posted on 2003-07-13 11:21:07 by MazeGen