public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: Chris Metcalf <cmetcalf@tilera.com>
To: <libc-ports@sourceware.org>, David Miller <davem@davemloft.net>,
	Carlos O'Donell <carlos@redhat.com>
Cc: <vapier@gentoo.org>
Subject: [PATCH] tile: default to little-endian in bits/endian.h
Date: Wed, 12 Jun 2013 20:57:00 -0000	[thread overview]
Message-ID: <201306122057.r5CKvRl0008808@farm-0002.internal.tilera.com> (raw)

2013-06-12  Chris Metcalf  <cmetcalf@tilera.com>

	* sysdeps/tile/bits/endian.h (__BYTE_ORDER): Default to little.

This turns out to be helpful when doing a from-scratch cross-compile of
gcc and glibc, since you can then do "make install-headers" in glibc
even before you have a functioning tile gcc.

This was pointed out by Mike Frysinger (cc'ed).

David, Carlos, I'd like to also backport this to glibc 2.17 and 2.16,
to make cross-building easier there.  It applies to 2.15 as well, but
I'm not sure how far back it makes sense to go with this kind of thing.

diff --git a/ports/sysdeps/tile/bits/endian.h b/ports/sysdeps/tile/bits/endian.h
index 43d94bb..835042a 100644
--- a/ports/sysdeps/tile/bits/endian.h
+++ b/ports/sysdeps/tile/bits/endian.h
@@ -6,8 +6,6 @@
 
 #if defined __BIG_ENDIAN__
 # define __BYTE_ORDER __BIG_ENDIAN
-#elif defined __LITTLE_ENDIAN__
-# define __BYTE_ORDER __LITTLE_ENDIAN
 #else
-# error "Endianness not declared!!"
+# define __BYTE_ORDER __LITTLE_ENDIAN
 #endif
-- 
1.7.10.3

             reply	other threads:[~2013-06-12 20:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-12 20:57 Chris Metcalf [this message]
2013-06-13  2:53 ` Mike Frysinger
2013-06-13 14:26 ` Carlos O'Donell
2013-06-15 17:21 ` Joseph S. Myers
2013-06-15 18:55   ` Chris Metcalf
2013-06-19 16:36 ` Chris Metcalf
2013-06-19 19:21   ` David Miller

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=201306122057.r5CKvRl0008808@farm-0002.internal.tilera.com \
    --to=cmetcalf@tilera.com \
    --cc=carlos@redhat.com \
    --cc=davem@davemloft.net \
    --cc=libc-ports@sourceware.org \
    --cc=vapier@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.
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).