this post was submitted on 02 Oct 2023
47 points (100.0% liked)

Rust

5999 readers
21 users here now

Welcome to the Rust community! This is a place to discuss about the Rust programming language.

Wormhole

!performance@programming.dev

Credits

  • The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)

founded 1 year ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
EdTheLegendary@programming.dev
kahnclusions@programming.dev
torcherist@programming.dev
47
Progress Report #26: rustc_codegen_gcc can now compile Rust for Linux! (blog.antoyo.xyz)
submitted 1 year ago by antoyo@programming.dev to c/rust@programming.dev
6 comments fedilink hide all child comments
 

We just accomplished two big milestones:

  • We can now compile Rust for Linux without any patches to cg_gcc.
  • We can compile, run and pass all the tests from the most popular crates. This is huge!
you are viewing a single comment's thread
view the rest of the comments
[–] antoyo@programming.dev 2 points 1 year ago (1 children)

Do you mean the performance of the tests themselves? If so, how would you suggest that I measure this? By just comparing the execution time?

[–] robinm@programming.dev 2 points 1 year ago (1 children)

Yes exacly. And I assume that the test suite of all of those project are long enough to average the usual jitter of wall time mesurement.

What I'm hoping to see is if rust+llvm vs rustc+gcc binary speed are within a few percents or if there is a real difference between the two (I'm expected that we eventually reach the former once thinLTO and other optimisations are implemented).

And while doing so it could also be possible to measure the difference in max RSS.

[–] antoyo@programming.dev 3 points 1 year ago

Good. I'll attempt to do that for the next update.