public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/50919] [OOP] Don't use vtable for NON_OVERRIDABLE TBP Date: Mon, 31 Oct 2011 12:31:00 -0000 [thread overview] Message-ID: <bug-50919-4-TlnkAcosaH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50919-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50919 janus at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED AssignedTo|unassigned at gcc dot |janus at gcc dot gnu.org |gnu.org | --- Comment #2 from janus at gcc dot gnu.org 2011-10-31 12:31:03 UTC --- Created attachment 25672 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=25672 patch Here is a patch, which does two things: 1) The resolve.c part prevents the conversion to a PPC call (for functions and subroutines). 2) The class.c parts prevents adding the non-overridable TBP to the vtable. The second one breaks the ABI, while the first one does not. So, should I start by committing the first part only, and waiting with the second one for the ABI cleanup?
next prev parent reply other threads:[~2011-10-31 12:31 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-30 10:09 [Bug fortran/50919] New: " burnus at gcc dot gnu.org 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 [this message] 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-TlnkAcosaH@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).