rust-embedded / rust-embedded/riscv
`riscv`: Support more fence variants
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.1k
- Forks
- 200
- Avg merge
- 11d 2h
- Merged PRs (30d)
- 2
Description
The default fence instruction with no parameters is the strongest form of barrier. But it also takes an optional set of flags to give fine-grained control over exactly what operations the fence is a barrier for, and in which direction.
I see two design choices here:
- just let the caller specify an arbitrary set of flags (somehow), or
- have a set of canned variants for the common cases (like Linux's
rmb/wmb/...)
(These aren't exclusive of course.)
Thoughts?
cc @dreiss
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 examining the existing fence instruction API and how its default, parameterless form is exposed. Compare the proposed arbitrary flags with canned variants such as Linux's rmb and wmb, then determine which API design the project accepts. Done means the chosen fence variants or flag mechanism are supported and documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100