Disallowing legacy EH with new features

Abierto
#2,333 1 comentario 1 reacción 0 asignados Ver en GitHub

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
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
wasm
Área
compilers

Línea de trabajo

Start by reading the linked discussion in WebAssembly/exception-handling#344 and compare how V8, JSC, and SpiderMonkey currently handle legacy exception handling. The issue leaves consensus, the affected features, and the specification approach undecided, so first identify those open questions; completion would require agreement on which combinations are invalid and an agreed specification change.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

In https://github.com/WebAssembly/exception-handling/issues/344 we appeared to achieve consensus to disallow mixing legacy exception handling with new WebAssembly features in the same module. Unfortunately we never voted on that or made it official, and now the repo is archived.

I'd like to revive that discussion and see if we have consensus to make that change. If so, the next question would be how to specify it. I guess the most straightforward thing to do would maintain a list of instructions (and types? general syntax productions?) in the legacy EH spec with language saying it is a validation error if those instructions appear in the same module as the legacy EH instructions. That's not very formal by WebAssembly standards, but maybe that's ok? @rossberg, do you have thoughts about this?

Another question is what features we specifically should disallow using with legacy EH. Here are the features that have reached phase 4 since exception handling reached phase 4:

  • Memory64
  • JSPI
  • Wide Arithmetic
  • Compact Import Section

It's probably not web-compatible to disallow mixing legacy EH and Memory64 or JSPI at this point, but we should check. It probably is web-compatible to disallow mixing legacy EH and Wide Arithmetic and Compact Import Section, but again, we should check.

For reference, here are how the web engines currently gate legacy EH use:

  • V8: CompileError on mixing any use of legacy EH and standard EH in a module.
  • JSC: CompileError on using both try and try_table in a module when both are reachable.
  • SpiderMonkey: No restrictions, but prints a deprecation warning to the console whenever a module using legacy EH is instantiated.
Lenguaje dominante
WebAssembly
Estrellas
3.5k
Forks
545
Merge medio
1 d 4 h
PR fusionados (30 d)
25

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de WebAssembly/spec

Todos los issues de WebAssembly/spec

Issues similares

Más issues de Compilers

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.