-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rustc/LLVM DiagnosticKind mismatch causes crash when bootstrapping unoptimized w/ MIR. #35131
Comments
Probably the same as #34427 |
@eddyb You're darned tootin' right I do! But it's not a very good one...
I have no idea what's going on over in thread 2 there. |
This happens on my other machine aswell 😦 |
@eddyb Could be but a MIR-only memory error would have been too big a coincidence to ignore. |
I'm sure you're right, however the Rust cause is clearly related to MIR, and LLVM codegen could well be fine. (that's my bet for now) |
@eddyb Correct. |
With a debug LLVM (on the upgrade to 3.9 branch) I get this:
This only happened with |
@eddyb Well it was broken for me on yesterday's master, from a fresh clone 😕 |
I can reproduce on master, 535cea0, |
@sanxiyn Can you reproduce by running |
Yes, I can reproduce manually. Backtrace is similar to what @canndrew already posted.
|
@sanxiyn Can you dump |
On IRC @sanxiyn has provided enough information to track it down to There should be no C++ types in the rustllvm C APIThis is very important, for both compatibility with more than one version, and for keeping our Rust definitions working across LLVM upgrades without silent breakage (like this one). cc @alexcrichton @badboy @rust-lang/compiler |
@sanxiyn managed to get it to print:
I have no reason to believe this is MIR-specific, just triggered by MIR due to a combination of factors.
|
I'm unable to build rustc with MIR on my machine. I've tried to do a completely fresh build by running:
.. and rustc segfaults
I'm running gentoo linux-3.14.14 x86_64 on a Core i7-2677M with 4GB of RAM.
The text was updated successfully, but these errors were encountered: