> > Are UTF8-backed (as opposed to Latin1-backed) JS strings with random access
> > going to be a real possibility in SpiderMonkey? It’s obviously possible to
> > make random access work with an appropriate indexing data structure, but
> > popular JS benchmarks are pretty sensitive to string perfor
Another option we've just been discussing is to lazily compute a flag on the
string indicating "contents are 7-bit ascii" that allowed us to use array
indexing. I'd expect this to often be true. There are also many cases where
we'd eagerly have this flag (atoms produced during parsing, strings
Nick just brought up the topic of adding a second compact string representation
to the JS engine (motivated by string memory use). One question was whether to
use ASCII (which V8 does, iirc) or UTF8. Several DOM people have pointed out
over the years that if SM would accept UTF8 it'd be really
> Eventually I can imagine writing the JIT in Rust and using some kind of
> certified
> compilation to guard against compiler bugs.
I haven't really followed this topic; do you really think this would be a
feasible approach to a production JS engine? I appreciate that we'd only have
to certify
> I thought we were going to rely on Rust's
> isolation mechanisms for this kind of finer-grained isolation.
The JS jit will be a major hole in this software isolation scheme, even if
SpiderMonkey is rewritten in Rust. Furthermore, it doesn't seem like we can
fix this by putting the JS engine i
5 matches
Mail list logo
