From: Tobias Burnus <tobias@codesourcery.com>
To: Paul Richard Thomas <paul.richard.thomas@gmail.com>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Cc: Gilles Gouaillardet <gilles@rist.or.jp>
Subject: Re: [Patch, fortran] PR91926 - assumed rank optional
Date: Fri, 25 Oct 2019 07:29:00 -0000 [thread overview]
Message-ID: <16be6080-6c29-46fe-c5e5-70cac5ad4d9a@codesourcery.com> (raw)
In-Reply-To: <CAGkQGiK0a6Yw2KA_sQdiY1yvyFwAVxxt1bS_=x9WwTmDwdBnqw@mail.gmail.com>
On 10/21/19 7:28 PM, Paul Richard Thomas wrote:
> Please find attached a patch to keep 9-branch up to speed with trunk
> as far as the ISO_Fortran_binding feature is concerned.
>
> It bootstraps and regtests on 9-branch and incorporates the correction
> for PR92027, which caused problems for trunk on certain platforms.
>
> OK to commit?
OK. Thanks for the patch.
Tobias
> 2019-10-21 Paul Thomas<pault@gcc.gnu.org>
>
> Backport from trunk
> PR fortran/91926
> * trans-expr.c (gfc_conv_gfc_desc_to_cfi_desc): Correct the
> assignment of the attribute field to account correctly for an
> assumed shape dummy. Assign separately to the gfc and cfi
> descriptors since the atribute can be different. Add branch to
> correctly handle missing optional dummies.
>
> 2019-10-21 Paul Thomas<pault@gcc.gnu.org>
>
> Backport from trunk
> PR fortran/91926
> * gfortran.dg/ISO_Fortran_binding_13.f90 : New test.
> * gfortran.dg/ISO_Fortran_binding_13.c : Additional source.
> * gfortran.dg/ISO_Fortran_binding_14.f90 : New test.
prev parent reply other threads:[~2019-10-25 7:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-05 18:31 Paul Richard Thomas
2019-10-09 10:18 ` Christophe Lyon
2019-10-09 11:35 ` Paul Richard Thomas
2019-10-17 13:56 ` Tobias Burnus
2019-10-19 18:10 ` Paul Richard Thomas
2019-10-21 17:59 ` Paul Richard Thomas
2019-10-25 7:29 ` Tobias Burnus [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=16be6080-6c29-46fe-c5e5-70cac5ad4d9a@codesourcery.com \
--to=tobias@codesourcery.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gilles@rist.or.jp \
--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).