33 lines · plain
1; RUN: llc -mtriple=i686-- -o - < %s | FileCheck %s2 3; This used to be classified as a tail call because of a mismatch in the4; arguments seen by Analysis.cpp and ISelLowering. As seen by ISelLowering, they5; both return {i32, i32, i32} (since i64 is illegal) which is fine for a tail6; call.7 8; As seen by Analysis.cpp: i64 -> i32 is a valid trunc, second i32 passes9; straight through and the third is undef, also OK for a tail call.10 11; Analysis.cpp was wrong.12 13; FIXME: in principle we *could* support some tail calls involving truncations14; of illegal types: a single "trunc i64 %whatever to i32" is probably valid15; because of how the extra registers are laid out.16 17declare {i64, i32} @test()18 19define {i32, i32, i32} @test_pair_notail(i64 %in) {20; CHECK-LABEL: test_pair_notail21; CHECK-NOT: jmp22 23 %whole = tail call {i64, i32} @test()24 %first = extractvalue {i64, i32} %whole, 025 %first.trunc = trunc i64 %first to i3226 27 %second = extractvalue {i64, i32} %whole, 128 29 %tmp = insertvalue {i32, i32, i32} undef, i32 %first.trunc, 030 %res = insertvalue {i32, i32, i32} %tmp, i32 %second, 131 ret {i32, i32, i32} %res32}33