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: improve bounds checking for DATA with implied-do [PR35095]
Date: Thu, 24 Aug 2023 17:45:44 -0700 [thread overview]
Message-ID: <de6cdf18-8c78-e715-c8b4-7b0bf52195f5@gmail.com> (raw)
In-Reply-To: <trinity-805c458b-39ea-45ab-bc59-6331fd8b952e-1692912489967@3c-app-gmx-bap48>
On 8/24/23 2:28 PM, Harald Anlauf via Fortran wrote:
> Dear all,
>
> the attached patch adds stricter bounds-checking for DATA statements
> with implied-do. I chose to allow overindexing (for arrays of rank
> greater than 1) for -std=legacy, as there might be codes in the wild
> that need this (and this is accepted by some other compilers, while
> NAG is strict here). We now get a warning with -std=gnu, and an
> error with -std=fxxxx.
>
> Regtested on x86_64-pc-linux-gnu. OK for mainline?
>
> (The PR is over 15 years old, so no backport intended... ;-)
>
> Thanks,
> Harald
>
Looks good Harold, OK for mainline.
prev parent reply other threads:[~2023-08-25 0:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 21:28 Harald Anlauf
2023-08-25 0:45 ` 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=de6cdf18-8c78-e715-c8b4-7b0bf52195f5@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).