From owner-freebsd-current Sun Jul 11 1:39: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id B9C8314D3D for ; Sun, 11 Jul 1999 01:39:03 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA03758; Sun, 11 Jul 1999 09:39:22 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sun, 11 Jul 1999 09:39:22 +0100 (BST) From: Doug Rabson To: Alan Cox Cc: Matthew Dillon , Stephen McKay , Andrew Gallatin , freebsd-current@freebsd.org Subject: Re: "objtrm" problem probably found (was Re: Stuck in "objtrm") In-Reply-To: <19990711024217.B6401@cs.rice.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 11 Jul 1999, Alan Cox wrote: > On Sun, Jul 11, 1999 at 08:12:52AM +0100, Doug Rabson wrote: > > > > What a nightmare. This must be due to egcs compiling things differently > > from gcc 2.7.1. ... > > Yes, at least for the one case in vm_pageout_flush. (I checked > the analogous code on a 3.x-STABLE system and it appears to be fine > for this case.) I haven't looked for others. > > Alan > > P.S. I plan to move the fix to 3.X-stable even if it appears > that the compiler is generating safe code. There's really > no point in taking chances. Agreed. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message