Closed
Bug 639227
Opened 13 years ago
Closed 13 years ago
one trace hook is enough, really
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: gal, Assigned: gal)
References
Details
(Whiteboard: fixed-in-tracemonkey)
Attachments
(1 file, 2 obsolete files)
|
18.36 KB,
patch
|
dvander
:
review+
|
Details | Diff | Splinter Review |
We have a trace hook in ObjectOps and one in JSClass. non-native objects always also have a specific class, so we can as well always use that hook.
|
Assignee | |
Comment 1•13 years ago
|
||
Assignee: general → gal
|
|
Assignee | |
Comment 2•13 years ago
|
||
Attachment #517180 -
Attachment is obsolete: true
|
|
Assignee | |
Comment 3•13 years ago
|
||
Note that this is not an API change.
Attachment #517181 -
Attachment is obsolete: true
|
||
Updated•13 years ago
|
Attachment #517183 -
Flags: review+
|
|
Assignee | |
Comment 4•13 years ago
|
||
http://hg.mozilla.org/tracemonkey/rev/68352f572399
Whiteboard: fixed-in-tracemonkey
|
|
Assignee | |
Comment 5•13 years ago
|
||
Re-landed with a tiny fix (class trace hook has to be triggered for non-native objects too of course). http://hg.mozilla.org/tracemonkey/rev/5e8744f7c31a
|
||
Comment 6•13 years ago
|
||
http://hg.mozilla.org/mozilla-central/rev/5e8744f7c31a
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•