1673408 - Simplify marking of slots value ranges

Status: RESOLVED FIXED

(Core :: JavaScript: GC, enhancement, P3)

Description

[Jon Coppeard (:jonco)]

Currently GCMarker stores value ranges on the mark stack as either slots or elements ranges, and then for a slots range we work out whether it refers to fixed or dynamic slots later. We could simplify this by storing which kind of slots range we're referring to on the mark stack.

Comment 1

[Jon Coppeard (:jonco)]

Attachment: Bug 1673408 - Store slots range kind on the mark stack r?sfink

This stores the slots or elements range kind in the same word as the start
index (annoyingly there weren't enough spare bits to encode this in
MarkStack::TaggedPtr kind). This removes the need to add/subtract the number of
fixed slots when pushing/popping ranges for dynamic slots.

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/f64dc7ecb6e9
Store slots range kind on the mark stack r=sfink

Comment 3

[Razvan Maries]

https://hg.mozilla.org/mozilla-central/rev/f64dc7ecb6e9