core: mutex: fix DEBUG pointer output #10354
Merged
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.
Contribution description
Out of interest after some offline discussions regarding #10121 I tried to compile
hello-world
fornative
without the-m32
flag. Apart from obviously required adaptations incpu/native
(which needs some rework for 64-bit support), I only found some pointer conversion errors in the debug output ofcore/mutex
. I don't know why the output originally was converted to an integer in 350c341, but maybe @kaspar030 can answer that?Testing procedure
tests/mutex_order
should still compile withENABLE_DEBUG == 1
incore/mutex.c
and provide sensible debug output.Issues/PRs references
None, but out of curiosity if #10121 can be fixed by providing 64-bit support.