WebAssembly / WebAssembly/binaryen
Tail-Call optimization
Nobody has claimed this yet.
- Dominant language
- WebAssembly
- Stars
- 8.6k
- Forks
- 885
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 69
Description
I'm curious as to why binaryen doesn't implement an optimization pass for tailcall feature. Is the optimization itself not feasible?
If it is feasible, I would like to implement it.
The basic idea is we can convert
(func ...
(call $f)
)
to
(func ...
(return_call $f)
)
(func ...
(return (call $f))
)
to
(func ...
(return_call $f)
)
(func ...
(if
(condition)
(call $f)
)
)
to
(func ...
(if
(condition)
(return_call $f)
)
)
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
No file, test, or entry point is named in the issue. Start by locating Binaryen's existing tail-call support and optimization-pass tests, then verify whether the three shown transformations are valid in all relevant cases. Done means an implemented pass, if feasible, with coverage for the illustrated call, return-call, and conditional-call forms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100