Closed Bug 1604098 Opened 6 years ago Closed 6 years ago

Use bytecode operands instead of SRC_CLASS_SPAN

Categories

(Core :: JavaScript Engine, task, P2)

task

Tracking

()

RESOLVED FIXED
mozilla73
Tracking Status
firefox73 --- fixed

People

(Reporter: jandem, Assigned: jandem)

References

Details

Attachments

(1 file)

JSOP_CLASSCONSTRUCTOR and JSOP_DERIVEDCONSTRUCTOR always look up their SRC_CLASS_SPAN source note. This is not a good use of source notes: looking up source notes can be relatively slow and source notes should be used for metadata we typically don't need for bytecode execution (line, column, breakpoints, etc).

It seems nicer and more efficient to encode these offsets directly as bytecode immediates.

Blocks: 1604105

JSOP_CLASSCONSTRUCTOR and JSOP_DERIVEDCONSTRUCTOR always had to look up their
SRC_CLASS_SPAN source note. This means it's better and more efficient to encode
these offsets as bytecode operands. Source notes are for out-of-band data that
doesn't directly affect bytecode semantics.

Priority: -- → P2
Pushed by jdemooij@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/7fd4e59c05ae Replace SRC_CLASS_SPAN source note with bytecode operands. r=arai,tcampbell
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla73
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: