From owner-freebsd-stable Sun Nov 5 11:39:15 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 90EAD37B4C5 for ; Sun, 5 Nov 2000 11:39:13 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id LAA02760; Sun, 5 Nov 2000 11:39:07 -0800 (PST) (envelope-from obrien) Date: Sun, 5 Nov 2000 11:39:07 -0800 From: "David O'Brien" To: Randell Jesup Cc: freebsd-stable@FreeBSD.ORG Subject: Re: "Malloc type lacks magic" show-stopper solved Message-ID: <20001105113907.B2656@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from rjesup@wgate.com on Thu, Nov 02, 2000 at 11:37:09AM -0500 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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