From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-134873-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 17675 invoked by alias); 17 Mar 2005 00:19:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Received: (qmail 17623 invoked by uid 48); 17 Mar 2005 00:19:15 -0000
Date: Thu, 17 Mar 2005 00:19:00 -0000
From: "reichelt at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Message-ID: <20050317001912.20506.reichelt@gcc.gnu.org>
Reply-To: gcc-bugzilla@gcc.gnu.org
Subject: [Bug middle-end/20506] New: verify_stmts calls error() on internal errors
X-Bugzilla-Reason: CC
X-SW-Source: 2005-03/txt/msg02028.txt.bz2
List-Id: <gcc-bugs.sourceware.org>

When verify_stmts finds an inconsistency an error like the following
(taken from PR17483) is issued:

  bug.cc: In function `void bar()':
  bug.cc:15: error: address taken, but ADDRESSABLE bit not set
  D.1590

  bug.cc:15: internal compiler error: verify_stmts failed.
  Please submit a full bug report, [etc.]

But this is not a user error as the first part of the error message suggests,
this is an internal error.

The error reporting mechanism should be changed to reflect this in order
to avoid user confusion.

-- 
           Summary: verify_stmts calls error() on internal errors
           Product: gcc
           Version: 4.0.0
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P2
         Component: middle-end
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: reichelt at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20506