public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: fabiosmoker <fabiosmoker@libero.it> To: bug-gcc@gnu.org Subject: bug Date: Fri, 28 Dec 2001 09:54:00 -0000 [thread overview] Message-ID: <20011228183454.A195@libero.it> (raw) [-- Attachment #1: Type: text/plain, Size: 70 bytes --] question? the iterators shouldn't be indipendent from the data type ? [-- Attachment #2: data --] [-- Type: text/plain, Size: 1599 bytes --] Reading specs from /usr/local/lib/gcc-lib/i586-pc-linux-gnu/3.0.3/specs Configured with: ../configure --enable-share --with-gnu-as --enable-threads --enable-languages=c++ Thread model: posix gcc version 3.0.3 /usr/local/lib/gcc-lib/i586-pc-linux-gnu/3.0.3/cpp0 -lang-c++ -D__GNUG__=3 -D__GXX_DEPRECATED -D__EXCEPTIONS -D__GXX_ABI_VERSION=100 -v -D__GNUC__=3 -D__GNUC_MINOR__=0 -D__GNUC_PATCHLEVEL__=3 -D__ELF__ -Dunix -Dlinux -D__ELF__ -D__unix__ -D__linux__ -D__unix -D__linux -Asystem=posix -D__NO_INLINE__ -D__STDC_HOSTED__=1 -D_GNU_SOURCE -Acpu=i386 -Amachine=i386 -Di386 -D__i386 -D__i386__ -D__tune_i586__ -D__tune_pentium__ tree.cpp tree.ii GNU CPP version 3.0.3 (cpplib) (i386 Linux/ELF) ignoring nonexistent directory "/usr/local/i586-pc-linux-gnu/include" #include "..." search starts here: #include <...> search starts here: /usr/local/include/g++-v3 /usr/local/include/g++-v3/i586-pc-linux-gnu /usr/local/include/g++-v3/backward /usr/local/include /usr/local/lib/gcc-lib/i586-pc-linux-gnu/3.0.3/include /usr/include End of search list. /usr/local/lib/gcc-lib/i586-pc-linux-gnu/3.0.3/cc1plus -fpreprocessed tree.ii -quiet -dumpbase tree.cpp -version -o tree.s GNU CPP version 3.0.3 (cpplib) (i386 Linux/ELF) GNU C++ version 3.0.3 (i586-pc-linux-gnu) compiled by GNU C version 3.0.3. tree.cpp:7: Internal error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. ******************************* Question: the iterators shouldn't be indipendent from the data type ? [-- Attachment #3: tree.ii.bz2 --] [-- Type: application/octet-stream, Size: 28296 bytes --]
next reply other threads:[~2001-12-28 16:35 UTC|newest] Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-12-28 9:54 fabiosmoker [this message] -- strict thread matches above, loose matches on Subject: below -- 2007-02-08 18:07 bug Cseke Tamas 2006-07-19 18:57 bug kfahoo 2006-01-06 12:01 Bug Cavit Cahit VURAL 2005-12-18 12:14 bug Igor Selitsky 2005-03-03 12:15 Bug Administrator 2005-02-20 15:28 Bug Fikret Skrgic 2005-02-20 15:50 ` Bug Eric Botcazou 2002-07-30 14:56 bug Scott Dorsey 2002-01-08 17:46 bug ditty 2001-12-28 10:14 bug Paolo Carlini 2001-12-11 12:14 BUG Jason Beltrame 2001-10-22 20:55 Bug Bob Bomar 2001-09-19 15:56 bug Yves Dorfsman 2001-07-02 17:07 bug NOBUHIRO OKAMOTO 2001-07-02 17:58 ` bug Toshi Morita [not found] <000d01c01bcf$94785c30$e20f083d@wildcomm.net> 2000-09-11 20:51 ` Bug Alexandre Oliva 2000-08-17 23:31 bug Thomas Rudlof 2000-08-11 10:46 bug Joseph Meeks 2000-07-05 15:10 bug Jesus Ruiz 2000-07-05 15:20 ` bug Alexandre Oliva 2000-04-20 6:04 bug BRODIER Olivier 2000-03-31 15:26 BUG David [not found] <4.3.0.20000307111239.00aaea40@mail.questgate.net> 2000-03-07 12:05 ` bug Martin v. Loewis 2000-03-08 8:14 ` bug Michael Long 2000-03-09 16:33 ` bug Alexandre Oliva 2000-02-29 10:57 bug wieland Kroetz [not found] <3896F92C.87F1A9FF@godel.dis.eafit.edu.co> 2000-02-01 19:32 ` BUG Alexandre Oliva 1999-12-06 12:45 Bug George Christakis 1999-12-31 20:54 ` Bug Brian Ford 1999-11-30 23:39 bug Martin Richard 1999-11-09 21:32 ` bug Alexandre Oliva 1999-11-30 23:39 bug martin.schindelin 1999-11-30 23:39 ` bug Martin v. Loewis 1999-10-31 23:03 bug Mike Stump 1999-10-26 11:02 Bug Gustavo Niemeyer 1999-10-27 12:34 ` Bug Martin v. Loewis 1999-10-19 9:51 bug Helen Sun 1999-09-12 5:21 bug Stefan Wehner 1999-09-13 23:45 ` bug Martin v. Loewis 1999-09-10 19:53 Bug Samy 1999-09-10 23:48 ` Bug Mumit Khan 1999-07-31 23:33 bug Wael Hassan 1999-07-31 23:33 ` bug Brian Ford 1999-07-31 23:33 bug John Cotton 1999-08-31 22:45 ` bug Jeffrey A Law 1999-06-30 23:07 BUG root of all evil 1999-06-05 2:46 ` BUG Alexandre Oliva 1999-06-28 5:34 BUG Stelios Xanthakis 1999-06-29 1:34 ` BUG Alexandre Oliva 1999-06-18 11:51 bug Mohamed Zaakoun 1999-05-31 21:06 Bug Klaus Causemann 1999-05-22 1:41 ` Bug Philipp Thomas [not found] <99051319112100.00451@localhost.localdomain> 1999-05-31 21:06 ` Bug Martin v. Loewis 1999-04-30 23:15 bug holger 1999-04-30 23:15 BUG Chris Teli 1999-04-15 7:09 ` BUG Alexandre Oliva 1999-04-30 23:15 Bug David Corbin 1999-04-13 18:26 BUG Steven Chi 1999-04-30 23:15 ` BUG Alexandre Oliva 1999-04-04 8:53 Bug Mathias Creutz 1999-04-05 12:40 ` Bug Alexandre Oliva 1999-02-28 23:30 Bug Philip Rademakers 1999-02-28 23:30 ` Bug Nathan Sidwell 1999-02-04 6:49 Bug Dan Vasaru 1998-12-17 8:25 bug Jean-Benoit Pierrot 1998-11-23 6:46 bug Massimo Boninsegni 1998-11-23 13:26 ` bug Alexandre Oliva 1998-09-23 7:09 Bug Energoprom 1998-09-23 22:02 ` Bug Alexandre Oliva 1998-09-17 5:09 bug Thien Traitham 1998-09-17 10:49 ` bug Alexandre Oliva 1998-08-31 13:07 bug Brian Grossman 1998-09-01 20:17 ` bug Alexandre Oliva 1998-07-28 4:13 bug Henning Emmrich 1998-07-17 9:51 Bug J. de Antonio 1998-07-14 17:29 bug Fritz Koenig 1998-07-14 23:27 ` bug Martin von Loewis 1998-04-21 12:00 bug root 1998-03-23 23:23 bug Mats Hjelm 1998-02-09 23:36 bug Leeann Bent
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=20011228183454.A195@libero.it \ --to=fabiosmoker@libero.it \ --cc=bug-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).