From: Mike Frysinger <vapier@gentoo.org>
To: Nick Clifton <nickc@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: ARM SIM: Add support for VFP instructions
Date: Tue, 07 Jul 2015 17:15:00 -0000 [thread overview]
Message-ID: <20150707171505.GN17734@vapier> (raw)
In-Reply-To: <87si9bitv6.fsf@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 512 bytes --]
On 28 Jun 2015 19:13, Nick Clifton wrote:
> I am applying the patch below to add support for the ARM v6
> instructions to the ARM sim, including support for the VFP hardware
> floating point co-processor. With this patch applied the GCC
> testsuite for the -mabi=hard-float multilib of an arm-eabi toolchain
> goes from 2388 unexpected failures to 44, and no regressions are
> introduced. :-)
this has added trailing whitespace in a number of places. could you strip that
out ?
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-07-07 17:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-28 18:13 Nick Clifton
2015-07-07 17:15 ` Mike Frysinger [this message]
2015-07-14 11:07 ` Nicholas Clifton
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=20150707171505.GN17734@vapier \
--to=vapier@gentoo.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