From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: [PATCH] Clean but not very effective optimization (lex.c / dupstring_wlen)
Date: Wed, 17 Oct 2018 00:08:01 +0200 [thread overview]
Message-ID: <CAKc7PVCmFWuAzDbO-_r_FJKZ3AwoCCvuiCO212gGyJ-S2U=uUQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 782 bytes --]
Hello,
dupstring_wlen (i.e. with-len) is ready to use, so this patch is just
4 changes dupstring(s) -> dupstring_wlen(s, l). Each of those
dupstrings has a nice strlen() invocation already there in lex.c, a
few lines above.
Callgrind doesn't report any real change in number of instructions of
strlen() call and a test that repeatedly invokes (z) flag on a 32-line
buffer 150 times reports 24 ms for both unoptimized and optimized
version.
However performance test of F-Sy-Highlighting reports rather stable 40
ms gain – out of ~3000 ms, so not much.
In general simplicity of this patch made me send it.
--
Sebastian Gniazdowski
News: https://twitter.com/ZdharmaI
IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zplugin
Blog: http://zdharma.org
[-- Attachment #2: lex_4strlens.diff.txt --]
[-- Type: text/plain, Size: 1180 bytes --]
diff --git a/Src/lex.c b/Src/lex.c
index 44ad880..fa29da3 100644
--- a/Src/lex.c
+++ b/Src/lex.c
@@ -1626,7 +1626,7 @@ parsestrnoerr(char **s)
zcontext_save();
untokenize(*s);
- inpush(dupstring(*s), 0, NULL);
+ inpush(dupstring_wlen(*s, l), 0, NULL);
strinbeg(0);
lexbuf.len = 0;
lexbuf.ptr = tokstr = *s;
@@ -1658,7 +1658,7 @@ parse_subscript(char *s, int sub, int endchar)
if (!*s || *s == endchar)
return 0;
zcontext_save();
- untokenize(t = dupstring(s));
+ untokenize(t = dupstring_wlen(s, l));
inpush(t, 0, NULL);
strinbeg(0);
/*
@@ -1674,7 +1674,7 @@ parse_subscript(char *s, int sub, int endchar)
* length preservation.
*/
lexbuf.len = 0;
- lexbuf.ptr = tokstr = dupstring(s);
+ lexbuf.ptr = tokstr = dupstring_wlen(s, l);
lexbuf.siz = l + 1;
err = dquote_parse(endchar, sub);
toklen = (int)(lexbuf.ptr - tokstr);
@@ -1713,7 +1713,7 @@ parse_subst_string(char *s)
return 0;
zcontext_save();
untokenize(s);
- inpush(dupstring(s), 0, NULL);
+ inpush(dupstring_wlen(s, l), 0, NULL);
strinbeg(0);
lexbuf.len = 0;
lexbuf.ptr = tokstr = s;
next reply other threads:[~2018-10-16 22:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 22:08 Sebastian Gniazdowski [this message]
2018-10-16 22:24 ` Sebastian Gniazdowski
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='CAKc7PVCmFWuAzDbO-_r_FJKZ3AwoCCvuiCO212gGyJ-S2U=uUQ@mail.gmail.com' \
--to=sgniazdowski@gmail.com \
--cc=zsh-workers@zsh.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).