Closed
Bug 723985
Opened 14 years ago
Closed 1 year ago
Implement 'use moz::forceInterpreter' directive to prevent JITting
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
INACTIVE
People
(Reporter: sfink, Unassigned)
Details
Attachments
(1 file)
For testing, I've always wanted a way to force the mode in which a given script is compiled (without affecting other scripts.)
For my stackwalking work, it turns out that I need js::Interpret to run all the way through once before I can properly identify its address range. If I run in "mjit always" mode, there's no straightforward way to ensure that this happens before I start to try to walk the stack.
The most convenient way I could think of to do this would be to add something similar to 'use strict'. So I did.
I called it 'use moz::forceInterpreter'. It's a kinda hacky language change, and I haven't discussed it with anybody, but it seems to be working for my tests.
Any feedback welcome.
Obviously, this would need to be implemented for IonMonkey as well.
Reporter | ||
Comment 1•14 years ago
|
||
Reporter | ||
Comment 2•14 years ago
|
||
Whoops, you can see my ambivalence about the exact string to use. forceInterpret vs forceInterpreter.
Summary: Implement 'use moz::forceInterpret' directive to prevent JITting → Implement 'use moz::forceInterpreter' directive to prevent JITting
Reporter | ||
Comment 3•14 years ago
|
||
dmandelin suggested 'use nojit'
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: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•