From owner-freebsd-current@FreeBSD.ORG Wed Sep 5 09:31:25 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 397FA106564A for ; Wed, 5 Sep 2012 09:31:25 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) by mx1.freebsd.org (Postfix) with ESMTP id E44A68FC12 for ; Wed, 5 Sep 2012 09:31:24 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7:0:d43c:3039:49b5:2229] (unknown [IPv6:2001:7b8:3a7:0:d43c:3039:49b5:2229]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id A06145C44; Wed, 5 Sep 2012 11:31:23 +0200 (CEST) Message-ID: <50471BEE.6030708@andric.com> Date: Wed, 05 Sep 2012 11:31:26 +0200 From: Dimitry Andric User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20120828 Thunderbird/16.0 MIME-Version: 1.0 To: Garrett Cooper References: <5046670C.6050500@andric.com> <20120904214344.GA17723@troutmask.apl.washington.edu> <504679CB.90204@andric.com> <20120904221413.GA19395@troutmask.apl.washington.edu> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Steve Kargl Subject: Re: Compiler performance tests on FreeBSD 10.0-CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Sep 2012 09:31:25 -0000 On 2012-09-05 01:40, Garrett Cooper wrote: ... > Steve does have a point. Posting the results of > CFLAGS/CPPFLAGS/LDFLAGS/etc for config.log (and maybe poking through > the code to figure out what *FLAGS were used elsewhere) is more > valuable than the data is in its current state (unfortunately.. > autoconf makes things more complicated). Just to note, autoconf is not used in the FreeBSD source tree, so it does not apply to the first two builds in the performance test (e.g. building in-tree clang and gcc). The other build is Boost, which has yet another totally different build system, based on Perforce's Jam. Again, no autoconf. In any case, for all three builds, the default optimization options were used. Basically: 1) For building the FreeBSD in-tree version of clang 3.2: -O2 -pipe -fno-strict-aliasing These are just the default FreeBSD optimization flags for building clang, which are probably used by the majority of users out there. This is the case that I was interested in particularly. The -fno-strict-aliasing is not really my choice, but it was introduced in the past by Nathan Whitehorn, who apparently saw problems without it. It will hopefully disappear in the future. 2) For building the FreeBSD in-tree version of gcc 4.2.1: -O2 -pipe These are the default FreeBSD optimization flags. 3) For building Boost 1.50.0: -ftemplate-depth-128 -O3 -finline-functions These are the Boost defaults for gcc-compatible compilers, from tools/build/v2/tools/gcc.jam.