From: eijiro_sumii@anet.ne.jp
To: checker@d6.com
Cc: caml-list@inria.fr, gerd@gerd-stolpmann.de,
sumii@venus.is.s.u-tokyo.ac.jp
Subject: Re: substring match like "strstr"
Date: Thu, 14 Dec 2000 17:02:37 +0900 [thread overview]
Message-ID: <20001214170237M.sumii@yl.is.s.u-tokyo.ac.jp> (raw)
In-Reply-To: <4.3.2.7.2.20001213223322.00cb3c90@shell16.ba.best.com>
> Is that C the simple C one I posted, or the libc one on sparc?
It's the one in libc on Solaris, so may be tuned by hand in assembly.
> Your new strstr is actually slower on x86 than your first one, but I
> haven't looked into why yet.
That's interesting. I confirmed it myself on my x86 machine with my
program:
strstr_imp2 88.530
strstr_fun 124.210
strstr_fun2 127.120
glibc strstr 61.310
Seeing such strong machine dependency, it seems yet more reasonable to
use the "default" strstr provided by the system (unless the _pattern_
is long enough, in which case KMP or BM might perform better), even
though there is some overhead --- about 5% in my profiling on SPARC
--- of interfacing a C function to OCaml. This is a natural (though
boring) conclusion, I think.
Eijiro
next prev parent reply other threads:[~2000-12-14 18:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-08 6:04 eijiro_sumii
2000-12-08 12:57 ` Gerd Stolpmann
2000-12-10 13:16 ` eijiro_sumii
2000-12-10 15:39 ` Gerd Stolpmann
2000-12-11 3:57 ` eijiro_sumii
2000-12-12 13:58 ` Julian Assange
2000-12-11 21:07 ` Chris Hecker
2000-12-11 22:22 ` Gerd Stolpmann
2000-12-12 5:06 ` Chris Hecker
2000-12-12 12:28 ` Jean-Christophe Filliatre
2000-12-13 10:02 ` eijiro_sumii
2000-12-13 10:17 ` Eijiro Sumii
2000-12-13 10:53 ` Julian Assange
2000-12-13 13:28 ` Eijiro Sumii
2000-12-12 3:28 ` eijiro_sumii
2000-12-13 1:12 ` John Prevost
2000-12-13 2:35 ` Chris Hecker
2000-12-12 10:07 ` Sven LUTHER
2000-12-14 3:36 ` eijiro_sumii
2000-12-14 6:48 ` Chris Hecker
2000-12-14 8:02 ` eijiro_sumii [this message]
2000-12-14 21:53 ` Stephan Tolksdorf
2000-12-14 21:12 Ruchira Datta
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=20001214170237M.sumii@yl.is.s.u-tokyo.ac.jp \
--to=eijiro_sumii@anet.ne.jp \
--cc=caml-list@inria.fr \
--cc=checker@d6.com \
--cc=gerd@gerd-stolpmann.de \
--cc=sumii@venus.is.s.u-tokyo.ac.jp \
/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 NNTP newsgroup(s).