Short answer: yes.

Longer answer: mostly. The jit-test harness, currently part of |make check| and 
run under |B| on most TBPL builders, runs each test in a large number of 
different configurations, including the ones you are inquiring about: 
--baseline-eager, --ion-eager, and --baseline-eager --ion-eager. We would like 
to also run the jstests and jsapi-tests harnesses in these configurations, but 
that is not implemented at present.

Cheers,
Terrence

----- Original Message -----
From: "David Bruant" <bruan...@gmail.com>
To: "JS Internals list" <dev-tech-js-engine-internals@lists.mozilla.org>
Sent: Sunday, August 11, 2013 6:00:48 AM
Subject: [JS-internals] Conformance testing of "the" JavaScript engine(s?)

Hi,

In advance, I apologize if my question is naive or stupid but I couldn't 
find the answer simply (or figure out why it would be a wriong question).

There are "official" conformance tests [1] and "SpiderMonkey" also has 
its own form of conformance and regression tests. I quote "SpiderMonkey" 
(and "the" in the title), because I feel that this wording 
oversimplifies the situation.
JavaScript code first runs in an interpreter where warmth measurements 
are gathered. When code is warm, it's compiled* to more efficient 
machine code. If hot, it's compiled* again to something even more efficient.

Both compilation steps (*) generate a new source code and this 
transformation step may include bugs.
In essence, within SpiderMonkey, there are 3 JavaScript engines: the 
interpreter, the "warm code" compiler and the "hot code" compiler. 
(maybe 4 if you count the SpiderMonkey combination)

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).

David

[1] http://test262.ecmascript.org/#
_______________________________________________
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
_______________________________________________
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

Reply via email to