ZEsarUX beta 5.1
Re: ZEsarUX beta 5.1
An old request but that I hope to see realized sooner or later (or I'll try myself when I'll complete all debugging and enhancements setup): is possible to have a flag to write a profile dump file?
To explain better:
It would be really useful to understand which part of the program is executed the most in order to optimize it the most. I think this is quite general.
A simple counter of number of instruction fetched at instruction level would be enough. A more elaborate way would be to add (not substitute) also the T-States spent, but this is really not so important since if you look well it's enough clear, even if there are instruction with T-States that depends on operands.
It can be a simple array of 64K long integers, initialized to 0 at the beginning, with cells incremented during instruction fetch, and simply written to a text file at the program exit.
Cesar, what do you think about it?
To explain better:
It would be really useful to understand which part of the program is executed the most in order to optimize it the most. I think this is quite general.
A simple counter of number of instruction fetched at instruction level would be enough. A more elaborate way would be to add (not substitute) also the T-States spent, but this is really not so important since if you look well it's enough clear, even if there are instruction with T-States that depends on operands.
It can be a simple array of 64K long integers, initialized to 0 at the beginning, with cells incremented during instruction fetch, and simply written to a text file at the program exit.
Cesar, what do you think about it?
- chernandezba
- Posts: 176
- Joined: Tue Mar 11, 2014 4:30 pm
Re: ZEsarUX beta 5.1
Try Cpu transaction log (on debug menu)

- chernandezba
- Posts: 176
- Joined: Tue Mar 11, 2014 4:30 pm
Re: ZEsarUX beta 5.1
Sorry I don’t understand what is this trace file about
Re: ZEsarUX beta 5.1
I already did, time ago, but the result was a file of many gigabystes even for a very small computation, and it has to be post-processed to arrive to the identification of the number of execution of each instruction!...
Anyway it is surely a good candidate place for the change!

Re: ZEsarUX beta 5.1
The trace on port $35 / $53 !chernandezba wrote: ↑Sun Oct 22, 2017 12:18 pmSorry I don’t understand what is this trace file about

- chernandezba
- Posts: 176
- Joined: Tue Mar 11, 2014 4:30 pm
Re: ZEsarUX beta 5.1
Hi
This is an old thread but I want to follow it as I have added ZEsarUX hardware debug ports for ZX80/81

I have chosen these ports 35H/53H for register/value ports, and I have added a new register port (6) to output a byte to a file. The file must be chosen from settings->debug->byte file setting
This is documented here:
https://github.com/chernandezba/zesarux ... isters.txt
And I have created a simple ZX81 test program to do the outs:
https://github.com/chernandezba/zesarux ... xi-ports.p
These two files are (of course) included on the ZEsarUX source code.
To test it, you must compile from sources or wait to the next beta or stable ZEsarUX build.
I hope this will be useful for you (and others)

Regards
Cesar
Re: ZEsarUX beta 5.1
Wow, you really "expanded" the concept, nice!!!
)

- chernandezba
- Posts: 176
- Joined: Tue Mar 11, 2014 4:30 pm