Closed
Bug 784702
Opened 13 years ago
Closed 13 years ago
remove cx->fp/maybefp/regs/maybeRegs footguns
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: luke, Unassigned)
Details
Why are they footguns? Several reasons:
1. with JM inlining and all IM code, cx->fp might not be the innermost frame and cx->regs.pc might not be the current pc
2. with dummy frames removed (bug 625199), cx->fp might point to a StackFrame in a different compartment than cx->compartment
3. when VM code is reached by a direct JSAPI call (e.g., JSNative via JS_CallFunctionValue or native getter via JS_GetProperty), cx->fp will be completely unrelated (or non-existant)
Alternatives are ScriptFrameIter, StackIter, currentScript, currentScriptedScopeChain or making new semantically better-defined queries that we can place on ContextStack.
| Reporter | ||
Comment 1•13 years ago
|
||
n/m, most of the current uses just get turned into cx->stack.fp(), so this is needless churn
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•