Recognize table initialization code in start function and be able to devirtualize based on it
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 42/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- wasm
- Domain
- compilers, performance
Research direction
Start by tracing how Binaryen handles table.fill, start-function initialization code, and element segments, then compare that with the existing devirtualization and table-load folding behavior. Define the opt-in flag semantics and verify that recognized initialized regions are treated like immutable element-section regions without changing unrecognized tables.
Written by the indexing model from the issue text.
Description
Producers of wasm code prefer small binary size and may use table.fill instructions to initialize parts of a table (or other constructs, like a loop of increasing indices to initialize i31ref table) instead of emitting large element segments.
It would be nice if binaryen offered a flag (e.g. --trust-table-init-code or something like that) that would make it recognize this pattern and treat it as iff the regions were initialized in element sections and therefore be immutable and allow devirtualization / loads of the table to be folded away.
It could be an opt-in flag.
(In some sense an export of a table - e.g. in multi module scenarios - is in similar situation. One may want with a wasm-merge+wasm-opt+wasm-split the ability to devirtualize -- and would have an assumption that the exported table isn't used by 3rd party modules)
- Dominant language
- WebAssembly
- Stars
- 8.6k
- Forks
- 885
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 64
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.
More from WebAssembly/binaryen
-
Difficulty 2/5 Half a day Newbie friendliness 76/100
WebAssembly/binaryen#9018 · 3 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
WebAssembly/binaryen#9123 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
WebAssembly/binaryen#9122 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
WebAssembly/binaryen#9086 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
WebAssembly/binaryen#9038 · 5 comments ·
All issues in WebAssembly/binaryen
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
objectionary/eo#8869 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
EricSpencer00/Resilient#4824 · 1 comment ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
objectionary/jeo-maven-plugin#1758 ·
-
generics
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
mlir
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
llvm/llvm-project#224908 · 1 comment ·