public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paul Richard Thomas <paul.richard.thomas@gmail.com>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
	gcc-patches <gcc-patches@gcc.gnu.org>,
		Damian Rouson <damian@sourceryinstitute.org>,
	Daniel Celis Garza <celisdanieljr@gmail.com>
Subject: Re: [Patch, fortran] A first small step towards CFI descriptor implementation
Date: Tue, 31 Jul 2018 15:13:00 -0000	[thread overview]
Message-ID: <CAGkQGiKuz-28e+JLcyb9T4Cni9eBzaK1dD09Ni5u9J5EukixuQ@mail.gmail.com> (raw)
In-Reply-To: <CAFiYyc1pLYpfOu4ADgZHZUb91fBf6J094KCRYuD=+GSwPMbPkA@mail.gmail.com>

Hi Richard,

Ah yes, you are absolutely right. I will sit on it for a bit and do
the interchange at the descriptor conversion stage for now.

Thanks

Paul
On Tue, 31 Jul 2018 at 15:57, Richard Biener <richard.guenther@gmail.com> wrote:
>
> On Tue, Jul 31, 2018 at 2:07 PM Paul Richard Thomas
> <paul.richard.thomas@gmail.com> wrote:
> >
> > Daniel Celis Garza and Damian Rouson have developed a runtime library
> > and include file for the TS 29113 and F2018 C descriptors.
> > https://github.com/sourceryinstitute/ISO_Fortran_binding
> >
> > The ordering of types is different to the current 'bt' enum in
> > libgfortran.h. This patch interchanges BT_DERIVED and BT_CHARACTER to
> > fix this.
> >
> > Regtests on FC28/x86_64. OK for trunk?
>
> That's an ABI change, correct?
>
> Richard.
>
> > Cheers
> >
> > Paul
> >
> > 2018-07-31  Paul Thomas  <pault@gcc.gnu.org>
> >
> >     * gcc/fortran/libgfortran.h : In bt enum interchange BT_DERIVED
> >     and BT_CHARACTER for CFI descriptor compatibility(TS 29113).



-- 
"If you can't explain it simply, you don't understand it well enough"
- Albert Einstein

  reply	other threads:[~2018-07-31 15:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-31 12:07 Paul Richard Thomas
2018-07-31 14:57 ` Richard Biener
2018-07-31 15:13   ` Paul Richard Thomas [this message]
2018-07-31 17:10 ` Janus Weil
2018-08-02  9:04   ` 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=CAGkQGiKuz-28e+JLcyb9T4Cni9eBzaK1dD09Ni5u9J5EukixuQ@mail.gmail.com \
    --to=paul.richard.thomas@gmail.com \
    --cc=celisdanieljr@gmail.com \
    --cc=damian@sourceryinstitute.org \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=richard.guenther@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).