From: Mikael Morin <morin-mikael@orange.fr>
To: Tobias Burnus <tobias@codesourcery.com>,
Paul Richard Thomas <paul.richard.thomas@gmail.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>, fortran <fortran@gcc.gnu.org>
Subject: Re: [Patch, fortran] PR108961 - Segfault when associating to pointer from C_F_POINTER
Date: Tue, 20 Jun 2023 22:47:05 +0200 [thread overview]
Message-ID: <55395a67-3f4c-0163-866b-a13e7be4d235@orange.fr> (raw)
In-Reply-To: <b4fa68c0-5471-8159-bcbe-33c67e554f26@codesourcery.com>
Le 20/06/2023 à 18:30, Tobias Burnus a écrit :
> On 20.06.23 18:19, Paul Richard Thomas via Fortran wrote:
>
>> Is there a better way to detect a type(c_ptr) formal argument?
> u.derived->intmod_sym_id == ISOCBINDING_PTR ?
&& u.derived->from_intmod == INTMOD_ISO_C_BINDING ?
next prev parent reply other threads:[~2023-06-20 20:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 16:19 Paul Richard Thomas
2023-06-20 16:30 ` Tobias Burnus
2023-06-20 20:47 ` Mikael Morin [this message]
2023-06-21 16:08 ` Paul Richard Thomas
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=55395a67-3f4c-0163-866b-a13e7be4d235@orange.fr \
--to=morin-mikael@orange.fr \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=paul.richard.thomas@gmail.com \
--cc=tobias@codesourcery.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).