[Issue 13672] New: core.thread.Thread.start holds "slock" unnecessarily
via Digitalmars-d-bugs
digitalmars-d-bugs at puremagic.com
Sun Nov 2 09:02:14 PST 2014
https://issues.dlang.org/show_bug.cgi?id=13672
Issue ID: 13672
Summary: core.thread.Thread.start holds "slock" unnecessarily
Product: D
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P1
Component: druntime
Assignee: nobody at puremagic.com
Reporter: sean at invisibleduck.org
Looking at Thread.start, the bulk of the body of this function holds the global
"slock" and I can't figure out why. Most or all of the calls inside this lock
are either local operations or are already atomic. What actually needs to be
made mutually exclusive here? This seems like an easy candidate for
optimization.
--
More information about the Digitalmars-d-bugs
mailing list