Mail Archives: djgpp/1994/11/11/21:11:56
Looks like djgpp is treating "char" as "signed char". The info page
suggests that it should be defaulting to "unsigned char" (at least, that's
what the writeup on the SIGNED_CHAR_SPEC macro used to define the
gcc target stuff implies). In any case, I don't think it's a good idea
to make this sort of assumption; if you want to make the right thing
happen, declare things explicitly as "unsigned char". (If you do that,
the right code does get generated.)
paul
- Raw text -