[Feature Request] Make sure that compare exchange is there.
Nobody has claimed this yet.
- Dominant language
- Mojo
- Stars
- 29.8k
- Forks
- 3.2k
- PR merge metrics
- No merged PRs in 30d
Description
Review Mojo's priorities
- I have read the roadmap and priorities and I believe this request falls within the priorities.
What is your request?
This is important, because currently there is no way without spinwaiting on the same stride and really hard to CAS on warp level. Otherwise FAA methods etc must be used and wait is totally unnecesasry, which renders many things having low performance on the compute side.
What is your motivation for this change?
Faster computations, able to write warp level CAS.
Any other details?
Some platforms that Mojo compiles doesn't have CAS, since you are already documenting these. You can document that, e.g. Metal.
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 with Mojo's roadmap and the current documentation for FAA methods and platform support, including Metal. Determine the intended compare-exchange behavior across supported targets and what should happen where CAS is unavailable; done requires a settled implementation or documented limitation and corresponding validation.
Written by the indexing model from the issue text.
Assessment
- Domain
- compilers, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100