public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/95342] [9/10/11 Regression] ICE in gfc_match_subroutine, at fortran/decl.c:7913
Date: Thu, 26 Nov 2020 21:27:57 +0000	[thread overview]
Message-ID: <bug-95342-4-FeZFHOn7QL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95342-4@http.gcc.gnu.org/bugzilla/>

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

anlauf at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
                 CC|                            |anlauf at gcc dot gnu.org
      Known to fail|                            |10.2.1, 11.0, 9.3.1
           Assignee|unassigned at gcc dot gnu.org      |anlauf at gcc dot gnu.org
      Known to work|                            |7.4.1, 8.4.1

--- Comment #4 from anlauf at gcc dot gnu.org ---
Patch: https://gcc.gnu.org/pipermail/fortran/2020-November/055356.html

  parent reply	other threads:[~2020-11-26 21:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26 16:45 [Bug fortran/95342] New: " gscfq@t-online.de
2020-05-26 16:46 ` [Bug fortran/95342] " gscfq@t-online.de
2020-05-26 18:16 ` kargl at gcc dot gnu.org
2020-05-26 18:29 ` kargl at gcc dot gnu.org
2020-05-27  7:38 ` rguenth at gcc dot gnu.org
2020-06-09 10:54 ` dominiq at lps dot ens.fr
2020-11-26 21:27 ` anlauf at gcc dot gnu.org [this message]
2020-12-03 19:33 ` cvs-commit at gcc dot gnu.org
2020-12-04 22:18 ` cvs-commit at gcc dot gnu.org
2020-12-04 22:31 ` cvs-commit at gcc dot gnu.org
2020-12-04 22:33 ` anlauf 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-95342-4-FeZFHOn7QL@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).