This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.

Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] Make regexec thread-safe (BZ #934)

From: Ulrich Drepper <drepper at redhat dot com>
To: Jakub Jelinek <jakub at redhat dot com>
Cc: Glibc hackers <libc-hacker at sources dot redhat dot com>
Date: Fri, 06 May 2005 16:32:36 -0700
Subject: Re: [PATCH] Make regexec thread-safe (BZ #934)
References: <20050506093822.GM22843@sunsite.mff.cuni.cz>

Jakub Jelinek wrote:
> regexec is not listed in POSIX thread-safety exemption table and furthermore
> http://www.opengroup.org/onlinepubs/009695399/functions/regcomp.html
> has:
> "The interface is defined so that the matched substrings rm_sp and rm_ep
> are in a separate regmatch_t structure instead
> of in regex_t. This allows a single compiled RE to be used
> simultaneously in several contexts; in main() and a signal
> handler, perhaps, or in multiple threads of lightweight processes."

The latter is not in normative text and the former doesn't really mean
that this kind of concurrency is required.  Using the same regex_t
concurrently is unspecified.

Having said this, it certainly is a useful and not too expensive
extension.  I added the patch.

-- 
â Ulrich Drepper â Red Hat, Inc. â 444 Castro St â Mountain View, CA â

Attachment: signature.asc
Description: OpenPGP digital signature

References:
- [PATCH] Make regexec thread-safe (BZ #934)
  - From: Jakub Jelinek

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]