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/66973] Incorrect resolution of generic interface with TYPE(C_PTR)
Date: Wed, 12 Apr 2023 18:48:23 +0000	[thread overview]
Message-ID: <bug-66973-4-10qXbFF8QB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66973-4@http.gcc.gnu.org/bugzilla/>

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

anlauf at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|2015-07-22 00:00:00         |2023-4-12
                 CC|                            |anlauf at gcc dot gnu.org

--- Comment #7 from anlauf at gcc dot gnu.org ---
This issue still persists at r13-7146 when using separate files for the
module and the main program.

gfortran's behavior is fragile: using e.g.

  USE ISO_C_BINDING, only: C_PTR

in the module makes the code work as desired (needs USE ISO_C_BINDING in the
main).

However, using

  USE ISO_C_BINDING, only: C_PTR, C_LOC

in the module breaks it again.

The behavior also depends on the order of USE statements in the main:

  USE H5T
  USE ISO_C_BINDING

differs from

  USE ISO_C_BINDING
  USE H5T

which should not happen...

  parent reply	other threads:[~2023-04-12 18:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-22 20:07 [Bug fortran/66973] New: " brtnfld at hdfgroup dot org
2015-07-22 20:08 ` [Bug fortran/66973] " brtnfld at hdfgroup dot org
2015-07-22 20:11 ` brtnfld at hdfgroup dot org
2015-07-22 20:15 ` brtnfld at hdfgroup dot org
2015-07-22 20:30 ` brtnfld at hdfgroup dot org
2015-07-22 21:37 ` dominiq at lps dot ens.fr
2015-07-22 21:55 ` brtnfld at hdfgroup dot org
2023-04-12 18:48 ` anlauf at gcc dot gnu.org [this message]
2023-04-12 19:42 ` anlauf 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-66973-4-10qXbFF8QB@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).