This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: signed or unsigned char

To: Hua Ji <hji at netscreen dot com>
Subject: Re: signed or unsigned char
From: Bob Lee <bobl at agilestorage dot com>
Date: Thu, 19 Apr 2001 11:34:46 -0700
Cc: crossgcc at sourceware dot cygnus dot com
References: <A33AEFDC2EC0D411851900D0B73EBEF73D9EF8@NAPA>
Reply-To: bobl at agilestorage dot com

On Wed, Apr 18, 2001 at 08:43:29PM -0700, Hua Ji wrote:
> Hi, folks,

> I suddenly found this with my powerpc compiler targeted for 405GP.
> 
> The char is being treated **unsigned** **by default** by the compiler. I
> don't why this happened.

    That's the way the Sytem V ABI PowerPC Supplement decrees it.
    thus. We ran across this while I was at LynuxWorks with our tool
    chain. Planned to make all instantiations of gcc operate the
    same, when we found this issue in the ABI.

    I believe you can set the type of ABI when you build the compiler.
    There is at least one other choice, the embedded ABI from Motorola.
    I don't happen to have a copy of that handy.

> Mike

bob
--
bobl@agilestorage.com

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

References:
- signed or unsigned char
  - From: Hua Ji

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]