WebAssembly / WebAssembly/wasi-libc
Remove CLOCK_PROCESS_CPUTIME_ID/CLOCK_THREAD_CPUTIME_ID
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1k
- Forks
- 251
- Avg merge
- 7h 15m
- Merged PRs (30d)
- 3
Description
After https://github.com/WebAssembly/WASI/pull/197 has landed, CLOCK_PROCESS_CPUTIME_ID/CLOCK_THREAD_CPUTIME_ID are invalid in recent versions of wasmtime/uvwasi, even if targetting wasi snapshot 1. This leads to runtime error, so I propose we do something about it:
- Remove these two from
wasi-libcaltogether - Alias to
CLOCK_MONOTONICto make it sort of work
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
Start by reviewing how wasi-libc defines CLOCK_PROCESS_CPUTIME_ID and CLOCK_THREAD_CPUTIME_ID, then reproduce the runtime error with recent wasmtime or uvwasi. Determine whether the supported outcome is removing the constants or aliasing them to CLOCK_MONOTONIC; done when targeting WASI snapshot 1 no longer produces invalid-clock runtime errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, wasm
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100