From owner-freebsd-arch Fri Jan 11 14:37:18 2002 Delivered-To: freebsd-arch@freebsd.org Received: from gull.prod.itd.earthlink.net (gull.mail.pas.earthlink.net [207.217.120.84]) by hub.freebsd.org (Postfix) with ESMTP id E5FC237B404 for ; Fri, 11 Jan 2002 14:37:15 -0800 (PST) Received: from pool0202.cvx22-bradley.dialup.earthlink.net ([209.179.198.202] helo=mindspring.com) by gull.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16PAII-0000lV-00; Fri, 11 Jan 2002 14:37:02 -0800 Message-ID: <3C3F690B.9A5959A1@mindspring.com> Date: Fri, 11 Jan 2002 14:36:59 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Bakul Shah Cc: Dan Eischen , arch@freebsd.org Subject: Re: Request for review: getcontext, setcontext, etc References: <200201112141.QAA25529@devonshire.cnchost.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Bakul Shah wrote: [ ... ] > I am not prepared to speculate on the use of FP & SSE > registers at this point except for one thing: an FP exception > *must* be delivered to whichever thread caused it. Any bugs > in SIGFPE delivery is a separate discussion! [ ... ] Cool. We are all in agreement on this: the thread that caused it is the thread that executes an FPU instruction after an error in an instruction by some FPU using thread, whatever thread that is. 8-p The exception signalling lags the event that was the cause of the exception in x86 hardware, if this wasn't clear... -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message