public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/67624] arm/fp16.c __gnu_f2h_internal has wrong pattern for INF/NAN
Date: Fri, 18 Sep 2015 22:22:00 -0000	[thread overview]
Message-ID: <bug-67624-4-ahJ4LBgfgw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67624-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
All NaNs should have the top mantissa bit set in the result of the 
conversion (i.e. the result of the conversion should always be a quiet 
NaN, not a signaling NaN) - setting that bit also ensures the result is 
not an infinity.  Then I think the remaining bits in the mantissa of the 
result should match the corresponding high bits in the mantissa of the 
source (which appears to be what the hardware conversion instructions are 
documented to do).


  parent reply	other threads:[~2015-09-18 22:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-18 13:11 [Bug libgcc/67624] New: " pekka.jaaskelainen at parmance dot com
2015-09-18 17:00 ` [Bug libgcc/67624] " rearnsha at gcc dot gnu.org
2015-09-18 22:22 ` joseph at codesourcery dot com [this message]
2015-09-24  9:40 ` rearnsha at gcc dot gnu.org
2015-09-24  9:41 ` rearnsha at gcc dot gnu.org

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=bug-67624-4-ahJ4LBgfgw@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).