[prev in list] [next in list] [prev in thread] [next in thread] 

List:       netbsd-bugs
Subject:    Re: port-i386/43655 (integer division by zero delivers SIGFPE with wrong siginfo code on i386)
From:       Taylor R Campbell <campbell+netbsd () mumble ! net>
Date:       2010-07-26 17:45:02
Message-ID: 20100726174502.ADF3963BAE5 () www ! NetBSD ! org
[Download RAW message or body]

The following reply was made to PR port-i386/43655; it has been noted by GNATS.

From: Taylor R Campbell <campbell+netbsd@mumble.net>
To: christos@zoulas.com (Christos Zoulas)
Cc: gnats-bugs@NetBSD.org, port-i386-maintainer@netbsd.org,
	gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
Subject: Re: port-i386/43655 (integer division by zero delivers SIGFPE with wrong siginfo code on i386)
Date: Mon, 26 Jul 2010 17:41:53 +0000

    Date: Sun, 25 Jul 2010 22:15:31 -0400
    From: christos@zoulas.com (Christos Zoulas)
 
    On Jul 26,  1:37am, campbell+netbsd@mumble.net (Taylor R Campbell) wrote:
    -- Subject: Re: port-i386/43655 (integer division by zero delivers SIGFP=
 E wit
 
    | Thanks.  While you're at it, perhaps you could address the curious
    | situation of `floating poing operations' in the siginfo(2) man page.
    | I don't know what a poing is, but I'd be happier knowing there aren't
    | any floating around me, especially not when they're invalid.
 
    Well, it means usually invalid operand to the floating operation request=
 ed.
    I don't really want to rename it, or make it more specific, what would y=
 ou
    like to see instead?
 
 Sorry, I guess my joke wasn't clear enough -- there's just a typo,
 `poing' for `point' in the name of FPE_FLTINV.
 
[prev in list] [next in list] [prev in thread] [next in thread]