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/82314] internal compiler error: in gfc_conv_expr_descriptor, at fortran/trans-array.c:6972
Date: Thu, 16 Sep 2021 18:18:34 +0000 [thread overview]
Message-ID: <bug-82314-4-N6fvskGpYZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-82314-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82314
--- Comment #11 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:58c76fb477b51adeb9241de0b175a817e9c73b8a
commit r11-9008-g58c76fb477b51adeb9241de0b175a817e9c73b8a
Author: Harald Anlauf <anlauf@gmx.de>
Date: Mon Sep 13 19:28:10 2021 +0200
Fortran - ensure simplification of bounds of array-valued named constants
gcc/fortran/ChangeLog:
PR fortran/82314
* decl.c (add_init_expr_to_sym): For proper initialization of
array-valued named constants the array bounds need to be
simplified before adding the initializer.
gcc/testsuite/ChangeLog:
PR fortran/82314
* gfortran.dg/pr82314.f90: New test.
(cherry picked from commit 104c05c5284b7822d770ee51a7d91946c7e56d50)
next prev parent reply other threads:[~2021-09-16 18:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-82314-4@http.gcc.gnu.org/bugzilla/>
2020-06-03 15:41 ` gscfq@t-online.de
2020-06-30 20:26 ` anlauf at gcc dot gnu.org
2020-11-12 20:05 ` anlauf at gcc dot gnu.org
2021-09-07 20:32 ` anlauf at gcc dot gnu.org
2021-09-07 21:45 ` anlauf at gcc dot gnu.org
2021-09-13 17:28 ` cvs-commit at gcc dot gnu.org
2021-09-16 18:18 ` cvs-commit at gcc dot gnu.org [this message]
2021-09-30 19:04 ` cvs-commit at gcc dot gnu.org
2021-09-30 19:08 ` cvs-commit at gcc dot gnu.org
2021-09-30 19:09 ` 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-82314-4-N6fvskGpYZ@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).