From: Paul Richard Thomas <paul.richard.thomas@gmail.com>
To: Steve Kargl <sgk@troutmask.apl.washington.edu>
Cc: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>,
Damian Rouson <damian@sourceryinstitute.org>
Subject: Re: [Patch, fortran] PR68196 [4.9/5/6 Regression] ICE on function result with procedure pointer component
Date: Tue, 24 Nov 2015 20:47:00 -0000 [thread overview]
Message-ID: <CAGkQGi+LW1xEa3Q6Zfh6daSF0LUJJDyBXv8fKpRiEqi_T+2ZLg@mail.gmail.com> (raw)
In-Reply-To: <20151107155754.GA52836@troutmask.apl.washington.edu>
Committed to 5 branch as R230839.
Will deal with 4.9 branch next.
Paul
On 7 November 2015 at 16:57, Steve Kargl
<sgk@troutmask.apl.washington.edu> wrote:
> On Wed, Nov 04, 2015 at 04:03:10PM +0100, Paul Richard Thomas wrote:
>>
>> 2015-11-04 Paul Thomas <pault@gcc.gnu.org>
>>
>> PR fortran/68196
>> * class.c (has_finalizer_component): Prevent infinite recursion
>> through this function if the derived type and that of its
>> component are the same.
>> * trans-types.c (gfc_get_derived_type): Do the same for proc
>> pointers by ignoring the explicit interface for the component.
>>
>> PR fortran/66465
>> * check.c (same_type_check): If either of the expressions is
>> BT_PROCEDURE, use the typespec from the symbol, rather than the
>> expression.
>>
>> 2015-11-04 Paul Thomas <pault@gcc.gnu.org>
>>
>> PR fortran/68196
>> * gfortran.dg/proc_ptr_47.f90: New test.
>>
>> PR fortran/66465
>> * gfortran.dg/pr66465.f90: New test.
>
> OK. Thanks for the patch.
>
> --
> steve
--
Outside of a dog, a book is a man's best friend. Inside of a dog it's
too dark to read.
Groucho Marx
prev parent reply other threads:[~2015-11-24 20:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 15:03 Paul Richard Thomas
2015-11-07 15:57 ` Steve Kargl
2015-11-08 16:49 ` Paul Richard Thomas
2015-11-24 20:47 ` Paul Richard Thomas [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=CAGkQGi+LW1xEa3Q6Zfh6daSF0LUJJDyBXv8fKpRiEqi_T+2ZLg@mail.gmail.com \
--to=paul.richard.thomas@gmail.com \
--cc=damian@sourceryinstitute.org \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=sgk@troutmask.apl.washington.edu \
/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).