From owner-freebsd-hackers Fri Oct 10 19:09:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA23912 for hackers-outgoing; Fri, 10 Oct 1997 19:09:21 -0700 (PDT) (envelope-from owner-freebsd-hackers) Received: from usr02.primenet.com (tlambert@usr02.primenet.com [206.165.6.202]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA23907 for ; Fri, 10 Oct 1997 19:09:16 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id TAA09898; Fri, 10 Oct 1997 19:08:55 -0700 (MST) From: Terry Lambert Message-Id: <199710110208.TAA09898@usr02.primenet.com> Subject: Re: Floating point exceptions To: chuckr@glue.umd.edu (Chuck Robey) Date: Sat, 11 Oct 1997 02:08:54 +0000 (GMT) Cc: tlambert@primenet.com, gjohnson@nola.srrc.usda.gov, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Chuck Robey" at Oct 10, 97 05:34:04 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Terry, I figured if he understood his application's math well enough to do > the first fix, he'd have done it without asking us. Your worst case fix > doesn't have to be that way, he could set up a signal catcher, so that he > could identify which calculations are killing him, then maybe fix the code > from there. That's what I'd likely do, if I couldn't spot the original > killing calculation. Disagree? Nope; good plan, so long as the data being operated upon is the same each time; if it's a signal processing application, it's trouble. It'd help to know if it's overflow, underflow, or whatever, in any case, so a handler is the best bet. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.