From 47f3649374aeec6c029c45cd3ab44b47d7e7ea08 Mon Sep 17 00:00:00 2001 From: Ulrich Weigand Date: Wed, 16 Dec 2015 18:04:06 +0000 Subject: [SystemZ] Fix assertion failure in adjustSubwordCmp When comparing a zero-extended value against a constant small enough to be in range of the inner type, it doesn't matter whether a signed or unsigned compare operation (for the outer type) is being used. This is why the code in adjustSubwordCmp had this assertion: assert(C.ICmpType == SystemZICMP::Any && "Signedness shouldn't matter here."); assuming the the caller had already detected that fact. However, it turns out that there cases, in particular with always-true or always- false conditions that have not been eliminated when compiling at -O0, where this is not true. Instead of failing an assertion if C.ICmpType is not SystemZICMP::Any here, we can simply *set* it safely to SystemZICMP::Any, however. llvm-svn: 255786 --- llvm/test/CodeGen/SystemZ/int-cmp-52.ll | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 llvm/test/CodeGen/SystemZ/int-cmp-52.ll (limited to 'llvm/test/CodeGen/SystemZ/int-cmp-52.ll') diff --git a/llvm/test/CodeGen/SystemZ/int-cmp-52.ll b/llvm/test/CodeGen/SystemZ/int-cmp-52.ll new file mode 100644 index 00000000000..a0b72371d1c --- /dev/null +++ b/llvm/test/CodeGen/SystemZ/int-cmp-52.ll @@ -0,0 +1,24 @@ +; This used to crash the backend due to a failed assertion. +; No particular output expected, but must compile. +; +; RUN: llc < %s -mtriple=s390x-linux-gnu + +define void @test(i16 *%input, i32 *%result) { +entry: + %0 = load i16, i16* %input, align 2 + %1 = zext i16 %0 to i32 + %2 = icmp slt i32 %1, 0 + br i1 %2, label %if.then, label %if.else + +if.then: + store i32 1, i32* %result, align 4 + br label %return + +if.else: + store i32 0, i32* %result, align 4 + br label %return + +return: + ret void +} + -- cgit v1.2.3