Closed Bug 1740745 Opened 4 years ago Closed 4 years ago

Runtime check is no longer necessary in barriers

Categories

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

task

Tracking

()

RESOLVED FIXED
96 Branch
Tracking Status
firefox96 --- fixed

People

(Reporter: jonco, Assigned: jonco)

Details

Attachments

(3 files)

Following on from bug 1734801, we can improve our barriers in a similar way by removing the check we sometimes that the thing we're looking at is not from another runtime. If it is from another runtime it will always be black, so we can remove this check and let the mark check handle it.

With the following patches this may be read by other threads so we need to make
it atomic to avoid undefined behaviour. It is only ever written by the main
thread of the runtime that owns the zone.

This check is no longer required and can be handled by the mark check.

Depends on D130995

Attachment #9250408 - Attachment description: Bug 1740745 - Part 2: Remove runtime checks from barriers r?sfink → Bug 1740745 - Part 2: Remove permanent atom checks from barriers r?sfink
Pushed by jcoppeard@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/ff8c4f9a99fc Part 1: Make needs barrier state atomic r=sfink https://hg.mozilla.org/integration/autoland/rev/0694472ccb3d Part 2: Remove permanent atom checks from barriers r=sfink https://hg.mozilla.org/integration/autoland/rev/dc599b0ff23d Part 3: Remove runtime check from JIT code r=jandem
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: