Fix thpool.c volatile usage
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 5
- Forks
- 6
- Avg merge
- 3h 52m
- Merged PRs (30d)
- 1
Description
It seems like thpool.c makes a wrong assumption that volatile can be use for thread synchronization. We should replace the use of volatile with atomic variables.
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.
Research direction
Start by reviewing thpool.c and locating each use of volatile, then trace how those variables are used for thread synchronization. Replace the synchronization assumptions with atomic variables as described in the issue, and verify that the thread-pool behavior remains correct under concurrent use.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100