public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/47316] devirtualize calls to virtual methods that are never further overriden
Date: Mon, 17 Jan 2011 12:35:00 -0000	[thread overview]
Message-ID: <bug-47316-4-JdO7dUHxET@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47316-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-01-17 12:02:02 UTC ---
(In reply to comment #1)
> Actually better solution would be function and type attributes, hinting the
> function is never overriden.

C++0x has override control features:

struct B {
  virtual void f() const final;
};

As I've commented on several PRs, any work in this area should be done in line
with C++0x, not with GNU-specific attributes


  parent reply	other threads:[~2011-01-17 12:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-16 15:26 [Bug tree-optimization/47316] New: " zsojka at seznam dot cz
2011-01-17  8:02 ` [Bug tree-optimization/47316] " zsojka at seznam dot cz
2011-01-17 12:35 ` redi at gcc dot gnu.org [this message]
2011-01-17 12:39 ` jamborm at gcc dot gnu.org
2013-12-17 16:22 ` hubicka at gcc dot gnu.org
2013-12-17 16:25 ` hubicka 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=bug-47316-4-JdO7dUHxET@http.gcc.gnu.org/bugzilla/ \
    --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).