--- Comment #8 from vz-gcc at zeitlins dot org 2010-03-17 20:05 ---
Sorry for a late follow up but I've just discovered that this change broke
compilation of code using wxWidgets library with -pedantic-errors -std=c++98
switches because wxWidgets uses constructions such as (simplified):
--- Comment #7 from tromey at gcc dot gnu dot org 2008-07-12 17:06 ---
Fixed on trunk.
--
tromey at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #5 from aph at gcc dot gnu dot org 2008-07-03 10:14 ---
Subject: Bug 33305
Author: aph
Date: Thu Jul 3 10:13:48 2008
New Revision: 137411
URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=137411
Log:
2008-07-03 Andrew Haley [EMAIL PROTECTED]
PR
--- Comment #6 from aph at gcc dot gnu dot org 2008-07-03 10:32 ---
Subject: Bug 33305
Author: aph
Date: Thu Jul 3 10:31:50 2008
New Revision: 137414
URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=137414
Log:
2008-06-13 Andrew Haley [EMAIL PROTECTED]
PR
--- Comment #4 from manu at gcc dot gnu dot org 2007-11-09 02:09 ---
(In reply to comment #3)
Anyone know where in the preprocessor this should be done? I.e. which
function
in libcpp?
If someone would let me know, I'll write a patch.
This is the patch I was playing with
--- Comment #1 from manu at gcc dot gnu dot org 2007-09-05 09:24 ---
There was talking about creating a -Wundefined flag that warns about undefined
behaviour (PR30334). Would this fit in there? (-pedantic is not supposed to
warn about undefined constructions as far as I know).
--
On 5 Sep 2007 09:24:09 -, manu at gcc dot gnu dot org
[EMAIL PROTECTED] wrote:
There was talking about creating a -Wundefined flag that warns about undefined
behaviour (PR30334). Would this fit in there? (-pedantic is not supposed to
warn about undefined constructions as far as I know).
--- Comment #2 from pinskia at gcc dot gnu dot org 2007-09-05 09:29 ---
Subject: Re: We should warn about empty macro arguments
On 5 Sep 2007 09:24:09 -, manu at gcc dot gnu dot org
[EMAIL PROTECTED] wrote:
There was talking about creating a -Wundefined flag that warns about
--- Comment #3 from ghazi at gcc dot gnu dot org 2007-09-05 17:29 ---
Anyone know where in the preprocessor this should be done? I.e. which function
in libcpp?
If someone would let me know, I'll write a patch.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33305
