public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "deji_aking at yahoo dot ca" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/30316] New: internal compiler error: in set_lattice_value, at tree-ssa-ccp.c:434 Date: Thu, 28 Dec 2006 07:22:00 -0000 [thread overview] Message-ID: <bug-30316-8911@http.gcc.gnu.org/bugzilla/> (raw) O.k sorry about the bad summary (I know almost nothing about c++). I had installed 4.2.0 pre-release for my fortran needs and was trying to compile a package (beast-0.7.1, from beast.gtk.org) on fedora rawhide and I'm getting this ICE; >> if g++ -DHAVE_CONFIG_H -DBIRNET_LOG_DOMAIN='"signal"' -DPARANOID -DG_DISABLE_CONST_RETURNS -I. -I. -I../.. -I../.. -I../.. -I. -pthread -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -D_BIRNET_SOURCE_EXTENSIONS -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -g -DG_ENABLE_DEBUG -Wdeprecated -Wno-cast-qual -ftracer -finline-functions -fno-keep-static-consts -fmessage-length=80 -MT signal.o -MD -MP -MF ".deps/signal.Tpo" -c -o signal.o signal.cc; \ then mv -f ".deps/signal.Tpo" ".deps/signal.Po"; else rm -f ".deps/signal.Tpo"; exit 1; fi ./birnetsignalslot.hh: In function 'Birnet::Signals::Slot3<R0, A1, A2, A3, void> Birnet::Signals::slot(Class&, R0 (Class::*)(A1, A2, A3)) [with Class = <unnamed>::Connection3, R0 = void, A1 = int, A2 = Birnet::String, A3 = float]': ./birnetsignalslot.hh:126: internal compiler error: in set_lattice_value, at tree-ssa-ccp.c:434 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. make[3]: *** [signal.o] Error 1 >> I did try to run 'cpp -DHAVE_CONFIG_H -DBIRNET_LOG_DOMAIN='"datalist"' -DPARANOID -DG_DISABLE_CONST_RETURNS -I. -I. -I../.. -I../.. -I../.. -I. -pthread -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -D_BIRNET_SOURCE_EXTENSIONS -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -g -DG_ENABLE_DEBUG -Wdeprecated -Wno-cast-qual -ftracer -finline-functions -fno-keep-static-consts -fmessage-length=80 -MT datalist.o -MD -MP -MF ".deps/datalist.Tpo" datalist.cc >&datalist.cpp', the output is attached. [deji@agape tests]$ g++ --version g++ (GCC) 4.2.0 20061225 (prerelease) Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. -- Summary: internal compiler error: in set_lattice_value, at tree- ssa-ccp.c:434 Product: gcc Version: 4.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: deji_aking at yahoo dot ca http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30316
next reply other threads:[~2006-12-28 7:22 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-12-28 7:22 deji_aking at yahoo dot ca [this message] 2006-12-28 7:26 ` [Bug c++/30316] " deji_aking at yahoo dot ca 2006-12-28 17:43 ` [Bug tree-optimization/30316] " pinskia at gcc dot gnu dot org 2006-12-28 22:07 ` deji_aking at yahoo dot ca 2006-12-28 22:16 ` pinskia at gcc dot gnu dot org 2006-12-28 23:50 ` 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=bug-30316-8911@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: linkBe 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).