public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85982] ICE in resolve_component, at fortran/resolve.c:13696
Date: Thu, 02 Apr 2020 18:31:10 +0000	[thread overview]
Message-ID: <bug-85982-4-gawzur0R9C@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-85982-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85982

--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Fritz Reese
<foreese@gcc.gnu.org>:

https://gcc.gnu.org/g:f722c80a63cf0283acb7f7008c7a145293275d43

commit r8-10158-gf722c80a63cf0283acb7f7008c7a145293275d43
Author: Fritz Reese <foreese@gcc.gnu.org>
Date:   Thu Apr 2 13:50:11 2020 -0400

    Backport form master: Fix fortran/85982 ICE in resolve_component.

    2020-04-02  Fritz Reese  <foreese@gcc.gnu.org>

            Backport from master.
            2020-04-02  Fritz Reese  <foreese@gcc.gnu.org>

            PR fortran/85982
            * fortran/decl.c (match_attr_spec): Lump COMP_STRUCTURE/COMP_MAP
into
            attribute checking used by TYPE.

    2020-04-02  Fritz Reese  <foreese@gcc.gnu.org>

            Backport from master.
            2020-04-02  Fritz Reese  <foreese@gcc.gnu.org>

            PR fortran/85982
            * gfortran.dg/dec_structure_28.f90: New test.

  parent reply	other threads:[~2020-04-02 18:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-85982-4@http.gcc.gnu.org/bugzilla/>
2020-04-01 17:20 ` foreese at gcc dot gnu.org
2020-04-02 18:14 ` cvs-commit at gcc dot gnu.org
2020-04-02 18:31 ` cvs-commit at gcc dot gnu.org [this message]
2020-04-02 18:37 ` cvs-commit at gcc dot gnu.org
2020-04-02 19:31 ` foreese at gcc dot gnu.org

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=bug-85982-4-gawzur0R9C@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).