public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: greg.edwards@tenix.com To: gcc-gnats@gcc.gnu.org Subject: c++/2232: Numerous g++ internal errors #122 after trivial omissions of closing brackets/braces/parens Date: Sun, 01 Apr 2001 00:00:00 -0000 [thread overview] Message-ID: <20010308224656.19101.qmail@sourceware.cygnus.com> (raw) >Number: 2232 >Category: c++ >Synopsis: Numerous g++ internal errors #122 after trivial omissions of closing brackets/braces/parens >Confidential: no >Severity: non-critical >Priority: low >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Thu Mar 08 14:56:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Greg Edwards, Tenix Defence Systems, Sydney, Australia >Release: gcc version 2.96 20000731 (Red Hat Linux 7.0) >Organization: >Environment: HP Kayak PIII 500Mhz, RedHat 7.0, C++ code. >Description: Apologies for spartan report. I regularly get a g++ complete collapse with internal error (122 on this occasion) which turns out to be provoked by merely omitting the closing } on a function, or other block, or in some cases other incomplete statements, eg "myfunc(arg1," where I have typed half a line of code, gone away to think, come back and compiled. Completion of the statement, or the closing } on a block or func, always fixes the problem. Previous compilers I have used (not GNU) manage to resync and recover, albeit with usually bogus error messages around the error point. Do you want detailed reports of these cases ? Is g++ designed to simply give up at these large error points ? Happily remaining parsing seems very robust, congrats. Apologies again for spartan error report, I am quite happy to document a case completely if needed. Greg Edwards >How-To-Repeat: Leave the closing brace off a function in a large code file. Chop off the last half of a complex statement with lots of brackets. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2001-04-01 0:00 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010308224656.19101.qmail@sourceware.cygnus.com \ --to=greg.edwards@tenix.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).