[Bug 269] Many compiler warnings with gcc 4.0

Paul TBBle Hampson Paul.Hampson at Pobox.com
Thu Sep 1 13:22:03 CEST 2005

On Wed, Aug 31, 2005 at 12:38:03PM -0700, Frank Cusack wrote:
> On August 31, 2005 4:47:16 PM +1000 Paul TBBle Hampson <Paul.Hampson at Pobox.com> wrote:
> >Chars are unsigned on Linux PowerPC. I don't believe there's anything that
> >depends on chars being signed that doesn't explicitly declare such, as I ran
> >FreeRADIUS on LinuxPPC without issues for a few years. I think all
> >signed-char assumptions were therefore shaken out a fair while ago.
> ...

> To say that chars are unsigned on Linux PPC is meaningless.  Whether chars
> are signed or unsigned is up to the compiler.  Now it may be the case that
> gcc on Linux PPC does treat char as unsigned, but I highly doubt it.

OK, let me rephrase. gcc and glibc on Linux PPC (specifically tested on Debian)
have unsigned chars by default.

This affects applications that do not explicitly state their signedness
requirements, which luckily FreeRADIUS does, as far as I can tell.

(The first thing I did when I started running FreeRADIUS on PowerPC is look for
"comparison is always <blah> due to limited range of type" warnings from
compiler output.)

Paul "TBBle" Hampson, MCSE
8th year CompSci/Asian Studies student, ANU
The Boss, Bubblesworth Pty Ltd (ABN: 51 095 284 361)
Paul.Hampson at Pobox.Com

Of course Pacman didn't influence us as kids. If it did,
we'd be running around in darkened rooms, popping pills and
listening to repetitive music.
 -- Kristian Wilson, Nintendo, Inc, 1989

License: http://creativecommons.org/licenses/by/2.1/au/

More information about the Freeradius-Devel mailing list