From owner-freebsd-current Thu Dec 3 11:51:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA14467 for freebsd-current-outgoing; Thu, 3 Dec 1998 11:51:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA14461 for ; Thu, 3 Dec 1998 11:51:32 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA18267; Thu, 3 Dec 1998 11:41:25 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpda18265; Thu Dec 3 19:41:23 1998 Date: Thu, 3 Dec 1998 11:40:55 -0800 (PST) From: Julian Elischer To: Mark Tinguely cc: freebsd-current@FreeBSD.ORG Subject: Re: 3.0 and double operations in device drivers In-Reply-To: <199812031513.JAA18762@plains.NoDak.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG it always was taboo.. floating point operations need a process context to store results etc. in the case of context changes (e.g. interrupts) etc. BDE can be more accurate on this point I'm sure. julian On Thu, 3 Dec 1998, Mark Tinguely wrote: > I was testing a device driver that I wrote for FreeBSD 2.2.x on a > FreeBSD 3.0-RELEASE. When some double multiplication and divisions > were executed, the system froze. > > It took a long time to find it was a FP problem, it acted like > some aweful infinite loop. > > These routines are only used on a circuit setup to calculate some scheduling > parameters, and I guess they can be done with integer math after some head > scratching. > > My question is: "Is floating point math now taboo in the kernel?" > > --mark. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message