-
Notifications
You must be signed in to change notification settings - Fork 14
Assertion failed: (!SplitVirtReg->empty() && "expecting non-empty interval"), function allocatePhysRegs #36
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
Comments
I do note that there are |
It looks like even AVR-GCC only supports up to 64-bits. I wonder what the i128 support is like in AVR - I haven't written (nor have ever seen) any explicit 128bit support, but we don't even have to write code for 32-bit or 64-bit integers as LLVM transparently lowers them to many 16-bit operations. Does |
FWIW I've just now got the same assertion failure with no |
I don't think it's worth it - if you've got the same assertion without |
I was able to work around this in my code by inlining a lot of functions; however, this workaround then fails at linking time because the generated functions are suddenly too large. |
I can't reproduce this on current LLVM master, I think |
That would be exciting! I could totally see LLVM lower |
This seems to be fixed in LLVM 5.0, but not in avr-rust/llvm It should get fixed in our next LLVM update. |
I think this might be the one Not sure though |
Gergo has tried cherry-picking that commit and it is still broken |
The linked commit is already in the https://github.com/avr-rust/llvm/tree/avr-rust-2017-10-24 branch of LLVM, but I am still getting the error message when compiling |
Bisection implicates llvm-mirror/llvm@2a303c708 as the commit that fixed this. Unfortunately, that commit cannot be cleanly cherry-picked on its own. |
I am now building a version of
|
Nope; even with all these commits, LLVM fails to build with
So it seems we won't easily be getting this fix from LLVM until we migrate fully over to LLVM 5.0. |
Nice try, looked promising, hopefully the merge won't be too far away |
Since rust moved to LLVM 6 this can be marked as fixed. |
We've recently upgraded to LLVM 8 🎉 I'm going to close any bug that is reported against an older version of LLVM. If you are still having this issue with the LLVM-8 based code, please ping me and I can reopen the issue! |
I commented out all the bignum / dec2flt / flt2dec / diyfloat modules and got to this error.
The text was updated successfully, but these errors were encountered: