public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/51601] New: ice in verify_live_on_entry
Date: Sat, 17 Dec 2011 18:29:00 -0000 [thread overview]
Message-ID: <bug-51601-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51601
Bug #: 51601
Summary: ice in verify_live_on_entry
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: dcb314@hotmail.com
Created attachment 26121
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26121
gzipped C++ source code
I just tried to compile the package drumstick-0.5.0-1
on latest trunk dated 20111216 on an AMD x86_64 box.
The compiler said
dotLength_28 is defined in BB6, by:
dotLength_28 = PHI <dotLength_38(5), dotLength_41(6)>
It is also live-on-entry to entry BB 2 So it appears to have multiple defs.
/home/dcb/rpmbuild/BUILD/drumstick-0.5.0/library/src/qove.cpp: In member
function 'int OVE::NoteContainer::getDuration() const':
/home/dcb/rpmbuild/BUILD/drumstick-0.5.0/library/src/qove.cpp:4580:5: internal
compiler error: in verify_live_on_entry, at tree-ssa-live.c:1444
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
Preprocessed source code attached. Flag -O3 required.
next reply other threads:[~2011-12-17 18:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-17 18:29 dcb314 at hotmail dot com [this message]
2011-12-19 9:29 ` [Bug c++/51601] " rguenth at gcc dot gnu.org
2011-12-19 11:14 ` [Bug tree-optimization/51601] [4.7 Regression] " rguenth at gcc dot gnu.org
2011-12-19 11:23 ` 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-51601-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).