Chris Tateandjlucaso1 f168402e1f Name the reason in the CompileError for untranslated WebAssembly modules ...

A WebAssembly module the build finds but does not translate (one that uses
a proposal outside the translated feature set, an invalid one, or one the
translator rejects) now rejects with a CompileError that says the module
was found and names the reason, for example "it uses simd, outside the
translated WebAssembly feature set". Bytes the build did not see keep the
existing message.

The build emits the hash, length and reason of each such module in a
second table, scr_wasm_untranslated, next to scr_wasm_registry; the runtime
reads it when a lookup misses. WebAssembly.validate still answers false for
these modules, and the error stays a catchable CompileError.

Fixes #1617

Co-authored-by: jlucaso1 <55464917+jlucaso1@users.noreply.github.com>

2026-10-21 08:52:18 -05:00

..

corpus

Sort by several keys without calling a chained comparator

2026-10-21 08:31:35 -05:00

coverage-fixtures

Iterate generators from Symbol.asyncIterator and check return() results in for await

2026-10-20 18:16:20 -05:00

deadstrip

…

diagnostics

Type empty arrays filled by later writes inside functions by their reads (#1632)

2026-10-21 04:23:15 -05:00

ffi

…

fixtures

Compile the hot-shots StatsD client over UDP (#1568)

2026-10-20 21:29:48 -05:00

harness

Name the reason in the CompileError for untranslated WebAssembly modules

2026-10-21 08:52:18 -05:00

library-mode

Add the cstring class to library profiles

2026-10-17 23:40:06 -05:00

test262

…

wasm-spec

Merge main

2026-10-20 17:56:44 -05:00