mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Markus Wichmann <nullplan@gmx.net>
To: musl@lists.openwall.com
Subject: Re: FE Exception triggered by comparison
Date: Sun, 24 Feb 2019 18:12:50 +0100	[thread overview]
Message-ID: <20190224171250.GA28106@voyager> (raw)
In-Reply-To: <alpine.LRH.2.02.1902242244590.23511@key0.esi.com.au>

On Mon, Feb 25, 2019 at 12:28:20AM +1100, Damian McGuckin wrote:
> 
> What comparison of FP numbers trigger invalid operation exceptions?
> 
> Does a comparison like
> 
> 	if (x != x)
> 	{
> 		/* get to here if x == NaN *
> 	}
> 
> which tests for a NaN cause an invalid operation if given an sNaN?
> 
> Even reading the standard numerous times and I am not any wiser.
> 
> Thanks - Damian
> 

In cases like these, I like to read the documentation of an
implementation, under the assumption that it is conforming. One
implementation of IEE 754 general considered to be conforming is the x87
instruction set. And AMD's documentation of the same (AMD64 Architecture
Programmer's Manual, Volume 5, Order No. 26569) says about the FCOM
instruction, that it will generate an invalid-operation exception if any
source operand was a NaN. Same for FCOMI and FICOM.

Only difference for FUCOM and FUCOMI is that those only raise IE for an
SNaN.

Cross-checking with volume 4 shows that the SSE FP compare instructions
all raise IE in case of SNan source operand, and in case of "Undefined
operation". No idea what the latter is supposed to mean in context,
unless it means that QNaNs trigger it, too.

So yes, it appears at least in a PC, comparison with NaN raises IE.

Ciao,
Markus


  reply	other threads:[~2019-02-24 17:12 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-24 13:28 Damian McGuckin
2019-02-24 17:12 ` Markus Wichmann [this message]
2019-02-24 19:25 ` Szabolcs Nagy
2019-02-24 20:04   ` Jens Gustedt
2019-02-24 21:50     ` Damian McGuckin
2019-02-25  5:21       ` Damian McGuckin
2019-02-25 15:51       ` Markus Wichmann
2019-02-26  3:55         ` Damian McGuckin
2019-02-27 14:14           ` Alexander Monakov
2019-02-27 15:38             ` Damian McGuckin
2019-02-27 16:00               ` Alexander Monakov
2019-02-27 16:09                 ` Damian McGuckin
2019-02-27 16:14                   ` Markus Wichmann
2019-02-27 16:20                     ` Damian McGuckin
2019-02-28  1:07                     ` Damian McGuckin
2019-02-28  1:27                       ` Rich Felker
2019-02-28  2:28                         ` Damian McGuckin
2019-02-27 16:32                   ` Alexander Monakov
2019-02-27 16:42                     ` Rich Felker
2019-02-27 17:08                       ` Szabolcs Nagy
2019-02-27 17:14                       ` Alexander Monakov
2019-02-27 17:26                         ` Rich Felker
2019-02-27 19:36                           ` Szabolcs Nagy
2019-02-27 19:48                           ` Alexander Monakov
2019-02-27 20:16                             ` Szabolcs Nagy
2019-02-27 20:35                               ` Rich Felker
2019-02-27 21:03                                 ` Szabolcs Nagy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190224171250.GA28106@voyager \
    --to=nullplan@gmx.net \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).