Date: Sun, 5 Nov 2000 11:39:07 -0800 From: "David O'Brien" <obrien@FreeBSD.ORG> To: Randell Jesup <rjesup@wgate.com> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: "Malloc type lacks magic" show-stopper solved Message-ID: <20001105113907.B2656@dragon.nuxi.com> In-Reply-To: <ybubsvyfhze.fsf@jesup.eng.tvol.net.jesup.eng.tvol.net>; from rjesup@wgate.com on Thu, Nov 02, 2000 at 11:37:09AM -0500 References: <Pine.BSF.4.30.0011021247480.81655-100000@taygeta.dbai.tuwien.ac.at> <ybubsvyfhze.fsf@jesup.eng.tvol.net.jesup.eng.tvol.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Nov 02, 2000 at 11:37:09AM -0500, Randell Jesup wrote: > -O2 should work. I've never seen a bug with -O2 code generation > from GCC (not that they can't happen, of course). Most bugs I've seen in > my career with optimization levels were actually timing holes in the > source code, where someone was accessing a shared resource and counting > on ordering/etc, or bugs with accessing hardware registers where structures > weren't properly marked volatile. > > If there's a problem, find it and report it. IMHO. Love to, but its often too hard -- unless handing over an entire kernel source directory as the test case showing the bug is acceptable. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001105113907.B2656>