public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/49024] REAL*16 ERFC_SCALED inaccuracy
Date: Mon, 23 May 2011 22:12:00 -0000 [thread overview]
Message-ID: <bug-49024-4-OkHLozUK3I@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49024-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49024
Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|fxcoudert at gcc dot |unassigned at gcc dot
|gnu.org |gnu.org
--- Comment #4 from Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> 2011-05-23 21:48:42 UTC ---
(In reply to comment #3)
> For 128 bits: do you plan to handle it in libgfortran or directly in
> libquadmath? I think one can export another function directly in libquadmath,
> which should be easier to handle - and yield faster code.
I've thought about it a bit, both are fine with me. But… I don't have time to
play with Mathematica right now to find the good approximations in each
possible range, so I'll unassign myself.
next prev parent reply other threads:[~2011-05-23 22:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 14:28 [Bug libfortran/49024] New: " thenlich at users dot sourceforge.net
2011-05-23 11:01 ` [Bug libfortran/49024] " fxcoudert at gcc dot gnu.org
2011-05-23 20:54 ` fxcoudert at gcc dot gnu.org
2011-05-23 21:45 ` burnus at gcc dot gnu.org
2011-05-23 22:12 ` fxcoudert at gcc dot gnu.org [this message]
2013-11-20 22:19 ` fxcoudert at gcc dot gnu.org
2013-11-21 8:46 ` fxcoudert at gcc dot gnu.org
2013-11-21 8:46 ` fxcoudert at gcc dot gnu.org
2013-11-21 9:21 ` schwab@linux-m68k.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-49024-4-OkHLozUK3I@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).