public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: sdementen@hotmail.com To: gcc-gnats@gcc.gnu.org Subject: c++/8161: Infinite loop of the compiler when compiling Date: Mon, 07 Oct 2002 08:26:00 -0000 [thread overview] Message-ID: <20021007151637.22056.qmail@sources.redhat.com> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1509 bytes --] >Number: 8161 >Category: c++ >Synopsis: Infinite loop of the compiler when compiling >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: ice-on-illegal-code >Submitter-Id: net >Arrival-Date: Mon Oct 07 08:26:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Sébastien de Menten >Release: gcc version 3.2 (Mandrake Linux 9.0 3.2-1mdk) >Organization: >Environment: Fresh Mandrake 9.0 installation (gcc-2.96 is also installed) >Description: Compilation of the file leads to error_infinite_loop.cpp:6: parse error before `)' token error_infinite_loop.cpp:7: missing ';' before right brace error_infinite_loop.cpp: In constructor `foo::foo()': error_infinite_loop.cpp:6: parse error before `;' token and the the compiler loops infinitely (without increasing its memory usage) >How-To-Repeat: Compile the file with no special flags g++ error_build_modify_expr.cpp >Fix: Do not define the constructor in the body of the class but outside the class. >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: text/x-c++src; name="error_infinite_loop.cpp" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="error_infinite_loop.cpp" I2luY2x1ZGUgPGlvc3RyZWFtPgoKY2xhc3MgZm9vIHsKcHVibGljOgogIGNvbnN0IGludCBkWzNd OwogIGZvbygpIDogZCgoY29uc3QgaW50W10pezEsMiwzfSkgewogIH07Cn07CgppbnQgbWFpbihp bnQgYXJnYyxjaGFyICoqYXJndikgewogIGZvbyBiOwp9Owo=
next reply other threads:[~2002-10-07 15:26 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-07 8:26 sdementen [this message] 2002-10-18 12:12 paolo
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=20021007151637.22056.qmail@sources.redhat.com \ --to=sdementen@hotmail.com \ --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).