mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Willy Tarreau <willy@w.ods.org>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: Kill signed chars !!! => PPC uses unsigned chars
Date: Tue, 21 Jun 2005 14:54:04 +0200	[thread overview]
Message-ID: <20050621125404.GA13437@alpha.home.local> (raw)
In-Reply-To: <1117232503l.24619l.1l@werewolf.able.es>

On Fri, May 27, 2005 at 10:21:43PM +0000, J.A. Magallon wrote:
> ... and make gcc4 happy.
> 
> On 05.25, Andrew Morton wrote:
> > 
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc5/2.6.12-rc5-mm1/
> > 
> > 
> > - Again, if there are patches in here which you think should be merged in
> >   2.6.12, please point them out to me.
> > 
> 
> scripts/ is full of mismatches between char* params an signed char* arguments,
> and viceversa. gcc4 now complaints loud about this. Patch below deletes all
> those 'signed'. Anyways, which was the purpose of declaring 'signed char's
> to store text ?

Well, to my surprize, linux-ppc uses UNSIGNED chars by default. It has amazed
me but it's a fact. Let's compile this little program on tux-ppc :

$ cat ints.c
#include <stdio.h>

main()
{
        int i1, i2;
        char c1, c2;

        c1 = i1 = 0;

        c1--; c2 = c1;
        i1--; i2 = i1;

        c2 &= ~(c2 >> 1);
        i2 &= ~(i2 >> 1);

        if (c1 < 0) printf("c1<0: %d\n", c1); else printf("c1>=0: %d\n",c1);
        if (c2 < 0) printf("c2<0: %d\n", c2); else printf("c2>=0: %d\n",c2);
        if (i1 < 0) printf("i1<0: %d\n", i1); else printf("i1>=0: %d\n",i1);
        if (i2 < 0) printf("i2<0: %d\n", i2); else printf("i2>=0: %d\n",i2);
}

$ gcc-3.3 -v
Reading specs from /usr/lib/gcc-lib/powerpc-linux/3.3.5/specs
Configured with: ../src/configure -v --enable-languages=c,c++,java,f77,pascal,objc,ada --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared --enable-__cxa_atexit --with-system-zlib --enable-nls --without-included-gettext --enable-clocale=gnu --enable-debug --enable-java-gc=boehm --enable-java-awt=xlib --enable-objc-gc --disable-multilib powerpc-linux
Thread model: posix
gcc version 3.3.5 (Debian 1:3.3.5-13)

