Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
an instruction counting program 1
- Thread starter skata
- Start date
-
1
- #2
lionelhill
Technical User
I think you are looking for a profiler.
To be honest, the number of instructions executed is not especially interesting. Some instructions are preposterously slow compared to others, and most users are more interested in total execution time. What you probably need to know is how long your program is spending in its various functions?? (one obvious example: an op-code like rep movs can loop internally and move a massive chunk of memory in one go. It takes time, but it achieves the work of a lot of individual instructions).
It would, however, be fairly easy simply to count instructions. The 086 processors have a bit in their flag register called the trap bit, and if set, a particular interrupt is called after every single instruction. I don't know exactly how it behaves in protected mode. In old-fashioned 16-bit mode it used to be used by debuggers, because they could recover control after each instruction exectuted by another program. To count instructions you'd simply let the interrupt handler increment a counter each time the interrupt is called, before passing control back to the "counted" program.
To be honest, the number of instructions executed is not especially interesting. Some instructions are preposterously slow compared to others, and most users are more interested in total execution time. What you probably need to know is how long your program is spending in its various functions?? (one obvious example: an op-code like rep movs can loop internally and move a massive chunk of memory in one go. It takes time, but it achieves the work of a lot of individual instructions).
It would, however, be fairly easy simply to count instructions. The 086 processors have a bit in their flag register called the trap bit, and if set, a particular interrupt is called after every single instruction. I don't know exactly how it behaves in protected mode. In old-fashioned 16-bit mode it used to be used by debuggers, because they could recover control after each instruction exectuted by another program. To count instructions you'd simply let the interrupt handler increment a counter each time the interrupt is called, before passing control back to the "counted" program.
- Thread starter
- #3
- Status
Similar threads