Date: Fri, 7 May 2004 18:04:37 -0700 (PDT) From: Doug White <dwhite@gumbysoft.com> To: Scott Long <scottl@freebsd.org> Cc: current@freebsd.org Subject: Re: src/sys/vm/vm_init.c v1.43 hangs amd64 Message-ID: <20040507175115.U45649@carver.gumbysoft.com> In-Reply-To: <409BF210.8030307@freebsd.org> References: <20040430135155.C67990@carver.gumbysoft.com> <20040507130607.Q42861@carver.gumbysoft.com> <409BF210.8030307@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 7 May 2004, Scott Long wrote: > Doug White wrote: > > Also if we get into the 5.3 release timeframe we'll have to make a call to > > ship with a -O2 compiled kernel or not. > > > > Are you proposing dropping -O2 for 5.3 because you are afraid that there > are other, not-yet-detected broken cases? I thought that we found a > source code work-around that forced gcc to generate the correct assembly > with -O2. Maybe that should be committed for the time being? Dropping back to -O is the safer route of the two for sure ... who knows how many other similar constructions are out there and just happen to not cause hangs. I'd just like us to do *something* before 5.3 gets out the door and we have random amd64 boxes falling over in potentially unrecoverable scenarios. :) -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040507175115.U45649>