this post was submitted on 01 Sep 2026
9 points (100.0% liked)

Rust

8277 readers
26 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 3 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
EdTheLegendary@programming.dev
torcherist@programming.dev
9
rustc_codegen_gcc: Progress Report #43 (blog.antoyo.xyz)
submitted 1 week ago by antoyo@programming.dev to c/rust@programming.dev
4 comments fedilink hide all child comments
 

I'm happy that unwinding is finally fixed: that was the biggest unknown for me. I'm also happy that we have very few UI tests from the Rust test suite that fail now: there are still some other test suites to run, but having only 21 failures among the UI tests is a big achievement.

you are viewing a single comment's thread
view the rest of the comments
[–] BB_C@programming.dev 1 points 1 week ago (1 children)

Thank you for your detailed reply.

Focusing on x86_64 (and linux), can you expand on what's missing to reach ABI parity?

And somewhat relatedly, are you leaning towards publishing an std component built with the backend or not?

[–] antoyo@programming.dev 2 points 1 week ago

Focusing on x86_64 (and linux), can you expand on what’s missing to reach ABI parity?

I haven't look much into it, but perhaps the sret fix mentioned above would fix some issues on x86-64. For the rest, this is mostly bug fixing (we probably don't handle the alignment everywhere) and fuzzing with ABI cafe.

And somewhat relatedly, are you leaning towards publishing an std component built with the backend or not?

I haven't thought much about this, but I guess an idea would be to ship a std for targets not supported by LLVM.