public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/15269] __attribute__((deprecated)) broken with inline, ignored with pure virtual, misreported after definition
Date: Mon, 03 May 2004 19:20:00 -0000	[thread overview]
Message-ID: <20040503192012.19209.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040503180849.15269.eddy@opera.com>


------- Additional Comments From pinskia at gcc dot gnu dot org  2004-05-03 19:20 -------
For the last example I can confirm it also on the mainline, I think the problem is when creating the 
second decl for the definition.  For the virtual issue is that there is an indirect call to the function's entry 
in the vtable and that entry does not have the attribute on it. 

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |minor


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15269


  parent reply	other threads:[~2004-05-03 19:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-03 18:08 [Bug c++/15269] New: " gcc-bugzilla at gcc dot gnu dot org
2004-05-03 18:39 ` [Bug c++/15269] " bangerth at dealii dot org
2004-05-03 19:08 ` eddy at opera dot com
2004-05-03 19:17 ` bangerth at dealii dot org
2004-05-03 19:20 ` pinskia at gcc dot gnu dot org [this message]
     [not found] <bug-15269-8457@http.gcc.gnu.org/bugzilla/>
2007-09-23  4:33 ` jason at gcc dot gnu dot org
2007-09-23  4:37 ` jason at gcc dot gnu dot org
2007-09-23  4:40 ` jason at gcc dot gnu dot org
2007-09-25 15:54 ` eddy at opera dot com
     [not found] <bug-15269-4@http.gcc.gnu.org/bugzilla/>
2021-08-11 20:25 ` pinskia at gcc dot gnu.org

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=20040503192012.19209.qmail@sources.redhat.com \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).