3 ms·
This is rubbish. The bug exists in LLVM regardless of whether Rust has its own fork, and you don't even need to use Rust to reproduce it. Furthermore, using yo
by Diggsey 7y ago
This is rubbish. The bug exists in LLVM regardless of whether Rust has its own fork, and you don't even need to use Rust to reproduce it.
Furthermore, using your system (ie. unmodified) LLVM with Rust is supported, and still exhibits this bug.
- jfkebwjsbx 7y ago> This is rubbish. Please mind your manners. > The bug exists in LLVM regardless of whether Rust has its own fork, and you don't even need to use Rust to reproduce it. It is not a bug in the broken sense since it was intended. There is simply no way to create a formally infinite loop in LLVM IR. Clang in C mode (and rustc) are generating known broken LLVM IR for their semantics, Clang in C++ is fine. They could add something to the generated IR to make it formally finite in the IR instead of waiting years until LLVM IR adds something for that niche case. > Furthermore, using your system (ie. unmodified) LLVM with Rust is supported, and still exhibits this bug. That has nothing to do with what I said. The point is that if no frontend cares for such a feature, LLVM may not care about adding it. If rustc was inside the LLVM project, like Clang and others are, then it would be a "bug" of LLVM and they would have an incentive for fixing it. But given Clang does not care either in C mode, I don't have my hopes up.