Our great sponsors
-
-
llvm-project
The LLVM Project is a collection of modular and reusable compiler and toolchain technologies.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
-
-
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
There is also a project for rustc to use GCC instead of LLVM for codegen.
https://github.com/rust-lang/rustc_codegen_gcc
AVR should be working these days https://github.com/llvm/llvm-project/tree/main/llvm/lib/Targ...
Unless you mean some specific chips?
rustc_codegen_gcc¹ adds gcc as a backend to rustc alongside llvm, miri and (wip) cranelift. As a result, it always works with the newest version of rust and is already nearly complete after less work.
¹https://github.com/rust-lang/rust/tree/master/compiler/rustc...
>> I’ve come to the conclusion that fragmentation is inevitable as a language gets popular.
That's what language standards are for.
The Ferrocene project is working on standardizing Rust and creating a safety-critical version of the Rust toolchain:
https://ferrous-systems.com/ferrocene/
The Ferrocene Rust draft spec is out:
https://spec.ferrocene.dev/
As Rust continues to improve and be more widely used and adopted, there will be multiple implementations. As you've stated, it is inevitable as Rust gets popular. (For example, if Rust becomes popular enough to displace niches that C and C++ have occupied, when will Microsoft release a Rust toolchain? When will Intel release a Rust toolchain? And so forth.)
Standards help to better define what a Rust toolchain should do and what it means to be a conforming Rust implementation.
This is eventually going to be a feature-complete compiler, targeting a specific rustc version. I believe the plan is to use polonius [1], presumably as an "optional" feature so they can build a stage 1 without it, use that to build polonius, then build the final compiler with it included.
[1] https://github.com/rust-lang/polonius
You are right, this much more ambitious than I though! Here is more information about the project, for the curious: https://rust-gcc.github.io/
> (...) such as Typescript
It seems you're oblivious to the fact that projects such as swc[1] exist, and have been adopted by projects such as deno.
[1] https://swc.rs/
> Elixir etc
I'm not familiar with Elixir nor am I in a googling mood. Nevertheless that was an awfully short list. Why is that?
