3 ms·
Thanks for the pointer on running the tests. I noticed two big issues: 1. Some of the tests use shell functions like "read" that jsc doesn't provide. This is e
by bdash 13y ago
Thanks for the pointer on running the tests. I noticed two big issues:
1. Some of the tests use shell functions like "read" that jsc doesn't provide. This is easy enough to address.
2. I was mistaken about the quality of the typed array support in JavaScriptCore. While the interpreter has knowledge of typed arrays, the actual implementation that's used when running in-browser lives in WebCore rather than in JavaScriptCore. When running in the shell only a bare minimum typed array implementation, primarily intended for JSC-only regression tests, is available. This trips up some tests since the implementation is much less complete than the one in WebCore.
- azakai 13y agoHmm, I am guessing the minimum implementation is also less performant (if it's just meant for regression tests)? So probably it would be unfair to measure on it.
- bdash 13y agoI'm not sure about that. I'll follow up with some of my colleagues to see why typed arrays are in such an state. Am I correct in assuming that if JavaScriptCore starts successfully executing the tests, it'll automatically start showing up on the relevant part of arewefastyet.com?
- azakai 13y agoThanks, that information would be very helpful. I am not sure about automatically showing up, but that would be my guess. I can ask dvander (who runs awfy) for more details if that would be useful. In any case probably it is very easy to change (disable/enable).