You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using this custom target to compile libcore (and I'd assume any other crate), rustc ICEs on an unwrap in the above named function.
This unwrap at diagnostic.rs:88 seems to be only able to fail if there's a null reference in LLVM (or in the rustc shim)
The text was updated successfully, but these errors were encountered:
csmoe
added
A-codegen
Area: Code generation
A-LLVM
Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.
labels
Oct 20, 2018
Correction: The original diagnosis was wrong, the crash is in InlineAsmDiagnostic::unpack. it's expecting instruction to be non-None/null, but LLVM appears to permit this to be nullptr
make asm diagnostic instruction optional
`DiagnosticInfoInlineAsm::getInstruction` may return a null pointer, so
the instruction shouldn't be blindly unwrapped.
Reopening from #55193. I was unable to trigger the assertion on Windows after rebasing.
Fixes#23458.
Fixes#55216.
When using this custom target to compile libcore (and I'd assume any other crate), rustc ICEs on an unwrap in the above named function.
This unwrap at diagnostic.rs:88 seems to be only able to fail if there's a null reference in LLVM (or in the rustc shim)
The text was updated successfully, but these errors were encountered: