From owner-freebsd-current@FreeBSD.ORG  Sat Jul  5 13:10:56 2014
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 4AF9DAFF;
 Sat,  5 Jul 2014 13:10:56 +0000 (UTC)
Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "cloud.theravensnest.org",
 Issuer "StartCom Class 1 Primary Intermediate Server CA" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 102F328B2;
 Sat,  5 Jul 2014 13:10:55 +0000 (UTC)
Received: from [192.168.0.7] (cpc14-cmbg15-2-0-cust307.5-4.cable.virginm.net
 [82.26.1.52]) (authenticated bits=0)
 by theravensnest.org (8.14.7/8.14.7) with ESMTP id s65DAps0032754
 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
 Sat, 5 Jul 2014 13:10:53 GMT (envelope-from theraven@FreeBSD.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: [HEADS-UP] Problem with clang in 9-stable [was: r268244
 (stable/9) seems to break "sysctl hw.ncpu"]
From: David Chisnall <theraven@FreeBSD.org>
In-Reply-To: <F7112AF8-82DD-410D-97A1-C01FFB49B3B4@FreeBSD.org>
Date: Sat, 5 Jul 2014 14:10:46 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <771D269B-AC6D-4686-ABB0-04F7DCD3A8D9@FreeBSD.org>
References: <20140704123901.GR6056@albert.catwhisker.org>
 <53B6E218.5070009@selasky.org> <20140704174705.GS6056@albert.catwhisker.org>
 <53B6EDD1.8030506@selasky.org> <20140704181831.GV6056@albert.catwhisker.org>
 <909248A4-1B7C-4836-ADAA-F81A70A8AC3C@theravensnest.org>
 <F7112AF8-82DD-410D-97A1-C01FFB49B3B4@FreeBSD.org>
To: Dimitry Andric <dim@FreeBSD.org>
X-Mailer: Apple Mail (2.1878.6)
Cc: Hans Petter Selasky <hps@selasky.org>, stable@freebsd.org,
 "current@freebsd.org" <current@freebsd.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jul 2014 13:10:56 -0000

On 5 Jul 2014, at 14:07, Dimitry Andric <dim@FreeBSD.org> wrote:

> Interestingly, -Wno-uninitialized has been in bsd.sys.mk since r76861,
> and the accompanying comment ("XXX Delete -Wuninitialized by default =
for
> now -- the compiler doesn't always get it right") has never been
> changed. :-)
>=20
> It is probably time to re-enable that warning after 13 years, at =
least.

It probably only wants enabling for clang.  GCC (at least, GCC 4.2.1) =
performs this analysis based on analyses run by the optimisers and so =
the warnings are dependent on optimisation level.

David