public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug math/3268] fma for all targets without hardware fma instructions is incorrect.
Date: Sun, 26 Feb 2012 17:48:00 -0000	[thread overview]
Message-ID: <bug-3268-131-omOIJoDS5s@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-3268-131@http.sourceware.org/bugzilla/>

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

Joseph Myers <jsm28 at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |DUPLICATE

--- Comment #24 from Joseph Myers <jsm28 at gcc dot gnu.org> 2012-02-26 17:47:58 UTC ---
Bug 13304 is the bug with the most recent discussion of generic fma
implementations for systems without exceptions / rounding modes, so marking
this one as a duplicate; I don't think we need both open.

*** This bug has been marked as a duplicate of bug 13304 ***

-- 
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-02-26 17:48 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-3268-131@http.sourceware.org/bugzilla/>
2011-10-17 20:10 ` bruno at clisp dot org
2011-10-17 20:27 ` jakub at redhat dot com
2011-10-18  7:24 ` aj at suse dot de
2012-02-26 17:48 ` jsm28 at gcc dot gnu.org [this message]
2014-02-16 19:42 ` jackie.rosen at hushmail dot com
2014-05-28 19:40 ` schwab at sourceware dot org
2006-09-26 21:22 [Bug math/3268] New: fma for soft-fp is not correct sjmunroe at us dot ibm dot com
2006-10-04 18:27 ` [Bug math/3268] fma for all targets without hardware fma instructions is incorrect sjmunroe at us dot ibm dot com
2006-10-05 19:35 ` sjmunroe at us dot ibm dot com
2006-10-05 19:36 ` sjmunroe at us dot ibm dot com
2006-10-05 19:47 ` sjmunroe at us dot ibm dot com
2007-01-22 23:54 ` sjmunroe at us dot ibm dot com
2007-01-23  0:01 ` sjmunroe at us dot ibm dot com
2007-01-23  0:03 ` sjmunroe at us dot ibm dot com
2007-01-23  0:07 ` sjmunroe at us dot ibm dot com
2007-01-23  0:14 ` sjmunroe at us dot ibm dot com
2007-02-05 20:50 ` jakub at redhat dot com
2007-02-06 16:30 ` sjmunroe at us dot ibm dot com
2007-02-06 16:31 ` sjmunroe at us dot ibm dot com
2007-02-06 16:33 ` sjmunroe at us dot ibm dot com
2007-02-18 13:51 ` aj at suse dot de
2007-02-26 22:08 ` sjmunroe at us dot ibm dot com
2007-04-03 17:58 ` sjmunroe at us dot ibm dot com
2007-04-03 17:59 ` joseph at codesourcery dot com
2007-04-03 18:00 ` sjmunroe at us dot ibm dot com
2007-04-03 19:06 ` sjmunroe at us dot ibm dot com
2007-04-03 19:39 ` sjmunroe at us dot ibm dot com
2007-10-22 14:44 ` vincent+libc at vinc17 dot org
2010-02-02 21:56 ` nbowler at draconx dot ca
2010-02-02 21:57 ` nbowler at draconx dot ca
2010-06-29 11:50 ` zimmerma+gcc at loria dot fr

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-3268-131-omOIJoDS5s@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).