From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23976 invoked by alias); 5 Jan 2007 14:35:14 -0000 Received: (qmail 23947 invoked by uid 22791); 5 Jan 2007 14:35:14 -0000 X-Spam-Check-By: sourceware.org Received: from wr-out-0506.google.com (HELO wr-out-0506.google.com) (64.233.184.224) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 05 Jan 2007 14:35:10 +0000 Received: by wr-out-0506.google.com with SMTP id i3so2320260wra for ; Fri, 05 Jan 2007 06:35:08 -0800 (PST) Received: by 10.90.81.14 with SMTP id e14mr645954agb.1168007708318; Fri, 05 Jan 2007 06:35:08 -0800 (PST) Received: by 10.90.120.4 with HTTP; Fri, 5 Jan 2007 06:35:08 -0800 (PST) Message-ID: <24b520d20701050635g77d16a9vc54b290e1e9d12fb@mail.gmail.com> Date: Fri, 05 Jan 2007 14:35:00 -0000 From: "Doug Gregor" To: "Richard Guenther" Subject: Re: [PATCH, C++] Make Canonical ICE instead of just warn when mismatching Cc: "Brooks Moses" , gcc-patches@gcc.gnu.org In-Reply-To: <84fc9c000701050620v647343e2n30074cd15d47f02b@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <459DC221.4030201@codesourcery.com> <24b520d20701050613h10bddaceu567ee42e6b4e111f@mail.gmail.com> <84fc9c000701050620v647343e2n30074cd15d47f02b@mail.gmail.com> X-IsSubscribed: yes Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org X-SW-Source: 2007-01/txt/msg00388.txt.bz2 On 1/5/07, Richard Guenther wrote: > So for --disable-checking builds we can get the wrong answer for > T1 == T2 and so generate wrong code? In this case the error should > be fatal, so we get each error reported and not get silent failures > at the time 4.3 is released. I might be able to come up with a twisted example where we get wrong code from a wrong answer with canonical types... more likely, we'll just error or ICE on legal code. When users report such problems, we ask them to add "--param verify-canonical-types 1"... if that fixes the problem, they can continue to get work done and we can fix the problem. Cheers, Doug