From: "Ondřej Bílka" <neleai@seznam.cz>
To: Wilco Dijkstra <wdijkstr@arm.com>
Cc: azanella@linux.vnet.ibm.com, libc-alpha@sourceware.org
Subject: Re: [PATCH] Improve performance of strncpy
Date: Sun, 23 Nov 2014 16:52:00 -0000 [thread overview]
Message-ID: <20141123165227.GA27543@domone> (raw)
In-Reply-To: <001a01cfefa3$0fb21330$2f163990$@com>
On Fri, Oct 24, 2014 at 04:56:23PM +0100, Wilco Dijkstra wrote:
> Ping (there was some further discussion but I don't see an OK for this patch)
>
Looks ok, any reason why not simplify it more to strnlen+memcpy+memset?
next prev parent reply other threads:[~2014-11-23 16:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 15:56 Wilco Dijkstra
2014-11-23 16:52 ` Ondřej Bílka [this message]
2014-11-27 19:20 ` Wilco Dijkstra
2014-11-27 20:51 ` Ondřej Bílka
-- strict thread matches above, loose matches on Subject: below --
2014-09-10 15:21 Wilco Dijkstra
2014-09-10 17:34 ` Florian Weimer
2014-09-10 18:02 ` Rich Felker
2014-09-10 18:25 ` Wilco Dijkstra
2014-09-11 19:37 ` Wilco Dijkstra
2014-09-12 6:22 ` Ondřej Bílka
2014-09-12 11:04 ` Wilco Dijkstra
2014-09-10 18:09 ` Wilco Dijkstra
2014-08-20 12:44 Wilco Dijkstra
2014-08-22 12:02 ` Adhemerval Zanella
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=20141123165227.GA27543@domone \
--to=neleai@seznam.cz \
--cc=azanella@linux.vnet.ibm.com \
--cc=libc-alpha@sourceware.org \
--cc=wdijkstr@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).