Skip to content
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

Atomic instruction execution #40

Open
kremi151 opened this issue Nov 14, 2020 · 0 comments
Open

Atomic instruction execution #40

kremi151 opened this issue Nov 14, 2020 · 0 comments
Assignees
Labels
enhancement New feature or request on hold On hold for the time being

Comments

@kremi151
Copy link
Owner

Currently instructions are split up into several operands, where one operand is executed at a time.
This was implemented to have emulation that's closer to how the real hardware executes code.
But this comes with some performance overhead, e.g. the 3DS and Android implementations suffer from slow emulation.
One way to mitigate this is to switch back to atomic instructions, i.e. executing directly an entire instruction at a time. When upating the internal system clock correctly, this won't cause any issue as the end result will be the same, with improved performance.

@kremi151 kremi151 added the enhancement New feature or request label Nov 14, 2020
@kremi151 kremi151 self-assigned this Nov 14, 2020
kremi151 added a commit that referenced this issue Nov 16, 2020
kremi151 added a commit that referenced this issue Nov 16, 2020
kremi151 added a commit that referenced this issue Nov 18, 2020
kremi151 added a commit that referenced this issue Nov 18, 2020
kremi151 added a commit that referenced this issue Nov 18, 2020
kremi151 added a commit that referenced this issue Nov 18, 2020
kremi151 added a commit that referenced this issue Nov 18, 2020
kremi151 added a commit that referenced this issue Nov 18, 2020
kremi151 added a commit that referenced this issue Nov 18, 2020
kremi151 added a commit that referenced this issue Nov 18, 2020
kremi151 added a commit that referenced this issue Nov 30, 2020
kremi151 added a commit that referenced this issue Dec 3, 2020
kremi151 added a commit that referenced this issue Dec 4, 2020
kremi151 added a commit that referenced this issue Dec 4, 2020
kremi151 added a commit that referenced this issue Dec 4, 2020
kremi151 added a commit that referenced this issue Dec 4, 2020
kremi151 added a commit that referenced this issue Dec 4, 2020
kremi151 added a commit that referenced this issue Dec 5, 2020
kremi151 added a commit that referenced this issue Dec 5, 2020
kremi151 added a commit that referenced this issue Dec 5, 2020
kremi151 added a commit that referenced this issue Dec 5, 2020
kremi151 added a commit that referenced this issue Dec 5, 2020
kremi151 added a commit that referenced this issue Dec 5, 2020
kremi151 added a commit that referenced this issue Dec 5, 2020
kremi151 added a commit that referenced this issue Dec 6, 2020
kremi151 added a commit that referenced this issue Dec 6, 2020
kremi151 added a commit that referenced this issue Dec 6, 2020
kremi151 added a commit that referenced this issue Dec 6, 2020
kremi151 added a commit that referenced this issue Dec 6, 2020
kremi151 added a commit that referenced this issue Dec 6, 2020
kremi151 added a commit that referenced this issue Dec 6, 2020
kremi151 added a commit that referenced this issue Dec 6, 2020
kremi151 added a commit that referenced this issue Dec 6, 2020
#40)

This is very likely to be changed by a force push
kremi151 added a commit that referenced this issue Dec 6, 2020
kremi151 added a commit that referenced this issue Dec 6, 2020
kremi151 added a commit that referenced this issue Dec 6, 2020
kremi151 added a commit that referenced this issue Dec 6, 2020
@kremi151 kremi151 added the on hold On hold for the time being label Nov 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request on hold On hold for the time being
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant