From: Jerry D <jvdelisle2@gmail.com>
To: Harald Anlauf <anlauf@gmx.de>, fortran <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fortran: out of bounds access with nested implied-do IO [PR111837]
Date: Mon, 16 Oct 2023 17:32:36 -0700 [thread overview]
Message-ID: <324f457b-4642-4c47-9fd8-cf9abfe64030@gmail.com> (raw)
In-Reply-To: <trinity-327edd0e-7e3a-45b6-9546-0df8a1315f96-1697483503726@3c-app-gmx-bap45>
On 10/16/23 12:11 PM, Harald Anlauf wrote:
> Dear All,
>
> the attached patch fixes a dependency check in frontend optimzation
> for nested implied-do IO. The problem appeared for >= 3 loops only
> as the check considered dependencies to be only of band form instead
> of triangular form.
>
> Regtested on x86_64-pc-linux-gnu. OK for mainline?
>
> As this fixes a regression since 8-release, I plan to backport
> to all active branches.
>
> Thanks,
> Harald
>
OK for Mainline and backport
Thanks Harald
Jerry
prev parent reply other threads:[~2023-10-17 0:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 19:11 Harald Anlauf
2023-10-17 0:32 ` Jerry D [this message]
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=324f457b-4642-4c47-9fd8-cf9abfe64030@gmail.com \
--to=jvdelisle2@gmail.com \
--cc=anlauf@gmx.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@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).