Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 15 Jul 2018 16:01:25 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 229788] march=ivybridge breaks certain ports
Message-ID:  <bug-229788-227@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229788

            Bug ID: 229788
           Summary: march=3Divybridge breaks certain ports
           Product: Base System
           Version: 11.2-STABLE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: bin
          Assignee: bugs@FreeBSD.org
          Reporter: mi@FreeBSD.org
                CC: dim@FreeBSD.org, gerald@FreeBSD.org

The easiest way to reproduce this problem -- on a fresh FreeBSD-11.2/amd64 =
is
to attempt "make test" in multimedia/x265.

This works on my older system (where march is core2), but the two new ones =
--
with newer Ivy Bridge Xeons (E5-1620) -- break:

  =3D=3D=3D>  Testing for x265-2.6_1
  /symbion/ports/multimedia/x265/work/x265_v2.6/source/test/TestBench
  Using random seed 5B4B6D10 12bit
  Testing primitives: SSE2
  Testing primitives: SSE3
  Testing primitives: SSSE3
  cuTreeFix8Pack failed

  x265: asm primitive has failed. Go and fix that Right Now!

it does not matter, whether OPTIMIZED_CFLAGS is enabled (which adds -O3) --=
 it
builds either way. The only way to get it through is to use a lower march (=
like
core2) or none at all.

Another port, which does not build properly with march=3Divybridge for me is
qt5-core, but that's a lot hairier to deal with...

I noticed this problem after rebuilding world with the recently-committed
clang-6.0.1, but I haven't tested it with the earlier clang-6.0.0 so this m=
ay
be an older bug.

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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-229788-227>