From owner-freebsd-amd64@FreeBSD.ORG Wed Jan 26 21:32:20 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EECC616A4CE; Wed, 26 Jan 2005 21:32:20 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 76EE343D2F; Wed, 26 Jan 2005 21:32:20 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [IPv6:::1]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id j0QLTM7w031980; Wed, 26 Jan 2005 14:29:22 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Wed, 26 Jan 2005 14:29:22 -0700 (MST) Message-Id: <20050126.142922.78737749.imp@bsdimp.com> To: tinderbox@freebsd.org From: Warner Losh In-Reply-To: <20050126.142237.104061863.imp@bsdimp.com> References: <20050126180542.274137306E@freebsd-current.sentex.ca> <20050126.142237.104061863.imp@bsdimp.com> 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 cc: amd64@freebsd.org cc: current@freebsd.org Subject: Re: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jan 2005 21:32:21 -0000 From: Warner Losh Subject: Re: [current tinderbox] failure on amd64/amd64 Date: Wed, 26 Jan 2005 14:22:37 -0700 (MST) > Subject: [current tinderbox] failure on amd64/amd64 > > > cc -O2 -pipe -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I- -include /tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=8000 -fno-common -g -fno-omit-frame-pointer -I/tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/GENERIC -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /tinderbox/CURRENT/amd64/amd64/src/sys/modules/aio/../../kern/vfs_aio.c > > In file included from /tinderbox/CURRENT/amd64/amd64/src/sys/modules/aio/../../kern/vfs_aio.c:28: > > @/sys/buf.h: In function `BUF_KERNPROC': > > @/sys/buf.h:340: warning: dereferencing type-punned pointer will break strict-aliasing rules > > @/sys/buf.h:340: warning: dereferencing type-punned pointer will break strict-aliasing rules > > @/sys/buf.h:340: warning: dereferencing type-punned pointer will break strict-aliasing rules > > *** Error code 1 > > This looks ugly to fix. Why are we compiling without > -fno-strict-alias again? I've decided that I'm disinclined to fix this because it compiles correctly with the standard flags. It is time to fix tinerbox to not have these whacked out flags (eg lacking -fno-strict-alias). There turns out to be hundreds of these sorts of errors in the kernel right now. Warner