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/54870] New: gfortran.dg/array_constructor_4.f90 FAILs
Date: Tue, 09 Oct 2012 09:29:00 -0000 [thread overview]
Message-ID: <bug-54870-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54870
Bug #: 54870
Summary: gfortran.dg/array_constructor_4.f90 FAILs
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
CC: ebotcazou@gcc.gnu.org
Host: sparc*-*-solaris2*
Target: sparc*-*-solaris2*
Build: sparc*-*-solaris2*
Since about 20120608, the gfortran.dg/array_constructor_4.f90 FAILS on
Solaris/SPARC with -m64:
FAIL: gfortran.dg/array_constructor_4.f90 -O3 -fomit-frame-pointer execution
test
FAIL: gfortran.dg/array_constructor_4.f90 -O3 -fomit-frame-pointer
-funroll-loops execution test
FAIL: gfortran.dg/array_constructor_4.f90 -O3 -fomit-frame-pointer
-funroll-all-loops -finline-functions execution test
FAIL: gfortran.dg/array_constructor_4.f90 -O3 -g execution test
The -O3 -g test aborts like this:
Backtrace for this error:
#0 fffffffb5c822bcb
[New Thread 1 (LWP 1)]
Program received signal SIGABRT, Aborted.
[Switching to Thread 1 (LWP 1)]
0xffffffff7eee7620 in _lwp_kill () from /lib/64/libc.so.1
(gdb) where
#0 0xffffffff7eee7620 in _lwp_kill () from /lib/64/libc.so.1
#1 0xffffffff7ee94624 in raise () from /lib/64/libc.so.1
#2 0xffffffff7ee6a10c in abort () from /lib/64/libc.so.1
#3 0xfffffffb5c824ed8 in _gfortrani_sys_abort ()
at /vol/gcc/src/hg/trunk/local/libgfortran/runtime/error.c:173
#4 0xfffffffb5c8e3178 in _gfortran_abort ()
at /vol/gcc/src/hg/trunk/local/libgfortran/intrinsics/abort.c:33
#5 0x000000010000107c in MAIN__ ()
at
/vol/gcc/src/hg/trunk/local/gcc/testsuite/gfortran.dg/array_constructor_4.f90:9
#6 main (argc=<optimized out>, argv=0xffffffff7ffff538)
at
/vol/gcc/src/hg/trunk/local/gcc/testsuite/gfortran.dg/array_constructor_4.f90:23
#7 0x0000000100000d04 in _start ()
next reply other threads:[~2012-10-09 9:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-09 9:29 ro at gcc dot gnu.org [this message]
2012-10-09 9:30 ` [Bug fortran/54870] " ro at gcc dot gnu.org
2012-10-12 8:39 ` ro at gcc dot gnu.org
2012-10-13 21:33 ` [Bug fortran/54870] [4.8 regression] " ebotcazou at gcc dot gnu.org
2012-10-13 22:06 ` ebotcazou at gcc dot gnu.org
2012-10-16 22:49 ` [Bug rtl-optimization/54870] " ebotcazou at gcc dot gnu.org
2012-10-16 23:18 ` ebotcazou at gcc dot gnu.org
2012-10-16 23:19 ` ebotcazou at gcc dot gnu.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-54870-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).