public inbox for glibc-bugs-regex@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs-regex@sourceware.org
Subject: [Bug regex/1302] improve regex bitset performance (don't assume 32 bits)
Date: Wed, 05 Aug 2020 06:52:05 +0000 [thread overview]
Message-ID: <bug-1302-132-BTRnmNCWD5@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-1302-132@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=1302
--- Comment #4 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Paul Eggert <eggert@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=2cc478ed1be82711a6cac15aae683530b2e6732b
commit 2cc478ed1be82711a6cac15aae683530b2e6732b
Author: Paul Eggert <eggert@cs.ucla.edu>
Date: Tue Aug 4 23:45:27 2020 -0700
Copy regex_internal.h from Gnulib
Sync this file from Gnulib, thus incorporating the following
fix for a bug with regexps with 16 or more subexpressions:
* posix/regex_internal.h (struct re_backref_cache_entry):
Use bitset_word_t as the type of eps_reachable_subexps_map,
instead of unsigned short int. This fixes a bug I introduced
to glibc in 2005-09-28T17:33:18Z!drepper@redhat.com (glibc commit
2c05d33f90861d074dc12808dafbde30f487b1a0, BZ #1302).
Remove unused member 'unused'.
--
You are receiving this mail because:
You are on the CC list for the bug.
next parent reply other threads:[~2020-08-05 6:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-1302-132@http.sourceware.org/bugzilla/>
2020-08-05 6:52 ` cvs-commit at gcc dot gnu.org [this message]
2005-09-06 7:32 [Bug regex/1302] New: " eggert at gnu dot org
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=bug-1302-132-BTRnmNCWD5@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs-regex@sourceware.org \
/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).