public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Paul Eggert <eggert@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] Copy regex_internal.h from Gnulib
Date: Wed,  5 Aug 2020 06:52:04 +0000 (GMT)	[thread overview]
Message-ID: <20200805065204.A1C2A3842413@sourceware.org> (raw)

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'.

Diff:
---
 posix/regex_internal.h | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/posix/regex_internal.h b/posix/regex_internal.h
index e9aa74bf33..8c42586c42 100644
--- a/posix/regex_internal.h
+++ b/posix/regex_internal.h
@@ -591,9 +591,8 @@ struct re_backref_cache_entry
   Idx str_idx;
   Idx subexp_from;
   Idx subexp_to;
+  bitset_word_t eps_reachable_subexps_map;
   char more;
-  char unused;
-  unsigned short int eps_reachable_subexps_map;
 };
 
 typedef struct


                 reply	other threads:[~2020-08-05  6:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20200805065204.A1C2A3842413@sourceware.org \
    --to=eggert@sourceware.org \
    --cc=glibc-cvs@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).