From owner-freebsd-hackers@freebsd.org Thu Jun 16 12:35:33 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D55A3A47351 for ; Thu, 16 Jun 2016 12:35:33 +0000 (UTC) (envelope-from freebsd-hackers@herveybayaustralia.com.au) Received: from mail.unitedinsong.com.au (mail.unitedinsong.com.au [150.101.178.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 969601AF5 for ; Thu, 16 Jun 2016 12:35:33 +0000 (UTC) (envelope-from freebsd-hackers@herveybayaustralia.com.au) Received: from [192.168.0.134] (laptop1.herveybayaustralia.com.au [192.168.0.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.unitedinsong.com.au (Postfix) with ESMTPSA id 0D6A862065 for ; Thu, 16 Jun 2016 22:35:29 +1000 (EST) To: freebsd-hackers@freebsd.org From: Da Rock Subject: enabling cpu "features" in custom kernel Message-ID: <2fa5c2cb-81eb-d44a-3011-db27035e7965@herveybayaustralia.com.au> Date: Thu, 16 Jun 2016 22:35:28 +1000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jun 2016 12:35:33 -0000 I'm just trying to get my head around kernel building and clang. 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... One thing I did consider was that there might be some "include" or "option" somewhere that I missed, but I still can't find it. There must be something in the mk files or such, and I'm guessing that its due to the ability to build the freebsd with various workarounds for different systems - but how would I get around that so I can try testing something out? Cheers