linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: "DI BACCO ANTONIO - technolabs" <Antonio.DiBacco@technolabs.it>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: ppc_8xx-gcc from eldk strange behaviour
Date: Thu, 30 Aug 2007 01:28:00 +0200	[thread overview]
Message-ID: <20070829232800.EBD0524044@gemini.denx.de> (raw)
In-Reply-To: Your message of "Wed, 29 Aug 2007 11:28:36 +0200." <F1F6EC0C8B75034F9E3A79FC85122E8EA185B5@aquib01a>

In message <F1F6EC0C8B75034F9E3A79FC85122E8EA185B5@aquib01a> you wrote:
> > C does not specify the signedness of char.  If you care, you need to
> > explicitly specify.
> 
> Sorry, I didn't know this. Anyway I would expect the same behaviour from
> both host gcc and ppc_8xx-gcc. In this case host gcc is wrong. 

No, it is not wrong.  The  behaviour  is  just  not  defined  by  the
standard,  so  the compiler is free to do what he likes. Some systems
default to singend chars,  others  to  unsigned.  Both  is  perfectly
legal.

It is code that makes any such assumptions which is broken.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Death, when unnecessary, is a tragic thing.
	-- Flint, "Requiem for Methuselah", stardate 5843.7

  reply	other threads:[~2007-08-29 23:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-28 18:56 ppc_8xx-gcc from eldk strange behaviour DI BACCO ANTONIO - technolabs
2007-08-28 19:01 ` Scott Wood
2007-08-29  9:28   ` DI BACCO ANTONIO - technolabs
2007-08-29 23:28     ` Wolfgang Denk [this message]
2007-08-29  4:50 ` Ricardo Scop

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=20070829232800.EBD0524044@gemini.denx.de \
    --to=wd@denx.de \
    --cc=Antonio.DiBacco@technolabs.it \
    --cc=linuxppc-embedded@ozlabs.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).