public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "schmid at snake dot iap dot physik dot tu-darmstadt dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/14545] New: Cannot compile pooma-gcc (regression) Date: Fri, 12 Mar 2004 06:29:00 -0000 [thread overview] Message-ID: <20040312062911.14545.schmid@snake.iap.physik.tu-darmstadt.de> (raw) I cannot compile the file src/DataBrowser/DataBrowser.cmpl.cpp from pooma-gcc any more. Earlier gcc 3.4 snapshoths had no problems compiling it. g++ -v -c /home/peter/zuhause/home/trans/c++/pooma-gcc/src/DataBrowser/ DataBrowser.cmpl.cpp -o /home/peter/zuhause/home/trans/c++/pooma-gcc/src/ DataBrowser/LINUXgcc/DataBrowser.cmpl.o -ftemplate-depth-60 -Drestrict=__restrict__ -DNOPAssert -DNOCTAssert -I/home/peter/zuhause/home/ trans/c++/pooma-gcc/src -I/home/peter/zuhause/home/trans/c++/pooma-gcc/lib/ LINUXgcc Reading specs from /usr/local/lib/gcc/i686-pc-linux-gnu/3.4.0/specs Configured with: ../gcc/configure --enable-threads=posix --enable-languages=c,c ++,f77,objc --enable-__cxa_atexit --enable-libstdcxx-debug Thread model: posix gcc version 3.4.0 20040312 (prerelease) /usr/local/libexec/gcc/i686-pc-linux-gnu/3.4.0/cc1plus -quiet -v -I/home/ peter/zuhause/home/trans/c++/pooma-gcc/src -I/home/peter/zuhause/home/trans/c+ +/pooma-gcc/lib/LINUXgcc -D_GNU_SOURCE -Drestrict=__restrict__ -DNOPAssert -DNOCTAssert /home/peter/zuhause/home/trans/c++/pooma-gcc/src/DataBrowser/ DataBrowser.cmpl.cpp -quiet -dumpbase DataBrowser.cmpl.cpp -mtune=pentiumpro -auxbase-strip /home/peter/zuhause/home/trans/c++/pooma-gcc/src/DataBrowser/ LINUXgcc/DataBrowser.cmpl.o -version -ftemplate-depth-60 -o /tmp/ccZ1UkPd.s ignoring nonexistent directory "NONE/include" ignoring nonexistent directory "/usr/local/lib/gcc/ i686-pc-linux-gnu/3.4.0/../../../../i686-pc-linux-gnu/include" #include "..." search starts here: #include <...> search starts here: /home/peter/zuhause/home/trans/c++/pooma-gcc/src /home/peter/zuhause/home/trans/c++/pooma-gcc/lib/LINUXgcc /usr/local/lib/gcc/i686-pc-linux-gnu/3.4.0/../../../../include/c++/3.4.0 /usr/local/lib/gcc/i686-pc-linux-gnu/3.4.0/../../../../include/c++/3.4.0/ i686-pc-linux-gnu /usr/local/lib/gcc/i686-pc-linux-gnu/3.4.0/../../../../include/c++/3.4.0/ backward /usr/local/include /usr/local/lib/gcc/i686-pc-linux-gnu/3.4.0/include /usr/include End of search list. GNU C++ version 3.4.0 20040312 (prerelease) (i686-pc-linux-gnu) compiled by GNU C version 3.4.0 20040312 (prerelease). GGC heuristics: --param ggc-min-expand=64 --param ggc-min-heapsize=64274 In file included from /home/peter/zuhause/home/trans/c++/pooma-gcc/src/Domain/ Domain.h:63, from /home/peter/zuhause/home/trans/c++/pooma-gcc/src/Domain/ Interval.h:57, from /home/peter/zuhause/home/trans/c++/pooma-gcc/src/Layout/ INode.h:53, from /home/peter/zuhause/home/trans/c++/pooma-gcc/src/Layout/ SparseTileLayout.h:63, from /home/peter/zuhause/home/trans/c++/pooma-gcc/src/Engine/ IsValidLocation.h:55, from /home/peter/zuhause/home/trans/c++/pooma-gcc/src/Array/ PrintArray.h:57, from /home/peter/zuhause/home/trans/c++/pooma-gcc/src/ DataBrowser/DataBrowser.cmpl.cpp:30: /home/peter/zuhause/home/trans/c++/pooma-gcc/src/Domain/DomainBase.h: In member function `typename DT::AskDomain_t DomainBase<DT>::firsts() const': /home/peter/zuhause/home/trans/c++/pooma-gcc/src/Domain/DomainBase.h:215: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions -- Summary: Cannot compile pooma-gcc (regression) Product: gcc Version: 3.4.0 Status: UNCONFIRMED Severity: critical Priority: P1 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: schmid at snake dot iap dot physik dot tu-darmstadt dot de CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14545
next reply other threads:[~2004-03-12 6:29 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-03-12 6:29 schmid at snake dot iap dot physik dot tu-darmstadt dot de [this message] 2004-03-12 6:32 ` [Bug c++/14545] " schmid at snake dot iap dot physik dot tu-darmstadt dot de 2004-03-12 6:42 ` [Bug c++/14545] [3.4/3.5 Regression] " pinskia at gcc dot gnu dot org 2004-03-13 23:41 ` schmid at snake dot iap dot physik dot tu-darmstadt dot de 2004-03-14 3:45 ` pinskia at gcc dot gnu dot org 2004-03-15 13:41 ` giovannibajo at libero dot it 2004-03-15 16:58 ` giovannibajo at libero dot it 2004-03-16 15:20 ` pinskia at gcc dot gnu dot org 2004-03-17 1:19 ` giovannibajo at libero dot it 2004-03-17 1:34 ` mark at codesourcery dot com 2004-03-18 1:12 ` giovannibajo at libero dot it 2004-03-18 14:04 ` bangerth at dealii dot org 2004-03-18 14:42 ` giovannibajo at libero dot it 2004-03-18 15:09 ` bangerth at dealii dot org 2004-03-18 15:19 ` mark at codesourcery dot com 2004-03-18 15:30 ` bangerth at dealii dot org 2004-03-18 15:32 ` giovannibajo at libero dot it 2004-03-18 15:48 ` mark at codesourcery dot com 2004-03-18 15:53 ` bangerth at dealii dot org 2004-03-19 9:59 ` cvs-commit at gcc dot gnu dot org 2004-03-19 11:42 ` giovannibajo at libero dot it 2004-03-19 11:42 ` cvs-commit 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=20040312062911.14545.schmid@snake.iap.physik.tu-darmstadt.de \ --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).