CPUTYPE?= in make.conf

[tech-lists]

Hi,

I hope this is the right place to ask about this; if not please suggest where?

I have a large poudriere system running 12.1-STABLE #0 r352869. It compiles
ports in poudriere jails for many other smaller systems, some on same arch
(amd64) but different cpu types.

The host cputype is:

# llvm-tblgen --version
LLVM (http://llvm.org/):
  LLVM version 8.0.1
  Optimized build.
  Default target: x86_64-unknown-freebsd12.1
  Host CPU: sandybridge

The actual cpu is Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz (x2)

If I make a make.conf for a poudriere jail and define CPUTYPE?=btver1, several
ports fail to compile, like python36 and lzo2.

If I do the same and define it as CPUTYPE?=haswell, *everything* fails apart
from building the jail itself.

If I do the same thing on a different host, where the host cpu is: Intel(R)
Core(TM) i7-4770K CPU @ 3.50GHz

no failures happen. llvm-tblgen here reports haswell. The freebsd version is
the same.

What I'm asking is, is this a hardware failure on the failing system? Or is it
a capabilities issue, in that the one having the problem hasn't got the right
instruction set?

The Xenon differs from the i7 in that it doesn't have these cpu instructions
available:

AVX AVX2 BMI1 BMI2 F16C FMA3 
Supervisor Mode Execution Protection
Advanced Bit manipulation
Enhanced REP MOVSB/STOSB
INVPCID
MOVBE
RD/WR FSGSBASE instructions
RDRAND

I'm hoping for a performance boost if ports are compiled to the specific
cputype of the target machine. if I don't specify cputype at all on the
failing system, the ports will compile. Is it an instruction set issue or is
the Xenon actually failing in some way?

thanks,
-- 
J.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20191004/27d28dea/attachment.sig>