From: Janus Weil <janus@gcc.gnu.org>
To: Paul Richard Thomas <paul.richard.thomas@gmail.com>
Cc: gfortran <fortran@gcc.gnu.org>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch, Fortran, F08] PR 49562: [4.6/4.7 Regression] [OOP] assigning value to type-bound function
Date: Sat, 02 Jul 2011 12:21:00 -0000 [thread overview]
Message-ID: <CAKwh3qjPL1b0=brKxoSpz88eQsCCO267JPhKRoOOsc_WgTQT7Q@mail.gmail.com> (raw)
In-Reply-To: <CAGkQGiKkcmwngd7kE-26_FLQ_UkD68aF=-C90WfVa7u-06bPgg@mail.gmail.com>
> OK for trunk and 4.6.
Thanks, Paul.
Committed to trunk as r175779. Will apply to the 4.6 branch in a few days.
Cheers,
Janus
> On Tue, Jun 28, 2011 at 5:40 PM, Janus Weil <janus@gcc.gnu.org> wrote:
>> Hi all,
>>
>> here is a patch for a problem which was originally reported as an
>> ICE-on-invalid regression (assigning to a type-bound function).
>>
>> In the course of fixing it, I noticed that it becomes valid according
>> to F08 if the function is pointer-valued, and modified the patch such
>> that it will accept this variant. I also adapted the original test
>> case to be a run-time test of this F08 feature (in fact it is just a
>> very complicated way of performing an increment from 0 to 1, and would
>> still segfault without the patch).
>>
>> The patch was regtested on x86_64-unknown-linux-gnu. Ok for trunk and 4.6.2?
>>
>> Cheers,
>> Janus
>>
>>
>>
>> 2011-06-28 Janus Weil <janus@gcc.gnu.org>
>>
>> PR fortran/49562
>> * expr.c (gfc_check_vardef_context): Handle type-bound procedures.
>>
>>
>> 2011-06-28 Janus Weil <janus@gcc.gnu.org>
>>
>> PR fortran/49562
>> * gfortran.dg/typebound_proc_23.f90: New.
>>
>
>
>
> --
> The knack of flying is learning how to throw yourself at the ground and miss.
> --Hitchhikers Guide to the Galaxy
>
prev parent reply other threads:[~2011-07-02 12:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-28 15:53 Janus Weil
2011-07-01 14:29 ` Janus Weil
2011-07-02 8:29 ` Paul Richard Thomas
2011-07-02 12:21 ` Janus Weil [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='CAKwh3qjPL1b0=brKxoSpz88eQsCCO267JPhKRoOOsc_WgTQT7Q@mail.gmail.com' \
--to=janus@gcc.gnu.org \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--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).