From: Marcus Shawcroft <marcus.shawcroft@gmail.com>
To: Sofiane Naci <sofiane.naci@arm.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [AARCH64][Insn classification unification 2/N] Add cortex-a53 pipeline description
Date: Thu, 01 Aug 2013 09:14:00 -0000 [thread overview]
Message-ID: <CAFqB+PxwY-JkSsvm58H8Xgd0qkRm31CTHYjcK5NNjUm4SdcpzA@mail.gmail.com> (raw)
In-Reply-To: <51f925b5.0194420a.7ef5.fffff86eSMTPIN_ADDED_BROKEN@mx.google.com>
On 31 July 2013 15:56, Sofiane Naci <sofiane.naci@arm.com> wrote:
> Hi,
>
> This patch is part of the ongoing work to unify instruction classification
> between the ARM and AARCH64 backends.
>
> This patch wires up the cortex-a53 pipeline description defined in the ARM
> backend to be used in the AARCH46 backend.
>
> OK for trunk?
OK
/Marcus
next parent reply other threads:[~2013-08-01 9:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51f925b5.0194420a.7ef5.fffff86eSMTPIN_ADDED_BROKEN@mx.google.com>
2013-08-01 9:14 ` Marcus Shawcroft [this message]
2013-07-31 14:56 Sofiane Naci
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+PxwY-JkSsvm58H8Xgd0qkRm31CTHYjcK5NNjUm4SdcpzA@mail.gmail.com \
--to=marcus.shawcroft@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=sofiane.naci@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).