public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/50919] New: [OOP] Don't use vtable for NON_OVERRIDABLE TBP Date: Sun, 30 Oct 2011 10:09:00 -0000 [thread overview] Message-ID: <bug-50919-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50919 Bug #: 50919 Summary: [OOP] Don't use vtable for NON_OVERRIDABLE TBP Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: burnus@gcc.gnu.org CC: janus@gcc.gnu.org Current, gfortran uses always a vtable for type-bound procedures. However, a vtable only makes sense if the type-bound procedure can be overridden (C++: if it is "virtual"). Expected: a) gfortran call the procedure directly, which allows for inlining and avoids the pointer dereference. b) When the ABI is changed, the procedure is no longer added to the vtable. Hence, it should be added as item to http://gcc.gnu.org/wiki/LibgfortranAbiCleanup Test case. The dump shows the following rather than a simple "test ()": callit (struct __class_m_T & restrict x) { x->_vptr->test (); module m type t contains procedure, nopass, NON_OVERRIDABLE :: test end type t contains subroutine test() print *, "t's test" end subroutine test subroutine callit(x) class(t) :: x call x%test() end subroutine end module m tob@archimedes:/dev/shm> less poly.f90.* tob@archimedes:/dev/shm> cat poly.f90 module m type t contains procedure, nopass, NON_OVERRIDABLE :: test end type t contains subroutine test() print *, "t's test" end subroutine test subroutine callit(x) class(t) :: x call x%test() end subroutine end module m
next reply other threads:[~2011-10-30 10:09 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-30 10:09 burnus at gcc dot gnu.org [this message] 2011-10-31 12:08 ` [Bug fortran/50919] " janus at gcc dot gnu.org 2011-10-31 12:31 ` janus at gcc dot gnu.org 2011-10-31 13:56 ` janus at gcc dot gnu.org 2011-10-31 14:42 ` burnus at gcc dot gnu.org 2011-11-07 18:46 ` janus at gcc dot gnu.org 2011-11-07 19:14 ` janus 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-50919-4@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: linkBe 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).