From owner-freebsd-sparc64@FreeBSD.ORG Sat Feb 4 21:33:10 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 A373516A420; Sat, 4 Feb 2006 21:33:10 +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 ED3E943D48; Sat, 4 Feb 2006 21:33:08 +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 k14LUpQR016447; Sat, 4 Feb 2006 14:30:51 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sat, 04 Feb 2006 14:30:54 -0700 (MST) Message-Id: <20060204.143054.47698885.imp@bsdimp.com> To: des@des.no From: "M. Warner Losh" In-Reply-To: <86ek2iao05.fsf@xps.des.no> References: <20060204.121349.06228212.imp@bsdimp.com> <86ek2iao05.fsf@xps.des.no> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Sat, 04 Feb 2006 14:30:52 -0700 (MST) Cc: src-committers@freebsd.org, sparc64@freebsd.org, stable@freebsd.org, kmacy@fsmware.com, 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:33:10 -0000 In message: <86ek2iao05.fsf@xps.des.no> des@des.no (Dag-Erling Sm=F8rgrav) writes: : "M. Warner Losh" writes: : > If things have really changed, then we should change the default an= d : > remove the kludges. My main objection is the mismatch, not the act= ual : > value. Did you remove the kludges in the mk files at netapp to rem= ove : > the -fno-strict-alias? : = : Most of the kernel builds fine without -fno-strict-alias. Some parts= : do not, and the committer responsible for introducing those errors : added the kluges you mention to avoid having to fix his code. There's many different files in the tree that fail to compile. I find this hard to believe. A quick survey shows breakage in the following areas: firewire, advansys, an, amr, ciss, hifn, isp, mly, pccbb, rue, ubser, ucom, msdosfs, nullfs, portalfs, udf, unionfs, ext2fs, reiserfs, cd9660, init_main, kern_exit, kern_fork, kern_malloc, kern_mtxpool, kern_synch, kern_thread, link_elf, sys_pipe, vfs_mount, bluetooth, gif, ufs, xfs, sbni, i386/machdep, mp_machdep, pmap, sys_machdep, imgact_coff, npx I'm not sure about which committer you are talking about, but I can't imagine that one person is responsible for all of that... Warner