Date: Mon, 9 Feb 2004 11:23:18 -0200 From: "Bruno T." <bmrk@terra.com.br> To: David Schultz <das@FreeBSD.ORG> Cc: freebsd-current@FreeBSD.ORG Subject: Re: -fno-strict-aliasing Message-ID: <20040209112318.52058962@pyro.convolution.ti> In-Reply-To: <20040209070700.GA2342@VARK.homeunix.com> References: <c11ba4d1.a4d1c11b@etat.lu> <20040209022820.00faa408@pyro.convolution.ti> <20040209070700.GA2342@VARK.homeunix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 8 Feb 2004 23:07:00 -0800 David Schultz <das@FreeBSD.ORG> wrote: > On Mon, Feb 09, 2004, Bruno T. wrote: > > Hi everyone. > > i'm pretty new to bsd, but i have some background in linux development > > and for what i have seen until now, i must say that -CURRENT is rather impressive, congrats ! > > > > I was rebuilding my base sys and noticed that any compiler flag > > that implies -fstrict-aliasing (like -O2) would break some few things, > > adding "-fno-strict-aliasing" to "CFLAGS+=" in these makefiles > > solves the problem for now. > > > > usr.sbin/kldxref/Makefile > > lib/libc/Makefile > > lib/libpam/Makefile > > libexec/ypxfr/Makefile > > usr.sbin/rpc.yppasswd/Makefile > > I assume the problem is some specific C sources, rather than the > Makefiles themselves. It's generally known that there are a few > aliasing problems lurking around the source tree that break > -fstrict-aliasing, and patches to fix them would be appreciated. Thanks, I'll cook up that patches later tonight and send them back here. previously i just changed the makefiles because i haven't a good perspective of the whole base system stuff.:)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040209112318.52058962>