public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: wilson@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, jreiser@BitWagon.com,
	jsm28@cam.ac.uk, nobody@gcc.gnu.org, wilson@gcc.gnu.org
Subject: Re: c/2047: Internal compiler error in `require_complete_type', at c-typeck.c:96
Date: Mon, 10 Sep 2001 18:39:00 -0000	[thread overview]
Message-ID: <20010911013944.20535.qmail@sourceware.cygnus.com> (raw)

Synopsis: Internal compiler error in `require_complete_type', at c-typeck.c:96

Responsible-Changed-From-To: unassigned->wilson
Responsible-Changed-By: wilson
Responsible-Changed-When: Mon Sep 10 18:39:44 2001
Responsible-Changed-Why:
    IA-64 maintainer
State-Changed-From-To: open->closed
State-Changed-By: wilson
State-Changed-When: Mon Sep 10 18:39:44 2001
State-Changed-Why:
    I reproduced the problem with the old obsolete 000717
    release.  It is a problem with cascading errors, resulting
    in a type tree that is invalid.  The internal consistency
    checking code detects the problem and triggers an abort.
    
    With current gcc sources, when we detect an inconsistency,
    if there were prior errors in the source code, then instead
    of aborting, we emit an error message "confused by earlier
    errors" and exit cleanly.  This seems like a reasonable
    solution to me.  We could add more code to handle this
    case, but it doesn't seem worthwhile, since we would just
    get even more useless error messages than we already do.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=2047&database=gcc


             reply	other threads:[~2001-09-10 18:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-10 18:39 wilson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-06-22  7:03 jsm28
2001-06-22  3:49 jsm28

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=20010911013944.20535.qmail@sourceware.cygnus.com \
    --to=wilson@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=jreiser@BitWagon.com \
    --cc=jsm28@cam.ac.uk \
    --cc=nobody@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: link
Be 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).