Bug 41178 - Ambiguity checks for type-bound and interface operator calls
Summary: Ambiguity checks for type-bound and interface operator calls
Status: RESOLVED INVALID
Alias: None
Product: gcc
Classification: Unclassified
Component: fortran (show other bugs)
Version: unknown
: P3 normal
Target Milestone: ---
Assignee: Daniel Kraft
URL:
Keywords: diagnostic
Depends on:
Blocks: 29670
  Show dependency tree / graph
 
Reported: 2009-08-27 11:49 UTC by Daniel Kraft
Modified: 2019-01-23 16:20 UTC (History)
3 users (show)

See Also:
Host:
Target:
Build:
Known to work:
Known to fail:
Last reconfirmed: 2009-08-27 11:50:14

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Kraft 2009-08-27 11:49:56 UTC 
This is currently marked TODO in interface.c:gfc_expand_expr/gfc_expand_assign.  When looking for a matching interface or type-bound operator, we could always continue looking through all possibilities and see if more than one option is found, in which case we should emit an error (or at least warn about that one of those will be chosen "arbitrarily").
Comment 1 Daniel Kraft 2009-08-27 11:50:14 UTC 
I take this on.
Comment 2 Jürgen Reuter 2018-10-13 12:18:37 UTC 
Do the functions gfc_expand_expr/gfc_expand_assign exist at all anymore? At least not in interface.c, but I think I found them anywhere in gcc/fortran.
Could this PR be deprecated?
Comment 3 Jürgen Reuter 2019-01-23 16:07:19 UTC 
Nothing has been done here for a decade, and the functions mentioned below (gfc_expand_expr and gfc_expand_assign) do not exist any longer in the code.
Comment 4 Dominique d'Humieres 2019-01-23 16:20:49 UTC 
> Nothing has been done here for a decade, and the functions mentioned below
> (gfc_expand_expr and gfc_expand_assign) do not exist any longer in the code.

They don't even appear in the ChangeLogs, closing as INVALID.