From: Vladimir Makarov <vmakarov@redhat.com>
To: "Kewen.Lin" <linkw@linux.ibm.com>
Cc: bergner@linux.ibm.com, Bill Schmidt <wschmidt@linux.ibm.com>,
Segher Boessenkool <segher@kernel.crashing.org>,
Richard Sandiford <richard.sandiford@arm.com>,
crazylht@gmail.com, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH v4] ira: Support more matching constraint forms with param [PR100328]
Date: Mon, 5 Jul 2021 09:04:33 -0400 [thread overview]
Message-ID: <14fa3bad-240d-4a25-7777-9883f52d6e97@redhat.com> (raw)
In-Reply-To: <0f75aadc-c389-ad37-3383-3be5b093c3e5@linux.ibm.com>
On 2021-07-01 10:11 p.m., Kewen.Lin wrote:
> Hi Vladimir,
>
> on 2021/6/30 下午11:24, Vladimir Makarov wrote:
>>
>> Many thanks for your review! I've updated the patch according to your comments and also polished some comments and document words a bit. Does it look better to you?
>>
Sorry for the delay with the answer. The patch is better for me now and
can be committed into the trunk.
Thanks again for working on this performance issue.
next prev parent reply other threads:[~2021-07-05 13:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 5:18 [RFC/PATCH] ira: Consider matching constraints " Kewen.Lin
2021-06-28 6:26 ` [RFC/PATCH v3] ira: Support more matching constraint forms " Kewen.Lin
2021-06-28 7:12 ` Hongtao Liu
2021-06-28 7:20 ` Hongtao Liu
2021-06-28 7:27 ` Kewen.Lin
2021-06-30 8:53 ` Hongtao Liu
2021-06-30 9:42 ` Kewen.Lin
2021-06-30 10:18 ` Hongtao Liu
2021-06-30 15:42 ` Richard Sandiford
2021-07-02 2:18 ` Kewen.Lin
2021-06-30 15:24 ` Vladimir Makarov
2021-07-02 2:11 ` [PATCH v4] " Kewen.Lin
2021-07-02 2:28 ` [PATCH] i386: Disable param ira-consider-dup-in-all-alts [PR100328] Kewen.Lin
2021-07-02 8:05 ` Uros Bizjak
2021-07-05 13:04 ` Vladimir Makarov [this message]
2021-06-30 15:25 ` [RFC/PATCH v3] ira: Support more matching constraint forms with param [PR100328] Vladimir Makarov
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=14fa3bad-240d-4a25-7777-9883f52d6e97@redhat.com \
--to=vmakarov@redhat.com \
--cc=bergner@linux.ibm.com \
--cc=crazylht@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=linkw@linux.ibm.com \
--cc=richard.sandiford@arm.com \
--cc=segher@kernel.crashing.org \
--cc=wschmidt@linux.ibm.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).