Closed
Bug 716033
Opened 13 years ago
Closed 12 years ago
Move write barriers from jsapi.h to jsfriendapi.h
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
mozilla12
People
(Reporter: billm, Assigned: billm)
Details
Attachments
(1 file)
14.81 KB,
patch
|
luke
:
review+
bholley
:
review+
|
Details | Diff | Splinter Review |
I no longer have much faith left that outside developers will be able to correctly implement write barriers. So this patch moves the API to jsfriendapi.h, and also simplifies it somewhat. I also changed the SetProto barrier on XPCWrappedNative. Previously, the barrier used the existing tracing code to trace the wrapped native's proto. Now it uses a special write barrier call instead. The reason to do this is that it doesn't require a JSTracer. Requiring the runtime to have a JSTracer for XPConnect barriers is troublesome because of thread safety issues. Most of these are JSAPI changes for Luke. Also asking for Bobby's review of the XPConnect changes.
Attachment #586543 -
Flags: review?(luke)
Attachment #586543 -
Flags: review?(bobbyholley+bmo)
Updated•13 years ago
|
Attachment #586543 -
Flags: review?(luke) → review+
Updated•12 years ago
|
Attachment #586543 -
Flags: review?(bobbyholley+bmo) → review+
Assignee | ||
Comment 1•12 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/b1d7e7ac1b77
Target Milestone: --- → mozilla12
Comment 2•12 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/b1d7e7ac1b77
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•