There is a whitebox testing function, setARMHwCapFlags, that is used by exactly two test cases that I've been able to find so far, one for asm.js and the other for wasm. (The context is bug 1656335.) It changes the ARM hardware capabilities post-initialization, even when running on device. That's possibly useful but it's amazingly brittle, since it means that two checks of the HW capabilities may return different results.
Is this useful to anyone, or could we contemplate taking it out, so that flags are stable post-startup? It's possible to set the flags using an environment variable now, and this is a more well-behaved mechanism. --lars _______________________________________________ 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
