[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: SuperH port
From: |
Ulrich Mueller |
Subject: |
Re: SuperH port |
Date: |
Sat, 18 Oct 2008 00:56:54 +0200 |
>>>>> On Sat, 18 Oct 2008, Andreas Schwab wrote:
>> (To add some confusion, endian.h then also defines _all_ four of
>> __LITTLE_ENDIAN, LITTLE_ENDIAN, __BIG_ENDIAN, and BIG_ENDIAN,
>> regardless of the machine's byte sex. Go figure.)
> There is nothing wrong with that. They define the valid values for
> BYTE_ORDER.
Of course there's nothing wrong. But I think it's a bit awkward that
the same names are used for different purposes.
<offtopic>
On Powerpc, it's a complete mess: gcc defines both __BIG_ENDIAN__ and
_BIG_ENDIAN, and endian.h defines the four above-mentioned macros. ;-)
</offtopic>
Ulrich
- Re: SuperH port, (continued)
- Re: SuperH port, Ulrich Mueller, 2008/10/08
- Re: SuperH port, Dan Nicolaescu, 2008/10/08
- Re: SuperH port, Ulrich Mueller, 2008/10/08
- Re: SuperH port, Stefan Monnier, 2008/10/08
- Re: SuperH port, Ulrich Mueller, 2008/10/15
- Re: SuperH port, Dan Nicolaescu, 2008/10/15
- Re: SuperH port, Ulrich Mueller, 2008/10/16
- Re: SuperH port, Dan Nicolaescu, 2008/10/17
- Re: SuperH port, Ulrich Mueller, 2008/10/17
- Re: SuperH port, Andreas Schwab, 2008/10/17
- Re: SuperH port,
Ulrich Mueller <=
- Re: SuperH port, Ulrich Mueller, 2008/10/18
- Re: SuperH port, Dan Nicolaescu, 2008/10/18
Re: SuperH port, Ulrich Mueller, 2008/10/09