Re: moused(8): char signed-ness problem with gcc 3.1

Thomas David Rivers wrote:
>  Well - it's not counter-intuitive on many machines... For example,
>  on the IBM mainframe - there is an instruction to load a character
>  into a register - but not one that loads *and* sign-extends. So,
>  you can get much better code if characters are unsigned by default.

Sounds like time to get out the wire wrap tools... and fix the
hardware, not the software.

>  So in our C/C++ compilers for the mainframe, the default is
>  unsigned as well.
> 
>  I wonder if the AIX people were looking for mainframe
>  compatibility in this decision, or was it motivated
>  by the PowerPC instruction set?  Does anyone know what
>  the Mac default is (since they are PowerPC based as well?)

RS/6000's didn't used to use PPC processors at all; so it's
probably intentional software compatability.

-- Terry

To Unsubscribe: send mail to [email protected]
with "unsubscribe freebsd-audit" in the body of the message