c++/7755: Please make -Wno-deprecated do just that

[H. Peter Anvin]

The following reply was made to PR c++/7755; it has been noted by GNATS.

From: "H. Peter Anvin" <hpa@zytor.com>
To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
        hpa@zytor.com, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c++/7755: Please make -Wno-deprecated do just that
Date: Wed, 08 Jan 2003 12:38:41 -0800

 bangerth@dealii.org wrote:
 > 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__"?
 >     
 
 If -Wno-deprecated is not the right way to disable this warning, then
 please do provide another flag to do so.  Not being able to selectively
 squelsh this warning is a total showstopper for being able to use newer
 gcc's for several projects.
 
 Thanks,
 
 	-hpa