Add -fsigned-char #8
Merged
Conversation
This file contains hidden or 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
`char` type could be `unsigned char` or `signed char` depending on CPU architectures. It's `unsigned char` by default on aarch32 architectures, though it's `signed char` on intel architectures. This causes many unexpected behaviors on run68, and we need to specify `-fsigned-char` flag explicitly to make the behavior compatible on all platforms.
|
LGTM |
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.
chartype could beunsigned charorsigned chardepending on CPU architectures. It'sunsigned charby default on aarch32 architectures, though it'ssigned charon intel architectures. This causes many unexpected behaviors on run68, and we need to specify-fsigned-charflag explicitly to make the behavior compatible on all platforms.