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)

task

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.

Depends on: 1561935, 1561925, 1541404

The last part of my local interpreter patch stack that's necessary to pass jit-tests.

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

Priority: -- → P1
Depends on: 1562602
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
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
Keywords: leave-open
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla70
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: