-
Notifications
You must be signed in to change notification settings - Fork 12.5k
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
LLVM assertion failed: conflicting locations for variable #29541
Comments
Note that I have enabled 2 codegen units (https://github.com/tomaka/rustc-issue-repro/blob/master/Cargo.toml#L8), but it's also buggy even without that line. Using |
I can reproduce this on Linux. |
I have not had the time to really debug into this but my hunch is that LLVM messes up the debuginfo during optimization. This might still be a problem of rustc producing LLVM IR that is not quite valid. |
@michaelwoerister you might check out whether this is still an issue sometime. |
Yes, let's hope that a year of LLVM progress has solved this... |
I cannot reproduce, but for unrelated reasons:
|
Likewise, no repro but for apparently unrelated reasons, like so:
|
I'm not sure if this is still relevant. The original code can't be compiled anymore, because outdated dependencies e.g.:
and a lot more of that. Even when updating all dependencies with So... can this be closed? |
To reproduce, just clone this repo: https://github.com/tomaka/rustc-issue-repro (it's a stripped down version of my project)
cargo build
should trigger:This is with the MSVC 64bits nightly from a few days ago.
The only clue that I have is that here if you replace the call to
VertexBuffer::immutable
withunsafe { ::std::mem::zeroed() }
, it fixes the problem.The problematic call graph is:
The text was updated successfully, but these errors were encountered: