public inbox for glibc-bugs-regex@sourceware.org
help / color / mirror / Atom feed
From: "bonzini at gnu dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs-regex@sources.redhat.com
Subject: [Bug regex/11159] lock contention within regexec() when used from multiple threads
Date: Mon, 11 Jan 2010 18:03:00 -0000 [thread overview]
Message-ID: <20100111180335.30967.qmail@sourceware.org> (raw)
In-Reply-To: <20100111094018.11159.extproxy@gmail.com>
------- Additional Comments From bonzini at gnu dot org 2010-01-11 18:03 -------
regexec converts the NFA to DFA on demand, so the DFA representation is locked
(and some more stuff too, but TLS could indeed be used for that because it is
per-match data; DFA states are persistent).
--
http://sourceware.org/bugzilla/show_bug.cgi?id=11159
------- 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:[~2010-01-11 18:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 9:40 [Bug regex/11159] New: " extproxy at gmail dot com
2010-01-11 9:58 ` [Bug regex/11159] " schwab at linux-m68k dot org
2010-01-11 17:46 ` extproxy at gmail dot com
2010-01-11 17:55 ` bonzini at gnu dot org
2010-01-11 18:01 ` extproxy at gmail dot com
2010-01-11 18:03 ` bonzini at gnu dot org [this message]
2010-01-15 7:51 ` drepper at redhat dot com
[not found] <bug-11159-132@http.sourceware.org/bugzilla/>
2014-06-30 20:24 ` fweimer 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=20100111180335.30967.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--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).