We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Running be89521 with LLVM 16.
./cconv_more.t:600: scalar test failed for N=10, {uint8_t_2,uint8_t_2,uint8_t_2,uint8_t_2,uint8_t_2,uint8_t_2,uint8_t_2,uint8_t_2,uint8_t_2,uint8_t_2} -> uint8: error code 164
Comparing the signatures:
define zeroext i8 @cbb10(i64 %x1.coerce, i64 %x2.coerce, i64 %x3.coerce, i64 %x4.coerce, i64 %x5.coerce, i64 %x6.coerce, i64 %x7.coerce, i64 %x8.coerce, i64 %x9.coerce, i64 %x10.coerce) #0 { define internal i8 @"$tbb10"(i16 %0, i16 %1, i16 %2, i16 %3, i16 %4, i16 %5, i16 %6, i16 %7, i16 %8, i16 %9) #2 {
Looks like Clang is promoting the arguments to i64 which may result in extra padding if we pass them on the stack?
i64
The text was updated successfully, but these errors were encountered:
For posterity, I confirmed that it also fails on LLVM 11, 13, 14, and 15. (So not sensitive to LLVM version, and not a regression.)
Sorry, something went wrong.
No branches or pull requests
Running be89521 with LLVM 16.
Comparing the signatures:
Looks like Clang is promoting the arguments to
i64
which may result in extra padding if we pass them on the stack?The text was updated successfully, but these errors were encountered: