From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: Harald Anlauf via Fortran <fortran@gcc.gnu.org>
Cc: rep.dot.nop@gmail.com, Harald Anlauf <anlauf@gmx.de>,
Paul Richard Thomas <paul.richard.thomas@gmail.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch, fortran] PRs 105152, 100193, 87946, 103389, 104429 and 82774
Date: Mon, 24 Apr 2023 18:41:45 +0200 [thread overview]
Message-ID: <20230424184145.40e187ca@nbbrfq> (raw)
In-Reply-To: <27ee85f7-f52b-9b41-377a-9d025ddadbee@gmx.de>
On Sun, 23 Apr 2023 23:48:03 +0200
Harald Anlauf via Fortran <fortran@gcc.gnu.org> wrote:
> Am 22.04.23 um 10:32 schrieb Paul Richard Thomas via Gcc-patches:
> > PR103931 - I couldn't reproduce the bug, which involves 'ambiguous c_ptr'.
> > To judge by the comments, it seems that this bug is a bit elusive.
See Haralds comment 12, you need to remove the use cmodule:
module DModule
use AModule
!comment 12, 'use CModule' should not be needed: use CModule
!use CModule
implicit none
private
public :: DType
type, abstract :: DType
end type
end module
> PR103931: it is indeed a bit elusive, but very sensitive to code
> changes. Also Bernhard had a look at it. Given that there are
> a couple of bugs related to module reading, and rename-on-use,
> I'd recommend to leave that open for further analysis.
I would mark the dt sym that is used *as* the generic interface with
attr.generic.
Like: https://gcc.gnu.org/PR103931#c18
This seems to work and sounds somewhat plausible (to me).
If that is not correct, then i'm running out of ideas and will stop
looking at that PR.
cheers,
prev parent reply other threads:[~2023-04-24 16:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-22 8:32 Paul Richard Thomas
2023-04-23 21:48 ` Harald Anlauf
2023-04-23 21:48 ` Harald Anlauf
2023-04-24 16:41 ` Bernhard Reutner-Fischer [this message]
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=20230424184145.40e187ca@nbbrfq \
--to=rep.dot.nop@gmail.com \
--cc=anlauf@gmx.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=paul.richard.thomas@gmail.com \
/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).