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/98490] Unexpected out of bounds in array constructor with implied do loop
Date: Sat, 11 Sep 2021 19:03:57 +0000 [thread overview]
Message-ID: <bug-98490-4-9CVhboufV9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98490-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98490
--- Comment #13 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:7ca5bcb0f12380a399c6f88f82fa01b530eb85e5
commit r11-8980-g7ca5bcb0f12380a399c6f88f82fa01b530eb85e5
Author: Harald Anlauf <anlauf@gmx.de>
Date: Thu Sep 9 21:34:01 2021 +0200
Fortran - out of bounds in array constructor with implied do loop
gcc/fortran/ChangeLog:
PR fortran/98490
* trans-expr.c (gfc_conv_substring): Do not generate substring
bounds check for implied do loop index variable before it actually
becomes defined.
gcc/testsuite/ChangeLog:
PR fortran/98490
* gfortran.dg/bounds_check_23.f90: New test.
(cherry picked from commit 5fe0865ab788bdc387b284a3ad57e5a95a767b18)
next prev parent reply other threads:[~2021-09-11 19:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-31 18:42 [Bug fortran/98490] New: " ffadrique at gmail dot com
2020-12-31 18:53 ` [Bug fortran/98490] " dominiq at lps dot ens.fr
2020-12-31 19:11 ` ffadrique at gmail dot com
2020-12-31 19:48 ` kargl at gcc dot gnu.org
2020-12-31 19:49 ` kargl at gcc dot gnu.org
2021-01-02 4:08 ` jvdelisle at charter dot net
2021-01-02 4:12 ` jvdelisle at charter dot net
2021-01-02 4:24 ` sgk at troutmask dot apl.washington.edu
2021-01-02 21:03 ` sgk at troutmask dot apl.washington.edu
2021-01-25 13:40 ` pault at gcc dot gnu.org
2021-09-08 20:36 ` anlauf at gcc dot gnu.org
2021-09-08 20:43 ` kargl at gcc dot gnu.org
2021-09-09 19:34 ` cvs-commit at gcc dot gnu.org
2021-09-09 19:40 ` anlauf at gcc dot gnu.org
2021-09-11 19:03 ` cvs-commit at gcc dot gnu.org [this message]
2021-09-16 18:30 ` cvs-commit at gcc dot gnu.org
2021-09-30 19:12 ` cvs-commit at gcc dot gnu.org
2021-09-30 19:13 ` anlauf at gcc dot gnu.org
2021-11-02 18:33 ` anlauf at gcc dot gnu.org
2022-03-18 19:48 ` 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-98490-4-9CVhboufV9@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).