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/103607] [9/10/11/12 Regression] ICE in do_subscript, at fortran/frontend-passes.c:2927
Date: Fri, 10 Dec 2021 18:27:20 +0000	[thread overview]
Message-ID: <bug-103607-4-dl0KDp0LgA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103607-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:45cbfabe01878c3efd8b24f3fef06baf48983308

commit r10-10330-g45cbfabe01878c3efd8b24f3fef06baf48983308
Author: Harald Anlauf <anlauf@gmx.de>
Date:   Tue Dec 7 21:34:31 2021 +0100

    Fortran: perform array subscript checks only for valid INTEGER bounds

    gcc/fortran/ChangeLog:

            PR fortran/103607
            * frontend-passes.c (do_subscript): Ensure that array bounds are
            of type INTEGER before performing checks on array subscripts.

    gcc/testsuite/ChangeLog:

            PR fortran/103607
            * gfortran.dg/pr103607.f90: New test.

    (cherry picked from commit 9eec77c0df9e5c67454a2e8f83246104458ba4f0)

  parent reply	other threads:[~2021-12-10 18:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-07 19:41 [Bug fortran/103607] New: " gscfq@t-online.de
2021-12-07 20:47 ` [Bug fortran/103607] " anlauf at gcc dot gnu.org
2021-12-07 22:18 ` cvs-commit at gcc dot gnu.org
2021-12-08  7:51 ` pinskia at gcc dot gnu.org
2021-12-08  9:04 ` marxin at gcc dot gnu.org
2021-12-08 19:18 ` cvs-commit at gcc dot gnu.org
2021-12-10 18:27 ` cvs-commit at gcc dot gnu.org [this message]
2021-12-10 18:32 ` cvs-commit at gcc dot gnu.org
2021-12-10 20:20 ` 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-103607-4-dl0KDp0LgA@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).