Andreas Kling d9dd412440 LibJS: Use foldhash in parser and scope-collector hash maps ...

The std default RandomState (SipHash) was using ~9 percentage points
of CPU on hash_one and write across the parse hot path, with the
string interner adding another ~3 pp on top. The cost was spread
across the interner, the scope collector's IndexMap<Utf16String, _>,
and several parser-side HashSet<Utf16String> declarations.

Use foldhash::quality::RandomState for the parser, scope collector,
and string interner via a new fast_hash module. Quality keeps
HashDoS resistance (keys are lexer tokens, attacker-controlled in a
browser context) while shedding SipHash's per-byte cost, and on this
workload it benchmarks slightly faster than foldhash::fast.

2026-05-05 13:53:51 +02:00

..

src

LibJS: Use foldhash in parser and scope-collector hash maps

2026-05-05 13:53:51 +02:00

build.rs

LibJS: Range-check enum-typed bytecode fields in the validator

2026-05-03 08:43:19 +02:00

Cargo.toml

LibJS: Use foldhash in parser and scope-collector hash maps

2026-05-05 13:53:51 +02:00

cbindgen.toml

LibJS: Add bytecode validator scaffolding driven from Bytecode.def

2026-05-03 08:43:19 +02:00