From: Jakub Jelinek <jakub@redhat.com>
To: Sebastian Perta <sebastian.perta@renesas.com>
Cc: Nick Clifton <nickc@redhat.com>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: PING [PATCH] RX movsicc degrade fix
Date: Mon, 12 Feb 2018 13:49:00 -0000 [thread overview]
Message-ID: <20180212133011.GB5867@tucnak> (raw)
In-Reply-To: <000101d3a405$3926eb40$ab74c1c0$@renesas.com>
On Mon, Feb 12, 2018 at 01:27:24PM -0000, Sebastian Perta wrote:
> --- ChangeLog (revision 257583)
> +++ ChangeLog (working copy)
> @@ -129,8 +129,7 @@
>
> 2018-02-09 Sebastian Perta <sebastian.perta@renesas.com>
>
> - * config/rx.md: updated "movsicc" expand to be matched by GCC
> - * testsuite/gcc.target/rx/movsicc.c: new test case
> + * config/rx/rx.md (movsicc): Update expander to be matched by GCC.
>
> 2018-02-09 Peter Bergner <bergner@vnet.ibm.com>
>
> @@ -143,10 +142,10 @@
>
> 2018-02-09 Sebastian Perta <sebastian.perta@renesas.com>
>
> - * config/rx/constraints.md: added new constraint CALL_OP_SYMBOL_REF
> - to allow or block "symbol_ref" depending on value of TARGET_JSR
> - * config/rx/rx.md: use CALL_OP_SYMBOL_REF in call_internal and
> - call_value_internal insns
> + * config/rx/constraints.md (CALL_OP_SYMBOL_REF): Added new constraint
Still missing . at the end of the above line.
Otherwise LGTM.
Jakub
next prev parent reply other threads:[~2018-02-12 13:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 14:10 Nick Clifton
[not found] ` <20180209182349.GL5867@tucnak>
2018-02-12 11:06 ` Sebastian Perta
2018-02-12 11:19 ` Jakub Jelinek
2018-02-12 12:21 ` Oleg Endo
2018-02-12 12:49 ` Jakub Jelinek
2018-02-12 13:27 ` Sebastian Perta
2018-02-12 13:49 ` Jakub Jelinek [this message]
2018-02-12 13:37 ` Sebastian Perta
2018-02-12 16:49 ` Jakub Jelinek
-- strict thread matches above, loose matches on Subject: below --
2018-02-06 13:43 Sebastian Perta
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=20180212133011.GB5867@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nickc@redhat.com \
--cc=sebastian.perta@renesas.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).