This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/46244] gfc_compare_derived_types is buggy
- From: "paul.richard.thomas at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 21 Feb 2011 08:26:08 +0000
- Subject: [Bug fortran/46244] gfc_compare_derived_types is buggy
- Auto-submitted: auto-generated
- References: <bug-46244-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46244
--- Comment #16 from paul.richard.thomas at gmail dot com <paul.richard.thomas at gmail dot com> 2011-02-21 08:25:51 UTC ---
Dear Mikael,
....snip....
> Actually none of the gfc_compare_type/gfc_TK_compatible changes are absolutely
> necessary to fix this bug. It is just I found it odd that gfc_compare_type was
> calling gfc_type_compatible (compatible types are not necessary
> equal/equivalent), so I changed it so that gfc_type_compatible calls
> gfc_compare_type instead. And then the new gfc_TK_compatible function to not
> upset the testsuite.
>
> Maybe I just don't understand what "compare types" means. :-(
....snip....
> Hem, yes, who wrote this? ( I hope it's not me ;-) ).
There have been a number of contributors over the years. Therein lies
the problem. Quick fix has been piled on quick fix and the result is
something of a mess.
"It is just I found it odd that gfc_compare_type was calling
gfc_type_compatible (compatible types are not necessary
equal/equivalent), so I changed it so that gfc_type_compatible calls
gfc_compare_type instead."
That was indeed very peculiar. I know who the culprit was but I am
not telling :-)
If you have time to put this right I, for one, would be very pleased.
A
Paul