From: Jeff Law <law@redhat.com>
To: Wilco Dijkstra <Wilco.Dijkstra@arm.com>,
Bernd Schmidt <bschmidt@redhat.com>,
Richard Biener <richard.guenther@gmail.com>,
Jakub Jelinek <jakub@redhat.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>, nd <nd@arm.com>
Subject: Re: [PATCH] Optimize strchr (s, 0) to strlen
Date: Fri, 16 Sep 2016 15:37:00 -0000 [thread overview]
Message-ID: <9ca47fb1-c87a-7ef9-863e-6a508e4d5b3b@redhat.com> (raw)
In-Reply-To: <VI1PR0802MB2621668084642DB028635B8883F30@VI1PR0802MB2621.eurprd08.prod.outlook.com>
On 09/16/2016 07:28 AM, Wilco Dijkstra wrote:
>
> I noticed rawmemchr taking non-trivial amounts of time in various profiles
> despite no use of rawmemchr in any of the source code. It's apparently a
> common idiom to use strchr (s, 0) to find the end of a string.
A bit of a surprise, but it is what it is I guess.
jeff
prev parent reply other threads:[~2016-09-16 15:27 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 17:01 Wilco Dijkstra
2016-04-18 17:09 ` Jakub Jelinek
2016-04-18 17:31 ` Wilco Dijkstra
2016-04-18 22:55 ` Oleg Endo
2016-04-19 8:14 ` Richard Biener
2016-04-19 16:33 ` Wilco Dijkstra
2016-04-20 8:45 ` Richard Biener
2016-04-20 9:44 ` Richard Biener
2016-04-20 10:33 ` Jakub Jelinek
2016-04-20 10:50 ` Richard Biener
2016-04-20 11:17 ` Wilco Dijkstra
2016-04-20 13:01 ` Jakub Jelinek
2016-04-20 14:18 ` Wilco Dijkstra
2016-04-20 11:57 ` Wilco Dijkstra
2016-04-20 11:59 ` Richard Biener
2016-05-04 12:54 ` Wilco Dijkstra
2016-05-18 12:29 ` Wilco Dijkstra
2016-05-18 13:22 ` Richard Biener
2016-09-13 12:39 ` Wilco Dijkstra
2016-09-13 12:46 ` Oleg Endo
2016-09-14 13:46 ` Richard Biener
2016-09-14 13:55 ` Jakub Jelinek
2016-09-14 17:07 ` Szabolcs Nagy
2016-09-15 8:15 ` Richard Biener
2016-09-15 8:28 ` Jakub Jelinek
2016-09-15 13:51 ` Wilco Dijkstra
2016-09-15 14:17 ` Jakub Jelinek
2016-09-15 14:29 ` Szabolcs Nagy
2016-09-15 14:45 ` Jakub Jelinek
2016-09-15 15:04 ` Wilco Dijkstra
2016-09-15 15:28 ` Jakub Jelinek
2016-09-15 15:31 ` Wilco Dijkstra
2016-09-15 15:48 ` Jakub Jelinek
2016-09-15 16:46 ` Wilco Dijkstra
2016-09-15 14:24 ` Bernd Schmidt
2016-09-16 13:41 ` Wilco Dijkstra
2016-09-16 15:37 ` 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=9ca47fb1-c87a-7ef9-863e-6a508e4d5b3b@redhat.com \
--to=law@redhat.com \
--cc=Wilco.Dijkstra@arm.com \
--cc=bschmidt@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=nd@arm.com \
--cc=richard.guenther@gmail.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).