flat assembler
Message board for the users of flat assembler.
Index
> Macroinstructions > Performance Counter V2.1.3 [x86-64]+[x86] |
Author |
|
Inagawa 08 Jun 2012, 15:42
Well hello, I'd like to present the thing I have been working on since the release of the last 32bit PFC - the 64bit version.
This version is far superior to the old one in that it has an actual GUI, the ability to run sequential tests without recompilation and automatic file creation with the results. The best part? It's still a macro. The code has extensive comments, making it easy to navigate and to understand. The files are saved in the project directory (i.e. where the executable is), with a name pattern as follows: 'PerformanceReport_(yyyy-MM-dd)_(HH-mm).txt'. Now, the GUI is still on the main thread, which means that the GUI is unresponsive if a test is being run. It's a setback, but I consider it to be a minor shortcoming - there's nothing that interesting you can do when a test is in progress anyway. Also, you can no longer set the priority class. I doubt anyone used it anyway (It's still changeable via the code, all you need is still there). I can add it on request. This has taken me very long to create, so I hope you like it and in any case, I'd be happy to get at least some feedback. Version 2.1.3: - Now in x86 and x86-64 Version 2.1.2: - Register preservation Version 2.1.1: - Fixed a problem with creating a file, I accidentally broke it in 2.1.0 update. Version 2.1.0: - I have made additional changes that make this macro very reliable. The results are now as accurate as possible.
Last edited by Inagawa on 14 Jun 2012, 20:20; edited 22 times in total |
|||||||||||||||||||||
08 Jun 2012, 15:42 |
|
AsmGuru62 08 Jun 2012, 16:16
Good stuff!
Can it measure any code sequence? How do I tell it what sequence to measure? |
|||
08 Jun 2012, 16:16 |
|
Inagawa 08 Jun 2012, 17:17
Yes, it measures anything that RDTSC can, that you put between StartPerformanceCounter and EndPerformanceCounter, the rest is set in the GUI.
|
|||
08 Jun 2012, 17:17 |
|
JohnFound 08 Jun 2012, 17:47
Very good tool. I think now how to use it in Fresh IDE. The idea is to select the code snippet in the editor and click on "Measure performance" button in order to run your tool.
|
|||
08 Jun 2012, 17:47 |
|
Inagawa 08 Jun 2012, 18:57
Thanks for the praise, I have fixed the file saving now. Having it in Fresh IDE would be really cool btw!
|
|||
08 Jun 2012, 18:57 |
|
AsmGuru62 08 Jun 2012, 19:41
So, to measure a piece of code, I need to put it between calls and RE-COMPILE the GUI?
Can it be done with no recompiling? |
|||
08 Jun 2012, 19:41 |
|
Inagawa 08 Jun 2012, 19:48
Ah, I see what you mean. The first test needs compiling, the sequential tests, i.e. different amounts of loops/passes do not. I should've made myself more clear.
Edit: I don't know, can it? |
|||
08 Jun 2012, 19:48 |
|
AsmGuru62 08 Jun 2012, 21:44
It would have been nice to have an internal assembler there.
User types some code and assembler makes a binary piece from the sequence. Then you call that piece in between calls to Start/End and get results. That is too complex, however, but may be useful for CPU research. The assembler does not need a full blown abilities, just a sequence of few commands. I know, ... challenging ... |
|||
08 Jun 2012, 21:44 |
|
Inagawa 14 Jun 2012, 18:41
Now also in 32 bit.
|
|||
14 Jun 2012, 18:41 |
|
< Last Thread | Next Thread > |
Forum Rules:
|
Copyright © 1999-2024, Tomasz Grysztar. Also on GitHub, YouTube.
Website powered by rwasa.