wg-async
rustc_codegen_gcc
Our great sponsors
wg-async | rustc_codegen_gcc | |
---|---|---|
8 | 49 | |
365 | 874 | |
1.6% | 3.0% | |
5.9 | 9.7 | |
27 days ago | 3 days ago | |
Rust | Rust | |
Apache License 2.0 | Apache License 2.0 |
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.
wg-async
- Async Rust Is A Bad Language
-
Catch 22! Rust in Review
I believe the solution mentioned in rust-lang/wg-async is the way to go: Add traits like AsyncWrite, AsyncRead, Executor/Runtime to the std so that tokio/async-std can implement them.
-
Async Rust: What is a runtime? Here is how tokio works under the hood
This is a consequence of runtimes relying on global variables that their core future types are dependent on. Creating abstractions to solve this problem is one of the main goals of the the async working group [0].
[0]: https://github.com/rust-lang/wg-async
-
How should I structure an async/await/futures program with multiple event sources and mutable state?
Provided the futures you're selecting over are cancellation safe the plain loop over select! should be fine. Multiple channels in particular are safe to select over - if you have futures that aren't cancellation safe, you can just wrap them up in a task on the end of a channel and then select on that.
- Monoio – A thread-per-core Rust async runtime with io_uring
-
What Rust feature are you waiting for?
I'd like to be able to write runtime agnostic async libs.
-
Rust Weird Expressions
You might be interested in taking a look at and potentially participating in the "Async Vision Document"[1] which is an exercise the team is going through to collect feedback about the current state of the ecosystem and what the pain points are, as well as a way to lay doing what the desired future state of async Rust should be[2]. The process is happening, as you would expect, in the open and there's still time to influence it[3] if your concerns aren't yet addressed or even mentioned[4].
[1]: https://rust-lang.github.io/wg-async-foundations/vision.html
[2]: https://blog.rust-lang.org/2021/03/18/async-vision-doc.html
[3]: https://github.com/rust-lang/wg-async-foundations/pulls
[4]: https://github.com/rust-lang/wg-async-foundations/issues
-
Building a shared vision for Async Rust
Thanks for the feedback. I posted this comment to a relevant github issue, fyi.
rustc_codegen_gcc
-
How hard would it be to port the Rust toolchain to a new non-POSIX OS written in Rust and get it to host its own development? What would that process entail?
Alternatively, there's another initiative called codegen_gcc which is about using GCC as a backend for the rustc compiler. It's (much) more advanced in Rust support, but I am not sure how easy it would be to use a modified libgccjit from there.
-
"Rust makes me never want to touch C again" -- Matthew Ahrens
In addition to what others have said about platform support, Rust is also on its way to gaining more platform support through rustc_codegen_gcc, the GCC codegen backend for rustc, as an alternative to the LLVM backend. That means many of the platforms GCC supports will suddenly become available with Rust.
-
Rust contributions for Linux 6.4 are finally merged upstream!
Yeah, rustc_codegen_gcc is a GCC backend for rustc, and its making a lot of good regular progress.
-
GCC 13 and the State of Gccrs
gcc-rs is one of two projects for bringing Rust to gcc. gcc-rs is the more ambitious of the two, with an entirely new frontend. There is also rustc_codegen_gcc (https://github.com/rust-lang/rustc_codegen_gcc) that keeps the rustc frontend, and only swaps out LLVM for GCC at the codegen stage.
-
rustc_codegen_gcc: Progress Report #22
Fixing unwinding in release mode is still ungoing. I could use some help here, so anyone with some understanding of unwinding, landing pads or GCC, please come on this issue to discuss this.
-
Any alternate Rust compilers?
Additionally, there is gcc codegen for rustc (https://github.com/rust-lang/rustc_codegen_gcc), which is not a compiler per se, but an alternative code generator, with more architectures supported and other nice things. It's also coming along, but there's still a lot of work to do there too. There's also Cranelift codegen (https://github.com/bjorn3/rustc_codegen_cranelift), which is designed to make debug builds faster, but this is not as exciting/useful as the other 2.
-
rustc_codegen_gcc: Progress Report #21
Good idea. I added the tag "help wanted" to the issue.
-
Challenges writing a compiler frontend targeting both LLVM and GCC?
Also, there are indeed ABI issues, e.g. for 128-bit integers and NaN.
-
A brave new world: building glibc with LLVM
I'm excited about both the backend & the frontend.
-
Rust front-end merged in GCC trunk
There is also a project for rustc to use GCC instead of LLVM for codegen.
https://github.com/rust-lang/rustc_codegen_gcc
What are some alternatives?
smol - A small and fast async runtime for Rust
gccrs - GCC Front-End for Rust
ideas4 - An Additional 100 Ideas for Computing https://samsquire.github.io/ideas4/
gcc-rust - a (WIP) Rust frontend for gcc / a gcc backend for rustc
delimited
min-sized-rust - 🦀 How to minimize Rust binary size 📦
miniserve - 🌟 For when you really just want to serve some files over HTTP right now!
databend - 𝗗𝗮𝘁𝗮, 𝗔𝗻𝗮𝗹𝘆𝘁𝗶𝗰𝘀 & 𝗔𝗜. Modern alternative to Snowflake. Cost-effective and simple for massive-scale analytics. https://databend.com
rlimit - Resource limits
compiler-explorer - Run compilers interactively from your web browser and interact with the assembly
monoio - Rust async runtime based on io-uring.
libgccjit-patches - Patches awaiting review for libgccjit