Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Wilson <jim.wilson@linaro.org>
To: gdb-patches@sourceware.org
Cc: Nick Clifton <nickc@redhat.com>
Subject: Re: [PATCH] aarch64 sim big-endian support
Date: Fri, 10 Jun 2016 16:24:00 -0000	[thread overview]
Message-ID: <CABXYE2XbZ3ANw2BBf79Lvtn0=VbhKXQn7Gmn0RkwR6_89mFBcw@mail.gmail.com> (raw)
In-Reply-To: <CABXYE2UfwrSxRADdgFRuBJzTM-1_DPaP5LJSULSQ-808X8dccQ@mail.gmail.com>

ping

for the attachment, see
https://sourceware.org/ml/gdb-patches/2016-06/msg00046.html

On Thu, Jun 2, 2016 at 7:36 PM, Jim Wilson <jim.wilson@linaro.org> wrote:
> On aarch64, code is always little-endian, even when compiling
> big-endian, so we need to force little-endian when reading
> instructions.
>
> Running the gcc C language testsuite, I get for an aarch64-elf target
>
> # of expected passes            35433
> # of unexpected failures        254
> # of unsupported tests          131
>
> and for an aarch64_be-elf target with the attached patch I get
>
> # of expected passes            35200
> # of unexpected failures        487
> # of unsupported tests          131
>
> so this simple patch gets us most of the way there.  I haven't tried
> looking at the other problems yet.
>
> I also have a dejagnu patch I wrote to make this work, which I will be
> submitting to the dejagnu team shortly.
>
> Jim


  reply	other threads:[~2016-06-10 16:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-03  2:36 Jim Wilson
2016-06-10 16:24 ` Jim Wilson [this message]
2016-06-13 12:38   ` Nick Clifton
2016-06-30  1:33     ` Jim Wilson
2016-06-30  8:13       ` Nick Clifton
2016-06-10 18:06 ` Mike Frysinger

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='CABXYE2XbZ3ANw2BBf79Lvtn0=VbhKXQn7Gmn0RkwR6_89mFBcw@mail.gmail.com' \
    --to=jim.wilson@linaro.org \
    --cc=gdb-patches@sourceware.org \
    --cc=nickc@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