From owner-freebsd-current@FreeBSD.ORG Tue May 4 22:47:24 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F24016A4CE for ; Tue, 4 May 2004 22:47:24 -0700 (PDT) Received: from TRANG.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3373243D39 for ; Tue, 4 May 2004 22:47:24 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by TRANG.nuxi.com (8.12.11/8.12.10) with ESMTP id i455lNEg030670; Tue, 4 May 2004 22:47:23 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.11/8.12.11/Submit) id i455lNfE030669; Tue, 4 May 2004 22:47:23 -0700 (PDT) (envelope-from obrien) Date: Tue, 4 May 2004 22:47:23 -0700 From: "David O'Brien" To: Doug White Message-ID: <20040505054723.GB30514@dragon.nuxi.com> Mail-Followup-To: David O'Brien , Doug White , current@freebsd.org References: <20040430135155.C67990@carver.gumbysoft.com> <20040501082529.C80212@carver.gumbysoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040501082529.C80212@carver.gumbysoft.com> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 5.2-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 cc: current@freebsd.org Subject: Re: src/sys/vm/vm_init.c v1.43 hangs amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 May 2004 05:47:24 -0000 On Sat, May 01, 2004 at 08:42:46AM -0700, Doug White wrote: > 2. Changing COPTFLAGS to '-O -frename-registers -pipe' from the default > '-O2 -frename-registers -pipe' stops the crash. So it may be an > O2-specific optimization bug. ... > So in the end, at -O2, (nswbuf*MAXPHYS) != nswbuf*MAXPHYS. Creepy, eh? > I'll see if I can come up with a standalone test case to submit to the gcc > folks. Thanks! This is the first report of an -O2 problem, and I'm very happy you're willing to try to narrow this down so we don't have to return to -O[1]. -- -- David (obrien@FreeBSD.org)