Twitter | Pretraživanje | |
Patrick Walton
Rust compiler performance is hard to have meaningful discussions about because: (1) There’s no single part of the compiler which is slow. In fact the compiler is pretty well optimized.
Reply Retweet Označi sa "sviđa mi se" More
Patrick Walton 2. velj
Odgovor korisniku/ci @pcwalton
(2) There’s no high-profile language design decision you can point to and say “aha, that was a mistake!” No header files, for example. The slowness comes from a lot of smaller things that have real benefits, such as the borrow check.
Reply Retweet Označi sa "sviđa mi se"
Tony “Abolish ICE” Arcieri 🦀 3. velj
Odgovor korisniku/ci @pcwalton
How about a secure distribured compiler cache?
Reply Retweet Označi sa "sviđa mi se"
CuddleViper 21 h
Odgovor korisniku/ci @bascule @pcwalton
Could define secure? What are the requirements here?
Reply Retweet Označi sa "sviđa mi se"
Lefteris Stamatogiannakis 2. velj
Odgovor korisniku/ci @pcwalton
What % of the total compilation time is due to the checks? Maybe a quick no-check compilation mode would be beneficial for quick edits? Programming has a rhythm where big changes are followed by many smaller ones. A no-check compilation may be useful for the small changes.
Reply Retweet Označi sa "sviđa mi se"
Rich Felker 3. velj
Odgovor korisniku/ci @estama2 @pcwalton
Seems you'd always want no-check when building as a user rather than a developer unless you distrust upstream...
Reply Retweet Označi sa "sviđa mi se"
AVX-512 3. velj
Odgovor korisniku/ci @pcwalton
trait bounds resolution has something extremely non linear in it, i can point to that
Reply Retweet Označi sa "sviđa mi se"
AVX-512 3. velj
Odgovor korisniku/ci @pcwalton
i guess i should do the work if creating a minimal example and submit a pr
Reply Retweet Označi sa "sviđa mi se"
glandium 3. velj
Odgovor korisniku/ci @pcwalton @nnethercote
's work would tend to contradict this.
Reply Retweet Označi sa "sviđa mi se"
Nicholas Nethercote 3. velj
Odgovor korisniku/ci @MikeHommey @pcwalton
I would say that 3 years ago it wasn't well optimized, and finding improvements was really easy. Today it's much harder. So I think "pretty well optimized" is a reasonable description.
Reply Retweet Označi sa "sviđa mi se"
Dmitry Popov 15 h
Odgovor korisniku/ci @pcwalton
LLVM? Has anyone seen an LLVM-based compiler these days that wasn't slow?
Reply Retweet Označi sa "sviđa mi se"