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/105184] ICE in gfc_array_init_size, at fortran/trans-array.cc:5841
Date: Sun, 10 Apr 2022 18:28:14 +0000	[thread overview]
Message-ID: <bug-105184-4-reUQX0izPI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105184-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:54c5e064cc3dc3c9b3dff12b6d48dc3efd482b07

commit r12-8073-g54c5e064cc3dc3c9b3dff12b6d48dc3efd482b07
Author: Harald Anlauf <anlauf@gmx.de>
Date:   Wed Apr 6 22:24:21 2022 +0200

    Fortran: fix checking of coshape specification in ALLOCATE statement

    gcc/fortran/ChangeLog:

            PR fortran/105184
            * array.cc (match_subscript): Reject assumed size coarray
            specification with missing lower bound.
            * resolve.cc (resolve_allocate_expr): Fix logic for checking
            allocate-coshape-spec in ALLOCATE statement.

    gcc/testsuite/ChangeLog:

            PR fortran/105184
            * gfortran.dg/coarray_44.f90: Adjust expected output.
            * gfortran.dg/coarray_allocate_11.f90: Likewise.
            * gfortran.dg/coarray_allocate_12.f90: New test.

  parent reply	other threads:[~2022-04-10 18:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06 18:20 [Bug fortran/105184] New: " gscfq@t-online.de
2022-04-06 18:21 ` [Bug fortran/105184] " gscfq@t-online.de
2022-04-06 19:09 ` anlauf at gcc dot gnu.org
2022-04-06 20:03 ` anlauf at gcc dot gnu.org
2022-04-06 20:40 ` anlauf at gcc dot gnu.org
2022-04-10 18:28 ` cvs-commit at gcc dot gnu.org [this message]
2022-04-10 18:34 ` anlauf at gcc dot gnu.org
2022-04-12 17:23 ` gscfq@t-online.de

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-105184-4-reUQX0izPI@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).