Date: Sat, 04 Feb 2006 23:06:10 +0100 From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) To: "M. Warner Losh" <imp@bsdimp.com> Cc: src-committers@FreeBSD.org, harti@FreeBSD.org, sparc64@FreeBSD.org, stable@FreeBSD.org, ru@FreeBSD.org, kris@obsecurity.org Subject: Re: [releng_6 tinderbox] failure on sparc64/sparc64 Message-ID: <86fymyn5il.fsf@xps.des.no> In-Reply-To: <20060204.143353.109955782.imp@bsdimp.com> (M. Warner Losh's message of "Sat, 04 Feb 2006 14:33:53 -0700 (MST)") References: <20060204.085134.44793895.imp@bsdimp.com> <86irruao3i.fsf@xps.des.no> <20060204211357.GD7604@ip.net.ua> <20060204.143353.109955782.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"M. Warner Losh" <imp@bsdimp.com> writes: > Ruslan Ermilov <ru@FreeBSD.org> writes: > > 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". First of all, the kernel Makefiles contain a hack which force -fno-strict-aliasing whether you want it or not. Second, the kernel will *not* build without -fno-strict-aliasing, partly because of preexisting aliasing violations and partly because of aliasing violations which were introduced after the hack (and could have been avoided if that hack had not been in place). > There's a dozen or two files that will fail to compile -O2 w/o it > spread through the tree. not throughout the tree - only in the kernel. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86fymyn5il.fsf>