From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24730 invoked by alias); 11 Jan 2010 17:55:30 -0000 Received: (qmail 24627 invoked by uid 48); 11 Jan 2010 17:55:17 -0000 Date: Mon, 11 Jan 2010 17:55:00 -0000 Message-ID: <20100111175517.24626.qmail@sourceware.org> From: "bonzini at gnu dot org" To: glibc-bugs-regex@sources.redhat.com In-Reply-To: <20100111094018.11159.extproxy@gmail.com> References: <20100111094018.11159.extproxy@gmail.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug regex/11159] lock contention within regexec() when used from multiple threads X-Bugzilla-Reason: CC Mailing-List: contact glibc-bugs-regex-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-regex-owner@sourceware.org X-SW-Source: 2010-01/txt/msg00005.txt.bz2 ------- Additional Comments From bonzini at gnu dot org 2010-01-11 17:55 ------- The fact that is "const" does not mean that no internal data structures are modified (and this needs locking). C++ even has a "mutable" keyword for this. glibc does the locking per-regex_t. Could be a doc bug, leaving this decision to the glibc maintainers. -- 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.