Date: Wed, 7 Oct 2015 21:09:50 +0200 From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-current@freebsd.org, Dimitry Andric <dim@freebsd.org> Subject: Re: CURRENT: build failure with clang 3.7.0 Message-ID: <20151007210950.60474f36.ohartman@zedat.fu-berlin.de> In-Reply-To: <10633363.fQY0fDW1VU@ralph.baldwin.cx> References: <20151007093727.0db8e2e6@freyja.zeit4.iv.bundesimmobilien.de> <EB5AD370-5FFF-4C90-8510-14DB3EFED961@FreeBSD.org> <20151007133323.364655dd@freyja.zeit4.iv.bundesimmobilien.de> <10633363.fQY0fDW1VU@ralph.baldwin.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/l8OH.c3EiCUrReIOOC2qwYv Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Wed, 07 Oct 2015 11:03 -0700 John Baldwin <jhb@freebsd.org> schrieb: > On Wednesday, October 07, 2015 01:33:23 PM O. Hartmann wrote: > > On Wed, 7 Oct 2015 13:23:48 +0200 > > Dimitry Andric <dim@FreeBSD.org> wrote: > >=20 > > > On 07 Oct 2015, at 09:37, O. Hartmann <ohartman@zedat.fu-berlin.de> w= rote: > > > >=20 > > > > I hit on a box this nasty/sticky error when performing buildworld. > > > >=20 > > > > /usr/src is on r288980 > > > ... > > > > --- ieee802_11_common.o --- > > > ... > > > > -c /usr/src/usr.sbin/wpa/wpa_supplicant/../../../contrib/wpa//src/c= ommon/ieee802_11_common.c > > > > -o ieee802_11_common.o Cannot emit physreg copy instruction UNREACH= ABLE > > > > executed > > > > at /usr/src/lib/clang/libllvmx86codegen/../../../contrib/llvm/lib/T= arget/X86/X86InstrInfo.cpp:3935! > > >=20 > > > Somebody else reported the same to me yesterday. This is an upstream > > > bug with AVX (which is still present in llvm trunk), so for now you n= eed > > > to set your CPUTYPE to something that doesn't have AVX, or simply uns= et > > > your CPUTYPE. > > >=20 > > > The bug has been reported upstream, and once there is a fix, I will > > > import it ASAP. > > >=20 > > > -Dimitry > > >=20 > >=20 > > Funny, I have several other boxes, definitely having AVX aboard: > >=20 > > [... from dmesg] > > Jul 29 07:05:52 freyja kernel: CPU: Intel(R) Xeon(R) CPU E5-1650 v3 @ 3= .50GHz > > (3491.98-MHz K8-class CPU) > > Jul 29 07:05:52 freyja kernel: Origin=3D"GenuineIntel" Id=3D0x306f2 F= amily=3D0x6 > > Model=3D0x3f Stepping=3D2 > > Jul 29 07:05:52 freyja kernel: > > Features=3D0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,= PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > > Jul 29 07:05:52 freyja kernel: > > Features2=3D0x7dfefbff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2= ,SSSE3,SDBG,FMA,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,T= SCDLT,XSAVE,OSXSAVE,AVX,F16C,RDRAND> > > Jul 29 07:05:52 freyja kernel: AMD > > Features=3D0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM> > > Jul 29 07:05:52 freyja kernel: AMD Features2=3D0x21<LAHF,ABM> > > Jul 29 07:05:52 freyja kernel: Structured Extended > > Features=3D0x37ab<FSGSBASE,TSCADJ,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,= NFPUSG> > >=20 > > [...] > >=20 > > which is a most recent Haswell XEON and builds world fine. My personal = failing > > box is a i3-32XX, IvyBridge, but the IvyBridge E3-124XX XEON builds wel= l. >=20 > It's not about whether your CPU supports it, it is about whether or not y= ou have > asked the compiler to use it. Normally by setting 'CPUTYPE' in /etc/make= .conf > or the like. (I also was bitten by this yesterday on my sandbridge laptop > where I have 'CPUTYPE=3Dcorei7-avx' in /etc/src.conf.) The workaround is= to not > set CPUTYPE (or set it to something without AVX like just 'corei7'). >=20 Hello. Well, I guess I understood the usage of CPUTYPE. Maybe I did not express my= self in the clear, but I wanted to emphasize the fact that I'm using two CPUs supposedl= y of the same architectural design and if the AVX feature is indeed the culprit, then the= question is why the one CPU compiles and the other not. I use on all machines the very = same src.conf and make.conf except for the kernel name. So this would imply that on all b= oxes the very same feature set, identified by the CPU type, would be used. So far the the= ory. I did not check the expansion of CPUTYPE on both systems failing the buildw= orld, so maybe there is a slight difference there ... Oliver --Sig_/l8OH.c3EiCUrReIOOC2qwYv Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWFW3+AAoJEOgBcD7A/5N8uB4IAJZiNptjiMj6k2EqiBFfokv3 G1XpX9bi+byavLCoqd0MRfP6+qgmSdBe/80gay9rQRRsK8l27RHjLNrEbcmY1c4P FsH7nS8zCutmmc6h7I1UXkjauYnZRMO+j2veE/92bTEeXVEH25k1bcm2orgs4MhT Z9xqRIeYYiuRrtBECneL09zoMRq0K7drJ+16V2Zv6jaAyxTTf96PuvCT9AooAgx1 as44XUtgwCNrmOcKrhPSWENrl//hgYHPKHznpvdA2WSLs8a40Coz7ufjsIY0AsGD 9qXmmBGLx06QZfs4BtGiJTs/1ZPfXOPcGp1FIqUyuPyUnLC4qwkVggPnWOgqBmw= =JJQy -----END PGP SIGNATURE----- --Sig_/l8OH.c3EiCUrReIOOC2qwYv--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20151007210950.60474f36.ohartman>