From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Thomas Koenig via Fortran <fortran@gcc.gnu.org>
Cc: Andrew Pinski <apinski@marvell.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Fix fc-prototypes usage with C_INT64_T and non LP64 Targets.
Date: Thu, 30 Mar 2023 12:05:23 -0700 [thread overview]
Message-ID: <ZCXdc51oF/fkeTMR@troutmask.apl.washington.edu> (raw)
In-Reply-To: <f1372109-cca7-b171-972d-a5dd450367e4@netcologne.de>
On Thu, Mar 30, 2023 at 07:39:55PM +0200, Thomas Koenig via Fortran wrote:
> Hi Andrew,
>
> > "long long". This was just an oversight and a missing check.
> >
> > Committed as obvious after a bootstrap/test on x86_64-linux-gnu.
>
> Thanks!
>
> I think this one is obvious enough that it deserves a backport.
> I've cherry-picked this for gcc12, will do gcc11 tomorrow.
>
The patch is incomplete.
module foo
use, intrinsic :: iso_c_binding
implicit none
public :: bar
type, bind(c) :: bar
real(10) a
end type
end module
This yields
typedef struct bar {
long_double a /* WARNING: Converting 'REAL(10)' to interoperable type */;
} bar;
That should be 'long double'.
--
Steve
next prev parent reply other threads:[~2023-03-30 19:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 3:47 Andrew Pinski
2023-03-30 17:39 ` Thomas Koenig
2023-03-30 19:05 ` Steve Kargl [this message]
2023-04-01 8:24 ` Thomas Koenig
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=ZCXdc51oF/fkeTMR@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--cc=apinski@marvell.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@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).