From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13441 invoked by alias); 20 Sep 2004 21:00:23 -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 13434 invoked from network); 20 Sep 2004 21:00:22 -0000 Received: from unknown (HELO mail.codesourcery.com) (65.74.133.10) by sourceware.org with SMTP; 20 Sep 2004 21:00:22 -0000 Received: (qmail 14001 invoked from network); 20 Sep 2004 21:00:21 -0000 Received: from localhost (HELO ?192.168.0.105?) (mitchell@127.0.0.1) by mail.codesourcery.com with SMTP; 20 Sep 2004 21:00:21 -0000 Message-ID: <414F44E0.90506@codesourcery.com> Date: Mon, 20 Sep 2004 21:08:00 -0000 From: Mark Mitchell Organization: CodeSourcery, LLC User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616 MIME-Version: 1.0 To: Matt Austern CC: gcc@gcc.gnu.org, Dale Johannesen , Nathan Sidwell , Jason Merrill Subject: Re: DR handling for C++ References: <414F37E0.3020509@codesourcery.com> <79845B6C-0B44-11D9-8A65-000A95D7CD40@apple.com> <414F412C.90504@codesourcery.com> <4FFC8911-0B47-11D9-ADB7-000A95AA5E5E@apple.com> In-Reply-To: <4FFC8911-0B47-11D9-ADB7-000A95AA5E5E@apple.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-09/txt/msg01194.txt.bz2 Matt Austern wrote: > Isn't the fundamental problem that we're using pedwarns differently in > the C and C++ front ends? In the C front end you don't even see > pedwarns unless you use a special compiler flag, and making them into > errors requires an even more special compiler flag. It's very odd > that it means something so different in the C++ front end. > > This is really going off into a different subject (pedwarn policy, not > DR policy), but I'd suggest that we: > 1. Change the C++ front end's pedwarn defaults to match the C front > end's policy. > 2. Remove -fpermissive, which #1 will render redundant. > 3. Go through our pedwarns and decide which ones should be errors, > which ones should be warnings, and which ones really should just be > pedwarns. Yes, that's exactly what I was trying to suggest. -- Mark Mitchell CodeSourcery, LLC (916) 791-8304 mark@codesourcery.com