Closing the gap: cross-language LTO between Rust and C/C++

Re:Closing the gap: cross-language LTO between Rust and C/C++ by Piezoid on Thursday September 19, 2019 @12:42PM (#21017938)

Do you think it's planned to bring back noalias in rustc ?

This, along with const generics and simd, would make rust the perfect language for me.

[ Parent | on HN ]

Re:Closing the gap: cross-language LTO between Rust and C/C++ by adrianN on Thursday September 19, 2019 @12:49PM (#21018020)

There is an issue for that: https://github.com/rust-lang/rust/issues/54878

[ Parent | on HN ]

Re:Closing the gap: cross-language LTO between Rust and C/C++ by pcwalton on Thursday September 19, 2019 @01:03PM (#21018181)

The upstream fix seems to be blocked on DannyBee in fact…

[ Parent | on HN ]

Re:Closing the gap: cross-language LTO between Rust and C/C++ by DannyBee on Friday September 20, 2019 @06:32PM (#21031991)

???????

I stopped working on LLVM about 2 years ago (give or take), as i now have way too many reports to be able to do any effective patch or design review, or honestly, keep up with the mailing list. I'm also too far divorced from work being done.

(I unsubscribed late last year)

I specifically reviewed and approved the llvm.noalias patches before i stopped, which is why they are marked as accepted by hal, back in 2016.

More than that, i was one of the people who basically showed that !noalias/etc is fundamentally broken and can't be fixed.

Nothing should be blocked on me at this point, and my reviews account is deliberately disabled so that people can't assign/add me to things.

If something is blocked on me, hal certainly hasn't let me know :)

[ Parent | on HN ]

Re:Closing the gap: cross-language LTO between Rust and C/C++ by pcwalton on Saturday September 21, 2019 @12:17PM (#21036194)

Understood. Sorry, it was not clear to me what was going on. In any case, the fix seems to be blocked on something, as it hasn't landed yet, and it's unclear what.

[ Parent | on HN ]