public inbox for glibc-bugs-regex@sourceware.org
help / color / mirror / Atom feed
From: "bonzini at gnu dot org" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs-regex@sources.redhat.com
Subject: [Bug regex/558] regcomp and regexec bug
Date: Mon, 22 Nov 2004 09:15:00 -0000	[thread overview]
Message-ID: <20041122091537.27856.qmail@sourceware.org> (raw)
In-Reply-To: <20041118020600.558.vprodan.hosting@artstyle.ru>


------- Additional Comments From bonzini at gnu dot org  2004-11-22 09:15 -------
It can be fixed by lowering for example .{1,5} to (.(.(.(..?)?)?)?)? instead 
of .?.?.?.?.? --- of course the brackets are not capturing, they're only there 
to show what is the question mark applied to.

This has the property of making all the period nodes epsilon-transit to the end 
of the braced expression, rather than to the next period.  The epsilon closure 
thus is much smaller.

Another improvement is to use a special version of re_node_set_insert in 
calc_inveclosure, since we know that the node is being added at the end of the 
set.  I have a patch to do that and it obtains a 30% improvement on this test 
case.  It does not cure the complexity problem though, so I am not submitting 
it yet.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|gotom at debian dot or dot  |bonzini at gnu dot org
                   |jp                          |
             Status|NEW                         |ASSIGNED


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

------- 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-11-22  9:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-18  2:06 [Bug regex/558] New: " vprodan dot hosting at artstyle dot ru
2004-11-22  9:15 ` bonzini at gnu dot org [this message]
2004-11-23 12:31 ` [Bug regex/558] " bonzini at gnu dot org
2004-11-23 12:32 ` bonzini at gnu dot org
2004-12-10 16:56 ` bonzini at gnu dot org
2005-01-27 19:08 ` 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=20041122091537.27856.qmail@sourceware.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).