From owner-freebsd-sparc64@FreeBSD.ORG Sat Feb 4 21:36:42 2006 Return-Path: X-Original-To: sparc64@FreeBSD.org Delivered-To: freebsd-sparc64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 62E8116A420; Sat, 4 Feb 2006 21:36:42 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 76EFF43D49; Sat, 4 Feb 2006 21:36:39 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id k14LXoQX016468; Sat, 4 Feb 2006 14:33:50 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sat, 04 Feb 2006 14:33:53 -0700 (MST) Message-Id: <20060204.143353.109955782.imp@bsdimp.com> To: ru@FreeBSD.org From: "M. Warner Losh" In-Reply-To: <20060204211357.GD7604@ip.net.ua> References: <20060204.085134.44793895.imp@bsdimp.com> <86irruao3i.fsf@xps.des.no> <20060204211357.GD7604@ip.net.ua> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Sat, 04 Feb 2006 14:33:50 -0700 (MST) Cc: src-committers@FreeBSD.org, harti@FreeBSD.org, sparc64@FreeBSD.org, stable@FreeBSD.org, kris@obsecurity.org Subject: Re: [releng_6 tinderbox] failure on sparc64/sparc64 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Feb 2006 21:36:42 -0000 In message: <20060204211357.GD7604@ip.net.ua> Ruslan Ermilov writes: : On Sat, Feb 04, 2006 at 09:03:13PM +0100, Dag-Erling Sm?rgrav wrote: : > "M. Warner Losh" writes: : > > Dag-Erling Sm?rgrav writes: : > > > As I have repeatedly pointed out in the past, -O2 catches more : > > > bugs because it enables optimizations which require more extensive : > > > coverage analysis. : > > Then it should be the default, standard flag. : > : > I wish. Unfortunately, there is a very vocal minority which : > systematically opposes this kind of change. : > : What breakage do you mean if tinderboxes are run without it and : usually compile successfully? :-) : : I mean, I don't see a reason not to remove -fno-strict-aliasing : from the kernel builds now. Perhaps it's still needed for some : platforms that aren't covered by tinderbox, not sure... Can be : easily checked with "make universe". There's a dozen or two files that will fail to compile -O2 w/o it spread through the tree. Warner