public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aj at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/18040] New: ICE in for_each_index, at tree-ssa-loop-im.c:178
Date: Sun, 17 Oct 2004 12:36:00 -0000 [thread overview]
Message-ID: <20041017123619.18040.aj@gcc.gnu.org> (raw)
Compiling boost I get the following ICE:
/usr/lib/gcc/i586-suse-linux/4.0.0/cc1plus -fpreprocessed function.ii -quiet
-dumpbase function.cpp -mtune=pentium -auxbase-strip
bin/boost/libs/python/build/libboost_python.so/gcc/release/shared-linkable-true/function.o
-O3 -Wall -Wno-inline -version -ftemplate-depth-100 -finline-functions -fPIC -o
function.s
GNU C++ version 4.0.0 20041013 (experimental) (SUSE Linux) (i586-suse-linux)
compiled by GNU C version 4.0.0 20041013 (experimental) (SUSE Linux).
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
function.ii: In member function `void
boost::python::objects::function::argument_error(PyObject*, PyObject*) const':
function.ii:63053: internal compiler error: in for_each_index, at
tree-ssa-loop-im.c:178
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
--
Summary: ICE in for_each_index, at tree-ssa-loop-im.c:178
Product: gcc
Version: 4.0.0
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: middle-end
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: aj at gcc dot gnu dot org
CC: gcc-bugs at gcc dot gnu dot org
GCC build triplet: i586-linux-gnu
GCC host triplet: i586-linux-gnu
GCC target triplet: i586-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18040
next reply other threads:[~2004-10-17 12:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-17 12:36 aj at gcc dot gnu dot org [this message]
2004-10-17 12:37 ` [Bug middle-end/18040] " aj at gcc dot gnu dot org
2004-10-17 13:06 ` kazu at cs dot umass dot edu
2004-10-17 13:34 ` [Bug middle-end/18040] [4.0 Regression] " giovannibajo at libero dot it
2004-10-17 14:47 ` [Bug tree-optimization/18040] " pinskia at gcc dot gnu dot org
2004-10-17 16:01 ` rakdver at gcc dot gnu dot org
2004-10-17 16:11 ` pinskia at gcc dot gnu dot org
2004-10-17 16:17 ` pinskia at gcc dot gnu dot org
2004-10-17 16:23 ` rakdver at gcc dot gnu dot org
2004-10-17 16:30 ` pinskia at gcc dot gnu dot org
2004-10-17 19:18 ` rakdver at gcc dot gnu dot org
2004-10-17 22:06 ` pinskia at gcc dot gnu dot org
2004-10-17 22:17 ` pinskia at gcc dot gnu dot org
2004-10-17 22:19 ` pinskia at gcc dot gnu dot org
2004-11-27 21:17 ` neroden at gcc dot gnu dot org
2004-11-27 21:20 ` pinskia at gcc dot gnu dot org
2004-12-10 16:54 ` pinskia at gcc dot gnu dot org
2004-12-12 3:05 ` pinskia at gcc dot gnu dot org
2004-12-12 16:45 ` cvs-commit at gcc dot gnu dot org
2004-12-12 16:46 ` pinskia at gcc dot gnu dot 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=20041017123619.18040.aj@gcc.gnu.org \
--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).