[js-api] The type confusion in builtin section
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Refactorización
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Área
- documentation
Línea de trabajo
Read the JS API Builtins section and compare its create a builtin function steps with run a host function and the Core Spec's ToJSValue and ToWebAssemblyValue conversions. The issue proposes defining argument and result conversion, trap handling, store handling, and unsigned i32 interpretation across the builtins; work out the array handling details it identifies. Done means the builtin algorithms use one consistent convention and resolve the cited type mismatches.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
In the Core Spec and the rest of the JS API, a numeric WebAssembly value such as (i32.cosnt n) is a term,
and its actual value is compared only after it is taken out of one, with its signedness spelled out.
In the Core Spec, i32.lt_u and i32.lt_s take the payloads c1 and c2 out of two i32.const values and compare them with ilt: unsigned is c1 < c2, and signed is signed_32(c1) < signed_32(c2).
The JS API does the same when it tries to read a value:
ToJSValue matches i32.const u32 and uses signed_32(u32).
The Builtins section however, has no such convention.
create a builtin function only says the host function "executes steps when called",
so nothing says what the steps receive or return,
and the steps mix WebAssembly values, JavaScript values and plain numbers:
i32parameters are used both as numbers and as WebAssembly values.
fromCodePointchecksv > 0x10ffffand then callsToJSValue(v);
charCodeAt/codePointAt(index) andsubstring(start,end) do the same.- Conversions are written in some places only.
FromCharCodeandCharCodeAtassertis of type i32and callToJSValue,
butexternrefparameters are used as if they are already JavaScript values (If v is not a String),
and results are returned unconverted (Return 0.,Return -1., a JavaScript String). - Values of the wrong kind are passed on.
intoCharCodeArraypasses its loop counter, a number, toCharCodeAt, which asserts ani32.
fromCharCodeArraypasses a packedi16array element toFromCharCode, which asserts the same.
AndintoCharCodeArraystores ani32.constvalue into thati16array.
Why it matters
These implicit conversions brings ambiguity. For instance, substring(string, start, end) can have different interpretations:
1. Let string be ? UnwrapString(string).
1. Let length be the length of string.
1. If start > end or start > length,
1. Return the empty string.
1. Return ! Call(String.prototype.substring, string, « ToJSValue(start), ToJSValue(end) »).
For substring("hello", 1, -1):
- If
endstays a WebAssembly value and only>implicitly reads it as a number:- read as signed:
1 > -1, so the result is"". - read as unsigned: the check passes, then
ToJSValueturnsendback into-1,
andString.prototype.substring("hello", 1, -1)gives"h".
- read as signed:
- If
endis already implicitly a number or JSValue when the steps start (which makes the last step'sToJSValueredundant):- converted as signed (
-1):"". (This is what JavaScriptCore returns.) - converted as unsigned (
4294967295):"ello". (This is what V8 and SpiderMonkey return, and likely be the intention.)
- converted as signed (
Suggestion
The proposal's Overview does have a single convention, and V8 and SpiderMonkey follow it.
Builtins "have the same semantics as following create a host function",
so "Calling a function builtin from Wasm will have the Wasm parameters converted to JS values,
and JS results converted back to Wasm values", and each builtin then reinterprets its i32 parameters as unsigned:
// NOTE: `index` is interpreted as a signed 32-bit integer when converted to
// a JS value using standard conversions. Reinterpret as unsigned here.
index >>>= 0;
I would suggest writing the section in that convention:
-
create a builtin function's host function explicitly converts its arguments withToJSValueand the result withToWebAssemblyValue, asrun a host functiondoes, and maps a throw to a trap, perhaps something like:1. Let func parameters → results be the expansion of funcType. 1. Let hostfunc be a host function which performs the following steps when called with store store and arguments arguments: 1. Set the surrounding agent's associated store to store. 1. Let jsArguments be « ». 1. For each arg of arguments, append ToJSValue(arg) to jsArguments. 1. Let result be the result of running steps with jsArguments. 1. Let store be the surrounding agent's associated store. 1. If result is an abrupt completion, return (store, trap). 1. Return (store, « ! ToWebAssemblyValue(result.[[Value]], results[0]) »). 1. ... -
Each builtin starts by reinterpreting its
i32parameters with
ToUint32, and compares them withℝ(...). For example,substring:1. Let string be ? UnwrapString(string). 1. Let start be ! ToUint32(start). 1. Let end be ! ToUint32(end). 1. Let length be the length of string. 1. If ℝ(start) > ℝ(end) or ℝ(start) > length, 1. Return the empty string. 1. Return ! Call(String.prototype.substring, string, « start, end »).(Alternatively, the host function could pass
i32arguments as unsigned Numbers (𝔽(u32)) in the first place, instead ofToJSValue. That saves repeatingToUint32in every builtin) -
Results the steps return as plain numbers
(Return 0.,Return -1.,Return stringLength.,Return the length of string.)
become Numbers (+0𝔽,-1𝔽,𝔽(stringLength)),
so thatToWebAssemblyValuecan convert them like any other JavaScript result. -
The host function explicitly takes and returns the store, as #2326 does for
create a host function.
Some details would still need working out.
For example, with ToJSValue an array parameter arrives as an Exported GC Object,
so fromCharCodeArray and intoCharCodeArray would have to reach the array through its address.
I would work these out in the PR.
Does that direction sound right? If so, I can open a PR for it.
- Lenguaje dominante
- WebAssembly
- Estrellas
- 3.5k
- Forks
- 545
- Merge medio
- 1 d 4 h
- PR fusionados (30 d)
- 25
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de WebAssembly/spec
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
WebAssembly/spec#2321 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
WebAssembly/spec#2333 · 1 comentario · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
Dificultad 3/5 1-2 días Aptitud para principiantes 66/100
WebAssembly/spec#2302 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 53/100
WebAssembly/spec#2301 · 9 comentarios ·
Los mantenedores suelen responder en 1 día
-
il2al: host function rules become two independent conditionals and ignore the new store `s'`Abierto
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
WebAssembly/spec#2279 · 6 comentarios ·
Los mantenedores suelen responder en 1 día
Todos los issues de WebAssembly/spec
Issues similares
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 78/100
firefly-iii/firefly-iii#13259 · 3 comentarios ·
Los mantenedores suelen responder en 1 día
-
documentation
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
molgenis/molgenis-emx2#7059 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
[DOCS/SMU] Correct the 1 GiB window bullet and the coverage-target sentence in the SMU datasheetAbiertoDOCS SMU
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
tenstorrent/tt-oca-harness#3931 ·
Los mantenedores suelen responder en 1 día
-
[Sync EN] Document the getLastErrors() return value change in the PHP 8.2 migration guide (#6107)Abiertosync-en
Dificultad 1/5 Menos de una hora Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día