Q: signed vs unsigned char, PPC vs x86 gcc 3.3.5 compiler differences
linuxppcdev at qbjnet.com
Mon Oct 3 12:11:29 EST 2005
I'm trying to fix some of the AX25 code in the 2.6 kernel and traced down
a problem to the use of a char var which was being assigned
the value of -1. On x86 when the var was compared to -1 it succeded but
on PPC it failed. So I tried a simple test:
With GCC 3.3.5 on 2.6.14-rc1 x86 I get:
With GCC 3.3.5 on 2.6.14-rc1 PPC I get:
If I change the declaration of atest to a signed char on PPC I get the
same result as x86.
Does this mean the char in x86 is signed and in PPC it's unsigned?
Has it always been thus?
More information about the Linuxppc-dev