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/111837] [11/12/13/14 Regression] Out of bounds access with optimization inside io-implied-do-control
Date: Sat, 21 Oct 2023 20:06:28 +0000 [thread overview]
Message-ID: <bug-111837-4-y9e4oplmnx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111837-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111837
--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by Harald Anlauf
<anlauf@gcc.gnu.org>:
https://gcc.gnu.org/g:4d4d191e03d102d5afeb4b091e947560351004c3
commit r12-9934-g4d4d191e03d102d5afeb4b091e947560351004c3
Author: Harald Anlauf <anlauf@gmx.de>
Date: Mon Oct 16 21:02:20 2023 +0200
Fortran: out of bounds access with nested implied-do IO [PR111837]
gcc/fortran/ChangeLog:
PR fortran/111837
* frontend-passes.cc (traverse_io_block): Dependency check of loop
nest shall be triangular, not banded.
gcc/testsuite/ChangeLog:
PR fortran/111837
* gfortran.dg/implied_do_io_8.f90: New test.
(cherry picked from commit 5ac63ec5da2e93226457bea4dbb3a4f78d5d82c2)
next prev parent reply other threads:[~2023-10-21 20:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 15:12 [Bug fortran/111837] New: [8,9,10,11,12,13 " vladimir.fuka at gmail dot com
2023-10-16 16:57 ` [Bug fortran/111837] [8/9/10/11/12/13/14 " anlauf at gcc dot gnu.org
2023-10-16 18:03 ` anlauf at gcc dot gnu.org
2023-10-16 19:12 ` anlauf at gcc dot gnu.org
2023-10-17 17:06 ` [Bug fortran/111837] [11/12/13/14 " cvs-commit at gcc dot gnu.org
2023-10-21 19:51 ` cvs-commit at gcc dot gnu.org
2023-10-21 20:06 ` cvs-commit at gcc dot gnu.org [this message]
2023-10-21 20:22 ` cvs-commit at gcc dot gnu.org
2023-10-21 20:23 ` anlauf at gcc dot gnu.org
2023-12-24 22:23 ` pinskia 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-111837-4-y9e4oplmnx@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).