Last Comment Bug 720018 - consider removing dependency on NSPR and JS_THREADSAFE
: consider removing dependency on NSPR and JS_THREADSAFE
Status: NEW
:
Product: Core
Classification: Components
Component: JavaScript Engine (show other bugs)
: unspecified
: All All
: -- normal with 5 votes (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
:
Mentors:
Depends on: 650411 675078 720013 720045 931151 956899
Blocks: 719858
  Show dependency treegraph
 
Reported: 2012-01-20 14:52 PST by Igor Bukanov
Modified: 2014-07-24 11:07 PDT (History)
15 users (show)
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Attachments

Description Igor Bukanov 2012-01-20 14:52:41 PST
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 Luke Wagner [:luke] 2012-01-20 14:54:54 PST
To wit: the to-be-posted patch in bug 675078 removes jslock.cpp and almost all of jslock.h.

Note You need to log in before you can comment on or make changes to this bug.