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/605] regex goes uselessly through slow paths
Date: Tue, 28 Dec 2004 16:33:00 -0000 [thread overview]
Message-ID: <20041228163305.5581.qmail@sourceware.org> (raw)
In-Reply-To: <20041210165352.605.bonzini@gnu.org>
------- Additional Comments From bonzini at gnu dot org 2004-12-28 16:33 -------
Here it is. The only changes were in the context.
2004-12-28 Paolo Bonzini <bonzini@gnu.org>
* lib/regcomp.c (parse_bracket_exp): Do not modify DFA nodes
that were already created.
* lib/regex_internal.c (re_dfa_add_node): Set accept_mb field
in the token if needed.
(create_ci_newstate, create_cd_newstate): Set accept_mb field
from the tokens' field.
* lib/regex_internal.h (re_token_t): Add accept_mb field.
(ACCEPT_MB_NODE): Removed.
* lib/regexec.c (proceed_next_node, transit_states_mb,
build_sifted_states, check_arrival_add_next_nodes): Use
accept_mb instead of ACCEPT_MB_NODE.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |ASSIGNED
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.
next prev parent reply other threads:[~2004-12-28 16:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-10 16:54 [Bug regex/605] New: " bonzini at gnu dot org
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 [this message]
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=20041228163305.5581.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).