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/506] New: there is dead code in regex Date: Thu, 04 Nov 2004 08:59:00 -0000 [thread overview] Message-ID: <20041104085902.506.bonzini@gnu.org> (raw) The flurry of algorithms to efficiently implement backreferences left behind some dead code in regex. The patch at http://sources.redhat.com/ml/libc-alpha/2004-11/msg00016.html removes several unused parameters and struct fields. The most egregious is the "flag" struct re_backref_cache_entry field. Removing it turned a potentially quadratic loop into linear, though I did not try to find a case in which this actually happened. In another case, it looks like changing the algorithms would have required changing the node_set passed to sift_states_bkref, but this was not done. So this patch does that instead of only removing the unused parameter. -- Summary: there is dead code in regex 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=506 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2004-11-04 8:59 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-11-04 8:59 bonzini at gnu dot org [this message] 2004-11-09 7:49 ` [Bug regex/506] " bonzini at gnu dot org
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=20041104085902.506.bonzini@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: linkBe 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).