From owner-freebsd-current Mon Sep 7 00:57:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA05381 for freebsd-current-outgoing; Mon, 7 Sep 1998 00:57:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cons.org (knight.cons.org [194.233.237.86]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA05375 for ; Mon, 7 Sep 1998 00:57:08 -0700 (PDT) (envelope-from cracauer@cons.org) Received: (from cracauer@localhost) by cons.org (8.8.8/8.7.3) id JAA24213; Mon, 7 Sep 1998 09:56:52 +0200 (CEST) Message-ID: <19980907095651.A24204@cons.org> Date: Mon, 7 Sep 1998 09:56:51 +0200 From: Martin Cracauer To: Bruce Evans , cracauer@cons.org, current@FreeBSD.ORG Subject: Re: Floating Point Exceptions, signal handlers & subsequent ops References: <199809070513.PAA26505@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199809070513.PAA26505@godzilla.zeta.org.au>; from Bruce Evans on Mon, Sep 07, 1998 at 03:13:07PM +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <199809070513.PAA26505@godzilla.zeta.org.au>, Bruce Evans wrote: > >I could also imagine extending struct sigcontext with fields for > >control and status word so that the user can get the unmodified status > >if the one-bit trap code isn't sufficient (either because multiple > >bits may have been set or if the FPE_...... values aren't precise > >enough, for example if the user needs to tell under- from overflow). > > This can wait until we implement SA_SIGINFO (post-3.0). Will we give up the old signal handler calls or still send the old arguments to handlers not registered with SA_SIGINFO? Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 Paper: (private) Waldstrasse 200, 22846 Norderstedt, Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message