From: Steve Ellcey <sellcey@cavium.com>
To: James Greenhalgh <james.greenhalgh@arm.com>
Cc: gcc-patches@gcc.gnu.org, nd@arm.com
Subject: Re: [PATCH/AARCH64] Improve aarch64 conditional compare usage
Date: Tue, 20 Jun 2017 15:21:00 -0000 [thread overview]
Message-ID: <1497972084.31950.35.camel@cavium.com> (raw)
In-Reply-To: <20170620135833.GA23447@arm.com>
On Tue, 2017-06-20 at 14:58 +0100, James Greenhalgh wrote:
> On Fri, Jun 16, 2017 at 10:06:51AM -0700, Steve Ellcey wrote:
> >
> >
> > https://gcc.gnu.org/ml/gcc-patches/2017-05/msg00021.html
> >
> > Ping.
> Hi Steve,
>
> These changes all look like they are to the tree pass rather than to the
> AArch64 back end. Maybe reposting it without the AArch64 tag will get it
> more visibility from people other than the AArch64 maintainers?
>
> Cheers,
> James
Someone else made the same suggestion so I re-pinged here:
https://gcc.gnu.org/ml/gcc-patches/2017-06/msg01338.html
With the subject "[PATCH] Ping of ccmp.c (conditional compare) patch"
Steve Ellcey
sellcey@cavium.com
next prev parent reply other threads:[~2017-06-20 15:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 17:06 Steve Ellcey
2017-06-20 13:58 ` James Greenhalgh
2017-06-20 15:21 ` Steve Ellcey [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-05-01 17:16 Steve Ellcey
2017-06-27 22:46 ` Jeff Law
2017-06-29 18:30 ` Steve Ellcey
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=1497972084.31950.35.camel@cavium.com \
--to=sellcey@cavium.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=james.greenhalgh@arm.com \
--cc=nd@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).