public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: Marcus Shawcroft <marcus.shawcroft@gmail.com>
To: pinskia@gmail.com
Cc: Marcus Shawcroft <marcus.shawcroft@linaro.org>,
		"libc-ports@sourceware.org" <libc-ports@sourceware.org>
Subject: Re: [PATCH] [AArch64] Define BE loader name.
Date: Mon, 06 Jan 2014 11:06:00 -0000	[thread overview]
Message-ID: <CAFqB+PwUM2_gvQhvoMsEbm1u=JKpkN_7qM75efdNZyBBKn9sWw@mail.gmail.com> (raw)
In-Reply-To: <5B4A856A-A214-4F20-83D2-BAD886EB9F04@gmail.com>

Hi,

On 1 January 2014 19:31,  <pinskia@gmail.com> wrote:
>
>
>> On Jan 1, 2014, at 9:37 AM, Marcus Shawcroft <marcus.shawcroft@linaro.org> wrote:
>>
>> Hi,
>>
>> This patch defines the BE loader name for aarch64 to be ld-linux-aarch64_be.so.1.
>
> We (Cavium and Montavista) already have a distro out in the wild for big-endian and I think changing this is a bad idea as you won't have both little-endian and big-endian on the same system ever.

It is unfortunate that the loader name wasn't put in place before you
put code in the wild.

gcc has been able to configure and build for aarch64_be-none-linux-gnu
since it was upstreamed (4.8).  The 4.8 release of gcc was tested for
aarch64-elf, aarch64-linux-gnu and aarch64_be-elf , no
aarch64_be-linux-gnu kernel support was available for testing at the
time.  The BE gcc port of aarch64 is very much beta, there has been
flux in BE gcc support over the last year notably in advsimd support
and correctness.

glibc has been able to configure and build for aarch64_be since it was
upstreamed (2.17).  Releases 2.17 and 2.18 were tested for
aarch64-linux-gnu.  Neither were tested for aarch64_be-linux-gnu.  At
the time of those releases there was no functional BE linux port.

linux currently has no support for aarch64_be, the port will be  in
3.13 (due in a couple of weeks).

Therefore the situation right now for aarch64_be is that gcc is in a
state of flux and there is no released linux kernel kernel support.

Leaving the loader name overloaded between LE and BE closes doors for
the future, if it doesn't change now, a change further down the line
will be considerably more painful.

Cavium / montavista do have the option of creating a symlink in order
to ease the transition.

> Also you forgot to change both GCC and binutils.

Not forgotten. GCC will be posted shortly.  BINUTILS looks like it is
uses a broken loader name for both LE and BE, I'll sort that out
separately.

Cheers
/Marcus

  parent reply	other threads:[~2014-01-06 11:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-01 17:38 Marcus Shawcroft
2014-01-01 19:31 ` pinskia
2014-01-01 19:57   ` pinskia
2014-01-06 11:06   ` Marcus Shawcroft [this message]
2014-01-06 17:16     ` Andrew Pinski
2014-01-08 22:43       ` Carlos O'Donell
2014-01-13 18:17         ` Steve McIntyre
2014-01-17 23:04           ` Andrew Pinski
2014-01-20 15:53             ` Marcus Shawcroft
2014-01-20 16:13               ` Joseph S. Myers
2014-01-20 16:15             ` Policy: Require new dynamic loader names for entirely new ABIs? Carlos O'Donell
2014-01-20 17:10               ` Steve McIntyre

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='CAFqB+PwUM2_gvQhvoMsEbm1u=JKpkN_7qM75efdNZyBBKn9sWw@mail.gmail.com' \
    --to=marcus.shawcroft@gmail.com \
    --cc=libc-ports@sourceware.org \
    --cc=marcus.shawcroft@linaro.org \
    --cc=pinskia@gmail.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).