From: Ulrich Mueller <ulm@gentoo.org>
To: Andreas Schwab <schwab@suse.de>
Cc: sh@gentoo.org, Dan Nicolaescu <dann@ics.uci.edu>,
emacs-devel@gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
emacs@gentoo.org
Subject: Re: SuperH port
Date: Sat, 18 Oct 2008 00:56:54 +0200 [thread overview]
Message-ID: <18681.6198.274798.233457@a1ihome1.kph.uni-mainz.de> (raw)
In-Reply-To: <jeabd2uaew.fsf@sykes.suse.de>
>>>>> 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
next prev parent reply other threads:[~2008-10-17 22:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 9:17 SuperH port Ulrich Mueller
2008-10-08 10:37 ` Ulrich Mueller
2008-10-08 14:31 ` Dan Nicolaescu
2008-10-08 18:22 ` Ulrich Mueller
2008-10-08 18:47 ` Stefan Monnier
2008-10-15 21:16 ` Ulrich Mueller
2008-10-15 21:36 ` Dan Nicolaescu
2008-10-16 16:04 ` Ulrich Mueller
2008-10-17 6:04 ` Dan Nicolaescu
2008-10-17 20:26 ` Ulrich Mueller
2008-10-17 22:25 ` Andreas Schwab
2008-10-17 22:56 ` Ulrich Mueller [this message]
2008-10-18 8:39 ` Ulrich Mueller
2008-10-18 8:12 ` Dan Nicolaescu
2008-12-11 7:20 ` Ulrich Mueller
2008-12-11 7:58 ` Dan Nicolaescu
2008-10-09 10:24 ` Ulrich Mueller
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=18681.6198.274798.233457@a1ihome1.kph.uni-mainz.de \
--to=ulm@gentoo.org \
--cc=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=emacs@gentoo.org \
--cc=monnier@iro.umontreal.ca \
--cc=schwab@suse.de \
--cc=sh@gentoo.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).