Re: [current tinderbox] failure on amd64/amd64

From: Warner Losh <imp_at_bsdimp.com>
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_at_ -I_at_/contrib/altq -I_at_/../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:
> > _at_/sys/buf.h: In function `BUF_KERNPROC':
> > _at_/sys/buf.h:340: warning: dereferencing type-punned pointer will break strict-aliasing rules
> > _at_/sys/buf.h:340: warning: dereferencing type-punned pointer will break strict-aliasing rules
> > _at_/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