From: Thomas Koenig <tkoenig@netcologne.de>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: Jerry DeLisle <jvdelisle@charter.net>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch, fortran] Warn about out-of-bounds access with DO subscripts
Date: Tue, 26 Sep 2017 16:52:00 -0000 [thread overview]
Message-ID: <f5364853-8432-d3d6-e24f-e0112ffefe12@netcologne.de> (raw)
In-Reply-To: <87r2uuj5d7.fsf@euler.schwinge.homeip.net>
Hi!
> On Mon, 25 Sep 2017 18:50:49 +0200, Thomas Koenig <tkoenig@netcologne.de> wrote:
>> Thanks for the review, committed as r253156.
>>
>> Now, on to some other bugs...
>
> No, back to this one please. ;-)
OK, if you insist :-)
> Apparently, the changes you prepared for existing testcases did not get
> committed, so I'm now seeing some FAILs there. See also recent posts on
> the <gcc-regression@gcc.gnu.org> mailing list:
>
> FAIL: gfortran.dg/gomp/associate1.f90 -O (test for excess errors)
> FAIL: gfortran.dg/predcom-1.f -O (test for excess errors)
> FAIL: gfortran.dg/unconstrained_commons.f -O (test for excess errors)
I have committed those changes, so that should be gone.
> And the following gets highlighted, too:
>
> FAIL: compiler driver --help=fortran option(s): "^ +-.*[^:.]$" absent from output: " -Wdo-subscript Warn about possibly incorrect subscripts in do loops"
> FAIL: compiler driver --help=warnings option(s): "^ +-.*[^:.]$" absent from output: " -Wdo-subscript Warn about possibly incorrect subscripts in do loops"
This I don't understand. Was there anything wrong with my
change to fortran/lang.opt?
Regards
Thomas
next prev parent reply other threads:[~2017-09-26 16:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-23 12:33 Thomas Koenig
2017-09-25 2:30 ` Jerry DeLisle
2017-09-25 16:50 ` Thomas Koenig
2017-09-26 7:17 ` Thomas Schwinge
2017-09-26 11:47 ` Jakub Jelinek
2017-09-26 16:53 ` Thomas Koenig
2017-09-26 16:52 ` Thomas Koenig [this message]
2017-09-27 8:37 ` Thomas Schwinge
2017-09-27 18:44 W Spector
2017-09-28 17:38 ` Thomas Koenig
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=f5364853-8432-d3d6-e24f-e0112ffefe12@netcologne.de \
--to=tkoenig@netcologne.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jvdelisle@charter.net \
--cc=thomas@codesourcery.com \
/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).