From: Jeff Law <law@redhat.com>
To: gcc-patches@gcc.gnu.org, richard.sandiford@arm.com
Subject: Re: [PING] Use cmpstr and cmpstrn optabs
Date: Mon, 24 Aug 2015 17:26:00 -0000 [thread overview]
Message-ID: <55DB5369.1050007@redhat.com> (raw)
In-Reply-To: <87wpwl6imi.fsf@e105548-lin.cambridge.arm.com>
On 08/24/2015 05:17 AM, Richard Sandiford wrote:
> Originally posted here:
>
> https://gcc.gnu.org/ml/gcc-patches/2015-07/msg02660.html
>
> Kaz approved the SH parts and reported that there were no new failures
> on sh4-unknown-linux-gnu (thanks).
Sorry, this must have slipped through the cracks. Thanks for pinging it.
>> * builtins.c (expand_cmpstr, expand_cmpstrn): New functions.
>> (expand_builtin_strcmp, expand_builtin_strncmp): Use them. Remove
>> references to HAVE_cmpstr{,n}si and CODE_FOR_cmpstr{,n}si.
>> * config/m32c/blkmov.md (cmpstrsi): Fix predicates of operands 1 and 2.
>> Add predicates for operands 0 and 3.
>> * config/rx/rx.md (cmpstrnsi): Remove force_operand for the length
>> operand.
>> * config/sh/sh.md (cmpstrnsi): Change the length predicate from
>> immediate_operand to nonmemory_operand.
OK.
jeff
prev parent reply other threads:[~2015-08-24 17:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 12:16 Richard Sandiford
2015-08-01 9:28 ` Kaz Kojima
2015-08-24 11:19 ` [PING] " Richard Sandiford
2015-08-24 17:26 ` Jeff Law [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=55DB5369.1050007@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.sandiford@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).