From: "Christopher Friesen" <cfriesen@nortel•com>
To: Bob Brose <linuxppcdev@qbjnet•com>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: Q: signed vs unsigned char, PPC vs x86 gcc 3.3.5 compiler differences
Date: Sun, 02 Oct 2005 23:07:12 -0600 [thread overview]
Message-ID: <4340BC80.4000500@nortel.com> (raw)
In-Reply-To: <20051003021129.20564.qmail@kunk.qbjnet.com>
Bob Brose wrote:
> Does this mean the char in x86 is signed and in PPC it's unsigned?
> Has it always been thus?
From K+R:
"Whether plain chars are signed or unsigned is machine-dependent, but
printable characters are always positive."
Chris
prev parent reply other threads:[~2005-10-03 5:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-03 2:11 Q: signed vs unsigned char, PPC vs x86 gcc 3.3.5 compiler differences Bob Brose
2005-10-03 2:22 ` Hollis Blanchard
2005-10-03 5:07 ` Christopher Friesen [this message]
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=4340BC80.4000500@nortel.com \
--to=cfriesen@nortel$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=linuxppcdev@qbjnet$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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