From: "Carlos O'Donell" <carlos@redhat.com>
To: Chris Metcalf <cmetcalf@tilera.com>
Cc: libc-ports@sourceware.org, David Miller <davem@davemloft.net>,
vapier@gentoo.org
Subject: Re: [PATCH] tile: default to little-endian in bits/endian.h
Date: Thu, 13 Jun 2013 14:26:00 -0000 [thread overview]
Message-ID: <51B9D680.2030200@redhat.com> (raw)
In-Reply-To: <201306122057.r5CKvRl0008808@farm-0002.internal.tilera.com>
On 06/12/2013 04:48 PM, Chris Metcalf wrote:
> 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
>
This looks OK to me. It always seems correct to change
an error case into a default. Just make sure that LE
is exactly the default you want.
OK for 2.15.
Cheers,
Carlos.
next prev parent reply other threads:[~2013-06-13 14:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 20:57 Chris Metcalf
2013-06-13 2:53 ` Mike Frysinger
2013-06-13 14:26 ` Carlos O'Donell [this message]
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=51B9D680.2030200@redhat.com \
--to=carlos@redhat.com \
--cc=cmetcalf@tilera.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).