public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Richard Biener <richard.guenther@gmail.com>,
	Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: Szabolcs Nagy <szabolcs.nagy@arm.com>,
	Florian Weimer <fweimer@redhat.com>,
	GCC Development <gcc@gcc.gnu.org>,
	Siddhesh Poyarekar via Libc-alpha <libc-alpha@sourceware.org>,
	Carlos O'Donell <carlos@redhat.com>,
	"Joseph S. Myers" <joseph@codesourcery.com>
Subject: Re: unnormal Intel 80-bit long doubles and isnanl
Date: Tue, 24 Nov 2020 21:42:50 +0530	[thread overview]
Message-ID: <0cca4091-dc13-95e3-e5b7-cbf44320be6d@gotplt.org> (raw)
In-Reply-To: <CAFiYyc1L3MdbPK1=KXkq5ynD7X3ZeCLur+pQjFTtAyM8odVssw@mail.gmail.com>

On 11/24/20 8:13 PM, Richard Biener wrote:
>>>> compiling isnanl to a quiet fp compare is wrong with
>>>> -fsignalling-nans: classification is not supposed to
>>>> signal exceptions for snan.
> 
> Can you open a bugreport for this?  Note that the option is likely
> to invoke isnanl from libm ...

I believe Szabolcs is talking about this:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66462

Siddhesh

  reply	other threads:[~2020-11-24 16:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-24 10:53 Siddhesh Poyarekar
2020-11-24 13:41 ` Szabolcs Nagy
2020-11-24 13:49   ` Florian Weimer
2020-11-24 13:59   ` Siddhesh Poyarekar
2020-11-24 14:16     ` Adhemerval Zanella
2020-11-24 14:28       ` Siddhesh Poyarekar
2020-11-24 14:43       ` Richard Biener
2020-11-24 16:12         ` Siddhesh Poyarekar [this message]
2020-11-24 14:23   ` Andreas Schwab
2020-11-24 21:28 ` Joseph Myers
2020-11-25  2:47   ` Siddhesh Poyarekar
2020-11-25 19:27     ` Joseph Myers
2020-11-26  0:23       ` Siddhesh Poyarekar
2020-11-27 11:31   ` Florian Weimer
2020-11-27 11:45     ` Siddhesh Poyarekar
2020-11-27 14:29       ` Florian Weimer
2020-11-27 17:40         ` Joseph Myers

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=0cca4091-dc13-95e3-e5b7-cbf44320be6d@gotplt.org \
    --to=siddhesh@gotplt.org \
    --cc=adhemerval.zanella@linaro.org \
    --cc=carlos@redhat.com \
    --cc=fweimer@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=richard.guenther@gmail.com \
    --cc=szabolcs.nagy@arm.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).