Date: Sun, 29 Sep 2019 01:09:12 +0100 From: tech-lists <tech-lists@zyxst.net> To: freebsd-questions@freebsd.org Subject: Re: make.conf for a poudriere jail and CPUTYPE Message-ID: <20190929000912.GI49516@bastion.zyxst.net> In-Reply-To: <CAGLDxTXb8rnzRyc4W%2BQ6umkWbw9KwakAEBG8_NGmi8LWfkQwrw@mail.gmail.com> References: <20190927113336.GB49516@bastion.zyxst.net> <20190928121624.GC49516@bastion.zyxst.net> <20190928150629.914bf447.freebsd@edvax.de> <20190928133552.GD49516@bastion.zyxst.net> <CAGLDxTXb8rnzRyc4W%2BQ6umkWbw9KwakAEBG8_NGmi8LWfkQwrw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--FK65GREB+Evh/hTL Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, On Sat, Sep 28, 2019 at 01:58:03PM -0500, Clay Daniels Jr. wrote: >RE: " as btver1 and sandybridge are the same arch (amd64) just different >cpus " > >I'm confused here: >" *Sandy Bridge* is the codename for the microarchitecture used in the >"second generation" of the Intel Core processors (Core i7, i5, i3) " > >" AMD Bobcat CPU (btver1)" >" =E2=80=98btver1=E2=80=99 CPUs based on AMD Family 14h cores with x86-64 = instruction set >support." >" btver1 is a SSSE3/SSE4a only CPU - it doesn't have AVX and doesn't >support XSAVE." I'm getting this information from /usr/share/examples/etc/make.conf [..snip...] # The CPUTYPE variable controls which processor should be targeted for # generated code. This controls processor-specific optimizations in # certain code (currently only OpenSSL) as well as modifying the value # of CFLAGS to contain the appropriate optimization directive to cc. # The automatic setting of CFLAGS may be overridden using the # NO_CPU_CFLAGS variable below. # Currently the following CPU types are recognized: # Intel x86 architecture: # (AMD CPUs) amdfam10, opteron-sse3, athlon64-sse3, k8-sse3, # opteron, athlon64, athlon-fx, k8, athlon-mp, # athlon-xp, athlon-4, athlon-tbird, athlon, k7, # geode, k6-3, k6-2, k6 # (Intel CPUs) core2, core, nocona, pentium4m, pentium4, prescott, # pentium3m, pentium3, pentium-m, pentium2, # pentiumpro, pentium-mmx, pentium, i486 # (VIA CPUs) c7, c3-2, c3 # AMD64 architecture: amdfam10, opteron-sse3, athlon64-sse3, k8-sse3, # opteron, athlon64, k8, core2, nocona # SPARC-V9 architecture: v9 (generic 64-bit V9), ultrasparc (default # if omitted), ultrasparc3 # Additionally the following CPU types are recognized by clang: # Intel x86 architecture (for both amd64 and i386): # (AMD CPUs) znver1, bdver4, bdver3, bdver2, bdver1, btver2, btv= er1 # (Intel CPUs) tremont, goldmont-plus, icelake-server, # icelake-client, # cannonlake, knm, skylake-avx512, knl, goldmont, # skylake, broadwell, haswell, ivybridge, # sandybridge, westmere, nehalem, silvermont, bonnell # [...snip...] The reason I want to use CPUTYPE?=3Dbtver1 is because that's the cpu in the target machine, the machine in question has limited resources, and I want= =20 to build ports tailored to those resources and abilities. As you can see=20 =66rom the quoted text, both sandybridge and btver1 are recognised as=20 cputypes by clang. --=20 J. --FK65GREB+Evh/hTL Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEE8n3tWhxW11Ccvv9/s8o7QhFzNAUFAl2P9h4ACgkQs8o7QhFz NAW24w/9FiV7YeJTeDwrvsESQAGMRZB805etr3mMsVQQ/0OAfSBZyQDtVAR4iF7B j0h+p+PIjS7lV570RkzRmhYPm7P5q84xKbD7rSQq5RPYqFsBqgGPoVK27vE1KZC7 RhSsOvcsCh3Beh5M8AtkvXS3f4ykN4O08G9SHMQh8QoM2CntGYIkx/m6tsrqOu9o 1qaaop3A8AZHJ1Ch8FHtu8weW6NYi1JH/jGoURjy1lzMCpVZZl9iVI3mA2wisCoD MapX1JUdbjFAeWOgfDbUvtMeqxW9VP4x9iMeMum03IPcA1G7esicaxZjcEAtVleY RR0GlhGJgsTEGvu1zyn0SBoVkE90DUrV474zkTxmvjyfIYhB31d8P/RUBMSrNDs6 DbeCwW8naApkbPGqguqSW1/o380FtclTgjvyWmDu4E50WskctVbBnjr1TEHlSnR2 NhflUxiLUndA+/NmfysZbU46vpUBy2f2i+pZkfT03UpfZLOtr6CXqmjoE2u6MRHN PO/ANa5jgbL0zgcW00WFcUROYI6YSsdw908boCLjtV56IQtgUTFwnmyTa0ZLYJQ/ mJw/ud+L+cqVi73EnLSl84sW/YDngDg9hQ2iHpVDwCLESobYWg0xeefn0otUkENl h99vzRrKDsPMJ2upISrJUJey4MU3+Z1NNOiMD/GtpozJvEdWRQU= =S7y0 -----END PGP SIGNATURE----- --FK65GREB+Evh/hTL--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190929000912.GI49516>