This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] Improve strtok(_r) performance

From: Adhemerval Zanella <adhemerval dot zanella at linaro dot org>
To: Wilco Dijkstra <Wilco dot Dijkstra at arm dot com>, "libc-alpha at sourceware dot org" <libc-alpha at sourceware dot org>
Cc: nd <nd at arm dot com>
Date: Mon, 14 Nov 2016 10:56:44 -0200
Subject: Re: [PATCH] Improve strtok(_r) performance
Authentication-results: sourceware.org; auth=none
References: <AM5PR0802MB2610F3F2F9864ECF0089F9E583AD0@AM5PR0802MB2610.eurprd08.prod.outlook.com> <AM5PR0802MB261081079A9A4BC050B185E483BC0@AM5PR0802MB2610.eurprd08.prod.outlook.com> <fa025578-1b1e-35b0-6477-fc109fa62e67@linaro.org> <AM5PR0802MB26108ACD41E28FA333134D5C83BC0@AM5PR0802MB2610.eurprd08.prod.outlook.com>


On 14/11/2016 10:50, Wilco Dijkstra wrote:
> 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

Yes.

Follow-Ups:
- [PATCH v2] Improve strtok(_r) performance
  - From: Wilco Dijkstra

References:
- Re: [PATCH] Improve strtok(_r) performance
  - From: Wilco Dijkstra
- Re: [PATCH] Improve strtok(_r) performance
  - From: Adhemerval Zanella
- Re: [PATCH] Improve strtok(_r) performance
  - From: Wilco Dijkstra

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]