public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rmansfield at qnx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/45876] New: ICE: verify_gimple failed
Date: Sun, 03 Oct 2010 18:44:00 -0000 [thread overview]
Message-ID: <bug-45876-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45876
Summary: ICE: verify_gimple failed
Product: gcc
Version: 4.6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: rmansfield@qnx.com
Created attachment 21950
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=21950
preprocessed C source
$ ./xgcc -v
Using built-in specs.
COLLECT_GCC=./xgcc
Target: i686-pc-linux-gnu
Configured with: ../configure --disable-bootstrap --enable-languages=c++
Thread model: posix
gcc version 4.6.0 20101003 (experimental) [trunk revision 164915] (GCC)
$ ./xgcc -B. -O1 ~/t.i
/home/ryan/t.i: In function ‘gcLINKTREE_GenerateStates’:
/home/ryan/t.i:91:10: warning: excess elements in struct initialiser [enabled
by default]
/home/ryan/t.i:91:10: warning: (near initialisation for ‘codeGen’) [enabled by
default]
/home/ryan/t.i: In function ‘_ProcessSampler’:
/home/ryan/t.i:46:33: error: type mismatch in binary expression
short int
short unsigned int
gctUINT16
D.2116 = D.2115 + index;
/home/ryan/t.i:46:33: internal compiler error: verify_gimple failed
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
next reply other threads:[~2010-10-03 18:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-03 18:44 rmansfield at qnx dot com [this message]
2010-10-03 20:14 ` [Bug middle-end/45876] [4.6 Regression] " rguenth at gcc dot gnu.org
2010-10-04 1:09 ` hjl.tools at gmail dot com
2010-10-04 9:27 ` jakub at gcc dot gnu.org
2010-10-04 15:49 ` jakub at gcc dot gnu.org
2010-10-26 1:08 ` 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-45876-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).