Date: Tue, 8 Mar 2005 00:57:11 -0800 From: Peter Wemm <peter@wemm.org> To: freebsd-amd64@freebsd.org Cc: Damian Gerow <dgerow@afflictions.org> Subject: Re: Is -O2 supported for world? Message-ID: <200503080057.11835.peter@wemm.org> In-Reply-To: <20050308064225.GL67164@afflictions.org> References: <20050305043006.GN83265@afflictions.org> <20050308060910.GA32871@dragon.nuxi.com> <20050308064225.GL67164@afflictions.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 07 March 2005 10:42 pm, Damian Gerow wrote: > Thus spake David O'Brien (obrien@freebsd.org) [08/03/05 01:36]: > : It is suppored w/in /usr/src. > > Thanks for the clarification. > > : > /usr/src/lib/libc/i386/sys/_amd64_get_fsbase.c: In function > : > `_amd64_get_fsbase': /usr/src/lib/libc/i386/sys/_amd64_get_fsbase.c:40: > : > warning: dereferencing type-punned pointer will break strict-aliasing > : > rules > : > > : > without -fno-strict-aliasing. Not that I have any serious desire to > : > run with -O2, just curious. > : > : -O2 isn't supported in /usr/ports without -fno-strict-aliasing also. > : There are a few ports that aren't happy being compiled with any form of > : -O2 (such as the old perl). > > That error message was within /usr/src. I generally tell people to avoid -O2 like the plague. -O2 causes way too many "strange" things to happen. And as Kris said, compiling /usr/src with -O2 will cause several key ports to break (such as perl5.6) - even if perl itself is compiled with plain -O. So yes, gcc -O2 *is* miscompiling /usr/src. -Peter
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200503080057.11835.peter>