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/65533] New: [5 Regression] 252.eon in SPEC CPU 2000 failed to build
Date: Tue, 24 Mar 2015 02:19:00 -0000 [thread overview]
Message-ID: <bug-65533-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65533
Bug ID: 65533
Summary: [5 Regression] 252.eon in SPEC CPU 2000 failed to
build
Product: gcc
Version: 5.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: hjl.tools at gmail dot com
On Linux/x86-64, r221604 gave
g++ -c -o ggHMatrix3.o -DSPEC_CPU2000_LP64 -DHAS_ERRLIST -I. -DNDEBUG
-O3 -funroll-loops -ffast-math ggHMatrix3.cc
ggHMatrix3.cc: In function 'ggHPoint3 operator*(const ggHMatrix3&, const
ggHPoint3&)':
ggHMatrix3.cc:303:11: internal compiler error: in quick_push, at vec.h:867
ggHPoint3 operator*(const ggHMatrix3 &m, const ggHPoint3 &p) {
^
0xedabf3 vec<_slp_tree*, va_heap, vl_embed>::quick_push(_slp_tree* const&)
../../src-trunk/gcc/vec.h:867
0xedabf3 vec<_slp_tree*, va_heap, vl_ptr>::quick_push(_slp_tree* const&)
../../src-trunk/gcc/vec.h:1525
0xedabf3 vec<_slp_tree*, va_heap, vl_ptr>::safe_push(_slp_tree* const&)
../../src-trunk/gcc/vec.h:1538
0xedabf3 vect_build_slp_tree
../../src-trunk/gcc/tree-vect-slp.c:955
0xeda6a9 vect_build_slp_tree
../../src-trunk/gcc/tree-vect-slp.c:1054
0xeda445 vect_build_slp_tree
../../src-trunk/gcc/tree-vect-slp.c:1010
0xedc2bc vect_analyze_slp_instance
../../src-trunk/gcc/tree-vect-slp.c:1636
0xedda56 vect_analyze_slp(_loop_vec_info*, _bb_vec_info*, unsigned int)
../../src-trunk/gcc/tree-vect-slp.c:1768
0xeddf29 vect_slp_analyze_bb_1
../../src-trunk/gcc/tree-vect-slp.c:2300
0xeddf29 vect_slp_analyze_bb(basic_block_def*)
../../src-trunk/gcc/tree-vect-slp.c:2421
0xee0332 execute
../../src-trunk/gcc/tree-vectorizer.c:657
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.
next reply other threads:[~2015-03-23 23:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 2:19 hjl.tools at gmail dot com [this message]
2015-03-24 7:09 ` [Bug middle-end/65533] " hjl.tools at gmail dot com
2015-03-24 7:54 ` jakub at gcc dot gnu.org
2015-03-24 8:00 ` jakub at gcc dot gnu.org
2015-03-24 8:43 ` [Bug tree-optimization/65533] " jakub at gcc dot gnu.org
2015-03-24 8:49 ` jakub at gcc dot gnu.org
2015-03-24 9:10 ` rguenth at gcc dot gnu.org
2015-03-24 9:16 ` rguenth at gcc dot gnu.org
2015-03-24 9:32 ` rguenther at suse dot de
2015-03-24 10:53 ` jakub at gcc dot gnu.org
2015-03-24 11:43 ` jakub 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-65533-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).