From owner-freebsd-hackers Tue Jan 4 12:25:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from monkeys.com (i180.value.net [206.14.136.180]) by hub.freebsd.org (Postfix) with ESMTP id D4F7214F22 for ; Tue, 4 Jan 2000 12:25:16 -0800 (PST) (envelope-from rfg@monkeys.com) Received: from monkeys.com (localhost [127.0.0.1]) by monkeys.com (8.9.3/8.9.3) with ESMTP id MAA87634 for ; Tue, 4 Jan 2000 12:25:15 -0800 (PST) To: freebsd-hackers@FreeBSD.ORG Subject: Re: Should -mieee-fp equal fpsetmask(0) to avoid SIGFPE on FreeBSD? In-reply-to: Your message of Tue, 04 Jan 2000 12:14:59 +0100. <20000104121459.A8959@cons.org> Date: Tue, 04 Jan 2000 12:25:15 -0800 Message-ID: <87632.947017515@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000104121459.A8959@cons.org>, Martin Cracauer wrote: >Hence it is good to trap this and it is a bug in Mozilla, period. >... >I think we might discuss lowing the traps so that the softer >exceptions are disabled. But most cases where people cry about >FreeBSD's behaviour are serious errors like the one in mozilla, so we >won't gain much. I agree that it appears that the Mozilla code had a serious bug/flaw, and that having the FP traps enabled caused that fact to become apparent. But the issue for me is still one of standards conformance. Regardless of how helpful enabled FP traps may be, on occasion, for certain programs and/or certain programmers, the IEEE 754 standard is pretty darn clear and unambiguous regarding what the default setting should be, i.e. all traps disabled. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message