10
rustc_codegen_gcc: Progress Report #43 (blog.antoyo.xyz)
submitted 2 months ago by 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
[–] 1 point 2 months ago (1 child)

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?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] [S] 2 points 2 months 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.

  • permalink
  • fedilink
  • source
  • parent