WebAssembly / WebAssembly/wasi-libc
Keep/separate out a list of symbols that are only stubs
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1k
- Forks
- 251
- Avg merge
- 7h 15m
- Merged PRs (30d)
- 3
Description
Probably one of the biggest headaches in keeping CPython compatible with WASI is tracking the stubs that suddenly turn on "new" functionality thanks to configure discovering the new symbol. Having a list of the stubs (or https://github.com/WebAssembly/wasi-libc/blob/main/expected/wasm32-wasip2/defined-symbols.txt somehow delineating what are stubs) would be great as I can then turn off those function explicitly in the config.site file.
Contributor guide
No contributing guide indexed for this repository
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
Read the expected/wasm32-wasip2/defined-symbols.txt file and examine how configure discovers symbols and how config.site can disable them. Determine how a separate or marked stub list should represent those symbols, with completion defined as a reliable list that supports explicit config.site exclusions for CPython compatibility.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, wasm
- Domain
- build-system, operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100