From: Jim Blandy <jimb@redhat.com>
To: sid@sources.redhat.com
Subject: RFA: recognize AMD64 as a big-endian machine
Date: Thu, 09 Dec 2004 16:02:00 -0000 [thread overview]
Message-ID: <vt2zn0nwjeg.fsf@zenia.home> (raw)
2004-12-09 Jim Blandy <jimb@redhat.com>
* sidtypes.h: Recognize AMD64 (x86-64) as a big-endian machine.
Index: sid/include/sidtypes.h
===================================================================
RCS file: /cvs/cvsfiles/devo/sid/include/sidtypes.h,v
retrieving revision 1.29
diff -c -p -r1.29 sidtypes.h
*** sid/include/sidtypes.h 1 Dec 2000 16:32:41 -0000 1.29
--- sid/include/sidtypes.h 9 Dec 2004 15:57:49 -0000
***************
*** 25,31 ****
# define HOST_BIG_ENDIAN true
# endif
#else
! # if defined(__i386__) || defined(__alpha__)
# define HOST_BIG_ENDIAN false
# elif defined(__sparc__) || defined(__powerpc__)
# define HOST_BIG_ENDIAN true
--- 25,31 ----
# define HOST_BIG_ENDIAN true
# endif
#else
! # if defined(__i386__) || defined(__alpha__) || defined (__x86_64__)
# define HOST_BIG_ENDIAN false
# elif defined(__sparc__) || defined(__powerpc__)
# define HOST_BIG_ENDIAN true
reply other threads:[~2004-12-09 16:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=vt2zn0nwjeg.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=sid@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).