public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/56204] New: [4.8 regression] gfortran.dg/quad_[23].f90 FAIL on Solaris 9/x86
Date: Mon, 04 Feb 2013 13:32:00 -0000 [thread overview]
Message-ID: <bug-56204-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56204
Bug #: 56204
Summary: [4.8 regression] gfortran.dg/quad_[23].f90 FAIL on
Solaris 9/x86
Classification: Unclassified
Product: gcc
Version: 4.8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: ro@gcc.gnu.org
Host: i386-pc-solaris2.9
Target: i386-pc-solaris2.9
Build: i386-pc-solaris2.9
Since about 20121205, the quad_[23].f90 execution tests started to FAIL on
Solaris 9/x86:
FAIL: gfortran.dg/quad_2.f90 -O0 execution test
FAIL: gfortran.dg/quad_2.f90 -O1 execution test
FAIL: gfortran.dg/quad_2.f90 -O2 execution test
FAIL: gfortran.dg/quad_2.f90 -O3 -fomit-frame-pointer execution test
FAIL: gfortran.dg/quad_2.f90 -O3 -fomit-frame-pointer -funroll-loops
execution test
FAIL: gfortran.dg/quad_2.f90 -O3 -fomit-frame-pointer -funroll-all-loops
-finline-functions execution test
FAIL: gfortran.dg/quad_2.f90 -O3 -g execution test
FAIL: gfortran.dg/quad_2.f90 -Os execution test
FAIL: gfortran.dg/quad_3.f90 -O0 execution test
FAIL: gfortran.dg/quad_3.f90 -O1 execution test
FAIL: gfortran.dg/quad_3.f90 -O2 execution test
FAIL: gfortran.dg/quad_3.f90 -O3 -fomit-frame-pointer execution test
FAIL: gfortran.dg/quad_3.f90 -O3 -fomit-frame-pointer -funroll-loops
execution test
FAIL: gfortran.dg/quad_3.f90 -O3 -fomit-frame-pointer -funroll-all-loops
-finline-functions execution test
FAIL: gfortran.dg/quad_3.f90 -O3 -g execution test
FAIL: gfortran.dg/quad_3.f90 -Os execution test
It aborts here:
Program received signal SIGABRT, Aborted.
0xb5b23b96 in _libc_kill () from /usr/lib/libc.so.1
(gdb) where
#0 0xb5b23b96 in _libc_kill () from /usr/lib/libc.so.1
#1 0xb5ad7dbe in raise () from /usr/lib/libc.so.1
#2 0xb5ac03fe in abort () from /usr/lib/libc.so.1
#3 0xb5c54714 in _gfortrani_sys_abort ()
at /vol/gcc/src/hg/trunk/local/libgfortran/runtime/error.c:173
#4 0xb5d0f3b8 in _gfortran_abort ()
at /vol/gcc/src/hg/trunk/local/libgfortran/intrinsics/abort.c:33
#5 0x080511b2 in test_qp ()
at /vol/gcc/src/hg/trunk/local/gcc/testsuite/gfortran.dg/quad_2.f90:34
#6 0x08051662 in main (argc=1, argv=0x8047a28)
at /vol/gcc/src/hg/trunk/local/gcc/testsuite/gfortran.dg/quad_2.f90:78
#7 0x08050a1d in _start ()
The test is l.34:
34 if (fp2 /= fp4) call abort()
but unfortunately gdb 7.5 can read neither variable.
(gdb) p fp2
$1 = <error reading variable>
(gdb) p fp4
$2 = <error reading variable>
The quad_2.f90 is a regression from 4.7, the quad_3.f90 test wasn't present
there.
Rainer
next reply other threads:[~2013-02-04 13:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 13:32 ro at gcc dot gnu.org [this message]
2013-02-08 15:47 ` [Bug fortran/56204] " rguenth at gcc dot gnu.org
2013-02-12 19:27 ` burnus at gcc dot gnu.org
2013-02-13 11:20 ` ro at CeBiTec dot Uni-Bielefeld.DE
2013-02-13 12:04 ` burnus at gcc dot gnu.org
2013-02-13 12:06 ` burnus at gcc dot gnu.org
2013-02-14 10:13 ` ro at CeBiTec dot Uni-Bielefeld.DE
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-56204-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).