public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rsa at us dot ibm.com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug math/887] Math library function "logb" and "nextafter" inconsistent
Date: Thu, 01 Mar 2012 21:26:00 -0000	[thread overview]
Message-ID: <bug-887-131-2ZjVLsDy2f@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-887-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=887

--- Comment #18 from Ryan S. Arnold <rsa at us dot ibm.com> 2012-03-01 21:26:05 UTC ---
A bit more investigation reveals the issue:

Building logb with -mcpu=power4 or -mcpu=ppc970 results in a negative signed
zero.  This is due to the power4 and ppc970 versions using fsub.

The fcfid insn was introduced after power4 and logb uses that when built for
power5 and power6.  A negative signed zero is not encountered in these cases.

So technically YES, this is still an issue, but it originates in GCC due to
insn selection.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2012-03-01 21:26 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-887-131@http.sourceware.org/bugzilla/>
2012-02-22 21:44 ` jsm28 at gcc dot gnu.org
2012-02-23 19:49 ` rsa at us dot ibm.com
2012-02-23 21:29 ` rsa at us dot ibm.com
2012-02-23 21:39 ` joseph at codesourcery dot com
2012-02-23 21:44 ` rsa at us dot ibm.com
2012-02-23 23:18 ` rsa at us dot ibm.com
2012-02-29 16:22 ` rsa at us dot ibm.com
2012-02-29 16:23 ` rsa at us dot ibm.com
2012-03-01 21:26 ` rsa at us dot ibm.com [this message]
2012-03-26 19:34 ` rsa at us dot ibm.com
2012-03-26 20:43 ` rsa at us dot ibm.com
2012-03-26 20:51 ` joseph at codesourcery dot com
2012-03-26 20:56 ` rsa at us dot ibm.com
2012-03-26 20:57 ` rsa at us dot ibm.com
2012-03-26 22:23 ` rsa at us dot ibm.com
2012-04-25 22:01 ` rsa at us dot ibm.com
2012-04-26 18:16 ` rsa at us dot ibm.com
2012-04-26 18:53 ` joseph at codesourcery dot com
2012-04-26 19:04 ` rsa at us dot ibm.com
2012-04-27 16:31 ` rsa at us dot ibm.com
2014-01-07 22:43 ` cvs-commit at gcc dot gnu.org
2015-10-01 21:50 ` jsm28 at gcc dot gnu.org
2015-10-01 21:51 ` jsm28 at gcc dot gnu.org
2015-10-05 17:48 ` cvs-commit at gcc dot gnu.org
2015-10-05 17:50 ` cvs-commit at gcc dot gnu.org
2015-10-05 17:51 ` jsm28 at gcc dot gnu.org
2005-04-28 17:50 [Bug math/887] New: " uttamp at us dot ibm dot com
2005-04-29 20:38 ` [Bug math/887] " uttamp at us dot ibm dot com
2005-06-16 19:12 ` uttamp at us dot ibm dot com
2005-07-19 22:16 ` uttamp at us dot ibm dot com
2005-10-25 17:05 ` uttamp at us dot ibm dot com
2005-11-02  1:29 ` uttamp at us dot ibm dot com
2005-11-21 17:57 ` uttamp at us dot ibm dot com
2005-11-21 18:07 ` jakub at redhat dot com
2006-09-30  5:03 ` rsa at us dot ibm dot com
2006-09-30  5:54 ` rsa at us dot ibm dot com

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-887-131-2ZjVLsDy2f@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.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).