Closed
Bug 1662502
Opened 5 years ago
Closed 5 years ago
Barrier implementations are repeated in several places
Categories
(Core :: JavaScript: GC, task, P1)
Core
JavaScript: GC
Tracking
()
RESOLVED
FIXED
82 Branch
| Tracking | Status | |
|---|---|---|
| firefox82 | --- | fixed |
People
(Reporter: jonco, Assigned: jonco)
Details
Attachments
(2 files)
We can refactor the barrier implementations to give Cell default implementations for pre and read barriers, and combine the existing post barrier implementations into a single function.
| Assignee | ||
Comment 1•5 years ago
|
||
This moves the default barrier implementations for the pre and read barriers to
the Cell base class and combines the existing post barrier implemenations in to
a single function.
| Assignee | ||
Comment 2•5 years ago
|
||
This should clarify why they are unsafe.
Also rename the overlong 'unsafeUnbarrieredForTracing' to 'unbarrieredAddress'
to be more like Rooted::address and since it is used outside of tracing in a
couple of places.
Depends on D89011
Pushed by jcoppeard@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/5c7a708e37e2
Refactor barrier implemenations r=sfink
https://hg.mozilla.org/integration/autoland/rev/0f13b3d0e5dd
Rename some methods on GC wrapped pointers to 'unbarriered' rather than 'unsafe' r=sfink
Comment 4•5 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/5c7a708e37e2
https://hg.mozilla.org/mozilla-central/rev/0f13b3d0e5dd
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox82:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 82 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•