From: William Clodius <w.clodius@icloud.com>
To: gfortran <fortran@gcc.gnu.org>
Subject: Re: [Patch, Fortran] PR 57160: short-circuit IF only with -ffrontend-optimize
Date: Wed, 08 Aug 2018 00:17:00 -0000 [thread overview]
Message-ID: <8ED8C5C1-1AA8-4339-B31E-72A94918D5DD@icloud.com> (raw)
In-Reply-To: <2F3C72A3-D2A6-479B-937F-316A1A4B1183@tkoenig.net>
The confusion of false negative is also a concern.
> On Aug 7, 2018, at 4:21 PM, Thomas König <tk@tkoenig.net> wrote:
>
> Hi Janus,
>
>> How is that even an option?!? gfortran accepts invalid code. What's
>> wrong with fixing that?
>
> Just a general remark, I am on a business trip in the US at the moment.
>
> There are errors which the compiler is required to diagnose, when a constraint is violated. And there are errors which the compiler is not required to catch, those marked with „shall“ in the standard.
>
> Issuing an error or a warning for those is always a balancing act because if the possibility of false positives.
>
> Regards, Thomas
next prev parent reply other threads:[~2018-08-08 0:17 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-27 16:42 Dominique d'Humières
2018-07-28 8:03 ` Janus Weil
2018-08-01 20:46 ` Janus Weil
2018-08-06 20:59 ` Janus Weil
2018-08-07 10:11 ` Dominique d'Humières
2018-08-07 17:14 ` Janus Weil
2018-08-07 22:21 ` Thomas König
2018-08-08 0:17 ` William Clodius [this message]
2018-08-08 5:41 ` Janus Weil
2018-08-08 8:35 ` Manfred Schwarb
2018-08-08 11:23 ` Janus Weil
2018-08-08 11:29 ` Arjen Markus
2018-08-08 18:21 ` Janus Weil
2018-08-08 20:48 ` Janus Weil
2018-08-09 1:05 ` Jerry DeLisle
2018-08-09 21:14 ` Janus Weil
2018-08-10 0:38 ` Jerry DeLisle
2018-08-10 14:14 ` Janus Weil
2018-08-08 19:50 ` Janus Weil
-- strict thread matches above, loose matches on Subject: below --
2018-07-24 9:12 Dominique d'Humières
2018-07-24 13:46 ` Janus Weil
2018-07-24 15:42 ` Janne Blomqvist
2018-07-24 16:18 ` Janus Weil
2018-07-20 21:38 Janus Weil
2018-07-23 7:40 ` Adam Hirst
2018-07-23 17:11 ` Janus Weil
2018-07-23 21:06 ` Fritz Reese
2018-07-24 18:46 ` Janus Weil
2018-07-24 19:49 ` Janus Weil
2018-07-24 19:50 ` Thomas Koenig
2018-07-24 20:14 ` Janus Weil
2018-07-25 20:05 ` Janus Weil
2018-07-25 20:59 ` Nicolas Koenig
2018-07-25 21:01 ` Thomas Koenig
2018-07-25 21:31 ` Janus Weil
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=8ED8C5C1-1AA8-4339-B31E-72A94918D5DD@icloud.com \
--to=w.clodius@icloud.com \
--cc=fortran@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).