Closed
Bug 1562129
Opened 5 years ago
Closed 5 years ago
Add a BaselineInterpreter configuration to jit-tests
Categories
(Core :: JavaScript Engine: JIT, task, P1)
Core
JavaScript Engine: JIT
Tracking
()
RESOLVED
FIXED
mozilla70
Tracking | Status | |
---|---|---|
firefox70 | --- | fixed |
People
(Reporter: jandem, Assigned: jandem)
References
Details
Attachments
(3 files)
Before enabling by default we should add a --blinterp-eager
configuration to jit-tests we run in CI.
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 1•5 years ago
|
||
The last part of my local interpreter patch stack that's necessary to pass jit-tests.
Assignee | ||
Comment 2•5 years ago
|
||
To not make jstests even slower, this adds --jitflags=jstests and uses it for
jstests in automation. For jstests we can use fewer jit configurations than
for jit-tests.
This also removes the bigint and bigintdebug autospider variants. BigInt is now
enabled by default so we no longer need the configure flag etc.
Depends on D36306
Assignee | ||
Comment 3•5 years ago
|
||
Depends on D36307
Updated•5 years ago
|
Priority: -- → P1
Pushed by jdemooij@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/2ed26063e1cf
part 1 - Fix GeneratorThrowOrReturn to initialize interpreter fields if necessary. r=tcampbell
Assignee | ||
Updated•5 years ago
|
Keywords: leave-open
Pushed by jdemooij@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/2e490776b07e
part 2 - Add --blinterp-eager to jit-test 'all' configuration. r=sfink
https://hg.mozilla.org/integration/autoland/rev/51782cb7fb8a
part 3 - Add BaselineInterpreter flags to fuzz-flags.txt. r=tcampbell
Assignee | ||
Updated•5 years ago
|
Keywords: leave-open
Comment 6•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/2ed26063e1cf
https://hg.mozilla.org/mozilla-central/rev/2e490776b07e
https://hg.mozilla.org/mozilla-central/rev/51782cb7fb8a
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
status-firefox70:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla70
You need to log in
before you can comment on or make changes to this bug.
Description
•