Date: Mon, 09 Feb 2004 08:11:58 -0500 From: Richard Coleman <richardcoleman@mindspring.com> To: Kris Kennaway <kris@obsecurity.org> Cc: freebsd-current@freebsd.org Subject: Re: -fno-strict-aliasing Message-ID: <4027871E.8080800@mindspring.com> In-Reply-To: <20040209043217.GA1009@xor.obsecurity.org> References: <c11ba4d1.a4d1c11b@etat.lu> <20040209022820.00faa408@pyro.convolution.ti> <20040209043217.GA1009@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Kris Kennaway wrote: > On Mon, Feb 09, 2004 at 02:28:20AM -0200, 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. > > > Don't do that then :-) > > Kris Although it's not urgent, I don't see why the aliasing problems can't be fixed. I think it would be more honest if the party line was "FreeBSD has bugs, so we can't use -O2 right now" rather than the standard reply of "-O2 is not supported, don't even try". Richard Coleman richardcoleman@mindspring.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4027871E.8080800>