public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bonzini at gnu dot org" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs@sources.redhat.com
Subject: [Bug regex/605] New: regex goes uselessly through slow paths
Date: Fri, 10 Dec 2004 16:54:00 -0000	[thread overview]
Message-ID: <20041210165352.605.bonzini@gnu.org> (raw)

An improvement of 10-30% in the speed of the matcher (LC_ALL=C or other
single-byte character sets) can be achieved by avoiding that OP_PERIOD goes
through the slow multibyte paths.  This is done by the attached patch.

While this patch only affects SBCS (i.e. scripts, which are starting to use
LC_ALL=C to avoid bugs due to the collation rules of some languages), in
principle UTF-8 optimization could be fixed to be optimizable as well.  The
slowness of prune_impossible_nodes, alas, makes this impractical yet.

-- 
           Summary: regex goes uselessly through slow paths
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: regex
        AssignedTo: bonzini at gnu dot org
        ReportedBy: bonzini at gnu dot org
                CC: glibc-bugs-regex at sources dot redhat dot com,glibc-
                    bugs at sources dot redhat dot com
OtherBugsDependingO 500
             nThis:


http://sources.redhat.com/bugzilla/show_bug.cgi?id=605

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


             reply	other threads:[~2004-12-10 16:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-10 16:54 bonzini at gnu dot org [this message]
2004-12-10 16:55 ` [Bug regex/605] " bonzini at gnu dot org
2004-12-20 10:21 ` bonzini at gnu dot org
2004-12-20 10:23 ` bonzini at gnu dot org
2004-12-27 16:40 ` drepper at redhat dot com
2004-12-28 16:33 ` bonzini at gnu dot org
2004-12-28 16:34 ` bonzini at gnu dot org
2005-01-21 14:01 ` bonzini at gnu dot org
2005-01-26 22:28 ` drepper at redhat dot com

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=20041210165352.605.bonzini@gnu.org \
    --to=sourceware-bugzilla@sources.redhat.com \
    --cc=glibc-bugs@sources.redhat.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).