Could you please point to the relevant source code for these? From what I could find here, this doesn't seem implemented for the LLVM backend either.
If VFP uses target-specific intrinsics, there's a chance that this doesn't work correctly in the GCC backend yet since our auto-generated mapping we have needs many adjustments and we only added the adjustments for x86-64.
We finally were able to finish the sync with the Rust compiler and now support the types f16 and f128!
I had a lot of stuff going on lately in my private life, so I wasn't able to work as much as I wanted on rustc_codegen_gcc. Hopefully, it should be back to normal after my vacation.
We fixed a couple of bugs and improved the support for Aarch64 which was requested by some people.
We now run part of the tests in the Rust repo's CI, which is the first step to eventually distributing the GCC codegen via rustup! We also improved a lot the cross-compilation situation.
Good. I'll attempt to do that for the next update.
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?
Antoyo's Personal Blog
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!