$ gcc-3.3 -O2 -o ints ints.c
ints.c: In function `main':
ints.c:16: warning: comparison is always false due to limited range of data type
ints.c:17: warning: comparison is always false due to limited range of data type

$ ./ints
c1>=0: 255
c2>=0: 128
i1<0: -1
i2>=0: 0

=> As you can see, 0 - 1 returns 255 as a char, and -1 & ~(-1 >> 1) = 128 !
ints are OK BTW. I'm gonna change some of my code to fix this because relying
on signed chars to to detect unassigned values (-1) is wrong !

Oh and BTW, here's the result on x86 :

$ gcc-3.3 -o ints ints.c
$ ./ints
c1<0: -1
c2>=0: 0
i1<0: -1
i2>=0: 0

Cheers,
Willy


  parent reply	other threads:[~2005-06-21 13:01 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-25 20:49 2.6.12-rc5-mm1 Andrew Morton
2005-05-25 21:37 ` 2.6.12-rc5-mm1 Alexandre Buisse
2005-05-25 21:51 ` 2.6.12-rc5-mm1 Brice Goglin
2005-05-25 21:58 ` 2.6.12-rc5-mm1 Brice Goglin
2005-05-26  5:29   ` 2.6.12-rc5-mm1 Yani Ioannou
2005-05-25 22:57 ` 2.6.12-rc5-mm1 Jesper Juhl
2005-05-26  1:17 ` 2.6.12-rc5-mm1 Matthew Dobson
2005-05-26  2:43 ` 2.6.12-rc5-mm1 Ed Tomlinson
2005-05-26  3:41   ` 2.6.12-rc5-mm1 Andrew Morton
2005-05-26  7:43     ` 2.6.12-rc5-mm1 J.A. Magallon
2005-05-26  7:58       ` 2.6.12-rc5-mm1 Andrew Morton
2005-05-26 13:54         ` 2.6.12-rc5-mm1 Rafael J. Wysocki
2005-05-26 20:45           ` 2.6.12-rc5-mm1 Andrew Morton
2005-05-26 21:04             ` 2.6.12-rc5-mm1 Lee Revell
2005-05-26 21:07             ` 2.6.12-rc5-mm1 Chris Wright
2005-05-27 10:29             ` 2.6.12-rc5-mm1 Rafael J. Wysocki
2005-05-27 17:38               ` 2.6.12-rc5-mm1 Chen, Kenneth W
2005-05-27 22:32                 ` 2.6.12-rc5-mm1 J.A. Magallon
2005-05-26 21:39         ` 2.6.12-rc5-mm1 J.A. Magallon
2005-05-26  7:44 ` 2.6.12-rc5-mm1 J.A. Magallon
2005-05-26  7:52   ` 2.6.12-rc5-mm1 Andrew Morton
2005-05-26  8:57 ` 2.6.12-rc5-mm1 Mikael Pettersson
2005-05-26 13:04   ` 2.6.12-rc5-mm1 Andrea Arcangeli
2005-05-26 19:15     ` 2.6.12-rc5-mm1 Mikael Pettersson
2005-05-26 22:22       ` 2.6.12-rc5-mm1 Andrea Arcangeli
2005-05-27  2:47         ` 2.6.12-rc5-mm1 Andrea Arcangeli
2005-05-27 21:13 ` 2.6.12-rc5-mm1 Arnd Bergmann
2005-05-28  7:07   ` 2.6.12-rc5-mm1 Christoph Hellwig
2005-06-29 13:42     ` 2.6.12-rc5-mm1 Arnd Bergmann
2005-06-29 16:22       ` Xtensa syscalls (Was: Re: 2.6.12-rc5-mm1) Christian Zankel
2005-06-29 16:29         ` Christoph Hellwig
2005-06-29 16:47         ` Andrew Morton
2005-06-29 19:11         ` Arnd Bergmann
2005-05-27 22:21 ` Kill signed chars !!! [was Re: 2.6.12-rc5-mm1] J.A. Magallon
2005-05-27 23:46   ` Jesper Juhl
2005-06-21 12:54   ` Willy Tarreau [this message]
2005-06-21 14:23     ` Kill signed chars !!! => PPC uses unsigned chars cutaway
2005-06-21 21:13       ` J.A. Magallon
2005-05-29 14:26 ` 2.6.12-rc5-mm1: fork connector doesn't compile with gcc 2.95 Adrian Bunk
2005-05-29 14:38 ` 2.6.12-rc5-mm1: drivers/char/tpm/ compile errors " Adrian Bunk
2005-05-29 14:38 ` 2.6.12-rc5-mm1: drivers/dlm/: compile error " Adrian Bunk
2005-05-29 14:43   ` Matthias-Christian Ott
2005-05-29 15:00     ` Adrian Bunk
2005-05-29 14:45 ` 2.6.12-rc5-mm1: drivers/media/dvb/dvb-usb/a800.c compile error Adrian Bunk
2005-05-30  8:29   ` Patrick Boettcher
2005-05-30  9:14     ` Johannes Stezenbach
2005-05-30  9:30       ` Patrick Boettcher
2005-05-29 15:12 ` 2.6.12-rc5-mm1: drivers/usb/atm/speedtch.c: gcc 2.95 " Adrian Bunk
2005-05-30  7:45   ` Duncan Sands
2005-05-30  8:04     ` Andrew Morton
2005-05-30  8:16       ` Duncan Sands
2005-05-30 13:52 ` 2.6.12-rc5-mm1 Stefano Rivoir
2005-05-30 19:50 ` [-mm patch] drivers/message/i2o/device.c: i2o_parm_issue has to be global Adrian Bunk
2005-05-31 12:00 ` [PATCH 2.6.12-rc5-mm1] m32r: Insert set_tsk_need_resched() to cpu_idle() (was Re: 2.6.12-rc5-mm1) Hirokazu Takata

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050621125404.GA13437@alpha.home.local \
    --to=willy@w.ods.org \
    --cc=akpm@osdl.org \
    --cc=jamagallon@able.es \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®