Re: -fno-strict-aliasing

----- Original Message ----- 
From: "Richard Coleman" <richardcoleman_at_mindspring.com>
To: "Kris Kennaway" <kris_at_obsecurity.org>
Cc: "Bruno T." <bmrk_at_terra.com.br>; <freebsd-current_at_freebsd.org>
Sent: Monday, February 09, 2004 9:11 PM
Subject: Re: -fno-strict-aliasing


> 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".
We can find out what applications broken with strict-alias and mark them in
the Makefile. This can make the whole system use -O2 or above. Besides this,
we can clean this problem one by one from our base.

Jun Su
>
> Richard Coleman
> richardcoleman_at_mindspring.com
>
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
>
>