From e29b7689bd181f35a515dac093858b56bf2a8b47 Mon Sep 17 00:00:00 2001 From: Matthias Braun Date: Fri, 20 May 2016 23:02:13 +0000 Subject: MachineVerifier: subregs so not require defs/valnos on every path It is fine for subregister ranges to be undefined on some CFG paths as we may have a "vregX:other_subreg =" def on that path. We do not (and should not) have live segments for the subregister ranges. The MachineVerifier should not complain about this. This is a slight variant of http://llvm.org/PR27705 llvm-svn: 270290 --- .../CodeGen/AMDGPU/undefined-subreg-liverange.ll | 26 ++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 llvm/test/CodeGen/AMDGPU/undefined-subreg-liverange.ll (limited to 'llvm/test/CodeGen/AMDGPU/undefined-subreg-liverange.ll') diff --git a/llvm/test/CodeGen/AMDGPU/undefined-subreg-liverange.ll b/llvm/test/CodeGen/AMDGPU/undefined-subreg-liverange.ll new file mode 100644 index 00000000000..4f8c69db019 --- /dev/null +++ b/llvm/test/CodeGen/AMDGPU/undefined-subreg-liverange.ll @@ -0,0 +1,26 @@ +; RUN: llc -verify-machineinstrs -o /dev/null %s +; We may have subregister live ranges that are undefined on some paths. The +; verifier should not complain about this. +target triple = "amdgcn--" + +define void @func() { +B0: + br i1 undef, label %B1, label %B2 + +B1: + br label %B2 + +B2: + %v0 = phi <4 x float> [ zeroinitializer, %B1 ], [ , %B0 ] + br i1 undef, label %B30.1, label %B30.2 + +B30.1: + %sub = fsub <4 x float> %v0, undef + br label %B30.2 + +B30.2: + %v3 = phi <4 x float> [ %sub, %B30.1 ], [ %v0, %B2 ] + %ve0 = extractelement <4 x float> %v3, i32 0 + store float %ve0, float addrspace(3)* undef, align 4 + ret void +} -- cgit v1.2.3