i don't really know how much could they optimise more, but they can predict it by fitting the number of cores with the amount of time taken, that is amdahl's law.
this post was submitted on 16 Apr 2025
41 points (90.2% liked)
Rust
6833 readers
3 users here now
Welcome to the Rust community! This is a place to discuss about the Rust programming language.
Wormhole
Credits
- The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)
founded 2 years ago
MODERATORS
Impressive improvement! But why did they choose Rust to compile on demand in the first place, if compile time was that important?
What's the advantage of compiling to Rust here? Maybe it would be faster if they just skipped straight to LLVM.
Cool and all. But missing some experiments:
- cranelift
- multi-threaded rustc
- undoing type erasure after the split
lto = "off"strip = false(for good measure)- [PRIORITY] a website that works with Tridactyl✋
multi-threaded rustc
I am still quite ignorant of the workings of rust/rustc (I'll learn it tomorrow, I swear!) but I'm surprised that multi threaded compilation isn't available by default. make/gcc have had it for several decades
make uses multiple processes for parallelism, or what the blog post (below) calls "interprocess parallelism". cargo/rustc has that and intraprocess parallelism for code generation (the backend) already. the plan is to have parallelism all the way starting from the frontend. This blog post explains it all:
[PRIORITY] a website that works with Tridactyl✋
A man of culture.
They changed the graphic already but holy AI on a stick! Now his arm is still behind the saw but his fingers are already gone. Lol
well at least the saw works right