From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15999 invoked by alias); 11 Jan 2010 17:46:07 -0000 Received: (qmail 15841 invoked by uid 48); 11 Jan 2010 17:45:45 -0000 Date: Mon, 11 Jan 2010 17:46:00 -0000 Message-ID: <20100111174545.15840.qmail@sourceware.org> From: "extproxy at gmail dot com" 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/msg00004.txt.bz2 ------- Additional Comments From extproxy at gmail dot com 2010-01-11 17:45 ------- > Use a separate regex_t object in each thread. Why is that ? The regexec() interface takes in a 'const regex_t *' object. This implies multiple threads can use the same object. In my program, all threads work with the same regular expression. So why use a different regex_t object ? At the very least, the regexec() documentation needs to clarify this performance limitation. I'm re-opening this bug - please change title if necessary to a doc bug if you still don't agree that this should be fixed. -- What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | 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.