Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: Jim Wilson <jim.wilson@linaro.org>, gdb-patches@sourceware.org
Subject: Re: [PATCH] fix for aarch64 sim FP stur bug
Date: Thu, 01 Dec 2016 09:13:00 -0000	[thread overview]
Message-ID: <1686e3a4-c622-9a5b-03d1-d3f03978df06@redhat.com> (raw)
In-Reply-To: <CABXYE2XMYdgCgjdQqaRb0LJi_otd55Bk7wgWQSyTCKZgu5Z3mA@mail.gmail.com>

Hi Jim,

> While debugging a gcc C testsuite failure on the aarch64 simulator, I
> noticed that the support for FP stur instructions is broken.  They
> accidentally have the two register operands swapped.  The problem can
> be seen by comparing them with the equivalent FP str instructions.
> 
> I tested the fix by running the gcc C testsuite.  I get 3122
> unexpected failures without the patch and 2856 unexpected failures
> with the patch.

Thanks for reporting and fixing this bug.

The patch is approved - please apply.

Cheers
  Nick


      reply	other threads:[~2016-12-01  9:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-01  7:36 Jim Wilson
2016-12-01  9:13 ` Nick Clifton [this message]

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=1686e3a4-c622-9a5b-03d1-d3f03978df06@redhat.com \
    --to=nickc@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jim.wilson@linaro.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