compiler-explorer/compiler-explorer

[REQUEST] Web Assembly JIT compiler

Open

#1,871 建立於 2020年3月3日

在 GitHub 查看
 (3 留言) (12 反應) (0 負責人)TypeScript (14,391 star) (1,605 fork)batch import
help wantednew-languagerequest

描述

It is possible to get native jitted code for web assembly(wasm) out of javascript engines like SpiderMonkey and V8. Here is an example.

I think it makes sense to add wat(wasm text)-to-x86 explorer in the future to study optimization opportunities. One could use CE to generate wat and then copy-paste that wat in the second window and get native assembly.

One way to get native assembly is to run v8 with --print-wasm-code option. There's also a way using v8's internals to get custom output.

Adding that would involve installing wasm tools for (wat -> wasm) conversion and one of the javasctipt engines. I personally tried using v8 and it wasn't difficult in terms of installing/compiling from source compared to llvm/clang. Although that would also involve pulling some google internal tools like depot_tools.

Thanks, Anton

貢獻者指南

技術棧
wasmtypescript
領域
backendtooling
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
5
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
over 1 week
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
WebAssembly understandingV8 or SpiderMonkey internalsWat to Wasm conversion toolsCompiler Explorer architecture
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
15
研究方向
Investigate integrating V8's wasm JIT output (using print wasm code) into Compiler Explorer. Explore using the wabt toolkit for wat to wasm conversion. Look at existing compiler backends in the repository (e.g., in lib/backends/) to understand the architecture for adding a new language. Consider using SpiderMonkey as an alternative and examine the feasibility of parsing the output. The issue mentions a WasmExplorer link and a Godbolt example that could guide the implementation.