On 08/11/2013 06:00 AM, David Bruant wrote:
And I was wondering if conformance and regression tests were run against all 3-4 engines (since each compilation step may introduce its own bugs) or whether only the combination was tested. I imagine that when I run [1], only the conformance of the interpreter is tested, because no test really have time to become warm or hot (not even the test harness since it's injected in a new iframe for each test for good reasons).
As terrence mentionned we do have eager compilation. Even if the eager compilation might not be enough to test the conformance. The fact that the test are present help fuzzers generating new tests by mutations. Such test can then be used in a differential tests to check for different behavior between the interpreter and the compiled code.
So as soon as we get it right in the interpreter the rest should catch-up if we forgot to update some corner cases of the JITs.
-- Nicolas B. Pierron _______________________________________________ dev-tech-js-engine-internals mailing list dev-tech-js-engine-internals@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
