Disallowing legacy EH with new features

オープン
#2,333 コメント 1 件 リアクション 1 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
25/100
issue の種類
機能追加
明瞭さ
説明が足りない
活発さ
活発
技術スタック
wasm
領域
compilers

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.
主要言語
WebAssembly
スター
3.5k
フォーク
545
平均マージ
1日 4時間
マージ済み PR(30日)
25

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

WebAssembly/spec のほかの issue

WebAssembly/spec の issue をすべて見る

似ている issue

Compilers の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。