coreinit: Add some missing field to the OSThread struct #319
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
Maschell
force-pushed
the
threads
branch
4 times, most recently
from
a9d2053 to
9a06a5e
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.
Most of the fields are coming from decaf.
Changes compared to decafs struct:
eh_*fields have been extracted into a seperate struct. The thread init function does a memset for 0x1D8 bytes at offset 0x3A0, this indicated an own struct. First 0x68 bytes are still unknown.stackSyncObjAllowedhas been added (but is only used on debug builds, and only for logging)reserved) are cleared by the thread init functions but never used. These are probably just unused reserved bits.