Allegrex v4.4.0 lock api & Fix CLOCKS_PER_SEC
#11
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.
This PR does 2 things:
Newlib by default defines
CLOCKS_PER_SEC
as1000
which is wrong,. it should be1000000
.Official info:
To have thread-safe operations for all the
newlib
operations we have been required to do several PR:newlib
psptoolchain-ee
pspsdk
This PR skips the usage of the dummy lock API, letting us implement the specific one in the
pspsdk/libcglue
Cheers