-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Profiling cpu and hardware registers. #78
Comments
I'm currently not capturing the registers for each cycle, probably quite a bit of data. But I'll see what I can do.
I'm not actually storing the custom registers in the capture, but recreate them based on the DMA writes.. Have to think about this some more.
I guess that's possible. I'm currently quite busy preparing the next vscode-amiga-debug seminar, so I can have a look at these improvements in November at the earliest. |
Understood! Maybe there is a subset of readable hardware registers worth recording without inflating the capture too much. Hopefully that seminar will be broadcast or release shortly after! I've really loved using this system and the improvements! |
Yes, as far as I understand it the seminar will be streamed. |
In case you missed it, here's a recording of my seminar about all the new features |
I did see your video and it was great! I hadn't realized the assembler output in the profile had those real world timings, so that'll be really nice to check when really getting down to some serious optimizing. |
Would it be possible to add the cpu registers to the profiler view so you can watch them change as the code in the assembly window changes?
Would it be possible to include changes to readable hardware registers, things like vposr/intenar/intreqr/dmaconr? Currently I only see vposw/intena/intreq/dmacon and they only update when written to (unsurprisingly). This would help debugging since you'd be able to see them change as you scrub the profile slider.
On a similar note is it possible to show the hardware registers inside the gdb debugger along with the existing cpu registers?
The text was updated successfully, but these errors were encountered: