https://bugzilla.suse.com/show_bug.cgi?id=1192067 https://bugzilla.suse.com/show_bug.cgi?id=1192067#c22 --- Comment #22 from William Brown <william.brown@suse.com> ---

Usually Mesa wants a newer LLVM and that's how it ends up in SLE. But I'd ship the newest version at the time of release in Leap even if it wasn't for Mesa.

Yep, thought it was something like this. But again, I'm not really involved in that side of things ....

I see two possible reasons why things didn't work out this time:

* Normally Rust doesn't compile with newer LLVMs because of interface changes, but this time that hasn't been the case. The relevant PR https://github.com/rust-lang/rust/pull/87570 was not in 1.55, yet we didn't have any compiler errors. With previous LLVM updates I saw that Rust didn't build and then I either ported back the "Upgrade to LLVM XX" PR or we waited for the next release to come out. This time we didn't see any errors, so we didn't do anything.

* The new pass manager is now the "default". Rust switched in https://github.com/rust-lang/rust/pull/88243, also in 1.56. The old PM is still maintained, but probably not as well-tested anymore since Clang made the switch.

I think 87570 is the likely missing piece, but it's a good lesson that we don't just need a minimum llvm version for rust, but also a maximum one because anything newer may not be tested or supported. So again, the lock-step will resolve that and reduce our potential surface area to issues. -- You are receiving this mail because: You are on the CC list for the bug.