From: James Greenhalgh <james.greenhalgh@arm.com>
To: Steve Ellcey <sellcey@cavium.com>
Cc: <gcc-patches@gcc.gnu.org>, <nd@arm.com>
Subject: Re: [PATCH/AARCH64] Improve aarch64 conditional compare usage
Date: Tue, 20 Jun 2017 13:58:00 -0000 [thread overview]
Message-ID: <20170620135833.GA23447@arm.com> (raw)
In-Reply-To: <201706161706.v5GH6p6Z026364@sellcey-dt.caveonetworks.com>
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
next prev parent reply other threads:[~2017-06-20 13:58 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 [this message]
2017-06-20 15:21 ` Steve Ellcey
-- 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=20170620135833.GA23447@arm.com \
--to=james.greenhalgh@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nd@arm.com \
--cc=sellcey@cavium.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).