Refactor to use a 'cycles target' #346
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Baekalfen
force-pushed
the
cpu_target
branch
6 times, most recently
from
2a0db1a
to
9565821
Compare
Baekalfen
force-pushed
the
cpu_target
branch
5 times, most recently
from
9ae4fc4
to
2a340ec
Compare
Baekalfen
force-pushed
the
cpu_target
branch
from
2a340ec
to
a6a895a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Refactor as a pre-cursor to JIT-compilation.
Run multiple CPU instructions without checking interrupts, based on information from each sub-component. If state-altering changes are made, we bail our current target and check in with each sub-component as usual. Then reiterate.
This could potentially improve host-performance too, as we're doing less overhead per CPU instruction.