Make wasm-opt faster for Asyncifying CRuby
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 875
- Forks
- 68
- Avg merge
- 9d 5h
- Merged PRs (30d)
- 1
Description
Asyncify pass is super slow against CRuby. Let's optimize the Asyncify pass implementation in Binaryen
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining Binaryen's Asyncify pass implementation and how wasm-opt processes CRuby. Benchmark the current pass against CRuby, identify the slow stages, and consider the work done when Asyncify completes faster without changing its behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby, wasm
- Domain
- compilers, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100