wasi
Experimental WASI API bindings for Rust (by bytecodealliance)
compiler-builtins
Porting `compiler-rt` intrinsics to Rust (by rust-lang)
Our great sponsors
wasi | compiler-builtins | |
---|---|---|
1 | 12 | |
230 | 338 | |
10.9% | 2.4% | |
6.3 | 8.1 | |
24 days ago | 5 days ago | |
Rust | Rust | |
Apache License 2.0 | GNU General Public License v3.0 or later |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
wasi
Posts with mentions or reviews of wasi.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-06-02.
-
#![no_std] with WASI is more complicated than I thought it would be
At this point, I look into Bytecode Alliance's WASI rust bindings, used by Rust's std.
compiler-builtins
Posts with mentions or reviews of compiler-builtins.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-03-01.
- Why do we need for an Undefined Behavior Annex to C++
-
Can I force rust to treat stdlib like other crates in terms of linkage?
I don't know which symbols are missing, haven't done anything on the llvm level. But I had the same problems creating a no-std no-libc application, if you add https://github.com/rust-lang/compiler-builtins as a dependency you should get all the symbols you need, std uses the same but if you want to use it outside of std you'll need nightly since it uses a lot a nightly features. It might apply to your case as well.
-
[Question] Need help with `avr-hal` for Arduino UNO
Ah, I see - you might be hitting https://github.com/rust-lang/compiler-builtins/issues/347.
-
Converting Integers to Floats Using Hyperfocus
There's a PR to the compiler-builtins crate which the rust implementation is based on.
-
rustc + avr = lovelove back again!
I'm glad to inform y'all that after a year, the infamous LLVM ERROR: Not supported instr bug¹ has been finally fixed and today's nightly can compile for AVR back again! 😎
- Hey Rustaceans! Got an easy question? Ask here (8/2022)!
- Porting Rust's Std to Rustix
-
Porting Rust's std to rustix
Then, some of the non-trivial things that are needed are already implemented and maintained in other crates, like memcpy and friends in compiler-builtins, all the math routines in libm and malloc in dlmalloc.
-
Rust for Embedded Development
3.Use scons to compile, if errors jumped on link up, find the solution on its official Github.
What are some alternatives?
When comparing wasi and compiler-builtins you can also consider the following projects:
cargo-wasi - A lightweight Cargo subcommand to build Rust code for the `wasm32-wasi` target
rt-thread - RT-Thread is an open source IoT real-time operating system (RTOS).