wee_alloc
The Wasm-Enabled, Elfin Allocator (by rustwasm)
compiler-builtins
Porting `compiler-rt` intrinsics to Rust (by rust-lang)
| wee_alloc | compiler-builtins | |
|---|---|---|
| 7 | 12 | |
| 632 | 340 | |
| 0.0% | 0.3% | |
| 0.0 | 8.1 | |
| about 1 year ago | 1 day ago | |
| Rust | Rust | |
| Mozilla Public 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.
wee_alloc
Posts with mentions or reviews of wee_alloc.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-07-18.
-
Rust + WASM + Typescript [+ React]
As a note, you might find some references to use wee_alloc, but it has been unmaintained for some time and shouldn't be used. I'm using the default allocator with the wasm32-wasi target and it works fine, but I don't know if that works with wasm32-unknown-unknown too; if not there's lol_alloc.
-
Junior Dev here -- How are we setting up Rust, WASM, and webpack?
Note that the wasm-pack tutorial recommends using the wee_alloc crate. This crate is unmaintained and leaks memory, so it should be avoided. Remove this crate, the default allocator works just fine in WebAssembly.
-
Don't use wee_alloc in production code targeting WebAssembly.
It leaks memory: https://github.com/rustwasm/wee_alloc/issues/106
-
Need advice on a project involving Webassembly+ web_sys + webgl
Last thing that comes to mind is switching the allocator to wee_alloc. I use it most of the time for wasm projects and it doesn't make too much of a difference in binary size but that always depends on the project and usually saves at least a few kB.
-
Developing a cross-platform game for browser, Ios, and Android using rust?
For example, check out wee_alloc.
-
Rust on the front-end
wee_alloc, an allocator optimized for small code size.
-
#![no_std] with WASI is more complicated than I thought it would be
Ok. Now I need to add in a global allocator. I use wee_alloc since I know it works pretty well with WASM: Cargo.toml
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 wee_alloc and compiler-builtins you can also consider the following projects:
wasm-bindgen - Facilitating high-level interactions between Wasm modules and JavaScript
rt-thread - RT-Thread is an open source IoT real-time operating system (RTOS).
wasi-libc - WASI libc implementation for WebAssembly
relibc - Mirror of https://gitlab.redox-os.org/redox-os/relibc
cargo-wasi - A lightweight Cargo subcommand to build Rust code for the `wasm32-wasi` target
rustix - Safe Rust bindings to POSIX-ish APIs
create-wasm-app - npm init template for consuming rustwasm pkgs
libm - A port of MUSL's libm to Rust.
wasm-pack - 📦✨ your favorite rust -> wasm workflow tool!
wgpu - Cross-platform, safe, pure-rust graphics api.
avr-device - Register access crate for AVR microcontrollers
wee_alloc vs wasm-bindgen
compiler-builtins vs rt-thread
wee_alloc vs wasi-libc
compiler-builtins vs relibc
wee_alloc vs cargo-wasi
compiler-builtins vs rustix
wee_alloc vs create-wasm-app
compiler-builtins vs libm
wee_alloc vs wasm-pack
compiler-builtins vs cargo-wasi
wee_alloc vs wgpu
compiler-builtins vs avr-device