On Tue, 22 Apr 2025 08:39:10 +0200, Ahmad Fatoum wrote:
> The C standard makes it implementation defined whether a plain char is
> unsigned or signed and the architectures where barebox is compiled for
> differ in that, e.g. chars are traditionally unsigned on ARM, but on x86
> for example they tend to be signed.
>
> This caused different bugs[1][2][3] in the past, especially around
> behavior when casted to int. Let's instruct the compiler to treat char
> as always unsigned. This may fix some issues that flew under the radar
> so far, but also break drivers that were compiled and used only for
> specific architectures, which implicitly assumed char is signed, which
> we'll have to fix.
>
> [...]
Applied, thanks!
[1/1] kbuild: treat char as always unsigned
https://git.pengutronix.de/cgit/barebox/commit/?id=2a6033a6610b (link may
not be stable)
Best regards,
--
Sascha Hauer <s.ha...@pengutronix.de>
