-
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
Assertion failed error on nightly-2017-04-22 #41479
Comments
Just wanted to add that it works with |
Which commit causes the assertion failure? Is it the latest one (e36e120)? |
Yep, that should do it. My current nightly is at Edit: Some more details:
|
Can confirm LLVM assertion. |
Looks like a ZST pair. |
Looking at the |
It would be good to come up with a simple test case which exhibits this crash, the code in question is in a macro, so not that easy to see what it's doing. |
Reduced failing code down to https://pastebin.com/RFKDmsbZ. Probably as far as I can easily go. |
@bitshifter That's correct - it's hard to see it in a diff, but if packing changed, unpacking should too. |
Seems it's not the indexing in this case, although that does look wrong. The
Which doesn't look right. |
PR at #41529. Not sure if I should add https://pastebin.com/RFKDmsbZ as a test. I haven't been able to come up with a simpler reproduction. And it's a copy of code from https://github.com/lloydmeta/frunk, not sure if that's OK. |
@bitshifter Okay let me try. |
fn split<A, B>(pair: (A, B)) {
let _a = pair.0;
let _b = pair.1;
}
fn main() {
split(((), ((), ())));
} |
Add missing OperandPair struct field index adjustments. Fixes rust-lang#41479. This is a bug fix for a regression in rust-lang@6d841da.
Add missing OperandPair struct field index adjustments. Fixes rust-lang#41479. This is a bug fix for a regression in rust-lang@6d841da.
triage: P-high (regression) |
Some accesses in OperandPairs were missing. Fixes rust-lang#41479.
Trying to bench Frunk with the latest nightly gives me the following error:
I was told to file a bug here by someone in the users forum
The text was updated successfully, but these errors were encountered: