Closed
Bug 579100
Opened 14 years ago
Closed 14 years ago
eliminating leftovers of heap-allocated doubles from jsgc.cpp
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
People
(Reporter: igor, Assigned: igor)
References
Details
(Whiteboard: fixed-in-tracemonkey)
Attachments
(1 file, 1 obsolete file)
30.89 KB,
patch
|
gwagner
:
review+
|
Details | Diff | Splinter Review |
As a leftover of slim values era jsgc.cpp still contains a few comments or struct definitions related to heap-allocated doubles. That should be removed.
Assignee | ||
Updated•14 years ago
|
Summary: eliminating traces of heap-allocated doubles from jsgc.cpp → eliminating leftovers of heap-allocated doubles from jsgc.cpp
Comment 1•14 years ago
|
||
There is also the HasMarkedDoubles function left.
Assignee | ||
Comment 2•14 years ago
|
||
Besides fixing comments/structs to remove double GC heap leftovers the patch does few more cleanups. In particular, JSGCTracer is renamed into js::GCMarker and all delayed marking-related fields are moved there from JSRuntime.
Attachment #460076 -
Flags: review?(anygregor)
Assignee | ||
Comment 3•14 years ago
|
||
here comes the proper patch - v1 is not finished version.
Attachment #460076 -
Attachment is obsolete: true
Attachment #460080 -
Flags: review?(anygregor)
Attachment #460076 -
Flags: review?(anygregor)
Updated•14 years ago
|
Attachment #460080 -
Flags: review?(anygregor) → review+
Assignee | ||
Comment 4•14 years ago
|
||
http://hg.mozilla.org/tracemonkey/rev/eb6c9591249e
Whiteboard: fixed-in-tracemonkey
Comment 5•14 years ago
|
||
http://hg.mozilla.org/mozilla-central/rev/eb6c9591249e
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Comment 6•14 years ago
|
||
could this have caused a regression in found in bug 579100
Comment 7•14 years ago
|
||
er, bug 594859
Assignee | ||
Comment 8•14 years ago
|
||
(In reply to comment #7) > er, bug 594859 The bug was mostly about renames and removal of unused functionality. The stack reported in 594859 just reflects this changes.
You need to log in
before you can comment on or make changes to this bug.
Description
•