From owner-freebsd-current  Mon Oct  6 04:41:56 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id EAA22646
          for current-outgoing; Mon, 6 Oct 1997 04:41:56 -0700 (PDT)
          (envelope-from owner-freebsd-current)
Received: from merlin.ee.swin.oz.au (merlin.ee.swin.oz.au [136.186.4.19])
          by hub.freebsd.org (8.8.7/8.8.7) with SMTP id EAA22640
          for <freebsd-current@freebsd.org>; Mon, 6 Oct 1997 04:41:52 -0700 (PDT)
          (envelope-from dtc@merlin.ee.swin.oz.au)
Received: (from dtc@localhost) by merlin.ee.swin.oz.au (8.6.9/8.6.9) id VAA08615; Mon, 6 Oct 1997 21:36:12 +1000
From: Douglas Thomas Crosher  <dtc@merlin.ee.swin.oz.au>
Message-Id: <199710061136.VAA08615@merlin.ee.swin.oz.au>
Subject: Re: xlock: caught signal 8 while running galaxy mode.
To: tlambert@primenet.com (Terry Lambert)
Date: Mon, 6 Oct 1997 21:36:11 +1000 (EST)
Cc: freebsd-current@freebsd.org
In-Reply-To: <199710060120.SAA02357@usr05.primenet.com> from "Terry Lambert" at Oct 6, 97 01:20:04 am
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-freebsd-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


> Floating point switching is lazy-bound.
...
> This is a good thing, and it is why things are the way they are: most
> programs do not use the FPU, and should not have to incurr the overhead
> simply because some minority of programs *do* use the FPU.

There would be no additional overhead in passing the FPU status word
as the signal code on a SIGFPE. If the application needs to
save/restore the FPU state it can do so, other applications avoid the
overhead.

Regards
Douglas Crosher