public inbox for glibc-bugs-regex@sourceware.org
help / color / mirror / Atom feed
From: "eggert at gnu dot org" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs-regex@sources.redhat.com
Subject: [Bug regex/1302] New: improve regex bitset performance (don't assume 32 bits)
Date: Tue, 06 Sep 2005 07:32:00 -0000	[thread overview]
Message-ID: <20050906073220.1302.eggert@gnu.org> (raw)

The regex bitset code currently uses an array of unsigned int words to
represent a bitset, and assumes these words are exactly 32 bits wide.
On modern 64-bit hosts, using a 64-bit word would require
approximately half the instructions for the bitset-related code.
Also, it's better not to assume 32-bits everywhere.  I'll attach a
patch.

-- 
           Summary: improve regex bitset performance (don't assume 32 bits)
           Product: glibc
           Version: 2.3.5
            Status: NEW
          Severity: normal
          Priority: P2
         Component: regex
        AssignedTo: gotom at debian dot or dot jp
        ReportedBy: eggert at gnu dot org
                CC: glibc-bugs-regex at sources dot redhat dot com,glibc-
                    bugs at sources dot redhat dot com
 BugsThisDependsOn: 1278,1285


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

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


             reply	other threads:[~2005-09-06  7:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-06  7:32 eggert at gnu dot org [this message]
2005-09-06  7:33 ` [Bug regex/1302] " eggert at gnu dot org
2005-09-06 17:48 ` eggert at gnu dot org
2005-09-06 23:30 ` drepper at redhat dot com
2005-09-28 17:33 ` drepper at redhat dot com
2006-04-25 18:21 ` 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=20050906073220.1302.eggert@gnu.org \
    --to=sourceware-bugzilla@sources.redhat.com \
    --cc=glibc-bugs-regex@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).