(In reply to Hans-Peter Jansen from comment #16) > If it's, after all, "just" an "impedance mismatch" between llvm 13 and rust > 1.55, something in the interface logic between them is broken, and the > lesson learned from this should be at least: build rust only with the llvm, > that upstream uses. I made this suggestion in the PR that fixed the issue, but they make me to understand that: 1. llvm is very slow to compile, so when compiling rustc / cargo is good to use the llvm from the system to gain some speed. 2. rustc is expected to work with some range of llvm versions I think that they are fair points, and TW can help in detecting early issues. But still I think that there should be an outcome of this bug, like working on enabling the tests inside the %check section on the rust package.