From: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Cc: nd <nd@arm.com>
Subject: Re: [PATCH] Improve strtok(_r) performance
Date: Mon, 14 Nov 2016 12:50:00 -0000 [thread overview]
Message-ID: <AM5PR0802MB26108ACD41E28FA333134D5C83BC0@AM5PR0802MB2610.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <fa025578-1b1e-35b0-6477-fc109fa62e67@linaro.org>
Adhemerval Zanella <adhemerval.zanella@linaro.org> wrote:
> Why not aim for simplicity and just use strtok_r and strtok? I should
> be a tail call in most architecture and performance loss should be
> minimum.
You mean avoiding the duplication of code? Say inlining or tailcalling
strtok_r in string/strtok_r.c?
Wilco
next prev parent reply other threads:[~2016-11-14 12:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 11:35 Wilco Dijkstra
2016-11-04 12:55 ` Adhemerval Zanella
2016-11-14 12:21 ` Wilco Dijkstra
2016-11-14 12:26 ` Adhemerval Zanella
2016-11-14 12:50 ` Wilco Dijkstra [this message]
2016-11-14 12:57 ` Adhemerval Zanella
2016-11-16 17:06 ` [PATCH v2] " Wilco Dijkstra
2016-11-16 18:07 ` Andreas Schwab
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=AM5PR0802MB26108ACD41E28FA333134D5C83BC0@AM5PR0802MB2610.eurprd08.prod.outlook.com \
--to=wilco.dijkstra@arm.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
--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).