On Wed, Oct 18, 2006 at 08:41:14AM +0000, Oliver Fromme wrote: > Simon 'corecode' Schubert wrote: > > Thomas Schlesinger wrote: > > > options CPU_ENABLE_EST > > > CONF_FLAGS=-march-pentium-m -O2 -fomit-frame-pointer -pipe > > > > don't use -O2 nor -fomit-frame-pointer > > Hm. I assumed that -O2 -fno-strict-aliasing was safe to > use with the newer gcc that DragonFly has (as opposed to > the old 2.9.x one of FreeBSD 4). Am I wrong? (It has > been FreeBSD's default on 5.x and 6.x for ages.)
IIRC, a bug in code generation of stack smash protector with -O2 or higher hasn't been addressed in our default compiler, and SSP is on by default, so you have the chance(though not big) to trigger the bug: http://leaf.dragonflybsd.org/mailarchive/bugs/2006-06/msg00086.html BTW, are we going to keep two gcc-4's in our source tree, in addition to the default? :) Cheers.
