public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/50487] FAIL: gfortran.dg/bessel_6.f90
Date: Thu, 22 Sep 2011 18:03:00 -0000 [thread overview]
Message-ID: <bug-50487-4-0Kk5AkeSZZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50487-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50487
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kargl at gcc dot gnu.org
--- Comment #1 from kargl at gcc dot gnu.org 2011-09-22 17:58:19 UTC ---
I've had this patch in my tree for nearly a year. I'm surprised
that glibc developers took nearly a year to apply a form of my
libm patch to their tree.
Index: gcc/testsuite/gfortran.dg/bessel_6.f90
===================================================================
--- gcc/testsuite/gfortran.dg/bessel_6.f90 (revision 179023)
+++ gcc/testsuite/gfortran.dg/bessel_6.f90 (working copy)
@@ -12,7 +12,7 @@
implicit none
real,parameter :: values(*) = [0.0, 0.5, 1.0, 0.9,
1.8,2.0,3.0,4.0,4.25,8.0,34.53, 475.78]
real,parameter :: myeps(size(values)) = epsilon(0.0) &
- * [2, 7, 5, 6, 9, 12, 12, 7, 7, 8, 75, 15 ]
+ * [2, 7, 5, 6, 9, 12, 12, 7, 7, 8, 92, 15 ]
! The following is sufficient for me - the values above are a bit
! more tolerant
! * [0, 5, 3, 4, 6, 7, 7, 5, 5, 6, 66, 4 ]
next prev parent reply other threads:[~2011-09-22 17:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 17:35 [Bug libfortran/50487] New: " hjl.tools at gmail dot com
2011-09-22 18:03 ` kargl at gcc dot gnu.org [this message]
2011-09-22 18:22 ` [Bug testsuite/50487] " hjl.tools at gmail dot com
2011-09-22 18:23 ` sgk at troutmask dot apl.washington.edu
2011-09-22 18:31 ` hjl.tools at gmail dot com
2011-09-22 18:36 ` kargl at gcc dot gnu.org
2011-09-22 18:36 ` kargl at gcc dot gnu.org
2011-09-22 18:42 ` kargl at gcc dot gnu.org
2011-09-22 18:43 ` sgk at troutmask dot apl.washington.edu
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-50487-4-0Kk5AkeSZZ@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).