Open Bug 1732932 Opened 4 years ago Updated 1 year ago

Investigate improving Heap<T> read barrier

Categories

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

Product:
Core
Component:
JavaScript: GC
Type:
task

Tracking

()

People

(Reporter: jonco, Unassigned)

References

(Blocks 1 open bug)

Details

There may be a couple of things we can do to improve ExposeGCThingToActiveJS. These are pretty small gains but since this is a read barrier it can be called a lot so anything we can do to improve it is a win.

  • inline the check for black cells to prevent a call into the JS engine in this case
  • use a single piece of state for incremental marking and gray unmarking barriers

Changing severity to N/A since this is a task

Severity: -- → N/A
Priority: -- → P2

The (In reply to Jon Coppeard (:jonco) from comment #0)

  • inline the check for black cells to prevent a call into the JS engine in this case

This happened as part of bug 1734392.

Blocks: GC.performance
Priority: P2 → P3
You need to log in before you can comment on or make changes to this bug.