public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
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] PR83021 - [7/8 Regression] gfortran segfault in polymorphic assignment
Date: Wed, 29 Nov 2017 10:09:00 -0000	[thread overview]
Message-ID: <CAGkQGiKx1+LFHscyzMqWJk87r-xt+1A-=Wvw4vuKtd0PTKvaHg@mail.gmail.com> (raw)
In-Reply-To: <CAGkQGi+94X_6s8=KRQMpi8wRbxqyxD0cRxr4Zm_cy6gAWVDJdA@mail.gmail.com>

Committed to 7-branch and trunk and r255205 and r255202 respectively.

Paul


On 26 November 2017 at 18:40, Paul Richard Thomas
<paul.richard.thomas@gmail.com> wrote:
> Dear All,
>
> This regression was caused by the patch for PR81447. The chunk that
> has been modified came about because use association of derived types
> in block data, in the presence of a vtable, was trying to add vtable
> procedures, which is not allowed. The original patch did not
> explicitly target block data and this is fixed here. I decided that a
> testcase was not necessary but this could be done if desired.
>
> Bootstrapped and regtested on FC23/x86_64 - OK for both branches?
>
> I will commit tomorrow morning if there are no complaints.
>
> Best regards
>
> Paul
>
> 2017-11-26  Paul Thomas  <pault@gcc.gnu.org>
>
>     PR fortran/83021
>     * resolve.c (resolve_component): Only escape for use assciated
>     vtypes if the current namespace has no proc_name and is most
>     particularly block data.



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

      reply	other threads:[~2017-11-29 10:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-26 21:57 Paul Richard Thomas
2017-11-29 10:09 ` 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='CAGkQGiKx1+LFHscyzMqWJk87r-xt+1A-=Wvw4vuKtd0PTKvaHg@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).