When a #warning directive is followed by tokens containing non-ASCII characters encoded in UTF-8, a broken string can be printed out as a diagnostic message on some systems. This is because the current code assumes char to be signed char, whereas on some systems char is in fact unsigned char.
Details
Details
Diff Detail
Diff Detail
Event Timeline
Comment Actions
The issue was first reported by @dev-bz at GitHub in https://github.com/termux/termux-packages/issues/9619.
Comment Actions
Thank you for this! Is there a way to add test coverage for this change? Also, this should come with a release note as it's fixing a bug someone reported.