public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/50487] New: FAIL: gfortran.dg/bessel_6.f90
Date: Thu, 22 Sep 2011 17:35:00 -0000 [thread overview]
Message-ID: <bug-50487-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50487
Bug #: 50487
Summary: FAIL: gfortran.dg/bessel_6.f90
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libfortran
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: hjl.tools@gmail.com
On Linux/x86-64, with glibc bug fix for
http://sourceware.org/bugzilla/show_bug.cgi?id=11589
which changes jn precision. I got
FAIL: gfortran.dg/bessel_6.f90 -O0 execution test
FAIL: gfortran.dg/bessel_6.f90 -O1 execution test
FAIL: gfortran.dg/bessel_6.f90 -O2 execution test
FAIL: gfortran.dg/bessel_6.f90 -O3 -fomit-frame-pointer execution test
FAIL: gfortran.dg/bessel_6.f90 -O3 -fomit-frame-pointer -funroll-all-loops
-finline-functions execution test
FAIL: gfortran.dg/bessel_6.f90 -O3 -fomit-frame-pointer -funroll-loops
execution test
FAIL: gfortran.dg/bessel_6.f90 -O3 -g execution test
FAIL: gfortran.dg/bessel_6.f90 -Os execution test
gfortran.dg/bessel_6.f90 compares scalar jnf vs bessel_jn_r4 in
libgfortran. Since scalar jn is changed in glibc, it fails at
YN for X = 34.529999 -- Epsilon = 1.19209290E-07
24 0.957530737E-02 0.957520306E-02 0.10E-06 91.3808822632 F F
[1] 15522 abort (core dumped) ./a.out
next reply other threads:[~2011-09-22 17:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 17:35 hjl.tools at gmail dot com [this message]
2011-09-22 18:03 ` [Bug libfortran/50487] " kargl at gcc dot gnu.org
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@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).