wasm-emu: record store-TCI benchmark and keep reliable default

Benchmark showed the narrowed 32-bit-only fallback is slightly faster when it
works but failed once with an app-init watchdog. Restore blanket store-TCI as
the default and document the narrowed result as diagnostic only.
This commit is contained in:
2026-07-22 19:47:47 -04:00
parent 4b1a0d72a2
commit fc2ec8a6ae
2 changed files with 15 additions and 1 deletions
+14
View File
@@ -434,3 +434,17 @@ normal URL: browser raw-sd test passed, open example.txt took 36.8s
This fixes the browser panic without disabling dynamic promotion globally. The
remaining upstream-quality improvement would be eliminating the 32-bit store-TCI
subset entirely by finding the exact cross-width/shared-memory state bug.
### E14 benchmark correction — 32-bit-only fallback rejected as default
A 3-run benchmark changed the decision:
| fallback | result | open times |
| --- | --- | --- |
| 32-bit-store-only TCI | 2 pass, 1 app-init watchdog | 34.0s, 33.8s |
| blanket store-TCI | 3 pass | 35.3s, 36.6s, 34.3s |
The narrowed fallback is a little faster when it works, but it is not reliable
enough: one run failed before controls enabled with an interrupt watchdog. The
default is restored to the upstream blanket store-TCI fallback. Keep the
32-bit-only result as a useful diagnostic, not a production fix.