From owner-freebsd-stable Sun Nov 5 11:38:10 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 14F1637B479 for ; Sun, 5 Nov 2000 11:38:07 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id LAA02729; Sun, 5 Nov 2000 11:37:30 -0800 (PST) (envelope-from obrien) Date: Sun, 5 Nov 2000 11:37:30 -0800 From: "David O'Brien" To: Gerald Pfeifer Cc: freebsd-stable@freebsd.org Subject: Re: "Malloc type lacks magic" show-stopper solved Message-ID: <20001105113730.A2656@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 pfeifer@dbai.tuwien.ac.at on Thu, Nov 02, 2000 at 12:54:23PM +0100 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 12:54:23PM +0100, Gerald Pfeifer wrote: > Cy Schubert wrote: > > Anything above -O is not recommended. I've had problems with > > optimisation above -O under gcc on Intel (FreeBSD & Linux) ever since I > > converted from IBM mainframe to UNIX (religious experience). > > I cannot recall any bug report on the GCC mailing lists. Nope. I haven't been able to cut the FreeBSD kernel down to a minimal snippet of code that exhibits the problem. The problem doesn't occur with every i386 kernel, just some. I actually did use -O2 on my kernel for a while and then one day it started locking up and didn't when I went back to -O. However on the Alpha it is _trivial_ to show code breakage with -O2. One cannot run a -O2 world (much less kernel) at all. Maybe once GCC officially builds on FreeBSD/Alpha one of the GCC developers would take a look at the issue... but I won't hold my breath. > David O'Brien wrote: > > Forgot to mention. I'm considering removing the ability to do -O2 and > > -O3 from the system C compiler again.... people are just proving over > > and over how much they want to shoot their foot off. > > Please don't. We are already seeing enough problems due to differences > between FSF GCC and FreeBSD's patched version. Please let's reduce those > differences, not introduce anything further. If a certain GCC developer would be more open to accepting our changes, I'd _love_ to reduce them. We followed an existing precedent -- OSF/ROSE, yet our changes are unacceptable... -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message