This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/60853] [OOP] Failure to disambiguate generic with unlimited polymorphic
- 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: Tue, 15 Nov 2016 13:41:40 +0000
- Subject: [Bug fortran/60853] [OOP] Failure to disambiguate generic with unlimited polymorphic
- Auto-submitted: auto-generated
- References: <bug-60853-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60853
janus at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pault at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |janus at gcc dot gnu.org
--- Comment #4 from janus at gcc dot gnu.org ---
(In reply to janus from comment #3)
> Regtesting now ...
I'm surprised to see that this removal does not cause any regressions.
Those lines in gfc_compare_interfaces come from r194622, which apparently was
Paul's very first commit to support unlimited polymorphism (back in 2012). I
guess the interface checks in compare_type/compare_rank have been refined since
then, so that this crutch is not needed any more (in particular since it's
wrong ;)
Paul, do you agree that the patch in comment 3 is ok to commit?