From: Stephane Laroche <stephane.laroche@sympatico.ca>
To: linuxppc-embedded@lists.linuxppc.org
Subject: char type is unsigned with PPC gcc?
Date: Wed, 19 Apr 2000 09:57:52 -0400 [thread overview]
Message-ID: <38FDBB60.34DE949@sympatico.ca> (raw)
I just finished debugging the ASH shell, which wasn't running properly
on my 860, and found out that it assumes (correctly if you ask me) that
the type 'char' is signed.
GCC 2.95.2 is configured to have chars unsigned by default on the
PowerPC platforms. The x86 GCC configures char to be signed... (looking
at gcc/config/rs6000/rs6000.h for the ppc)
Anyone knows why the PowerPC is different in this regard?
Surely I'm not the first one to come across this problem. Should I fix
ASH or should I reconfigured gcc to default to signed char? I think the
latter is a better idea since, if I remember correctly, ANSI C says that
char should be signed.
-Stephane
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-04-19 13:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-19 13:57 Stephane Laroche [this message]
2000-04-19 14:21 ` char type is unsigned with PPC gcc? Gabriel Paubert
2000-04-19 14:24 ` Stephane Laroche
2000-04-19 14:42 ` Gabriel Paubert
[not found] <Pine.HPX.4.10.10004192203100.19933-100000@gra-ux1.iram.es>
2000-04-20 16:50 ` Ron Flory
2000-04-20 21:58 ` Gabriel Paubert
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=38FDBB60.34DE949@sympatico.ca \
--to=stephane.laroche@sympatico.ca \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).