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.
To wit: the to-be-posted patch in bug 675078 removes jslock.cpp and almost all of jslock.h.
Depends on: 931151
JS_THREADSAFE was removed in bug 1031529, so this bug is probably no longer actionable, therefore closing as INCOMPLETE.
Status: NEW → RESOLVED
Last Resolved: 11 months ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.