public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: wwieser@gmx.de To: gcc-gnats@gcc.gnu.org Subject: c++/5963: gcc won't temrminate with simple source Date: Thu, 14 Mar 2002 05:06:00 -0000 [thread overview] Message-ID: <20020314130129.26543.qmail@sources.redhat.com> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1274 bytes --] >Number: 5963 >Category: c++ >Synopsis: gcc won't temrminate with simple source >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Thu Mar 14 05:06:01 PST 2002 >Closed-Date: >Last-Modified: >Originator: wwieser@gmx.de >Release: gcc-3.0.5 (prerelease) >Organization: >Environment: Linux i386 >Description: gcc-3.0.5 (prerelease) will not terminate if fed with the following code lines: (Note the missing `)´ in line 3.) -------------<loop.cc>------------ struct A { int foo8(int x) { return(foo16(x); } int foo16(int x); }; -------------------------------- bash# /usr/bin/time gcc -c loop.cc -o loop.o loop.cc: In member function `int A::foo8(int)': loop.cc:3: parse error before `;' token Command terminated by signal 2 0.00user 0.00system 1:02.61elapsed 0%CPU (0avgtext+0avgdata 0maxresident)k 0inputs+0outputs (111major+31minor)pagefaults 0swaps [Terminated by ^C after 1 minute on a fairly new Athlon system. NOTE: cc1plus is consuming 100% CPU, but gcc 0%, so `time´ reports `0%CPU´.] >How-To-Repeat: see above >Fix: Sorry, cannot help here. >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-03-14 13:06 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-03-14 5:06 wwieser [this message] 2002-07-23 8:13 lerdsuwa 2003-01-01 19:42 neroden
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=20020314130129.26543.qmail@sources.redhat.com \ --to=wwieser@gmx.de \ --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).