WebAssembly/wasi-libc

Keep/separate out a list of symbols that are only stubs

Open

#515 opened on Jul 16, 2024

View on GitHub
 (1 comment) (0 reactions) (0 assignees)C (245 forks)github user discovery
help wanted

Repository metrics

Stars
 (1,018 stars)
PR merge metrics
 (Avg merge 6d) (4 merged PRs in 30d)

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

Research direction
Examine the existing stubs in wasi libc, particularly those discovered by configure. Cross reference with defined symbols.txt and create a separate list of stub symbols. Document the process for updating this list.
Tech stack
c
Domain
build system
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
CBuild systems
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60