Re: [avr-gcc-list] New GCC warning - how to silence?

[Joerg Wunsch]

As larry barello wrote:

> One thing that still bothers me, maybe I just missed it: Why is char !=
> int8_t at this point?

Because that is how the C language is specified.

> It seems wrong to have to use "char" due to libc then have to explicitly
> type cast before using anywhere else...

Again, you have to blame C for this.  It's the only portable way.  That
is all the warning is going to tell you: if you are making assumptions
about an unqualified char being *either* signed or unsigned, you are at
risk of producing a non-conforming application.  OTOH, the C standard
library uses unqualified chars in a number of places, so avr-libc has
no chance here.

-- 
cheers, J"org               .-.-.   --... ...--   -.. .  DL8DTL

http://www.sax.de/~joerg/                        NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)