Can't use the crate for the target riscv32i-unknown-none-elf
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- rust
- Domain
- operating-systems
Research direction
Start by reproducing the riscv32i-unknown-none-elf build from the dependency declaration in Cargo.toml and inspect the AtomicUsize import in lock_api-0.4.9/src/remutex.rs. Determine whether the allocator can support this target without atomic instructions or whether the limitation should be documented; done means the behavior is resolved or clearly reported.
Written by the indexing model from the issue text.
Description
I don't know if this is an issue and I would like to apologize for that. (It is my first issue that i wrote. )
What I did was only include the linked_list_allocator in the Cargo.toml .
/* Cargo.toml */
[dependencies]
linked_list_allocator = "0.10.4"
Terminal Output:
error[E0432]: unresolved import `core::sync::atomic::AtomicUsize`
--> /home/user123/.cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.9/src/remutex.rs:19:20
|
19 | sync::atomic::{AtomicUsize, Ordering},
| ^^^^^^^^^^^ no `AtomicUsize` in `sync::atomic`
The problem is that the Riscv32i does not contain an atomic instruction set (A) and that is why the error occurs.
I do not know if I have forgotten something or if it is a bug.
- Dominant language
- Rust
- Stars
- 242
- Forks
- 56
- PR merge metrics
- No merged PRs in 30d
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.
More from rust-osdev/linked-list-allocator
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
rust-osdev/linked-list-allocator#86 · 3 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
help wanted
Difficulty 4/5 3-5 days Newbie friendliness 35/100
rust-osdev/linked-list-allocator#83 · 2 comments ·
All issues in rust-osdev/linked-list-allocator
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100