From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18393 invoked by alias); 6 Sep 2005 16:12:59 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 18366 invoked by alias); 6 Sep 2005 16:12:54 -0000 Date: Tue, 06 Sep 2005 16:12:00 -0000 Message-ID: <20050906161254.18365.qmail@sourceware.org> From: "gdr at integrable-solutions dot net" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20050729205340.23139.thor@math.tu-berlin.de> References: <20050729205340.23139.thor@math.tu-berlin.de> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug c++/23139] [3.4/4.0/4.1 Regression] -pedantic -ffast-math breaks working code X-Bugzilla-Reason: CC X-SW-Source: 2005-09/txt/msg00702.txt.bz2 List-Id: ------- Additional Comments From gdr at integrable-solutions dot net 2005-09-06 16:12 ------- Subject: Re: [3.4/4.0/4.1 Regression] -pedantic -ffast-math breaks working code "mmitchel at gcc dot gnu dot org" writes: | The problem behind both diagnostics fact that the C++ front-end pre-lexes the | entire source file. As a result, the lexing routines, which depends on the | setting of pedantic to determine whether or not to issue errors, are | called when pedantic is set, even though we are within an | __extension__ block. Because the parsing of __extension__ blocks is | complex, we need to either (a) eliminate the up-front lexing, or (b) | defer issuing diagnostics until we are actually in | position to know the correct value of pedantic. In long term, I believe (b) is a better alternative. -- Gaby -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23139