Disallowing legacy EH with new features
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 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
tryandtry_tablein 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 小时
- 30 天内合并 PR
- 25
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
WebAssembly/spec 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 75/100
WebAssembly/spec#2321 · 2 条评论 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 35/100
WebAssembly/spec#2330 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 66/100
WebAssembly/spec#2302 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 53/100
WebAssembly/spec#2301 · 9 条评论 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 25/100
WebAssembly/spec#2279 · 6 条评论 ·
维护者通常 1 天内回复
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 73/100
维护者通常 1 天内回复
-
DAE2 crashes on call.without.effects with a non ref.func expression可能已有人在做 @stevenfontanella 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
WebAssembly/binaryen#9404 ·
维护者通常 1 天内回复
-
area:compiler effort:S impact:med platform:windows type:bug
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
area:Analysis enhancement
难度 1/5 1-3 小时 新手友好度 69/100
facebookresearch/atlas-lean#5118 ·
维护者通常 1 天内回复
-
C-bugfix
难度 2/5 1-3 小时 新手友好度 82/100
Quantinuum/hugr#3354 ·
维护者通常 1 天内回复