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/101327] ICE in find_array_element, at fortran/expr.c:1355
Date: Sat, 11 Sep 2021 19:01:41 +0000	[thread overview]
Message-ID: <bug-101327-4-d6wOCkPZpa@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101327-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Harald Anlauf
<anlauf@gcc.gnu.org>:

https://gcc.gnu.org/g:0d09acc0d627dcc7b3d82d873ee9da2f7546414e

commit r11-8979-g0d09acc0d627dcc7b3d82d873ee9da2f7546414e
Author: Harald Anlauf <anlauf@gmx.de>
Date:   Tue Sep 7 20:51:49 2021 +0200

    Fortran - improve error recovery determining array element from constructor

    gcc/fortran/ChangeLog:

            PR fortran/101327
            * expr.c (find_array_element): When bounds cannot be determined as
            constant, return error instead of aborting.

    gcc/testsuite/ChangeLog:

            PR fortran/101327
            * gfortran.dg/pr101327.f90: New test.

    (cherry picked from commit 2a1537a19cb2fa85823cfa18ed40baa4b259b4e3)

  parent reply	other threads:[~2021-09-11 19:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-05 16:38 [Bug fortran/101327] New: " gscfq@t-online.de
2021-07-06 17:50 ` [Bug fortran/101327] " kargl at gcc dot gnu.org
2021-08-30 19:35 ` anlauf at gcc dot gnu.org
2021-08-30 20:02 ` sgk at troutmask dot apl.washington.edu
2021-08-30 20:13 ` anlauf at gcc dot gnu.org
2021-08-30 21:41 ` anlauf at gcc dot gnu.org
2021-09-07 18:52 ` cvs-commit at gcc dot gnu.org
2021-09-11 19:01 ` cvs-commit at gcc dot gnu.org [this message]
2021-09-16 18:33 ` cvs-commit at gcc dot gnu.org
2021-09-30 19:28 ` cvs-commit at gcc dot gnu.org
2021-09-30 19:30 ` 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-101327-4-d6wOCkPZpa@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).