From owner-freebsd-stable@freebsd.org Tue Oct 3 15:38:53 2017 Return-Path: Delivered-To: freebsd-stable@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 77DE5E408B2 for ; Tue, 3 Oct 2017 15:38:53 +0000 (UTC) (envelope-from mack@macktronics.com) Received: from borg.macktronics.com (gw.macktronics.com [209.181.253.70]) (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 57F697E506 for ; Tue, 3 Oct 2017 15:38:52 +0000 (UTC) (envelope-from mack@macktronics.com) Received: from pandora.local (olive.macktronics.com [209.181.253.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by borg.macktronics.com (Postfix) with ESMTPS id AA2811F2; Tue, 3 Oct 2017 10:38:50 -0500 (CDT) From: Dan Mack To: Jakub Lach Cc: freebsd-stable@freebsd.org Subject: Re: my build time impact of clang 5.0 References: <1507039968621-0.post@n6.nabble.com> Date: Tue, 03 Oct 2017 10:38:49 -0500 In-Reply-To: <1507039968621-0.post@n6.nabble.com> (Jakub Lach's message of "Tue, 3 Oct 2017 07:12:48 -0700 (MST)") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (darwin) MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Oct 2017 15:38:53 -0000 Jakub Lach writes: > On the other hand, I'm having tremendous increases in Unixbench scores > comparing to > 11-STABLE in the April (same machine, clang 4 then, clang 5 now) (about > 40%). > > I have never seen something like that, and I'm running Unixbench on -STABLE > since > 2008. Agree; clang/llvm and friends have added a lot of value. It's worth it I think. It is however getting harder to continue with a source based update model, which I prefer even though most people just use package managers today. I still like to read the commits and understand what's changing, why, and select the version I am comfortable with given the nuances of my configuration(s). I think that's why 'knock-on-wood' I've been able to track mostly CURRENT and/or STABLE without any outages since about 1998 on production systems :-)