Data count section is insufficient for shared data segments
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- wasm
- Domain
- compilers
Research direction
Start by reading the data count section, code section, and data section discussion in the proposal. Trace how shared data segments are currently represented and how generated code refers to pre-allocated segments. Done means agreeing on and specifying a way to determine shared segment handling before code generation, either by ordering the sections or extending the data count section.
Written by the indexing model from the issue text.
Description
The point of the data count section is to pre-declare the number of data segments so that the code section can be parsed to refer to pre-allocated segments. The code should be able to be generated and then the segments should be filled in once the data section is parsed and everything should just work. But there's not currently any way to know in advance if a data segment will be shared, so if the code needs to be generated differently for shared segments, we're plumb out of luck.
It seems we need to be able to emit the data section before the code section or introduce a beefier version of the data count section that can declare data segment types.
- Dominant language
- WebAssembly
- Stars
- 97
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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/shared-everything-threads
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
WebAssembly/shared-everything-threads#119 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
WebAssembly/shared-everything-threads#114 · 7 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
WebAssembly/shared-everything-threads#105 · 6 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
WebAssembly/shared-everything-threads#99 · 5 comments ·
All issues in WebAssembly/shared-everything-threads
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
confirmed llvm:optimizations miscompilation
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
llvm/llvm-project#227071 · 1 comment ·
Maintainers usually reply within 1 day
-
Every compiled IO program carries ~1 MiB of zeros: io_eff_rows is baked into .data.rel.ro by clangOpen
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
HigherOrderCO/Bend#1163 ·