From: Marcus Shawcroft <marcus.shawcroft@gmail.com>
To: Jiong Wang <jiong.wang@arm.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [AArch64/GCC][2/N] Let parameter type be consistent
Date: Wed, 23 Jul 2014 16:00:00 -0000 [thread overview]
Message-ID: <CAFqB+PzaKpk4LhGuRkU9-o2cG48kRkmb7d6rSCnuKFtsDeU5yw@mail.gmail.com> (raw)
In-Reply-To: <53CE79EA.3040705@arm.com>
On 22 July 2014 15:49, Jiong Wang <jiong.wang@arm.com> wrote:
> gcc/
> * config/aarch64/aarch64.c (aarch64_save_or_restore_fprs): Change type to
> HOST_WIDE_INT.
OK and applied.
/Marcus
prev parent reply other threads:[~2014-07-23 15:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 14:49 Jiong Wang
2014-07-23 16:00 ` Marcus Shawcroft [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=CAFqB+PzaKpk4LhGuRkU9-o2cG48kRkmb7d6rSCnuKFtsDeU5yw@mail.gmail.com \
--to=marcus.shawcroft@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jiong.wang@arm.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).