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/103505] ICE in compare_bound_mpz_t, at fortran/resolve.c:4587 since r8-7594-g078c5aff5ed83e9c
Date: Sat, 04 Dec 2021 21:31:38 +0000	[thread overview]
Message-ID: <bug-103505-4-4cXCxJiLKT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103505-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #12 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:9e9c674dfc6fae8f967341759699b4d75943d256

commit r11-9355-g9e9c674dfc6fae8f967341759699b4d75943d256
Author: Harald Anlauf <anlauf@gmx.de>
Date:   Thu Dec 2 22:33:49 2021 +0100

    Fortran: improve checking of array specifications

    gcc/fortran/ChangeLog:

            PR fortran/103505
            * array.c (match_array_element_spec): Try to simplify array
            element specifications to improve early checking.
            * expr.c (gfc_try_simplify_expr): New.  Try simplification of an
            expression via gfc_simplify_expr.  When an error occurs, roll
            back.
            * gfortran.h (gfc_try_simplify_expr): Declare it.

    gcc/testsuite/ChangeLog:

            PR fortran/103505
            * gfortran.dg/pr103505.f90: New test.

    Co-authored-by: Steven G. Kargl <kargl@gcc.gnu.org>
    (cherry picked from commit f46d32dd29b7623915e31b0508e2e925526fa7d8)

  parent reply	other threads:[~2021-12-04 21:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-30 18:47 [Bug fortran/103505] New: ICE in compare_bound_mpz_t, at fortran/resolve.c:4587 gscfq@t-online.de
2021-11-30 20:44 ` [Bug fortran/103505] " anlauf at gcc dot gnu.org
2021-11-30 20:48 ` kargl at gcc dot gnu.org
2021-12-01  9:25 ` [Bug fortran/103505] ICE in compare_bound_mpz_t, at fortran/resolve.c:4587 since r8-7594-g078c5aff5ed83e9c marxin at gcc dot gnu.org
2021-12-01 20:26 ` anlauf at gcc dot gnu.org
2021-12-01 21:00 ` sgk at troutmask dot apl.washington.edu
2021-12-01 21:42 ` anlauf at gcc dot gnu.org
2021-12-01 22:29 ` sgk at troutmask dot apl.washington.edu
2021-12-02 21:51 ` anlauf at gcc dot gnu.org
2021-12-03 20:08 ` cvs-commit at gcc dot gnu.org
2021-12-03 20:26 ` sgk at troutmask dot apl.washington.edu
2021-12-03 21:24 ` anlauf at gcc dot gnu.org
2021-12-04 21:31 ` cvs-commit at gcc dot gnu.org [this message]
2021-12-19 20:29 ` cvs-commit at gcc dot gnu.org
2021-12-19 21:00 ` [Bug fortran/103505] [9 Regression] " anlauf at gcc dot gnu.org
2022-01-17  9:01 ` rguenth at gcc dot gnu.org
2022-05-27  9:51 ` rguenth 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-103505-4-4cXCxJiLKT@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).