public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, hpa@zytor.com,
	nobody@gcc.gnu.org
Subject: Re: c++/7755: Please make -Wno-deprecated do just that
Date: Wed, 08 Jan 2003 19:53:00 -0000	[thread overview]
Message-ID: <20030108195343.6513.qmail@sources.redhat.com> (raw)

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


             reply	other threads:[~2003-01-08 19:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-08 19:53 bangerth [this message]
2003-01-08 20:46 H. Peter Anvin
2003-01-08 20:56 Wolfgang Bangerth
2003-01-08 21:16 H. Peter Anvin
2003-01-08 23:06 Joseph S. Myers
2003-01-08 23:46 H. Peter Anvin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030108195343.6513.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=hpa@zytor.com \
    --cc=nobody@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).