public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Hurugalawadi, Naveen" <Naveen.Hurugalawadi@cavium.com>
To: James Greenhalgh <james.greenhalgh@arm.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	Richard Earnshaw	<Richard.Earnshaw@arm.com>,
	Marcus Shawcroft <marcus.shawcroft@arm.com>,
	"nd@arm.com" <nd@arm.com>,
	"Pinski, Andrew" <Andrew.Pinski@cavium.com>
Subject: Re: [PING] [PATCH] [AArch64] vec_pack_trunc_<mode> should split after register allocator
Date: Fri, 11 Aug 2017 06:09:00 -0000	[thread overview]
Message-ID: <CO2PR07MB269340785CE21DE7C4D2868783890@CO2PR07MB2693.namprd07.prod.outlook.com> (raw)
In-Reply-To: <CO2PR07MB26932740F6783B49FB886B7983890@CO2PR07MB2693.namprd07.prod.outlook.com>

Hi,  

Please consider this as a personal reminder to review the patch
at following link and let me know your comments on the same.  

https://gcc.gnu.org/ml/gcc-patches/2017-07/msg01529.html

Thanks,
Naveen



      

      parent reply	other threads:[~2017-08-11  4:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-27  7:37 [PATCH][AArch64] " Hurugalawadi, Naveen
2017-05-11  5:43 ` [PING] [PATCH] [AArch64] " Hurugalawadi, Naveen
2017-05-26  6:27   ` [PING 2] " Hurugalawadi, Naveen
2017-06-15  3:49     ` [PING 3] " Hurugalawadi, Naveen
2017-06-30  6:29       ` [PING 4] " Hurugalawadi, Naveen
2017-07-19  2:57         ` [PING 5] " Hurugalawadi, Naveen
2017-07-21 16:42 ` [PATCH][AArch64] " James Greenhalgh
2017-07-25  7:30   ` Hurugalawadi, Naveen
2017-07-25  8:57     ` James Greenhalgh
2017-07-25 11:40       ` Hurugalawadi, Naveen
     [not found]         ` <CO2PR07MB26932740F6783B49FB886B7983890@CO2PR07MB2693.namprd07.prod.outlook.com>
2017-08-11  6:09           ` Hurugalawadi, Naveen [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=CO2PR07MB269340785CE21DE7C4D2868783890@CO2PR07MB2693.namprd07.prod.outlook.com \
    --to=naveen.hurugalawadi@cavium.com \
    --cc=Andrew.Pinski@cavium.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=james.greenhalgh@arm.com \
    --cc=marcus.shawcroft@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).