From: Josh Triplett <josh@freedesktop.org>
To: Al Viro <viro@ftp.linux.org.uk>, linux-sparse@vger.kernel.org
Subject: Re: [PATCH] switch to hash-based get_one_special()
Date: Tue, 24 Oct 2006 08:42:34 -0700 [thread overview]
Message-ID: <453E346A.1010203@freedesktop.org> (raw)
In-Reply-To: <20061001185502.GA29920@ftp.linux.org.uk>
Al Viro wrote:
> Weird, but true: the set of C two-character punctuators and
> two-symbol prefices of three-character punctuators is
> distinguishable by 5-bit hash function (27 out of 32).
> Application is obvious - we get much faster get_one_special()
> out of that...
>
> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
> ---
>
> [and now all patches older than a month are gone]
>
> token.h | 18 +++++++-------
> tokenize.c | 78 +++++++++++++++++++++++++++++++++++++++++++++++++++---------
> 2 files changed, 75 insertions(+), 21 deletions(-)
Added to my sparse tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/josh/sparse.git
Thanks,
Josh Triplett
prev parent reply other threads:[~2006-10-24 15:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-01 18:55 [PATCH] switch to hash-based get_one_special() Al Viro
2006-10-24 15:42 ` Josh Triplett [this message]
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=453E346A.1010203@freedesktop.org \
--to=josh@freedesktop.org \
--cc=linux-sparse@vger.kernel.org \
--cc=viro@ftp.linux.org.uk \
/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).