[Bug 211563] CPUTYPE=skylake build broken

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Sat Aug 13 14:36:16 UTC 2016


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211563

--- Comment #4 from Dimitry Andric <dim at FreeBSD.org> ---
Hm, so after hand merging llvm r263417 [1], which fixes your original test
case, I tried a buildworld with CPUTYPE=skylake, and I got another crash:

fatal error: error in backend: Cannot select: t24: i32 = X86ISD::CMP t48, t51
  t48: i1 = truncate t47
    t47: i8 = and t32, t35
      t32: i8 = X86ISD::SETCC Constant:i8<4>, t30
        t31: i8 = Constant<4>
        t30: i32 = X86ISD::CMP t4, Constant:i8<0>
          t4: i8 = AssertZext t2, ValueType:ch:i1
            t2: i8,ch = CopyFromReg t0, Register:i8 %vreg375
              t1: i8 = Register %vreg375
          t5: i8 = Constant<0>
      t35: i8 = X86ISD::SETCC Constant:i8<4>, t34:1
        t31: i8 = Constant<4>
        t34: i32,i32 = X86ISD::SUB t9, Constant:i32<101>
          t9: i32,ch = CopyFromReg t0, Register:i32 %vreg378
            t8: i32 = Register %vreg378
          t11: i32 = Constant<101>
  t51: i1 = truncate t50
    t50: i8 = or t32, t38
      t32: i8 = X86ISD::SETCC Constant:i8<4>, t30
        t31: i8 = Constant<4>
        t30: i32 = X86ISD::CMP t4, Constant:i8<0>
          t4: i8 = AssertZext t2, ValueType:ch:i1
            t2: i8,ch = CopyFromReg t0, Register:i8 %vreg375
              t1: i8 = Register %vreg375
          t5: i8 = Constant<0>
      t38: i8 = X86ISD::SETCC Constant:i8<9>, t37:1
        t25: i8 = Constant<9>
        t37: i32,i32 = X86ISD::SUB t9, Constant:i32<112>
          t9: i32,ch = CopyFromReg t0, Register:i32 %vreg378
            t8: i32 = Register %vreg378
          t14: i32 = Constant<112>
In function: __vfwscanf

So all is not well yet for -march=skylake.  I will investigate further, but
maybe complete Skylake support is something that has to wait for clang 3.9.0.

[1] http://llvm.org/viewvc/llvm-project?view=revision&revision=263417

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-bugs mailing list