Closed
Bug 761324
Opened 13 years ago
Closed 1 year ago
[jsdbg2] Can we delete JSScript::debugMode?
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: jimb, Unassigned)
Details
(Whiteboard: [js:p3])
Could we delete JSScript::debugMode? Right now it's barely used at all:
- jsdbgapi's JS_SetFrameReturnValue uses it to assert.
- js_InternalInterpret's REJOIN_THIS_PROTOTYPE case uses it to decide whether to call js::ScriptDebugPrologue, but it seems like that might as well use f.cx->compartment->debugMode().
- js_PutCallObject uses it to decide whether to copy out args and vars from stack frame to call object en masse; it seems like something else could be used there, too.
![]() |
||
Comment 1•13 years ago
|
||
(In reply to Jim Blandy :jimb from comment #0)
> - js_PutCallObject uses it to decide whether to copy out args and vars from
> stack frame to call object en masse; it seems like something else could be
> used there, too.
*used*, as of b863ef9946b8 ;-)
![]() |
||
Comment 2•13 years ago
|
||
Just beware that if you remove it, you'll probably have to tweak the padding to keep sizeof(JSScript) to a multiple of 8, including on --disable-methodjit builds.
Updated•13 years ago
|
Whiteboard: [js:p3]
Assignee | ||
Updated•11 years ago
|
Assignee: general → nobody
Updated•3 years ago
|
Severity: normal → S3
Updated•1 year ago
|
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•