This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: c++/7755: Please make -Wno-deprecated do just that
- From: bangerth at dealii dot org
- To: gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, hpa at zytor dot com, nobody at gcc dot gnu dot org
- Date: 8 Jan 2003 19:53:43 -0000
- Subject: Re: c++/7755: Please make -Wno-deprecated do just that
- Reply-to: bangerth at dealii dot org, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, hpa at zytor dot com, nobody at gcc dot gnu dot org, gcc-gnats at gcc dot gnu dot org
Synopsis: Please make -Wno-deprecated do just that
State-Changed-From-To: feedback->open
State-Changed-By: bangerth
State-Changed-When: Wed Jan 8 11:53:38 2003
State-Changed-Why:
The documentation says that -Wno-deprecated is C++ only.
Starting with 3.3, the C front end does indeed reject this
flag, so I guess it erroneously just accepted it, but did
nothing.
Compiling the code with the C++ front end yields errors
with 3.2.2 and 3.3, and is accepted with 3.4. I think it
should yield an error with 3.4 as well, since the C++
front end treated __FUNCTION__ differently from the
beginning. I don't know why it does now.
Since -Wno-deprecated is a C++ option, I change the category
of this report. Given the strange behavior above, shall I
also change the synopsis to something like "Incorrect
behavior of __FUNCTION__"?
W.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7755