This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/54594] [OOP] Type-bound ASSIGNMENTs (elemental + array version) rejected as ambiguous
- From: "burnus at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sun, 16 Sep 2012 21:25:18 +0000
- Subject: [Bug fortran/54594] [OOP] Type-bound ASSIGNMENTs (elemental + array version) rejected as ambiguous
- Auto-submitted: auto-generated
- References: <bug-54594-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54594
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |burnus at gcc dot gnu.org
--- Comment #9 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-09-16 21:25:18 UTC ---
(In reply to comment #8)
> > Is it expected?
(Both the original example and the one of comment 1 do compile and run with
crayftn.)
> That's a good question. I could not find that restriction in the standard on a
> quick check. In any case, the error message comes from
> 'get_checked_tb_operator_target' (resolve.c), which was committed in r150856
That's PR 37425 (you had one digit wrong).
The constraint is (F2008):
C468 (R450) If generic-spec is not generic-name, each of its specific bindings
shall have a passed-object dummy argument (4.5.4.5).
with
R1207 generic-spec is generic-name
or OPERATOR ( dened-operator )
or ASSIGNMENT ( = )
or defined-io-generic-spec