-
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
LLVM ERROR: Cannot select: 0xffff6c0e10d8: i32 = vecreduce_mul 0xffff6c072990 #54510
Comments
I think that's some flavor of https://bugs.llvm.org/show_bug.cgi?id=36796. On stdsimd/packed_simd we work around this by falling back to scalar code instead, so this shouldn't be used anywhere in the ecosystem on aarch64 anyways. The "fix" for this is to just ignore this test on aarch64. |
This fails on AArch64 see rust-lang#54510
Ignore aarch64 in simd-intrinsic-generic-reduction This fails on AArch64 see rust-lang#54510 Disabling it for now until it's fixed/implemented in LLVM cc @gnzlbg
Ignore aarch64 in simd-intrinsic-generic-reduction This fails on AArch64 see rust-lang#54510 Disabling it for now until it's fixed/implemented in LLVM cc @gnzlbg
Ignore aarch64 in simd-intrinsic-generic-reduction This fails on AArch64 see rust-lang#54510 Disabling it for now until it's fixed/implemented in LLVM cc @gnzlbg
Update: LLVM PR36796 is fixed. |
It's not merged to Rust's LLVM fork. |
FWIW the commit was released in LLVM 9 which rustc currently uses, so this ought to be fixed. |
Seems like we need to add a test in that case. |
No need for a new test, reverting #57827 (not ignoring that test on AArch64 any longer) should suffice. Although I'm not sure if we have CI for that target. |
I'd suggest to wait for the LLVM 10 upgrade, which will address some additional issues. While LLVM 9 fixed the majority of this, there were still issues with ordered and non-fast reductions in some cases. |
Triage: #57827 is already "reverted" in 6fae7db#diff-1910500d7497a3476e28b7c81e4954faR5 and we're on LLVM 10 now. I think there's nothing more we could do here? Closing. |
Running
x.py test --stage 1
onaarch64-unknown-linux-gnu
I get one failed test as shown below. This is the first time I've run the tests on this target some I'm unsure if it's a regression.Nightly commit af50e38
CC @gnzlbg ?
The text was updated successfully, but these errors were encountered: