31 lines · plain
1; RUN: llc < %s -asm-verbose=false -verify-machineinstrs -disable-wasm-fallthrough-return-opt -wasm-disable-explicit-locals -mattr=+simd128 | FileCheck %s2 3; Regression test for an issue with patterns like the following:4;5; t101: v4i32 = BUILD_VECTOR t99, t99, t99, t996; t92: i32 = extract_vector_elt t101, Constant:i32<0>7; t89: i32 = sign_extend_inreg t92, ValueType:ch:i88;9; Notice that the sign_extend_inreg has source value type i8 but the10; extracted vector has type v4i32. There are no ISel patterns that11; handle mismatched types like this, so we insert a bitcast before the12; extract. This was previously an ISel failure. This test case is13; reduced from a private user bug report, and the vector extracts are14; optimized out via subsequent DAG combines.15 16target triple = "wasm32-unknown-unknown"17 18; CHECK-LABEL: foo:19; CHECK: .functype foo (i32) -> ()20; Implementation omitted...21; CHECK: return22define void @foo(ptr %p) {23 %1 = load <4 x i8>, ptr %p24 %2 = sitofp <4 x i8> %1 to <4 x double>25 %3 = fmul <4 x double> zeroinitializer, %226 %4 = fadd <4 x double> %3, zeroinitializer27 %5 = fptrunc <4 x double> %4 to <4 x float>28 store <4 x float> %5, ptr undef29 ret void30}31