Date: Wed, 28 Mar 2007 14:13:35 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Dag-Erling Sm?rgrav <des@des.no> Cc: Matteo Riondato <matteo@freebsd.org>, i386@freebsd.org, current@freebsd.org, FreeBSD Tinderbox <tinderbox@freebsd.org> Subject: Re: [head tinderbox] failure on i386/i386 Message-ID: <20070328181335.GA24652@xor.obsecurity.org> In-Reply-To: <86648lsmmu.fsf@dwp.des.no> References: <20070323212254.54F7D73039@freebsd-current.sentex.ca> <20070323214145.GA3822@krapfengeist> <46044D6C.1070304@samsco.org> <86648lsmmu.fsf@dwp.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Mar 28, 2007 at 12:11:53PM +0200, Dag-Erling Sm?rgrav wrote: > Scott Long <scottl@samsco.org> writes: > > The tinderboxes have stricter compile flags than the normal buildworld > > environment. The hope is that we'll be able to go to -O2 as the default > > optimization someday, which requires the stricter flags. I think what > > you're missing here is the -fstrict-aliasing flag. > > No, the tinderbox just uses -O2 (which implies -fno-strict-aliasing). No, it implies -fstrict-aliasing, which is why the tinderbox often breaks on code that was tested 100% correctly by the committer prior to running with your nonstandard flags ;) Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070328181335.GA24652>