Closed
Bug 1572504
Opened 6 years ago
Closed 6 years ago
Use BytecodeLocation and BytecodeIterator in BytecodeAnalysis::init
Categories
(Core :: JavaScript Engine, enhancement, P1)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
mozilla72
People
(Reporter: asorholm, Assigned: asorholm)
References
Details
Attachments
(1 file)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0
Steps to reproduce:
Replace uses of jsbytecode*
and pcOffset
inside BytecodeAnalysis::init
with BytecodeLocation
and BytecodeIterator
.
Updated•6 years ago
|
Assignee: nobody → asorholm
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Priority: -- → P3
Replacing uses of jsbytecode
and pcToOffset
with BytecodeLocation
and BytecodeIterator
Updated•6 years ago
|
status-firefox70:
--- → affected
Priority: P3 → P1
Keywords: checkin-needed
Updated•6 years ago
|
Keywords: checkin-needed
Pushed by nbeleuzu@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/9262dd831ebd
Use BytecodeLocation and BytecodeIterator in BytecodeAnalysis::init. r=mgaudet
Comment 4•6 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
status-firefox72:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla72
Comment 5•6 years ago
|
||
Since the status are different for nightly and release, what's the status for beta?
For more information, please visit auto_nag documentation.
status-firefox71:
--- → ?
Updated•6 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•