public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/66409] Reporting ambiguous interface when overloading assignment with polymorphic array
Date: Fri, 07 Oct 2022 20:10:26 +0000	[thread overview]
Message-ID: <bug-66409-4-YY1wZfgkSg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66409-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66409

--- Comment #6 from anlauf at gcc dot gnu.org ---
(In reply to Steve Kargl from comment #5)
> Both match type "integer", kind "4", rank "0".
> 
> AFAIK, there is no other consideration than TKR to discern which function
> to call.

Yes, assuming that there is no prioritization (as for non-elemental vs.
elemental).

> Perhaps, someone, who cares about this bug, can point at the language in
> the Fortran standard.

I looked again at F2018 and couldn't find anything.

BTW: Crayftn 13.0.1 says:

module f
       ^ 
ftn-855 crayftn: ERROR F, File = pr66409.f90, Line = 1, Column = 8 
  The compiler has detected errors in module "F".  No module information file
will be created for this module.

     module procedure test_f08ts
                      ^          
ftn-487 crayftn: ERROR F, File = pr66409.f90, Line = 6, Column = 23 
  The specific interfaces for "TEST_F08TS" and "TEST_F08" make the GENERIC
interface "TEST" ambiguous.

  parent reply	other threads:[~2022-10-07 20:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-03 20:06 [Bug fortran/66409] New: " cmacmackin at gmail dot com
2015-09-13 15:14 ` [Bug fortran/66409] " dominiq at lps dot ens.fr
2022-10-07 13:55 ` jeff.science at gmail dot com
2022-10-07 18:30 ` kargl at gcc dot gnu.org
2022-10-07 19:15 ` anlauf at gcc dot gnu.org
2022-10-07 19:54 ` sgk at troutmask dot apl.washington.edu
2022-10-07 20:10 ` anlauf at gcc dot gnu.org [this message]
2022-10-07 20:42 ` mikael at gcc dot gnu.org
2022-10-07 21:02 ` sgk at troutmask dot apl.washington.edu
2022-10-07 21:08 ` mikael at gcc dot gnu.org
2022-10-07 21:12 ` anlauf at gcc dot gnu.org
2022-10-08  6:53 ` jeff.science at gmail dot com
2022-10-08 16:02 ` kargl at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-66409-4-YY1wZfgkSg@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).