Closed
Bug 720018
Opened 13 years ago
Closed 7 years ago
consider removing dependency on NSPR and JS_THREADSAFE
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: igor, Unassigned)
References
Details
With bug 675078 and bug 720013 fixed the difference between JS_THREADSAFE and !JS_THREADSAFE builds will be in the support of the background finalization and allocation thread and the corresponding locking. That can be coded in a straightforward way using the corresponding Windows and Posix API directly removing the dependency on NSPR and eliminating the need for JS_THREADSAFE.
Comment 1•13 years ago
|
||
To wit: the to-be-posted patch in bug 675078 removes jslock.cpp and almost all of jslock.h.
Depends on: 931151
Updated•11 years ago
|
Assignee | ||
Updated•10 years ago
|
Assignee: general → nobody
Comment 2•7 years ago
|
||
JS_THREADSAFE was removed in bug 1031529, so this bug is probably no longer actionable, therefore closing as INCOMPLETE.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•