This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/50919] [OOP] Don't use vtable for NON_OVERRIDABLE TBP
- From: "janus at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 31 Oct 2011 12:31:03 +0000
- Subject: [Bug fortran/50919] [OOP] Don't use vtable for NON_OVERRIDABLE TBP
- Auto-submitted: auto-generated
- References: <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?