public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: serpent@ms5.hinet.net To: gcc-gnats@gcc.gnu.org Subject: c++/3529: g++-3.0 fails to compile a simple c++ prog., g++-2.95.2 compiles fine Date: Mon, 02 Jul 2001 04:56:00 -0000 [thread overview] Message-ID: <20010702115046.30704.qmail@sourceware.cygnus.com> (raw) >Number: 3529 >Category: c++ >Synopsis: g++-3.0 fails to compile a simple c++ prog., g++-2.95.2 compiles fine >Confidential: no >Severity: critical >Priority: high >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Mon Jul 02 04:56:01 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Crystal Lynn >Release: gcc-3.0 >Organization: >Environment: linux-2.4.5/Suse-7.1 >Description: Reading specs from /home/crystal/local/gcc-3.0/lib/gcc-lib/i586-pc-linux-gnu/3.0 /specs Configured with: ../configure --prefix=/home/crystal/local/gcc-3.0 --enable-shar ed --enable-languages=c,c++,java --enable-version-specific-runtime-libs --enable -threads --without-fast-fixincludes --verbose Thread model: posix gcc version 3.0 /home/crystal/local/gcc-3.0/lib/gcc-lib/i586-pc-linux-gnu/3.0/cc1plus -v -D__GN UC__=3 -D__GNUC_MINOR__=0 -D__GNUC_PATCHLEVEL__=0 -D__ELF__ -Dunix -Dlinux -D__E LF__ -D__unix__ -D__linux__ -D__unix -D__linux -Asystem=posix -D__NO_INLINE__ -D __STDC_HOSTED__=1 -Wall -D_GNU_SOURCE -Acpu=i386 -Amachine=i386 -Di386 -D__i386 -D__i386__ -D__tune_i586__ -D__tune_pentium__ a.cpp -D__GNUG__=3 -D__GXX_DEPRECA TED -D__EXCEPTIONS -D__GXX_ABI_VERSION=100 -quiet -dumpbase a.cpp -Wall -version -o /tmp/cc3Gkh8K.s GNU CPP version 3.0 (cpplib) (i386 Linux/ELF) GNU C++ version 3.0 (i586-pc-linux-gnu) compiled by GNU C version 3.0. ignoring nonexistent directory "/home/crystal/local/gcc-3.0/i586-pc-linux-gnu/in clude" #include "..." search starts here: #include <...> search starts here: /home/crystal/local/gcc-3.0/lib/gcc-lib/i586-pc-linux-gnu/3.0/include/g++ /home/crystal/local/gcc-3.0/lib/gcc-lib/i586-pc-linux-gnu/3.0/include/g++/i586- pc-linux-gnu /home/crystal/local/gcc-3.0/lib/gcc-lib/i586-pc-linux-gnu/3.0/include/g++/backw ard /usr/local/include /home/crystal/local/gcc-3.0/lib/gcc-lib/i586-pc-linux-gnu/3.0/include /usr/include End of search list. g++: Internal error: Killed (program cc1plus) Please submit a full bug report. see <URL: http://www.gnu.org/software/gcc/bugs.html > for instructions. >How-To-Repeat: g++ -c a.cpp And(after several minutes...) you'll see 'internal compiler error' >Fix: >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: application/octet-stream; name="a.cpp" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="a.cpp" Y2xhc3MgU3RyaW5nQnVmZmVyOwoKY2xhc3MgU3RyaW5nCnsKCXB1YmxpYzoKCQlTdHJpbmcoKTsK CQlTdHJpbmcoU3RyaW5nQnVmZmVyIHNiKTsKCQlTdHJpbmcoY29uc3QgU3RyaW5nICYgcmhzKTsK CQl+U3RyaW5nKCk7CgoJCVN0cmluZyYgb3BlcmF0b3IrPSAoY29uc3QgU3RyaW5nICYgcmhzKTsK fTsKCmNsYXNzIFN0cmluZ0J1ZmZlcjogcHVibGljIFN0cmluZwp7CglwdWJsaWM6CgkJU3RyaW5n QnVmZmVyKCk7CgkJflN0cmluZ0J1ZmZlcigpOwoKCQlTdHJpbmdCdWZmZXIgYXBwZW5kKFN0cmlu ZyBzdHIyKQoJCXsKCQkJKnRoaXMgKz0gc3RyMjsKCQkJcmV0dXJuICp0aGlzOwoJCX0KfTsK
next reply other threads:[~2001-07-02 4:56 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-07-02 4:56 serpent [this message] 2001-07-07 7:24 lerdsuwa 2001-07-24 3:25 nathan 2001-07-25 2:40 nathan
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=20010702115046.30704.qmail@sourceware.cygnus.com \ --to=serpent@ms5.hinet.net \ --cc=gcc-gnats@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).