From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27771 invoked by alias); 24 Nov 2001 00:03:25 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 27457 invoked from network); 24 Nov 2001 00:02:06 -0000 Received: from unknown (HELO navy.csi.cam.ac.uk) (131.111.8.49) by sourceware.cygnus.com with SMTP; 24 Nov 2001 00:02:06 -0000 Received: from student.cusu.cam.ac.uk ([131.111.179.82] helo=kern.srcf.societies.cam.ac.uk ident=mail) by navy.csi.cam.ac.uk with esmtp (Exim 3.22 #1) id 167QGg-0006D1-00; Sat, 24 Nov 2001 00:02:02 +0000 Received: from jsm28 (helo=localhost) by kern.srcf.societies.cam.ac.uk with local-esmtp (Exim 3.12 #1 (Debian)) id 167QGg-00040M-00; Sat, 24 Nov 2001 00:02:02 +0000 Date: Wed, 14 Nov 2001 10:06:00 -0000 From: "Joseph S. Myers" X-X-Sender: To: Neil Booth cc: Zack Weinberg , Subject: Re: ICE in change_address at emit_rtl.c In-Reply-To: <20011123235256.A31269@daikokuya.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2001-11/txt/msg00638.txt.bz2 On Fri, 23 Nov 2001, Neil Booth wrote: > Hmm, OK, if you think it's possible too then it probably is. I might > have a stab at gradually removing it from the C and ObjC front ends > after 3.1 has branched; it's not worth it now. Does that seem a > reasonable goal to you Joseph? What of the other idea that has been discussed in the past, of typed error marks (separate ones for erroneous types, erroneous decls, ...)? We should first define the goals: * How much do we want to help users by finding multiple errors in a single compilation run (the point of not just stopping after the first error)? * What should we not try to do after error? For example, after error we should not attempt to optimize or convert to RTL any later part of the file, even if this means we miss some diagnostics; we should simply do the basic parsing and error checking. Are there other warning checks - beyond the basic constraint checking required by the standard - which should be disabled after error? * On error, how far should we skip before trying to make sense of the code again? -- Joseph S. Myers jsm28@cam.ac.uk