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 middle-end/67909] New: [6 Regression] 416.gamess in SPEC CPU 2006 is miscompiled
Date: Fri, 09 Oct 2015 16:36:00 -0000 [thread overview]
Message-ID: <bug-67909-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67909
Bug ID: 67909
Summary: [6 Regression] 416.gamess in SPEC CPU 2006 is
miscompiled
Product: gcc
Version: 5.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: hjl.tools at gmail dot com
Target Milestone: ---
On Linux/x86-64, revision 228616 gave
Running 416.gamess ref peak lnx32e-gcc default
416.gamess: copy 0 non-zero return code (exit code=11, signal=0)
****************************************
Contents of h2ocu2+.gradient.err
****************************************
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
Backtrace for this error:
#0 0x7f558732ecd9 in ???
#1 0x7f558732df5d in ???
#2 0x31c64344af in ???
#3 0x7f877e in ???
#4 0x7fe28b in ???
#5 0x10ad021 in ???
#6 0xf99f8c in ???
#7 0x8b9d40 in ???
#8 0x8ba1d4 in ???
#9 0x8bb7a7 in ???
#10 0x8bbf64 in ???
#11 0x8bc995 in ???
#12 0x4015cc in ???
#13 0x31c64206af in ???
#14 0x401618 in ???
#15 0xffffffffffffffff in ???
/bin/sh: line 1: 3415 Segmentation fault (core dumped) taskset -c
$TASK_CPU ../run_peak_ref_lnx32e-gcc.0000/gamess_peak.lnx32e-gcc
****************************************
Invalid run; unable to continue.
If you wish to ignore errors please use '-I' or ignore_errors
when compiled with
gfortran -O3 -funroll-loops -ffast-math -DSPEC_CPU_LP64
next reply other threads:[~2015-10-09 16:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 16:36 hjl.tools at gmail dot com [this message]
2015-10-09 19:03 ` [Bug middle-end/67909] " hjl.tools at gmail dot com
2015-10-12 20:12 ` [Bug tree-optimization/67909] " pthaugen at gcc dot gnu.org
2015-10-13 12:05 ` ysrumyan at gmail dot com
2015-10-13 12:07 ` ysrumyan at gmail dot com
2015-10-13 13:09 ` ienkovich at gcc dot gnu.org
2015-10-13 18:20 ` pthaugen at gcc dot gnu.org
2015-10-14 9:37 ` ienkovich 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-67909-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).