--
What|Removed |Added
Target Milestone|4.0.2 |4.0.3
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23139
--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-09-15
19:10 ---
Subject: Bug 23139
CVSROOT:/cvs/gcc
Module name:gcc
Changes by: [EMAIL PROTECTED] 2005-09-15 19:09:28
Modified files:
fixincludes: ChangeLog inclhack.def fixincl.x
--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-09-15
19:12 ---
Subject: Bug 23139
CVSROOT:/cvs/gcc
Module name:gcc
Branch: gcc-4_0-branch
Changes by: [EMAIL PROTECTED] 2005-09-15 19:12:00
Modified files:
fixincludes:
--- Additional Comments From mmitchel at gcc dot gnu dot org 2005-09-06
15:29 ---
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
--- Additional Comments From joseph at codesourcery dot com 2005-09-06
15:42 ---
Subject: Re: [3.4/4.0/4.1 Regression] -pedantic -ffast-math
breaks working code
On Tue, 6 Sep 2005, mmitchel at gcc dot gnu dot org wrote:
The problem behind both diagnostics fact that the C++
mmitchel at gcc dot gnu dot org [EMAIL PROTECTED] 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
--- 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 [EMAIL PROTECTED] writes:
| The problem behind both diagnostics fact that the C++
--- Additional Comments From mmitchel at gcc dot gnu dot org 2005-09-06
22:03 ---
The floating constant exceeds range message comes from interpret_float in
c-lex.c, which does test just pedantic, rather than CPP_PEDANTIC(pfile). So,
while the preprocessor warning about use of a
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-07-30
15:26 ---
3.4 produces a warning and not an error, maybe the warning became a pedwarn in
4.0.0 but this
should not produce a warning or an error at all.
For some reason the C front-end does not produce a warning
