This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


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

[Bug regex/11159] lock contention within regexec() when used from multiple threads


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


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