From: Paul Richard Thomas <paul.richard.thomas@gmail.com>
To: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch, fortran] PR49630 - [OOP] ICE on obsolescent deferred-length type bound character function
Date: Thu, 21 Jun 2018 15:23:00 -0000 [thread overview]
Message-ID: <CAGkQGiJaeiXJ1du2dTKeKpmh5szyFKZndLraMGf0nJf_-ufP1w@mail.gmail.com> (raw)
In-Reply-To: <CAGkQGi+6NqYydemVd=zaP-T=dtmf322L_FwyzdDg0fik8Ua8sQ@mail.gmail.com>
Ping!
On 19 June 2018 at 10:16, Paul Richard Thomas
<paul.richard.thomas@gmail.com> wrote:
> I got caught with a wild goose chase with this one. I tried to get it
> to work before seeing the standard reference in trans-expr.c. In fact,
> it would be impossible to fix because there is no way to resolve
> different instances of the abstract interface with different character
> lengths.
>
> Bootstrapped and regtested on FC28/x86_64 - OK for trunk.
>
> I do not intend to backport it unless there is any enthusiasm for me to do so.
>
> Regards
>
> Paul
>
> 2018-06-19 Paul Thomas <pault@gcc.gnu.org>
>
> PR fortran/49630
> * resolve.c (resolve_contained_fntype): Change standard ref.
> from F95 to F2003: C418. Correct a spelling error in a comment.
> It is an error for an abstract interface to have an assumed
> character length result.
> * trans-expr.c (gfc_conv_procedure_call): Likewise change the
> standard reference.
>
> 2018-06-19 Paul Thomas <pault@gcc.gnu.org>
>
> PR fortran/49630
> * gfortran.dg/assumed_charlen_function_7.f90: New test.
--
"If you can't explain it simply, you don't understand it well enough"
- Albert Einstein
next prev parent reply other threads:[~2018-06-21 8:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 13:05 Paul Richard Thomas
2018-06-21 15:23 ` Paul Richard Thomas [this message]
2018-06-21 18:45 ` Steve Kargl
2018-06-22 22:54 ` Martin Liška
2018-06-23 16:55 ` Christophe Lyon
2018-06-24 18:29 ` Steve Kargl
2018-06-25 0:35 ` Christophe Lyon
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=CAGkQGiJaeiXJ1du2dTKeKpmh5szyFKZndLraMGf0nJf_-ufP1w@mail.gmail.com \
--to=paul.richard.thomas@gmail.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).