News for hackers. Stuff that matters.

A comment on Closing the gap: cross-language LTO between Rust and C/C++. Parent comment

Re:Closing the gap: cross-language LTO between Rust and C/C++ by kzrdude on Thursday September 19, 2019 @04:17PM (#21020285)
Wouldn't MIR be more portable to the future as well? Building on Rust's own equity and all that, because future Rust will probably still use MIR but could replace LLVM(?)
[ Parent | on HN ]
Re:Closing the gap: cross-language LTO between Rust and C/C++ by monocasa on Thursday September 19, 2019 @07:52PM (#21021935)
They wouldn't want to do MIR without upstreaming the Rust frontend, which I don't see happening anytime soon.
[ Parent | on HN ]
Re:Closing the gap: cross-language LTO between Rust and C/C++ by kzrdude on Friday September 20, 2019 @06:38AM (#21025147)
MIR should stay with Rustc, and that's the point — to work on optimizations that happen in Rustc, and not later when the code is turned over to llvm, or other backend.
[ Parent | on HN ]