Date: Fri, 17 Jun 2016 12:20:21 +0200 From: Dimitry Andric <dim@FreeBSD.org> To: Da Rock <freebsd-hackers@herveybayaustralia.com.au> Cc: freebsd-hackers@freebsd.org Subject: Re: enabling cpu "features" in custom kernel Message-ID: <092CD08F-3896-451D-8A7E-8DCB056D0118@FreeBSD.org> In-Reply-To: <2fa5c2cb-81eb-d44a-3011-db27035e7965@herveybayaustralia.com.au> References: <2fa5c2cb-81eb-d44a-3011-db27035e7965@herveybayaustralia.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_D8E4B48C-DD0C-4A02-94BF-98C22256DEA8 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 16 Jun 2016, at 14:35, Da Rock = <freebsd-hackers@herveybayaustralia.com.au> wrote: >=20 > I'm just trying to get my head around kernel building and clang. >=20 > If I want to enable certain features available on my cpu which are = available by clang, how do I enable them? As I understand it using = ccflags is a no no (ie /etc/make.conf), so how do I go about enabling = them? I seem to be missing something in my research here... You can set CPUTYPE in /etc/make.conf, for example: CPUTYPE?=3Dbroadwell then it will be automatically picked up in the correct places during buildworld, or during ports building. See also make.conf(5) and /usr/share/examples/etc/make.conf. -Dimitry --Apple-Mail=_D8E4B48C-DD0C-4A02-94BF-98C22256DEA8 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.30 iEYEARECAAYFAldjzu4ACgkQsF6jCi4glqOuGwCfeW5Rx0bCC6D6Flk0XBHRzcS+ m6AAn2BBLwYJuZiv/6UmpN07zTMZVBxI =LXDq -----END PGP SIGNATURE----- --Apple-Mail=_D8E4B48C-DD0C-4A02-94BF-98C22256DEA8--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?092CD08F-3896-451D-8A7E-8DCB056D0118>