From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 4 20:13:27 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B33016A4CE for ; Fri, 4 Jun 2004 20:13:27 -0700 (PDT) Received: from VARK.homeunix.com (ar59.lsanca2-4.27.98.47.lsanca2.dsl-verizon.net [4.27.98.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id CBBCF43D1D for ; Fri, 4 Jun 2004 20:13:26 -0700 (PDT) (envelope-from das@FreeBSD.ORG) Received: from VARK.homeunix.com (localhost [127.0.0.1]) by VARK.homeunix.com (8.12.11/8.12.10) with ESMTP id i553D8Sl004189; Fri, 4 Jun 2004 20:13:08 -0700 (PDT) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by VARK.homeunix.com (8.12.11/8.12.10/Submit) id i553D7CJ004188; Fri, 4 Jun 2004 20:13:07 -0700 (PDT) (envelope-from das@FreeBSD.ORG) Date: Fri, 4 Jun 2004 20:13:07 -0700 From: David Schultz To: Tim Robbins Message-ID: <20040605031307.GB4004@VARK.homeunix.com> References: <20040602064846.GA6124@VARK.homeunix.com> <20040603002015.GA14544@cat.robbins.dropbear.id.au> <20040603015315.GA739@VARK.homeunix.com> <20040605023127.GA26469@cat.robbins.dropbear.id.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040605023127.GA26469@cat.robbins.dropbear.id.au> cc: amd64@FreeBSD.ORG Subject: Re: Initial FP exception flags incorrect on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2004 03:13:27 -0000 On Sat, Jun 05, 2004, Tim Robbins wrote: > Apologies for the late response -- the new patch no longer causes panics > on startup, and gives the expected results with your test program (0x00.) > It doesn't seem to break any applications, but I don't do anything > numerically intensive (X, KDE, Mozilla, compiling.) Great! Thanks, Tim. If nothing catastrophic happened under a normal workload, then resetting the CSR to its default value probably didn't break anything. I'll go ahead and commit the patch.