Closed Bug 1921546 Opened 1 year ago Closed 1 year ago

Avoid superflous data storate for fuses

Categories

(Core :: JavaScript Engine, task, P5)

task

Tracking

()

RESOLVED FIXED
133 Branch
Tracking Status
firefox133 --- fixed

People

(Reporter: mgaudet, Assigned: mgaudet)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

So our current set of fuses store some fairly superflous data

  • EmulatesUndefined fuse stores the CompileRuntime
  • RealmFuses store the realm

This is at least gently silly: These are both invariant over the course of a compilation.

One fix would be to stop storing this data, and instead providing it as arguments to checkDependency and registerDependency. But it's sort of awkward, because RealmFuse dependencies want a CompileRealm argument and EmulatesUndefinedDependency wants a CompileRuntime argument. It feels silly to pass both?

Potentially downstream of this may be the ability to remove the silly UniquePtr nonsense here.

Should be cautious here, because over-fixing on the current design may ultimately make something like https://phabricator.services.mozilla.com/D215566 too hard to do.

Doesn't try to remove the UniquePtr stuff though, because I think we will
want that if we try to bring back the invalidation-for-generation-count,
and generally provides flexibility for the contents of a dependency

Assignee: nobody → mgaudet
Status: NEW → ASSIGNED
Pushed by mgaudet@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/5ac82b3eea1f Avoid superflous data storage for fuses r=jandem
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 133 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: