-
Notifications
You must be signed in to change notification settings - Fork 14
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
back end crashes on this IL: LowerFormalArguments didn't emit the correct number of values (original source had a tuple return value) #89
Comments
Here's a reproduction that compiles standalone declare i8 @do_something(i8 %val)
define { i1, i8 } @main(i8) #2 {
entry:
%1 = call zeroext i8 @do_something(i8 zeroext %0)
%2 = insertvalue { i1, i8 } { i1 true, i8 undef }, i8 %1, 1
ret { i1, i8 } %2
} This bug still occurs on LLVM trunk. |
This is likely a duplicate of #57. That bug is currently titled "Assertion failure on i128". That title is not really accurate though, as from memory I believe when I investigated it the bug did not seem to be I will retitle that issue so that it is also more discoverable if anybody else gets the same error output. |
Cool. Sounds good. :)
Sent from my BlackBerry® wireless device
…-----Original Message-----
From: Dylan McKay <[email protected]>
Date: Thu, 08 Feb 2018 10:25:12
To: avr-rust/rust<[email protected]>
Reply-To: avr-rust/rust <[email protected]>
Cc: Carl Peto<[email protected]>; Author<[email protected]>
Subject: Re: [avr-rust/rust] back end crashes on this IL: LowerFormalArguments
didn't emit the correct number of values (original source had a tuple return
value) (#89)
This is likely a duplicate of #57.
That bug is currently titled "Assertion failure on i128". That title is not really accurate though, as from memory I believe when I investigated it the bug did not seem to be `i128` specific.
I will retitle that issue so that it is also more discoverable if anybody else gets the same error output.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#89 (comment)
|
From this swift code....
...the llvm IR produced is...
...but this crashes llc...
The text was updated successfully, but these errors were encountered: